| Figures and Tables Preface
What the ECSAM Method Is
The History of the ECSAM Method
The Audience
for This Book Part I Conceptual Modeling of Systems: The
External View (The E-Level Model) 1 Introduction
1.1 Engineering of Computer-Based Systems
1.2 Requirements Handling in
ECBS
1.3 Model-Based Requirements Analysis
1.4 The ECSAM Approach
1.5 The ECSAM Process Overview
1.6 Supporting Tools
1.7 Summary
2 The System’s Context Diagram 2.1 The Top-Level
Specification
2.1.1 Identification of the system’s scope
2.1.2
Determination of the system’s boundaries
2.2 Context Diagram and Module-Chart
Notation
2.3 The Initial Data Dictionary
2.4 The Environmental System’s
Module-Chart
2.5 The Initial Top-Level Specification
2.6 Summary
2.7 Exercises 3 Statecharts and E-Level Modes
3.1 Modes and States
3.2 Statecharts
3.3 Extensions of the Statechart
Notation
3.4 Recommended Analysis Steps
3.5 Summary
3.6 Exercises
4 The E-Level System Capabilities
4.1 What Are E-Level System Capabilities?
4.2 Identification of the E-Level
System Capabilities
4.3 Graphical Representations of Capabilities
4.4
Control and Timing
4.5 The E-Level Module-Chart versus the E-Level Capabilities
Activity-Chart
4.6 System Specification Update
4.7 Recommended Analysis
Steps
4.8 Summary
4.9 Exercises 5 E-Level Processes
5.1 E-Level Processes Overview
5.2 Representation of E-Level Processes
5.3 Process Analysis Method
5.4 Impact of Analysis of E-Level Processes
on E-Level Capabilities
5.5 The Concept of Time in Descriptions of Dynamic
Behavior
5.6 Summary
5.7 Exercises 6 The Integrated
Conceptual E-Level Model
6.1 The Need for an Integrated
Conceptual E-Level Model
6.2 The Relationship Between the E-Level Conceptual
Views
6.3 Refinement of the E-Level Model
6.4 Scoping
6.5 Completing
the E-Level Model
6.6 Update of the Top-Level Specification
6.7 Summary
7 Operational Scenarios
7.1 Overview of Operational
Scenarios
7.2 Operational Scenarios in Systems and Software Development Standards
7.3 Scenario Derivation Method
7.4 Example: The Derivation of an Operational
Scenario
7.5 Representation of Scenarios by Message-Sequence Charts
7.6 Specifying Scenarios Using a Bottom-Up Approach
7.7 Summary
7.8
Exercises
Part II Conceptual Modeling of Systems: The Internal View (The
S-Level Model) 8 Concepts of White-Box Modeling
8.1 Introduction
8.2 Conceptual Models versus Design Models
8.3 Multilevel Description of Systems
8.4 Reuse of Conceptual System
Models and Specifications
8.5 Development Steps of Conceptual White-Box Models
8.6 Summary 9 Object-Based System Decomposition
9.1 Basic Concepts
9.1.1 Assumptions
9.1.2 Objects
9.2 Overview of Decomposition Methods
9.3 Decomposition Methods
9.4 Decomposition of Evaluation Criteria
9.4.3 Modularity
9.5 Conceptual
Decomposition of the Home Alarm System
9.6 Summary
9.7 Exercises
10 Analysis of the System’s Internal Information-Flows and Subsystem Capabilities
10.1 Analyzing the Information-Flows
10.2 Analyzing the
Internal Flows in the S-Level Module-Chart
10.3 Analyzing the Internal Flows
of the S-Level Activity-Chart
10.4 Identifying the Capabilities of Subsystems
10.5 Summary
10.6 Exercises 11 Internal System
Modes (S-Level Modes) 11.1 S-Level versus E-Level Modes
11.2 Recommended Analysis Steps
11.3 Home Alarm System S-Level Modes
Example
11.4 Summary
11.5 Exercises 12 Internal
System Processes (S-Level Processes)
12.1 Internal
System Processes versus E-Level Processes
12.2 The System Controller and
Process Control-Signals
12.3 Control of Capabilities That Participate in a
Process
12.4 Synthesis of Internal Processes
12.5 Examples of HAS Internal
Processes
12.6 Uncluttering the Process Activity-Charts
12.7 Preliminary
Specification of Subsystems
12.8 Summary
12.9 Exercises
13 Transition to Design
13.1 Introduction
13.2 Analysis and Design
13.3 Description of System Architectures
13.4
The Relationship Between Conceptual Models and Design Models
13.5 Summary
Part III Overview of Requirements Engineering
14
The Stakeholders’ Requirements Process
14.1 Introduction
14.2 Processing Stakeholders’ Requirements
14.3 Stakeholders’ Requirements
and the E-Level Model
14.4 The What and How of Requirements Formulation
14.5 Success Factors
14.6 Supporting Tools
14.7 Examples
14.8 Summary
14.9 Exercises 15 Model-Driven Refinement of Requirements
15.1 Introduction
15.2 Requirements and the ECSAM Model
15.3 Allocation and Association of Requirements
15.4 Derivation (Expansion)
and Focusing of Requirements
15.5 Requirements Flowdown
15.6 The Working
Process
15.7 Verification of Requirements Refinement and Flowdown
15.8
Summary
15.9 Exercises 16 Requirements Management
16.1 Introduction
16.2 Requirements and Traceability
16.3 Baselining of Requirements and Change Management
16.4 Measurements
Associated with Requirements
16.5 Summary Observations
and Conclusions Appendix A Case Studies for Book Exercises
A1: An Integrated Automated Teller Machine: Statement of Need
and Specification of Basic Characteristics
A2: “Go Anywhere” Universal
Personal Communicator: Statement of Need and Specification of Basic Characteristics
A3: Chariot, a “Smart” Mobile Chair for the Disabled: Statement
of Need and Specification of Basic Characteristics
A4: Automated Parking
Facility Control and Billing System: Statement of Need and Specification of Basic
Characteristics
A5: SARAH, a Search-and-Rescue Automatic Helicopter: Statement
of Need and Specification of Basic Characteristics
Appendix
B Summary of Notation
B1: Names and Expressions
B2: Information-Flows and Information Items
Glossary
Bibliography
Index | 
