Sample Application of OOSEM to Real Time Application

Transcription

1 Sample Application of OOSEM to Real Time Application Doug Ferguson INCOSE OOSEM Working Group Copyright INCOSE All rights reserved. 1

2 m2 s13 SE Interface with Hardware/Software Inputs to SW/HW (Partial List) Allocated requirements Design constraints System architecture System scenarios Outputs to Systems (Partial List) Requirements compliance SW/HW Design Verification results Risks and issues Manage Development HW/SW Level: SE Interface HW/SW Req ts & Design Integrate and Test SE Interface Implement Design 2

3 Software Requirements Analysis Inputs: Concept of Operations Context Diagram Mission Use Cases System Architecture Diagram Functional Design Documents [System] Use Cases Use Case Scenarios System Constraints Diagram Software & I/F Rqmts Outputs: Updated Rqmts Derived Software Rqmts Updated Use Cases Updated Use Case Scenarios State Diagrams Software Requirements Specification (SRS) Software Test Plan (STP) s47 3

4 Context Diagram Sets the boundary of the system, what is inside and what is outside Specifies all external actors Specifies all I/O between each external and the system If complex, the top captures the kinds of I/O and lower context diagrams for subsystems capture details Starts capture of External Interface Control Documentation 4

5 System Architecture Diagram Specifies Logical components I/O between components Allows reasoning of which components will perform what operations 5

6 Use Cases Mission From the CONOPS System From the Requirements Specification 6

7 Traditional Functional Decomposition and Allocation to Components Top Level Function F1 Data / Control Flow F2 F3 F1.2 F1.2 F1.3 F2.1 F2.2 F2.3 F3.1 F3.2 F3.3 C1.1 C1.2 C1.3 C2.1 C2.2 C2.3 C3.1 C3.2 C3.3 7

8 OO System Decomposition & Allocation Mission Use Case Mission UseCase Enterprise Actors Enterprise Enterprise Scenarios Message1() Message2() Enter Actor 1 Enter Actor 2 Ext Sys 1 System Ext Sys 2 Message1.1() System Scenarios Message1.2() Message2.2() Message1.3() Message 2.1() Message2.3() This is a notional chart with multiple diagram types 8

9 m4 s155 Allocate Logical Components Logical Component Allocation SW Data HW Procedure Deployment HW HW People 9

10 ESS Allocation Table (partial) m4 s156 Each Logical Component in each node is allocated to HW, SW, Data, and Procedures components in the Reference Architecture Logical Components Physical Components Entry Perimeter Entry/Exit Event Site Customer Customer System Alarm Type Sensor Exit Sensor Sensor Monitor Monitor Comms I/F Event Log I/F Output Mgr Status Fault Mgr Generator Alarm I/F «software» Device Mgr X SF Comm I/F User I/F Event Mgr X X Site Status Mgr Site RDBMS X X CMS RDBMS X «data» Video File X CMS Database X Site Database X X «hardware» Optical Sensor X X DSL Modem X User Console X Video Camera X Alarm X X X X 10

11 Software Allocations 11

12 Detect and Report Fire Condition Use Case 12

13 Software Internal Block Diagram 13

14 State Diagram 14

15 Software Architectural Design 15

16 Concurrency Diagram 16

17 Timing Constraints 17

18 Reporting and Fire Dispatch 18

19 Reporting and Dispatch Classes 19