1. 1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Supplementary Slides for Software Engineering: A Practitioner's Approach, 5/e Supplementary Slides for Software Engineering: A Practitioner's Approach, 5/e copyright © 1996, 2001 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited. This presentation, slides, or hardcopy may NOT be used for short courses, industry seminars, or consulting purposes.

2. 2 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Chapter 10 System Engineering

3. 3 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Agenda  Computer Based Systems  The System Engineering Hierarchy  Business Process Engineering  Product Engineering  Requirement Engineering  System Modeling

4. 4 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Computer Based Systems  A Set of arrangement of elements that are organized to accomplish some predefied goal by processing information  Elements  Software  Hardware  People  Database  Documentation  Procedures

5. 5 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 The Hierarchy

6. 6 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 System Modeling  Define the Processes  Represent the Behavior of the Processes  Define exogenous and endogenous inputs  Represent all the linkages (and output)  Consider the Restraining Factors:  Assumptions  Simplifications  Limitations  Constraints  Preferences

7. 7 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Business Process Engineering  uses an integrated set of procedures, methods, and tools to identify how information systems can best meet the strategic goals of an enterprise  focuses first on the enterprise and then on the business area  creates enterprise models, data models and process models  creates a framework for better information management distribution, and control

8. 8 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 The BPE Hierarchy  Information strategy planning (ISP)  strategic goals defined  success factors/business rules identified  enterprise model created  Business area analysis (BAA)  processes/services modeled  interrelationships of processes and data  Application Engineering  software engineering  modeling applications/procedures that address (BAA) and constraints of ISP  Construction and delivery  using CASE and 4GTs, testing

9. 9 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Information Strategy Planning  Management issues  define strategic business goals/objectives  isolate critical success factors  conduct analysis of technology impact  perform analysis of strategic systems  Technical issues  create a top-level data model  cluster by business/organizational area  refine model and clustering

10. 10 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Defining Objectives and Goals  Objective—general statement of direction  Goal—defines measurable objective: “reduce manufactured cost of our product”  Subgoals :  decrease reject rate by 20% in first 6 months  gain 10% price concessions from suppliers  re-engineer 30% of components for ease of manufacture during first year  objectives tend to be strategic while goals tend to be tactical

11. 11 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Business Area Analysis  define “naturally cohesive groupings of business functions and data” (Martin)  perform many of the same activities as ISP, but narrow scope to individual business area  identify existing (old) information systems / determine compatibility with new ISP model  define systems that are problematic  defining systems that are incompatible with new information model  begin to establish re-engineering priorities

12. 12 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 The BAA Process sales acct manufacturing QC eng’ring distribution admin. Data Model Process Decomp. Diagram Matrices e.g., entity/process matrix Process Flow Models

13. 13 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Product Engineering

14. 14 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Requirements Engineering  Elicitation — determining what the customer requires  Analysis & negotiation — understanding the relationships among various customer requirements and shaping those relationships to achieve a successful result  Requirements specification — building a tangible model of requirements

15. 15 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Requirements Engineering  System Modeling — building a representation of requirements that can be assessed for correctness, completeness, and consistency  Validation — reviewing the model  Management — identify, control and track requirements and the changes that will be made to them (Use Traceability Tables)

16. 16 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 Requirement Management Traceability Tables  Feature TT: How reqs. are related to important system/product features.  Source TT: Identifies the source of each req.  Dependency TT: How reqs. are related to each other.  Subsystem TT: Categorizes reqs. by the subsystems.  Interface TT: How reqs. are related to I/E interfaces.

17. 17 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 System Modeling Process  System Context Diagrams (SCD) – top level node in system hierarchy used to establish the boundary between the system being implemented (system model template servers as its basis)  System Flow Diagrams (SFD) – refinement of the process and control functions from SCD, derived by identifying the major subsystems and lines of information flow (precursor to DFD discussed chapter 12)

18. 18 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 System Modeling Process (Cont’d)  Initial SFD becomes the top level node of a hierarchy of more successively more detailed SFD’s  System Specification – developed by writing narrative description for each subsystem and definitions for all data that flow between subsystems

19. 19 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001 System Modeling Template  It is used to develop the system model  The system engineer allocates system elements to each of five processing regions within the template:  User Interface  Input  System function and control  Output  Maintenance and self-test