Vous êtes sur la page 1sur 3

Components of the Architecture

System of Interest Architecture Architecture of Operating Environment System Interfaces Organization Roles, Missions and System Applications Problem, Opportunity and Solution Spaces System Interaction with Operating Environment

Lecture 9: System Archi-3


K S Rajan IIIT, Hyderabad

System Interfaces
Objective 1: Physically link or bind two or more system elements or entities. Objective 2: Adapt one or more incompatible system elements or entities. Objective 3: Buffer the effects of incompatible system elements. Objective 4: Leverage human capabilities. Objective 5: Restrain system element or its usage. InteroperabilityThe Ultimate Interface Challenge

Types of Interfaces
Active Interfaces Passive Interfaces Combined Passive/Active Interfaces Logical Physical Mech, Elect, Optical, Acoustic, Natural, Chemical, Biological, etc Access limited or otherwise Caution: Engineers have a strong tendency to jump to defining the physical interface BEFORE anyone has decided WHAT the interface is to accomplish.

Understanding Interfaces
What Constitutes an Interface Failure? Consequences of an Interface Failure Interface Failures
1) disruption, 2) intrusion, 3) stress loading, and 4) physical destruction.

Organization Roles, Missions and System Applications


The Planning process
Strategic Tactical Frame of Reference or Terms of References

Interface Vulnerabilities Interface Latency Interface Failure Mitigation and Prevention

System Objectives and Mission Objectives Contextual Roles


Mission system Support system

Mission Event Timeline

Problem, Opportunity and Solution Spaces


Problem space and Opportunity Space
Risk mitigation; vulnerability assessment

Problem Space
Problem vs Symptom solving Dynamics of the problem
Dynamic nature of the problem vs Static view

Look at what you have products, services, etc that can fit Modify the products, if need Ones Problem is Others Opportunity
Example: Saint-Gobains DryWall

Forecasting of the Problem


Gap Problem

Establish Problem Space Boundaries


Control, resources or spheres of influence

Partition the Problem Space

Solution Spaces
Depends on the Boundary conditions
Clear, rigid vs. Fuzzy vs. Overlapping/Conflicting

System Use Cases

Force Multipliers Selecting Candidate solutions Operating Environment

Attributes of Use Case



Event-based timeline Unique identifier Frequency of occurrence Objective (performance) and utility priorities Outcome-based results Processing capabilities / response function Assumptions Scenarios and Initial state consequences Final state Environmental conditions Preceding circumstances (optional) Operating constraints External inputs Resources

UML Use Case Diagram

Probability of occurrence Use case scenario actors Stimuli and cues Consequences Compensating/mitigating actions

Use Case Sequence Diagram

Vous aimerez peut-être aussi