1. Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define data objects visible at the business area level (+ relationships & data flow) –Identify information support systems

2. Business System Design Focus: Element View (specific information system in a business area) Goals: –Model the requirements –Design: Data Architecture Applications Architecture Technology Infrastructure

3. Construction & Integration Focus: Detailed View (implementation of an element) Goals: –Implement the architectures and infrastructure –Insert the completed system into the business area (training, logistics, …)

4. Product Engineering Hierarchy

5. Requirements Engineering Elicitation Analysis & Negotiation Specification Modeling Validation Management How can we specify a system that meets the customer’s needs and expectations?

6. Requirements Elicitation Challenges –Scope: Defining the system boundary Lack of clarity on overall objectives –Understanding: Customer not skilled Doesn’t state the obvious Requirements ambiguous, conflicting, … –Volatility: Requirements change over time

7. Elicitation [2] Assess feasibility Identify people & their role(s) Define technical environment Identify domain constraints Select elicitation method(s) Solicit participation from several perspectives Identify ambiguous requirements Create usage scenarios

8. Analysis & Negotiation Is each requirement: –Consistent with overall objective? –Sufficiently abstract? –Essential to overall objective? –Bounded and unambiguous? –Attributed to a source? (person) –Conflicting with other requirements? –Achievable in technical environment? –Testable, once implemented?

9. Requirements Specification Elements of a Specification: –Written documents –Graphical models –Formal mathematical models Final work product: System Specification

10. System Modeling Evaluate the system’s components in relation to one another Link requirements to system components Validate assumptions about data flow, work flow, input / output,...

11. Requirements Validation Is each requirement: –Stated clearly? –Verified by an identified source? –Bounded in a quantitative way? –Associated with other requirements? –Consistent with domain constraints? –Testable, with specified tests? –Traceable to the system model? –Traceable to overall objectives?

12. Requirements Management Identify, control, and track: –New requirements –Changes to requirements Active throughout the life-cycle Traceability Table –Relates requirements to features, source, dependency, subsystem, interface, etc.

13. Generic Traceability Table

14. USER INTERFACE PROCESSING INPUT PROCESSING OUTPUT PROCESSING Process and control functions Maintenance and self-test Figure:-System Model template