Transcript UML for SE Requirements Review INCOSE IW Tampa, Florida

UML for SE
Requirements Review
INCOSE IW
Tampa, Florida
February 4-5, 2003
Sanford Friedenthal
INCOSE Liaison/ OMG SE DSIG Chair
Lockheed Martin Corporation
(703) 293-5557
[email protected]
LMC_SF
1
Requirements Review
• Purpose
– Review requirements in the Draft RFP for “UML for Systems
Engineering” dated Jan 20, 2003 rev A
– URL - http://syseng.omg.org/SE_UML_Profile_RFP.htm
• Agenda
Tue, Feb 4 9:00 – 12:00
• SE DSIG Overview & SE UML Req’ts Overview – S. Friedenthal
• RFP Process and Roadmap – Roger Burkhart
• UML 2 Status and Proposal Summary – Cris Kobryn
• An Application of UML for SE – Andrew Winkler
Wed, Feb 5 9:00- 4:00
• Detailed walk-thru of requirements in draft RFP
LMC_SF
2
SE DSIG Overview
LMC_SF
3
SE DSIG Background
• Joint INCOSE / OMG Initiative to extend UML to SE
• Chartered Systems Engineering Domain Special
Interest Group (SE DSIG) in July ‘01
• SE DSIG kickoff in Sept ‘01
• Aligned with ISO AP-233 Systems Engineering
data interchange standard
LMC_SF
4
SE DSIG Goals
• 2002
– Analyze requirements and candidate
approaches for UML for SE
– Influence UML 2.0 responses to address SE
concerns
• 2003
– Issue RFP for UML for Systems Engineering
– Support Submission teams
– Determine follow-on roadmap
LMC_SF
5
Roadmap to “UML for SE” RFP
AP-233, OMG
& INCOSE
SE
Inputs
Concept
Model
Other sources
UML Meta-Model
& Profiles
Industry
Responses
SE Req’ts
Analysis
SE UML
Proto. &
Eval.
SE UML
RFI
Issues &
Approaches
UML for
SE UML SE RFP
Profile
RFP prep
SE DSIG /
UML 2.0
Collaborations UML
V2.0
Input
LMC_SF
6
Top Level Conceptual Model – Draft 8
Domain
of Interest
Category
categorizes
System
View
C
Stakeholder
Environment
has view
SE_Thing
exhibits
C
has
Stakeholder
Need
satisfied by
Interacts
with
System
Requirement
represented by
System
allocated to
Property
Reference
Property
reference for
statement of
derived from
Physical
Property
Structure
Behavior
C
allocated to
C
budgeted to
LMC_SF
7
UML for SE Req’ts Analysis
• SE UML Requirements Analysis V0.4 Nov 2002
– Initial version July ‘02/updated to V0.4 Nov ‘02
– Identifies req’ts, candidate SE UML approaches, and issues
– Made available as early input to UML V2.0 submitters
– Resulting req’ts are input to RFP for UML for SE
• Primary Sources
– UML specifications
– SE Conceptual Model
– SE UML RFI responses
– SE UML prototyping
– UML V2.0 submitter Interaction
– Related papers
– Other sources as inputs
LMC_SF
8
System UML Modeling (Notional)
ATC
Pilot
Taxi
Airplane
*
*
Request to proceed
*
Authorize
Take-off
*
**
Power-up
*
*
Initiate power-up
Power-up
*
*
*
*
*
Fly
Report Status
*
Direct taxiway
Pilot
Initiate Taxi
Ready
ATC
*
Power-down
Land
Executed cmds
Degraded
*
Behavior Models
X(t)
Safety Model
Pilot I/F
Processor
Gain
+
-
Structure Models
1/S
Y(t)
Dy namics
Aileron
Elevator
-Weight
Control System
Processor
1
Navigation
Processor
1/S
Performance Model
Airplane
LAN
Compensation
Fuselage
-Length
1
1
2
Wing
-Span
Controller
2
Flap
Engine
-Diameter
Engine
LMC_SF
9
Summary of Perceived UML 1.x
Limitations (Partial List)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Continuous time behavior
Decision tree (e.g. support for trade studies)
Hierarchical modeling of scenarios and behavior
Input/output flow (including data and mass/energy flow)
Integration with other specialty engineering models
Integration with geometric and spatial models
Parametric relationships (e.g. performance models)
Performance and physical characteristics (incl probabilities)
Physical interfaces and connections
Problem definition and causal analysis
Requirements constructs
System, subsystem, element & component representations
Terminology harmonization
Verification and validation results
LMC_SF
10
UML Revision Status
• Current Version is UML
– V1.41 sent to ISO
– V1.5 = V1.41 + action semantics
• UML V2.0 RFP’s
– Superstructure
– Infrastructure
– OCL
– Diagram Interchange
• Multiple submitters
LMC_SF
• Final submissions due Jan ’03 / vote in March ‘03
11
SE DSIG / UML V2.0 Collaboration
• SE DSIG Collaboration goals to ensure UML V2
provides
• direct support for SE where practical
• doesn’t preclude the ability to profile
• Significant collaboration with U2P team and others
LMC_SF
12
RFP for UML for SE - Draft
Requirements Overview
LMC_SF
13
RFP for UML for SE
• Draft RFP (Jan 20, 2003)
– OMG Doc # syseng/2003-01-02
– http://syseng.omg.org/SE_UML_Profile_RFP.htm
• Scheduled reviews
– OMG Meeting – Jan 28 – 30, 2003
– INCOSE IW – Feb 4-5, 2003
• Issue OMG Orlando Meeting – March 28, 2003
• Initial Submissions to RFP – Jan 12, 2004
LMC_SF
14
RFP Outline
1. Introduction
2. Architectural Context
3. Adoption Process
4. Instructions for Submitters
5. General Requirements on Proposals
6. Specific Requirements on Proposals
Appendix A: References and Glossary
LMC_SF
15
Scope of RFP
• Focuses on general purpose modeling of a system
– Includes both software and hardware systems
– System level vs detailed hw/sw implementation
models (code, 3D geometry, VHDL, ..)
– Integrate with discipline specific models (I.e.
reliability, safety, ..)
LMC_SF
16
Evaluation Criteria (6.8)
•
•
•
•
•
•
•
•
•
•
•
Ease of use
Unambiguous
Precise
Complete
Scalable
Adaptable to different domains
Capable of model interchange
Capable of diagram interchange
Process and method independent
Compliant with UML metamodel
Verifiable
LMC_SF
17
RFP Outline (Cont.)
6. Specific Requirements on Proposals
1.
2.
3.
4.
5.
6.
7.
Problem Statement
Scope of Proposals Sought
Relationship to Existing OMG Specifications
Related Activities, Documents & Standards
Mandatory Requirements
Optional Requirements
Issues to be discussed
– Sample problem description
8. Evaluation Criteria
9. Other Information unique to this RFP
– Glossary
10. RFP Timetable
LMC_SF
18
Mandatory Requirements (6.5)
•
SE UML shall provide the capability to model:
– Structure
– Behavior
– Property
– Requirement
– Verification
– Other
LMC_SF
19
Structure
• Hierarchy of systems
• Types of system components
• Interconnection of systems
• Environment and system boundary
• Deployment
• System store
LMC_SF
20
Behavior
• Functional transformation of inputs to outputs
• Function activation/deactivation
– control input
– control operators
– events/conditions
• State based behaviors
• Allocation of behavior to systems
LMC_SF
21
Property
• Property association (I.e. system, I/O, function, ..)
• Property attributes (type, value, prob distr...)
• Time reference (global variable, time varying
properties)
• Parametric model (parametric relationships)
• Parametric plots
LMC_SF
22
Requirements
• Requirement type (functional, performance, physical)
• Requirement attribute (criticality, TBD, verif status, )
• Effectiveness measure (optimization criterion)
• Requirement relationships (allocation, traceability, ..)
LMC_SF
23
Requirement (Cont.)
• Problem (ability to satisfy a req’t or need)
• Problem association with systems, components, ..
• Problem cause (relationship to root cause)
LMC_SF
24
Verification
• Test case (stimulus and expected response)
• Verification result
• Requirement verification, which compares verif
result with requirement
• Verification procedure (steps to execute test case)
• Verification system which implements the
procedure
LMC_SF
25
Other
• Model view as subset of model elements (default
diagrams and user defined views)
• System role as subset of system behavior, properties,
and structure to support
• Topology as graph of nodes and arcs
• Representation for simple geometric relationships
LMC_SF
26
UML Customization
• Define UML constructs to support SE requirements
– Use UML as-is where applicable (I.e. a function
can be represented by an activity)
– Customize UML constructs using UML built in
extension mechanisms (I.e. profile)
• Rename model element
• Add attributes and constraints
LMC_SF
27
Summary
• Need system modeling language to address system
complexity and bridge systems & software gap
• Systems modeling requires robust capabilities
• Extending UML offers a potential solution
• INCOSE/OMG established SE DSIG
• RFP is initial milestone towards developing a standard
SE modeling language
LMC_SF
28
More Information
• OMG SE DSIG Website
http//syseng.omg.org
LMC_SF
29
SE UML Definition Dependencies
Property
Parametric Relationship
Time Reference
Action
Item
Activity
Function
Component
Input/Output
Event
Control Operator
Requirement Traceability
Structure
Requirement
Activation / Deactivation Event
Behavior
System
Interaction
Need
Test Case
Requirement Verification
Port
Verification Result
State (finite)
Environment
Connection
Problem
Dependency
LMC_SF
30
Challenges to Adopting SE UML
• Developing a robust modeling language that addresses the
broad system modeling requirements
• The evolution of model based methodologies
• Acceptance of the model based approach by the SE
community, implementers, and customers
• Ability to integrate the SE models with other disciplinespecific models (i.e. software, hardware, simulation and
analysis, etc)
• Ensuring adequate infrastructure to support the use of
models, including tools and training
• Continued adaptation and evolution of the modeling
framework
LMC_SF
31
RFP Preparation Milestones
• OMG SE DSIG Review – Jan 28-30, 2003
• INCOSE IW Review – Feb 4-5, 2003
• Update RFP
• Incorporate Sample Problem Description
• Submit to OMG – March 3
• Review and finalize – March 24
• OMG Vote to issue – March 28
LMC_SF
32