SENG 5130 Systems engineering processes Module 14

Transcript:SENG 5130 Systems engineering processes Module 14:
SENG 5130 Systems engineering processes Module 14 A system Last Lecture Module 14 Module 1 - Introduction Remember remember… A system Component Interrelationship Boundary Environment System Environment Outside of the system boundary Outside system’s control Influences (or is influenced by ) system’s performance Characteristics of a system Constitutes a complex combination of resources Is contained within some form of hierarchy May be broken down into subsystems and related components that interact with each other Must have a purpose (defined need, goals and objectives which must be clearly stated by the user) 3 Phase Lifecycle Definition Development Deployment Module 2 – Bringing systems into being Remember remember… Objective for Module 2 Principles and processes To “engineer” a system Integration and iteration in system design Implementation of systems engineering and analysis Process Models of Systems Engineering The Waterfall model Spiral Model Generic “Vee” Model Evolutionary Model Incremental Development Model The Waterfall Model The “waterfall model” of the software life cycle. Source: SOFWARE ENGINEERING ECONOMICS by Bohem, B.W. FEEDBACK Spiral Model “Vee” Process Model Define system requirements Allocate system functions to sub-systems Detail design of components Full system operation and verification Verification of sub-systems Verify components Integration and Verification Sequence Decomposition and Definition Sequence Testing Evolutionary Process Model A complete, or virtually complete, software system is developed at each of several repetitions of the life cycle Allows for full development of user requirements over time Figure 2.21 (Sage & Armstrong, 2000) Incremental Development Model (Sage & Armstrong, 2000) Hybrid Process Model SE vs engineering discipline influence on design Module 3 – Conceptual Design Phase Remember remember… Conceptual Design Domain of customer Functional design Responsibility of the customer What does the system need to do? How well? Conceptual Design Preliminary Design Module 4 – Preliminary Design Remember remember… Preliminary Design Responsibility: Contractor (whose responsibility was Conceptual Design?) Customer’s role: Monitoring Reviewing Supporting contractor progress Preliminary Design Module 5 – Detailed Design and Development Remember remember… The Big Picture Detailed Design Realization and documentation of individual components Describe lower-level components Define component characteristics Finalize design of all interfaces Procure items for development Develop and test prototype Conduct critical design review Revise development specifications Define detailed requirements for units, assemblies, and components Define detailed requirements for interfaces Produce product specifications Conduct detailed design of units, assemblies, and components Buy, build, and integrate (prototype) Finalize product, material, and process specifications Until satisfactory Until complete To Construction and