Holt Jon. UML for Systems Engineering: watching the wheels

2nd ed. — Stevenage: The Institution of Engineering and Technology, 2007. — 375 p. — (IET Professional Applications of Computing 4). — ISBN 978-0-86341-354-4.Up until a few years ago there were over 150 different modelling languages available to software developers. This vast array of choice however, only served to severely hinder effective communication. Therefore, to combat this, every methodologist and many companies agreed to speak the same language, hence the birth of the unified modelling language (UML). The UML offers a means to communicate complex information in a simple way using visual modelling; i.e. drawing diagrams to create a model of a system. This fully revised edition, based on a training course given by the author, coincides with the release of UML version 2 by the standard body, the Object Management Group, and covers the significant changes that have occurred since its release. It also includes material on life cycle management, examining the way the UML can be used to control and manage projects and the UML systems engineering profile.Systems engineering
Problems with systems
Systems
Defining systems engineering – first attempt
The need for systems engineering
Disasters and failures
Causes of problems
Defining a system
Defining systems engineering – second attemptComplexity, communication and understandingComplexity
Minimising complexity
Communications
A good approach
QualityThe need for quality
Level of responsibility
Requirements for systems professionals
Processes and quality
Standards
Problems with standards
Consequences of problems with standards
Compliance with standards
ProcessesConclusions
Further discussionModelling
Introduction to modelling
The importance of modelling
Why projects fail
Modelling
Defining a «model»
Principles of modelling 31
The UMLAspects of the model
Views versus models
Extending the UML
Background of the UML
A nonproprietary language
Conclusions
Further discussionStructural modellingStructural modelling using class diagrams
Modelling classes and relationships
Basic modelling
Adding more detail to classes
Adding more detail to relationships
Other structural diagramsFurther discussionBehavioural modellingBehavioural modelling using state machine diagrams
Behavioural modelling – a simple example
Solving the inconsistency
Alternative state machine modelling
Actions and activities
Comparing the approaches
Other behavioural models
Conclusions
Further discussionThe UML diagramsOverview
Conceptual changes between UML 1.x and UML 2.0
Terminology
The structure of UML 2.0 diagrams
Comparison of the types of diagram
The UML meta-model
Class diagrams (structural)
Overview
Diagram elements
Example diagrams and modelling – class diagrams
Using class diagrams
Object diagrams
Overview
Diagram elements
Example diagrams and modelling – object diagrams
Using object diagrams
Composite structure diagrams (structural)
Overview
Diagram elements
Examples and modelling – composite structure diagrams
Using composite structure diagrams
Package diagrams (structural)
Examples of package diagrams
Using package diagrams
State machine diagrams (behavioural)
Overview
Diagram elements
Examples and modelling – state machine diagrams
Using state machine diagrams
Interaction diagramsOverview – communication diagrams
Diagram elements – communication diagrams
Examples and modelling – communication diagrams
Using communication diagrams
Overview – sequence diagrams
Diagram elements – sequence diagrams
Examples and modelling – sequence diagrams
Using sequence diagrams
Overview – interaction overview diagrams
Diagram elements – interaction overview diagrams
Examples and modelling – interaction overview diagrams
Using interaction overview diagrams
Overview – timing diagrams
Diagram elements – timing diagrams
Examples and modelling – timing diagrams
Using timing diagrams
Activity diagrams
Overview
Diagram elements
Examples and modelling
Using activity diagrams
Use case diagrams
Overview
Diagram elements
Examples and modelling
Using use case diagrams
Component diagrams
Overview
Diagram elements
Examples and modelling
Using component diagrams
Deployment diagrams
Overview
Diagram elements
Examples and modelling
Using deployment diagramsConclusions
Further discussionModelling standards, processes and proceduresStandards
Standards, standards, standards
Requirements for using standards
Analysing standards
Aspects of modelling using the UML
Modelling example
EIA 632 Processes for engineering a system
ISO 15504 Software process improvement and capability determination (SPICE)
Comparing models
Other standards and processesDefining new processes using the UML
A new procedure
Completing the modelTailoring the process
Defining deliverables
Deliverables by type
Deliverables by process
Deliverables by structure
Implementing the systems engineering process using a tool
Uses for a tool
The information model
The profile definition
The implementation modelConclusions
Further discussionModelling requirementsRequirements engineering basicsThe requirements phase
Capturing requirements
Requirements
StakeholdersUsing use case diagrams (usefully)
Context modelling
Types of context
Practical context modellingRequirements modellingModelling requirements
Describing use cases
Modelling scenarios
Scenarios in the UML
Example scenarios
Communication versus sequence diagrams
Wrapping up scenarios
Documenting requirements
Overview
Populating the document
Finishing the document
Summary and conclusions
Further discussionLife cycle management
Life cycles and life cycle models
Different life cycle modelsWhen to choose
Linear versus iterative models
The linear approach
The iterative approach
STUMPI – an example of life cycle managementThe STUMPI life cycle
The STUMPI life cycle model
The STUMPI process model
Phase iterations
Process behaviour
Project planningExerciseSystem architecturesIntroduction to architectures
Architecture – definitions
Not an architecture
Architecture versus model
Architectural views
Example of architecture – Department of Defense Architectural Framework (DoDAF)
Example architecture – IEEE 1471
Conceptual model of architectural description
Common themes
Validation with architecturesGenerating the architecture
Using an architecture for project validationApplying the UMLThe requirements model architecture
The analysis model architecture
The design model architecture
ConclusionsExtending the UMLCreating a profileBackground to process modelling example
Identifying and reading stereotypes
Declaring and defining stereotypes
Adding more knowledge
Declaring a profile
Stereotyping symbolsIntroduction to constraints
Formal constraints – the object constraint language (OCL)
Introduction to tagged values
Conclusions
Further discussionToolsCASE tools
Selecting a tool
What tools can do
What tools cannot do
A requirements model for CASE tool evaluation
Requirements model overview
Modelling capability provision
Provision of interoperability capability
Provision of other capabilities
Provision of application capability
Ensuring process compatibility
Provision of system functionality
Ensuring compatibility with the UML
Ensuring vendor’s quality of service
Conclusions
Further discussion