book

Strategies for Real-Time System Specification

by Derek J. Hatley, Imtiaz A. Pirbhai

July 2013

Intermediate to advanced

440 pages

9h 41m

English

Addison-Wesley Professional

Read now

Unlock full access

Organization and audience of the book

1.1. The Birth of the Requirements Model1.2. The Birth of the Architecture Model1.3. Compatibility of the Models1.4. Applicability of the Models1.5. The System Life Cycle
2.1. Structured Methods: What They Are2.2. System Requirements Model2.3. System Architecture Model2.4. System Specification Model2.5. The Development Life Cycle2.6. Structured Methods: What They Are Not2.7. Summary
3.1. The Structure of the Model
4.1. Data Context Diagrams4.2. Data Flow Diagrams4.3. Leveling and Balancing4.4. The Numbering System4.5. Data Flows4.6. Data Stores4.7. Process Specifications4.8. Interpreting the Process Model4.9. Summary
5.1. Control Context Diagrams5.2. Control Flow Diagrams5.3. Control Flows5.4. Data Conditions5.5. Control Stores5.6. Control Specifications5.7. Process Controls5.8. Summary
6.1. Combinational Machines6.2. Sequential Machines6.3. Incorporating Finite State Machines into CSPECs6.4. Summary
7.1. Repetition Rate7.2. Input-to-Output Response Time7.3. Summary
8.1. Primitive Attributes8.2. Group Structure8.3. Dictionary Data Bases8.4. Summary
9.1. The Requirements Model Interpreted9.2. Requirements Model Summary
10.1. Model Users and Builders10.2. The Sources of Requirements10.3. The Model Building Process
11.1. User Requirements Statements11.2. Separating Data and Control11.3. Establishing the System Context11.4. Partitioning the Top Levels11.5. Summary
12.1. Abstraction and Decomposition12.2. The Seven-Plus-or-Minus-Two Principle12.3. Grouping and Decomposing Processes12.4. Grouping and Decomposing Flows12.5. Naming Processes and Flows12.6. Use of Stores12.7. Functionally Identical Processes12.8. De-emphasizing the Control Model12.9. Control Intensive Systems12.10. The Dilemma of Detail: Requirements Versus Design12.11. The Final Product12.12. Summary
13.1. The Role of Process Specifications13.2. The Different Types of PSPECs13.3. Some Important Signal Conventions13.4. Structured English13.5. Annotating with Comments13.6. Summary
14.1. Avoiding Control Specifications14.2. Combinational Control14.3. Sequential Control14.4. Multi-Sheet CSPECs14.5. Fitting CSPECs In14.6. Summary
15.1. Timing Overview15.2. Response Time Specification15.3. Summary
16.1. Flow Types16.2. Dictionary Symbols16.3. Summary
17.1. Requirements-to-Architecture Template17.2. Architecture Model Symbols
18.1. Architecture Context Diagrams18.2. Flows and Interconnects18.3. Architecture Flow Diagrams18.4. Architecture Interconnect Diagrams18.5. Summary
19.1. Architecture Module Specification19.2. Architecture Interconnect Specification19.3. Timing Requirements19.4. Architecture Dictionary19.5. Summary
20.1. Allocation to Hardware and Software20.2. The Hardware and Software Architectures20.3. The Complete Architecture Model
21.1. Architecture Development Process21.2. Systems Come in Hierarchies
22.1. Input and Output Processing22.2. User Interface Processing22.3. Maintenance and Self-Test Processing22.4. The Complete Enhanced Requirements Model22.5. Technology-Independent Versus Technology-Nonspecific22.6. Organizational Implications22.7. Summary
23.1. Architecture Context Diagram23.2. Architecture Flow and Interconnect Diagrams23.3. Example of AFD and AID Mapping23.4. Model Consistency and Balancing23.5. The Complete Architecture Model23.6. Summary
24.1. Hardware and Software Partitioning24.2. Applying the Template to Software Requirements24.3. Developing the Software Architecture24.4. The Hardware and Software Architecture Process24.5. Summary
25.1. Partitioning the Modeling Process
26.1. Problem Statement26.2. Requirements and Architecture Development26.3. Requirements Model26.4. Architecture Model
27.1. Problem Statement27.2. Requirements Model27.3. Architecture Model
28.1. Customer Dialogue28.2. Requirements Model28.3. Architecture Model
A.1. IntroductionA.2. Standard SymbolsA.3. Requirements ModelA.4. Architecture Model
B.1. Organizing the ModelsB.2. Military Standards
Additional information

Content preview from Strategies for Real-Time System Specification

Foreword

“Most systems people use the term real-time rather loosely,” the young manager said. We were seated over dinner with three members of her staff and some other managers who took part in the day’s seminar. “They say they’ve got a real-time constraint when they’re worried about impatient insurance brokers or bankers sitting in front of their terminals. A real-time system, in their minds, is just one that needs to be ‘quick as a bunny.’ If they fail to meet that constraint, their users might be inconvenienced or even annoyed. When we use the term, it means something rather different.”

Her co-workers began to smile, knowing what was coming. “We build systems that reside in a small telemetry computer, equipped with all kinds of sensors to ...