1. Software Engineering Week 9 – Brief Introduction of Requirement #1 A.A. Gde Bagus Ariana, S.T. gungariana@yahoo.com http://gungariana.wordpress.com

2. Objectives To introduce the concepts of user and system requirements To describe functional and non-functional requirements To explain how software requirements may be organised in a requirements document

5. Why Important? The hardest single part of building a software system is deciding precisely what to build. No other part of conceptual work is as difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines and to other software systems. No other part of the work so cripples the resulting system If done wrong. No other part is more difficult to rectify later. (Brooks 1987)

6. Causes of the failed projects Incomplete requirements (13.1%) Lack of user involvement (12.4%) Lack of resources (10.6%) Unrealistic expectations (9.9%) Lac of executive support (9.3%) Changing requirements and specifications (8.7%) Lack of planning (8.1%) System no longer needed (7.5%)

9. Requirements Engineering Domains

10. Boundary

11. The Requirements Process : 2 Documents Req. definition – Complete listing of customer’s system expectations – High-level abstract description of req. – Natural language + simple diagrams – Limitations & constraints – From customer-supplied info. – Written for customers

12. The Requirements Process Definition of Requirement – Feature of system – Description of system Process – Action to determine the req. Capable of doing There is a purpose

13. Req. specification – Restates req. definition in technical terms – For sys. designers to follow – Detailed desc.  ? system should do – Sets out sys. services in detail – A.k.a. Functional Spec. – Cust./User/Developer contract – Written as a contract between customer and developer The Requirements Process : 2 Documents

14. The Requirements Process S/W specification – More detailed description – Bridge req. process & design activities – S/W abstracts  basis: design & implementation

15. The Requirements Process ProblemAnalysisProblemDescriptionPrototyping and testing Documentation & Validation Have we captured all the user need? Are we using the right techniques or views? Is this function feasible? Have we captured what the user expects? Req n Elicitation and Analysis Req n Definition and Specification Feasibility study Req n Analysis Req n Definition Req n Specification System models Definition of req n Specification of req n Req n Document Feasibility Report

16. The Requirements Process Req. elicitation – Developers work with cust. : Asking questions Demonstrating similar systems Developing prototypes – Problem analysis  identify: People Processes Resources ProblemAnalysisProblemDescriptionPrototyping and testing Have we captured all the user need? Are we using the right techniques or views? Is this function feasible? Req n Elicitation and Analysis

17. The Requirements Process Req. definition & spec. – 3 categories of req.: Must be met Highly desirable but not necessary Possible but could be eliminated Documentation & Validation Have we captured what the user expects? Req n Definition and Specification

18. The Requirements Process Req. definition & specification – Doc.  formal agreement Req.  specific descriptions of functions/charateristics Req.  does not specify “how” (E.g. what DBMS or pgm. Lang. to use)

19. The Requirements Process 2 steps  ensuring req. fully mapped & understood: – Verification  complete, correct & consistent requirements – Validation  developers described what customer intends

20. Configuration Mgmt. Set of procedures that track: – Requirements – Designs – Program codes – Tests strategies & approaches – Documents

21. Functional & Non Functional req. – Capture the intended behavior of the system ie. tasks or functions the system is required to perform. – Use cases have quickly become a widespread practice for capturing functional requirements – E.g. engine for a vehicle & invoice generation for a Debtors accounting system

23. Functional & Non Functional req.

24. Functional & Non Non-functional req. – Describes a restriction on the system – Split into two types: performance and development. Performance Constraints – The response time for information to appear to a user. – The number of hours a system should be available. – The number of records a system should be able to hold. – The capacity for growth of the system. – The length of time a record should be held for auditing purposes.

25. Functional & Non For the customer records example these might be: – Information should be made available and be stored in a maximum of 3 seconds. – The system should be available from 9am to 5 pm Monday to Friday. – The system should be able to hold a 100,000 customer records initially. – The system should be able to add 10,000 records a year for 10 years. – A record should be fully available on the system for at least 7 years.

26. Functional & Non Development constraints: – Time - When a system should be delivered is the obvious time constraint. – Resource - How much money is available to develop the system is obvious, but a key resource would be the amount of time business staff could spend in briefing system development staff. – Quality - Any standards which are used to develop the system including project management, development methods etc.

27. How to Express Req.? Natural language – Problem Not precise & unambiguous Not easily separated system elements Difficult to trace back – Solution Formal notation Automated tools

28. A Picture Is Worth thousand Words

29. How to Express Req.? Additional Req n Notations – Hierarchical Techniques (Warnier-Orr Diagram) – Data Flow Diagrams (DFD) – Software Req. Engineering Methodology (SREM) – Structured Analysis & Design Technique (SADT) – Formal Specification (Z)

30. How to Express Req.? Data Abstraction – Describing what the data are for – Each kind of data  an object  class type – Methods identified – UML’s diamond  aggregation – UML’s horizontal arrow  association

31. How to Express Req.? STUDENT Student number Credit-Hours Compute Tuition IN-STATE STUDENT Student number In-State Rate Compute Tuition OUT-STATE-STUDENT Student number Out-of-State Rate Compute Tuition class name attributes methods

32. How to Express Req.? Object-Oriented Specification Focus on entities involved Data-abstraction elements within Objects, attributes & methods Distinguishable: – Encapsulation – Information hiding – Class hierarchies – Inheritance – Polymorphism

33. How to Express Req.? Data Flow Diagram (DFD) – You already know

34. IEEE requirements standard Defines a generic structure for a requirements document that must be instantiated for each specific system. – Introduction. – General description. – Specific requirements. – Appendices. – Index.

35. Requirements document structure Preface Introduction Glossary User requirements definition System architecture System requirements specification System models System evolution Appendices Index

36. Key points Requirements set out what the system should do and define constraints on its operation and implementation. Functional requirements set out services the system should provide. Non-functional requirements constrain the system being developed or the development process. User requirements are high-level statements of what the system should do. User requirements should be written using natural language, tables and diagrams.

37. Key points System requirements are intended to communicate the functions that the system should provide. A software requirements document is an agreed statement of the system requirements. The IEEE standard is a useful starting point for defining more detailed specific requirements standards.

38. Thank You Question?

39. Tugas Buat resume tentang Requirement yang baik. Kriteria requirement yang baik adalah SMART: – Specific / spesifik – Measurable / terukur – Attainable / dapat dicapai – Realizable / daapt direalisasikan – Traceable / dapat dilacak Jelaskan dan beri contoh masing-masing kriteria diatas