A distributed system reference architecture for adaptive QoS and resource management

Welch, Lonnie R.; Masters, Michael W.; Madden, Leslie A.; Marlow, D.T.; Irey, Philip M.; Werme, Paul V.; Shirazi, Behrooz

doi:10.1007/bfb0098011

Cited by 4 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The quality of service (QoS) of a distributed system is commonly associated with a set of parameters representing different characteristics of individual applications or of the overall system [35,36], not as a dimension of control. Traditional QoS mechanisms afford users the ability to select different classes of service related to various functional dimensions of a system such as accessibility, reliability and performance.…”

Section: Key Concepts and Technologiesmentioning

confidence: 99%

A cloud-oriented cross-domain security architecture

Nguyen

Gondree

Shifflett

et al. 2010

2010 - Milcom 2010 Military Communications Conference

View full text Add to dashboard Cite

The Monterey Security Architecture addresses the need to share high-value data across multiple domains of different classification levels while enforcing information flow policies. The architecture allows users with different security authorizations to securely collaborate and exchange information using commodity computers and familiar commercial client software that generally lack the prerequisite assurance and functional security protections. MYSEA seeks to meet two compelling requirements, often assumed to be at odds: enforcing critical, mandatory security policies, and allowing access and collaboration in a familiar work environment. Recent additions to the MYSEA design expand the architecture to support a cloud of cross-domain services, hosted within a federation of multilevel secure (MLS) MYSEA servers. The MYSEA cloud supports single-sign on, service replication, and network-layer quality of security service. This new crossdomain, distributed architecture follows the consumption and delivery model for cloud services, while maintaining the federated control model necessary to support and protect crossdomain collaboration within the enterprise. The resulting architecture shows the feasibility of high-assurance, cross-domain services hosted within a community cloud suitable for interagency, or joint, collaboration. This paper summarizes the MYSEA architecture and discusses MYSEA's approach to provide an MLS-constrained cloud computing environment.

show abstract

Section: Key Concepts and Technologiesmentioning

confidence: 99%

A cloud-oriented cross-domain security architecture

Nguyen

Gondree

Shifflett

et al. 2010

2010 - Milcom 2010 Military Communications Conference

View full text Add to dashboard Cite

show abstract

“…Another early reference to a variable security service is that of Schneck and Schwan [67], which discusses variable packet authentication rates with respect to the management of system performance. References to security in the QoS literature can be found in [19,4,77], although little is mentioned there of security as a functional QoS dimension.…”

Section: Dynamic Security Servicesmentioning

confidence: 99%

MYSEA: The Monterey Security Architecture

Irvine¹,

Nguyen²,

Shifflett³

et al. 2009

View full text Add to dashboard Cite

Mandated requirements to share information across different sensitivity domains necessitate the design of distributed architectures to enforce information flow policies while providing protection from malicious code and attacks devised by highly motivated adversaries. The MYSEA architecture uses component security services and mechanisms to extend and inter-operate with commodity PCs, commodity client software, applications, trusted components, and legacy single level networks, providing new capabilities for composing secure, distributed multilevel secure solutions. This results in an architecture that meets two compelling requirements: first, that users have a familiar work environment, and, second, that critical mandatory security policies are enforced.

show abstract

“…• System reference architecture, such as a distributed system reference architecture for adaptive QoS and resource management [51].…”

Section: Where Software Reference Architecture Belongs Tomentioning

confidence: 99%

Gathering empirical evidence and building a business case for software reference architectures in industry

Martínez Fernández

View full text Add to dashboard Cite

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to understand how software reference architectures are engineered, and to know their return on investment. Unfortunately, there is a lack of evidence-based support to help organizations with these challenges. Goal: The main goal of this PhD thesis is to support organizations making informed decisions about software reference architecture acquisition, design, and use based on empirical evidence. Methods: To accomplish this goal, we have conducted an action research approach in an industry-academia collaboration between everis (a multinational IT consulting firm based in Spain) and our Research Group of Software and Service Engineering (GESSI). Results: The results from our industry-academia collaboration led to uncover novel evidence on the use of software reference architectures in practice. The procedures and evidence obtained have been packaged to design guidelines that could be used in similar contexts as the one of everis. Conclusions: This PhD thesis supports organizations to acquire and engineer software reference architectures by providing evidence-based support. Such evidence-based support consists of the results of the empirical studies conducted in this PhD thesis, and the presented guidelines for gathering new corporate evidence. Context: Les arquitectures del software de referència estan sent àmpliament adoptades per les organitzacions que necessiten dissenyar i mantenir aplicacions software d’un domini compartit. Per les organitzacions que tenen previst adoptar aquest enfocament centrat en l’arquitectura, esdevé fonamental entendre com es dissenyen les arquitectures del software de referència, i conèixer el seu retorn d’inversió. Desafortunadament, hi ha una manca de recolzament basat en l’evidència per ajudar aquestes organitzacions a afrontar aquests reptes. Objectiu: L’objectiu principal d’aquesta tesi doctoral és recolzar les organitzacions a prendre decisions informades i basades en l’evidència empírica sobre l’adquisició, disseny i ús d’arquitectures del software de referència. Mètodes: Per aconseguir aquest objectiu, s’ha portat a terme un enfocament d’investigació-acció en una col·laboració empresa-universitat entre “everis” (una empresa multinacional de consultoria tecnològica amb seu a Espanya) i el nostre Grup d’investigació en Enginyeria del Software i Serveis (GESSI). Resultats: Fruït de la nostra col·laboració empresa-universitat, s’han descobert noves evidències sobre l’ús d’arquitectures del software de referència a la pràctica. Els procediments i les evidències obtingudes han estat empaquetades per dissenyar directrius que podrien ser utilitzades en contextos similars com el d’everis. Conclusions: Aquesta tesi doctoral és una contribució per les organitzacions que adopten i dissenyen arquitectures del software de referència, proporcionant recolzament basat en l’evidència empírica. Aquest recolzament es constitueix dels resultats dels estudis empírics realitzats en aquesta tesi doctoral, i les directrius que es presenten per la recol·lecció de noves evidències corporatives.

show abstract

A distributed system reference architecture for adaptive QoS and resource management

Cited by 4 publications

References 7 publications

A cloud-oriented cross-domain security architecture

A cloud-oriented cross-domain security architecture

MYSEA: The Monterey Security Architecture

Gathering empirical evidence and building a business case for software reference architectures in industry

Contact Info

Product

Resources

About