[PDF] mécanisme du rejet de greffe
[PDF] quelles sont les cellules qui interviennent lors d'un rejet de greffe
[PDF] rejet de greffe définition
[PDF] rejet aigu
[PDF] antigène mineur d'histocompatibilité
[PDF] rejet cellulaire et humoral
[PDF] rejet hyperaigu
[PDF] synthèse de l acétanilide corrigé
[PDF] mécanisme réactionnel de la synthèse de l'acétanilide
[PDF] fables de la fontaine théâtre
[PDF] synthèse de l'aspirine ? partir de l'acide salicylique
[PDF] la cigale et la fourmi version theatre
[PDF] synthèse de l'acétanilide tp
[PDF] synthèse aspirine tp
[PDF] les fables de la fontaine mise en scene par robert wilson
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University1
System of Systems (SoS) Quality Attribute
Specification and Architecture Evaluation
SEI Webinar
Jan. 21, 2010
Mike Gagliardi
Bill Wood
Tim Morrow
John Klein
2
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Mike Gagliardi has more than 25 years experience in real-time, mission- critical software architecture and engineering activities on a variety of DoD systems. He currently works in the SEI Research, Technology, and System Solutions Program on the Architecture-Centric Engineering Initiative, and is leading the development of architecture evaluation and quality attribute specification methods for system and SoS architectures. 3
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Leveraging Our Success in Software Architecture
We have lots of experience and success with proven methods for quality attribute elicitation (QAW*) and architecture evaluation (ATAM**) of software architectures, in many contexts:
DoD
Commercial
Acquisition
These methods have been adopted by a wide variety of organizations to specify quality attributes and identify architectural risks early in the life- cycle. We have expanded the scope to system and system-of-system (SoS) architectures. *Quality Attribute Workshop **Architecture Trade-off Analysis Method 4
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
SEI Software Architecture Axioms
1.Software architecture a bridge between business and mission goals
and a software-reliant system.
2.Quality attribute requirements drive the design of the software
architecture. ²Quality attribute requirements stem from business and mission goals. ²Key quality attributes need to be characterized in a system-specific way. ²Scenarios are a powerful way to characterize quality attributes and represent stakeholder views.
3.Software architecture drives software development throughout the
life cycle. ²Software architecture must be central to software development activities. ²These activities must have an explicit focus on quality attributes. ²These activities must directly involve stakeholders not just the architecture team. 5
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
QAW
Conceptual Flow of System and Software ATAM
Qualitative
Analysis
Architectural
Decisions
ScenariosQuality
Attributes
Architectural
Approaches
Business
Drivers
System and
Software
Architecture
Risks
Tradeoffs
Non-Risks
Impacts
Risk Themes
distilled into 6
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Concerns Addressed by Software Architecture
Achieving Key Properties in Software-Reliant Systems
Design-time
Modifiability
Maintainability
Reusability
Portability
Testability
Etc.
Run-time
Performance
Security
Reliability
Availability
Scalability
Interoperability
Throughput
Capacity
Etc.
Software In Its
Environment
Usability
Supportability
Configurability
Sustainability
Buildability
Etc. 7
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Problem
Integration and operational problems arise due to inconsistencies, ambiguities, and omissions in addressing quality attributes between system and software architectures. This is further exacerbated in an SoS. Example quality attributes: predictability in performance, security, availability/reliability, usability, testability, safety, interoperability, maintainability, force modularity, spectrum management. Functionality and capability are important, but the architecture must be driven by the quality attributes. Identifying and addressing quality attributes early and evaluating the architecture to identify risks is key to success. Architecture plays an important role in every stage. 8
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Common Symptoms Stemming From
Architectural Deficiencies
Operational
Communication bottlenecks under various load conditions in systems or throughout system of systems Systems that hang up or crash; portions that need rebooting too often Difficulty synching up after periods of disconnect and resume operations Judgment by users that system is unusable for variety of reasons
Database access sluggish and unpredictable
Developmental
Integration schedule blown, difficulty identifying root causes of problems Proliferation of patches and workarounds during integration and test Integration of new capabilities taking longer than expected, triggering breaking points for various resources Significant operational problems ensuing despite passage of integration and test
Anticipated reuse benefits not being realized
9
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
The Need for Augmented Mission Threads in
DoD SoS Architecture Definition
DoDAF is the SoS architecture framework for the DoD. It provides a good set of architectural views for an SoS architecture. However, it inadequately addresses cross-cutting quality attribute considerations. System use cases focus on a functional slice of the system. More than DoDAF and system use cases are needed to ensure that the SoS architecture satisfies its cross-cutting quality attribute needs. SoS end-to-end mission threads augmented with quality attribute considerations are needed to help define the SoS Architecture precepts and guidelines, and then later evaluate the SoS architecture. 10
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Vignette: A description of the geography, own force structure and mission, strategies and tactics, the enemy forces and their attack strategies and tactics, including timing. There may be associated Measures of Performance (MOP) and Measures of Effectiveness (MOE). A vignette provides context for one or more mission threads.
Mission Thread:
A sequence of end-to-end activities and events beginning with an opportunity to detect a threat or element that ought to be attacked and
C4ISR for Future Naval Strike (Operational)
Sustainment: A sequence of activities and events which focus on development, deployment and maintenance.
Definitions (DoD Context)
11
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Vignettes Are the Starting Point Example
Wording
Two ships (Alpha and Beta) are assigned to integrated air and missile defense (IAMD) to protect a fleet containing two high-value assets (HVA). A surveillance aircraft SA and 4 UAVs are assigned to the fleet and controlled by the ships. Two UAVs flying as a constellation can provide fire-control quality tracks directly to the two ships. A three- pronged attack on the fleet occurs: 20 land-based ballistic missiles from the east 5 minutes later from 5 aircraft-launched missiles from the south 3 minutes later from 7 submarine-launched missiles from the west.
The fleet is protected with no battle damage.
12
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Vignettes Are the Starting Point Example
Context
13
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Mission Threads Flow from Vignettes Example
(Non-Augmented)
1. 20 land-based missiles launched -X minute window
2. Satellite detects missiles -cues CMDR
3. CMDR executes re-planning reassigns Alpha and Beta
4. Satellite sends track/target data -before they cross horizon
N Engagement cycle is started on each ship
N+1. Aircraft are detected heading for fleet
N+2. SA detects missile launches tells CMDR
N+3. CMDR does re-planning -UAVs are re-directed
N+4. FCQ tracks are developed from UAV inputs
14
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Other End-to-End Mission Threads
commercial SoS contexts, we have piloted this in:
Commercial Call-Center context
Stock Market Transaction context
The methods hold up,
the inputs change:
End-to-End Business Process
Threads
End-to-End Transaction Threads
15
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Overview
Mission Thread
Workshops
Vignettes
Mission Threads
Sos Architecture
Plans
SoS Mission/
Business Drivers
Quality Attribute Augmented
End-to-End Mission Threads
SoS Architecture Challenges
16
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Overview
Mission Thread
Workshops
Vignettes
Mission Threads
Sos Architecture
Plans
SoS Mission/
Business Drivers
Quality Attribute Augmented
End-to-End Mission Threads
SoS Architecture Challenges
Architecture
Challenge
Workshops
and Legacy
Arch Evals
17
SEI Webinar
Gagliardi, Wood, Morrow, Klein
© 2010 Carnegie Mellon University
Overview
Mission Thread
Workshops
Vignettes
Mission Threads
Sos Architecture
Plans
SoS Mission/
Business Drivers
quotesdbs_dbs16.pdfusesText_22
System of Systems Engineering and Family of Systems