1. Coming up: What is a requirement? 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 5 Requirements Engineering Modified to include some Agile Concepts Software Engineering: A Practitioner’s Approach, 7/e Chapter 5 Requirements Engineering Modified to include some Agile Concepts copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. NOTE: Some slides referenced from: Ian Sommerville Slides for Software Engineering.

2. Last week Software process models Software process models UML UML Class diagrams Class diagrams AAA 2

3. This week Requirements Requirements UML UML Use cases Use cases Guest speaker! Guest speaker! AAA 3

4. What is the most difficult part of developing software? AAA 4

5. Coming up: Requirements come in many forms 5 What is a requirement? Requirements are used to describe all Requirements are used to describe all aspects of a system They may range from a high-level abstract They may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification They serve many roles They serve many roles May be the basis for a bid for a contract - therefore must be open to interpretation May be the basis for a bid for a contract - therefore must be open to interpretation May be the basis for the contract itself - therefore must be defined in detail May be the basis for the contract itself - therefore must be defined in detail Are always used to communicate what you intend to build Are always used to communicate what you intend to build

6. Requirements come in many forms Requirements Statements Requirements Statements ex: “The system shall ….” ex: “The system shall ….” UML Use-case diagrams UML Use-case diagrams eXtreme Programming “User Stories” eXtreme Programming “User Stories” Any other documents that communicate what you intend to build Any other documents that communicate what you intend to build Prototypes can be used as requirements Prototypes can be used as requirements Existing systems can serve as requirements “Build this system, but use Java instead of Fortran” Existing systems can serve as requirements “Build this system, but use Java instead of Fortran” UML Sequence diagrams, State charts, activity diagrams… UML Sequence diagrams, State charts, activity diagrams… 6 Coming up: All Requirements

7. Coming up: Typical Requirements Statements 7 All Requirements Should specify external behavior of the Should specify external behavior of thesystem what the system does, not how what the system does, not how Includes functional and non-functional requirements Includes functional and non-functional requirements Functional requirements are statements of the services that the system must provide Functional requirements are statements of the services that the system must provide What must the system do? (Start all with the phrase “The system shall…”) What must the system do? (Start all with the phrase “The system shall…”) Non-functional requirements are constraints on the services and functions offered by the system Non-functional requirements are constraints on the services and functions offered by the system How must it do it? or a constraint on the system How must it do it? or a constraint on the system

8. Coming up: Why do we care? 8 Typical Requirements Statements Functional: The system shall display the heart rate, blood pressure and temperature of a patient connected to the patient monitor. Functional: The system shall display the heart rate, blood pressure and temperature of a patient connected to the patient monitor. Non-Functional: "Display of the patient's vital Non-Functional: "Display of the patient's vital signs must respond to a change in the patient's status within 2 seconds.” ‘ilities’ - Performance, Scalability, Capacity, ‘ilities’ - Performance, Scalability, Capacity, Availability Reliability, Recoverability, Maintainability, Serviceability, Security, Regulatory, Manageability What are some functional requirements on an iPod? Non-functional?

9. Coming up: Prescriptive versus Agile approach 9 Why do we care? Most large software systems address wicked problems Most large software systems address wicked problems Problems which are so complex that they can never be fully understood and where understanding develops during the system development Problems which are so complex that they can never be fully understood and where understanding develops during the system development Therefore, requirements are normally both incomplete and inconsistent Therefore, requirements are normally both incomplete and inconsistent Requirements help by giving you the best understanding you can have at the beginning Requirements help by giving you the best understanding you can have at the beginning

10. Change in requirements Recall the process models we discussed last week Recall the process models we discussed last week Are they good at handling changing requirements? Are they good at handling changing requirements? Do you think these prescriptive models would work when trying to reverse engineer a system? Do you think these prescriptive models would work when trying to reverse engineer a system? i.e., “build this system but in Java” i.e., “build this system but in Java” AAA 10

11. Prescriptive versus Agile approach Prescriptive – approach is to minimize/prevent change by understanding system thoroughly at the beginning Prescriptive – approach is to minimize/prevent change by understanding system thoroughly at the beginning Typically heard: “A change during implementation costs 10 times more than a change during requirements phase” Typically heard: “A change during implementation costs 10 times more than a change during requirements phase” Agile – approach is to manage change Agile – approach is to manage change by being flexible (i.e. Agile) by being flexible (i.e. Agile) Typically heard: Requirements planned for 6 months from now are most likely completely inaccurate. Don’t waste resources planning far ahead. Plan short iterations and adjust the plan as you go. Typically heard: Requirements planned for 6 months from now are most likely completely inaccurate. Don’t waste resources planning far ahead. Plan short iterations and adjust the plan as you go. 11 Coming up: Typical Prescriptive Requirements Engineering Process

12. Coming up: Requirements Engineering-II 12 Typical Prescriptive Requirements Engineering Process Inception—ask a set of questions that establish … Inception—ask a set of questions that establish … basic understanding of the problem basic understanding of the problem the people who want a solution the people who want a solution the nature of the solution that is desired, and the nature of the solution that is desired, and the effectiveness of preliminary communication the effectiveness of preliminary communication and collaboration between the customer and the developer Elicitation—elicit requirements from all stakeholders Elicitation—elicit requirements from all stakeholders to identify the problem to identify the problem propose elements of the solution propose elements of the solution negotiate different approaches, and negotiate different approaches, and specify a preliminary set of solution requirements specify a preliminary set of solution requirements Elaboration—create an analysis model that identifies data, functional and behavioral requirements Elaboration—create an analysis model that identifies data, functional and behavioral requirements Negotiation—agree on a set of requirements among all stakeholders (realistic, non-conflicting, inline with budget) Negotiation—agree on a set of requirements among all stakeholders (realistic, non-conflicting, inline with budget)

13. Coming up: Typical Prescriptive System Requirements Specification (SRS) Document Structure 13 Requirements Engineering-II Specification—can be any one (or more) of the following: Specification—can be any one (or more) of the following: A written document A written document A set of models A set of models A formal mathematical proof A formal mathematical proof A collection of user scenarios (use-cases) A collection of user scenarios (use-cases) A prototype A prototype Validation—a review mechanism that looks for Validation—a review mechanism that looks for errors in content or interpretation errors in content or interpretation areas where clarification may be required areas where clarification may be required missing information missing information inconsistencies (a major problem when large products or systems are engineered) inconsistencies (a major problem when large products or systems are engineered) conflicting or unrealistic (unachievable) requirements. conflicting or unrealistic (unachievable) requirements. Requirements management Requirements management Similar to source code management Similar to source code management

14. Coming up: Analysis Model 14 Typical Prescriptive System Requirements Specification (SRS) Document Structure Purpose Purpose Overall Description Overall Description System Features (Functional Requirements/Use Cases) System Features (Functional Requirements/Use Cases) External Interface Requirements External Interface Requirements User interface requirements or standards User interface requirements or standards Hardware interfaces to other systems Hardware interfaces to other systems Software interfaces to other systems Software interfaces to other systems Communication Interfaces Communication Interfaces Non-functional Requirements Non-functional Requirements Appendices - analysis model diagrams Appendices - analysis model diagrams See SRS Template on CS421 Project Page (provided by http://www.processimpact.com/ … but essentially from IEEE). See SRS Template on CS421 Project Page (provided by http://www.processimpact.com/ … but essentially from IEEE).http://www.processimpact.com/

15. Coming up: Use-Cases 15 Analysis Model Included to provide more clarification Included to provide more clarification about textual requirements (where needed) Elements of the analysis model Elements of the analysis model Scenario-based elements Scenario-based elements Functional—processing narratives for software functions Functional—processing narratives for software functions Use-case—descriptions of the interaction between an “actor” and the system Use-case—descriptions of the interaction between an “actor” and the system Class-based elements – e.g. class diagram Class-based elements – e.g. class diagram Behavioral elements – e.g. state diagram, sequence diagram, activity diagram, etc.. Behavioral elements – e.g. state diagram, sequence diagram, activity diagram, etc.. Flow-oriented elements – e.g. data flow diagram Flow-oriented elements – e.g. data flow diagram

16. Coming up: Use-Case Diagram 16Use-Cases A collection of usage scenarios that describe the thread of usage of a system A collection of usage scenarios that describe the thread of usage of a system Each scenario is described from the point-of-view of an “actor”—a person or device that interacts with the software in some way Each scenario is described from the point-of-view of an “actor”—a person or device that interacts with the software in some way Each scenario answers the following questions: Each scenario answers the following questions: Who is the primary actor, the secondary actor (s)? Who is the primary actor, the secondary actor (s)? What are the actor’s goals? What are the actor’s goals? What preconditions should exist before the story begins? What preconditions should exist before the story begins? What main tasks or functions are performed by the actor? What main tasks or functions are performed by the actor? What extensions might be considered as the story is What extensions might be considered as the story isdescribed? What variations in the actor’s interaction are possible? What variations in the actor’s interaction are possible? What system information will the actor acquire, produce, or change? What system information will the actor acquire, produce, or change? Will the actor have to inform the system about changes in the external environment? Will the actor have to inform the system about changes in the external environment? What information does the actor desire from the system? What information does the actor desire from the system? Does the actor wish to be informed about unexpected changes? Does the actor wish to be informed about unexpected changes?

17. Coming up: Use Case Description 17 Use-Case Diagram Each oval is a separate use case that has a description Each stick figure is an actor in your system The block is an external system that interacts with your system. Any system you aren’t developing is external

18. Use Case Description ID - ID - A unique to reference this use case U01, U02, etc… Objective - What is the ultimate objective of the use-case. What is it trying to achieve? Objective - What is the ultimate objective of the use-case. What is it trying to achieve? Priority – The overall priority of this use-case (Low, Medium, High) Priority – The overall priority of this use-case (Low, Medium, High) Source – Who is the main source of this use case. Who cares most about this functionality? This should be the one person you would ask if there is a question about this use-case. (Make up a name and cite their: John Smith (End-user) here.) Source – Who is the main source of this use case. Who cares most about this functionality? This should be the one person you would ask if there is a question about this use-case. (Make up a name and cite their: John Smith (End-user) here.) Actors – Which actors/stakeholders are involved in the use-case? Actors – Which actors/stakeholders are involved in the use-case? Flow of Events Flow of Events Basic Flow - flow of events normally executed in the use-case Basic Flow - flow of events normally executed in the use-case Alternative Flow(s) - a secondary flow of events due to infrequent conditions Alternative Flow(s) - a secondary flow of events due to infrequent conditions Exception Flow(s) - Exceptions that may happen during the execution of the use case Exception Flow(s) - Exceptions that may happen during the execution of the use case Includes - other use case IDs that are referenced in steps in the flow of events. Includes - other use case IDs that are referenced in steps in the flow of events. Preconditions - Any condition that must be satisfied before the use case begins. If the condition is “User is logged in”, then the first step of the use case is NOT “User logs in”. They are already logged in if that is a pre- condition! Preconditions - Any condition that must be satisfied before the use case begins. If the condition is “User is logged in”, then the first step of the use case is NOT “User logs in”. They are already logged in if that is a pre- condition! Post conditions - The conditions that will be satisfied after the use case successfully completes (typically same as objective) Post conditions - The conditions that will be satisfied after the use case successfully completes (typically same as objective) Notes/Issues - Any relevant notes or issues that need to be resolved Notes/Issues - Any relevant notes or issues that need to be resolved 18 Coming up: Alternate and Exception Flows

19. Alternate and Exception Flows 1. Basic Flow 1. User enters user name 2. User enters password 3. User submits the form 4. Password is validated as correct 5. Main menu is displayed 2. Alternate Flow 1: No password is present at step 1.4 1. System displays error message. 2. System continues at step 1.2 3. Alternate Flow 2: Password is incorrect as step 1.4 1. … 4. Exception Flow 1: Database is unreachable 1. System displays an unrecoverable error and exits. Coming up: Includes versus Preconditions 19 Show when in the basic flow this happens and where you end up after the alt flow You may not know when this happens. That’s okay

20. Includes versus Preconditions Basic Flow User selects option 4 from main menu screen … Preconditions: User is logged in Includes: None Basic Flow User selects option 4 from main menu screen … Preconditions: User is logged in Includes: None Coming up: eXtreme Programming (XP): User Stories 20 Basic Flow User executes U2: Login User selects option 4 from main menu screen … Preconditions: None Includes : U2: Login Basic Flow User executes U2: Login User selects option 4 from main menu screen … Preconditions: None Includes : U2: Login Don’t forget to show this on the use case diagram as “includes” Includes are steps in the use-case Pre-conditions happen before the use case Items are one or the other, not both!

21. eXtreme Programming (XP): User Stories Serve as requirements within the XP Serve as requirements within the XP process process Written by customers Written by customers Time Estimated by developers Time Estimated by developers Replaces large requirements documents Replaces large requirements documents Represents anything that is “progress” to the customer Represents anything that is “progress” to the customer Examples: Examples: Students can purchase monthly parking passes online. Students can purchase monthly parking passes online. Parking passes can be paid via credit cards. Parking passes can be paid via credit cards. Parking passes can be paid via PayPal Parking passes can be paid via PayPal Professors can input student marks. Professors can input student marks. Students can obtain their current seminar schedule. Students can obtain their current seminar schedule. Students can order official transcripts. Students can order official transcripts. 21 Coming up: eXtreme Programming (XP): User Stories

22. eXtreme Programming (XP): User Stories Short – 1 or 2 sentences. Usually Short – 1 or 2 sentences. Usually supposed to fit on a 3x5 notecard Easy to estimate (project velocity) Easy to estimate (project velocity) Allows requirements to change frequently with less impact Allows requirements to change frequently with less impact Without accompanying validation tests may lead to misinterpretation Without accompanying validation tests may lead to misinterpretation Difficult to scale to very large projects Difficult to scale to very large projects Requires close customer contact to ensure correct implementation Requires close customer contact to ensure correct implementation 22 Coming up: Format for User Stories (CS421 only… not standard!)

23. Format for User Stories (CS421 only… not standard!) Unique Identifier Unique Identifier Source – who should developer contact with questions about this? Source – who should developer contact with questions about this? Story – short (1-3 sentence) high-level description of story. When the developer plans to implement they should discuss with the customer the details. Story – short (1-3 sentence) high-level description of story. When the developer plans to implement they should discuss with the customer the details. As a [user role], I want to [goal], so I can [reason]. As a [user role], I want to [goal], so I can [reason]. Time estimate – how long in “ideal development time” – time without meetings or any interruptions Time estimate – how long in “ideal development time” – time without meetings or any interruptions Client’s Priority – how important is the story to the client? (Low, Medium, High) Client’s Priority – how important is the story to the client? (Low, Medium, High) Coming up: The web has MANY references about User Stories and Use Cases. 23

24. The web has MANY references about User Stories and Use Cases. User Stories: http://www.agile-software- development.com/search/label/user%20stories User Stories: http://www.agile-software- development.com/search/label/user%20stories Use Cases: http://alistair.cockburn.us/Use+case+fundamentals Use Cases: http://alistair.cockburn.us/Use+case+fundamentals Which is better? Many arguments – here is one: http://alistair.cockburn.us/Why+I+still+use+use+cases Which is better? Many arguments – here is one: http://alistair.cockburn.us/Why+I+still+use+use+cases Coming up: Characteristics of requirements 24

25. Characteristics of requirements Coming up: Negotiating Requirements 25

26. Coming up: Requirements Rationale 26 Negotiating Requirements Identify the key stakeholders Identify the key stakeholders These are the people who will be involved in the negotiation These are the people who will be involved in the negotiation Determine each of the stakeholders’ “win conditions” Determine each of the stakeholders’ “win conditions” Win conditions are not always obvious Win conditions are not always obvious Negotiate Negotiate Work toward a set of requirements that lead to Work toward a set of requirements that lead to“win-win” Different stakeholders have different ideas of Different stakeholders have different ideas of what they want

27. Coming up: Non-Functional Requirement Types 27 Requirements Rationale It is important to provide rationale with It is important to provide rationale withrequirements This helps the developer understand the This helps the developer understand the application domain and why the requirement is stated in its current form Particularly important when requirements have to be changed. The availability of rationale reduces the chances that change will have unexpected effects Particularly important when requirements have to be changed. The availability of rationale reduces the chances that change will have unexpected effects In this class we’ll provide the requirement’s source and assume they can contact the source to get a rationale if needed instead of an explicit “rationale”. This is more “agile” In this class we’ll provide the requirement’s source and assume they can contact the source to get a rationale if needed instead of an explicit “rationale”. This is more “agile”

28. Coming up: Non-Functional Requirement Examples 28 Non-Functional Requirement Types Product requirements Product requirements Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc. Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc. Organizational requirements Organizational requirements Requirements which are a consequence of Requirements which are a consequence of organizational policies and procedures e.g. process standards used, implementation requirements, etc. External requirements External requirements Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc. Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc. Remember: Non Functional = Constraints on the system

29. Coming up: Requirements must be testable 29 Non-Functional Requirement Examples Product requirement Product requirement 4.C.8 It shall be possible for all necessary communication between the APSE and the user to be expressed in the standard Ada character set. 4.C.8 It shall be possible for all necessary communication between the APSE and the user to be expressed in the standard Ada character set. Organizational requirement Organizational requirement 9.3.2 The system development process and deliverable documents shall conform to the process and deliverables defined in XYZCo-SP- STAN-95. 9.3.2 The system development process and deliverable documents shall conform to the process and deliverables defined in XYZCo-SP- STAN-95. External requirement External requirement 7.6.5 The system shall provide facilities that allow any user to check if personal data is maintained on the system. A procedure must be defined and supported in the software that will allow users to inspect personal data and to correct any errors in that data. 7.6.5 The system shall provide facilities that allow any user to check if personal data is maintained on the system. A procedure must be defined and supported in the software that will allow users to inspect personal data and to correct any errors in that data. security, maintainability constraint: quality constraint: interoperability Agile stories? How?

30. Coming up: Requirements: testable metrics 30 Requirements must be testable Traditional requirements must be written so that they can be objectively verified. Traditional requirements must be written so that they can be objectively verified. XP requirements have explicit acceptance test XP requirements have explicit acceptance test cases written by the customers to solve this problem. The problem with this requirement is its use of vague terms such as ‘errors shall be minimized” The problem with this requirement is its use of vague terms such as ‘errors shall be minimized” The system should be easy to use by experienced controllers and should be organized in such a way that user errors are minimized. The system should be easy to use by experienced controllers and should be organized in such a way that user errors are minimized. The error rate should be been quantified The error rate should be been quantified Experienced controllers should be able to use all the system functions after a total of two hours training. After this training, the average number of errors made by experienced users should not exceed two per day. Experienced controllers should be able to use all the system functions after a total of two hours training. After this training, the average number of errors made by experienced users should not exceed two per day.

31. Coming up: Requirements Validation 31 Requirements: testable metrics

32. Coming up: Validating Requirements-I 32 Requirements Validation Ensure the requirements define the system that the customer really wants Ensure the requirements define the system that the customer really wants Requirements error costs are high Requirements error costs are high so validation is very important Fixing a requirements error after Fixing a requirements error after delivery may cost up to 100 times the cost of fixing an implementation error

33. Coming up: Requirements final thoughts… 33 Validating Requirements-I Is each requirement consistent with the overall objective for the system/product? Work with all parties on this question! Is each requirement consistent with the overall objective for the system/product? Work with all parties on this question! Is each requirement bounded and unambiguous? (e.g. testable) Is each requirement bounded and unambiguous? (e.g. testable) Does each requirement have attribution? That is, is a source (generally, a specific individual) noted for each requirement? Does each requirement have attribution? That is, is a source (generally, a specific individual) noted for each requirement? Do any requirements conflict with other requirements? Do any requirements conflict with other requirements? Is each requirement testable, once implemented? Is each requirement testable, once implemented? Does the requirements model cover the system to be Does the requirements model cover the system to be built (information, function and behavior). Requirements errors are cheaper to fix before implementation and deployment

34. Coming up: Requirements final thoughts… 34 Requirements final thoughts… Requirements should specify one and only one thing Requirements should specify one and only one thing Requirements and User Stories can only pass or fail, they can’t partially pass. If you want to partially pass a requirement split into two Requirements and User Stories can only pass or fail, they can’t partially pass. If you want to partially pass a requirement split into two Requirements must be testable Requirements must be testable Requirements must specify what YOUR system must do, not what other (external) systems do Requirements must specify what YOUR system must do, not what other (external) systems do To make this easier, in this class all functional requirements must begin with “The system shall…” To make this easier, in this class all functional requirements must begin with “The system shall…” Must have a source (make it up for CS421) Must have a source (make it up for CS421)

35. Coming up: Requirements must have a unique ID 35 Requirements final thoughts… Should not be a design choice (this is hard to get right). Should not be a design choice (this is hard to get right). The system shall store user information including name, DOB, address and SSN. <-- Good! The system shall store user information including name, DOB, address and SSN. <-- Good! The system shall store user information in an Oracle database including name, DOB, address, SSN. <-- bad The system shall store user information in an Oracle database including name, DOB, address, SSN. <-- bad Is Oracle really REQUIRED? Hard to say… maybe, but probably not. This is a decision you would make at implementation design time. Is Oracle really REQUIRED? Hard to say… maybe, but probably not. This is a decision you would make at implementation design time. Question: Does the customer care that you use Oracle? MySQL? Etc.. Maybe someone found some other MUCH BETTER approach storing the data on moon rocks. Question: Does the customer care that you use Oracle? MySQL? Etc.. Maybe someone found some other MUCH BETTER approach storing the data on moon rocks. Again: This is hard to avoid… and I’m not to concerned with it on the SRS, but I want you to be very aware of when you are making design choices instead of required features. Again: This is hard to avoid… and I’m not to concerned with it on the SRS, but I want you to be very aware of when you are making design choices instead of required features.

36. Coming up: Bad Example Requirements Statements 36 Requirements must have a unique ID Must have a unique ID. Must have a unique ID. When testing you need to reference REQ-1 or REQ-287. Multiple things cannot be labeled REQ-1. When testing you need to reference REQ-1 or REQ-287. Multiple things cannot be labeled REQ-1. Later our test cases will say: This Later our test cases will say: This test case validates requirements REQ-1, REQ-27, and REQ-56.

37. Coming up: Bad Examples 37 Bad Example Requirements Statements Bad requirements examples: The system shall validate and accept credit cards and cashier’s checks. High priority. The system shall validate and accept credit cards and cashier’s checks. High priority. The system shall process all mouse clicks very fast to ensure user’s do not have to wait. The system shall process all mouse clicks very fast to ensure user’s do not have to wait. The user must have Adobe Acrobat installed. The user must have Adobe Acrobat installed. These don’t have a source or unique ID, but what else is wrong?

38. Coming up: SRS Functional Requirements Checklist 38 Bad Examples The system shall validate and accept credit cards and cashier’s checks. High priority. The system shall validate and accept credit cards and cashier’s checks. High priority. Problem: two requirements instead of one. Problem: two requirements instead of one. If the credit card processing works, but the cashier’s check validation does not… is this requirement pass or fail? Has to be fail, but that is misleading. If the credit card processing works, but the cashier’s check validation does not… is this requirement pass or fail? Has to be fail, but that is misleading. Maybe only credit cards are high priority and cashier’s checks are low priority. Maybe only credit cards are high priority and cashier’s checks are low priority. The system shall process all mouse clicks very fast to ensure user’s do not have to wait. The system shall process all mouse clicks very fast to ensure user’s do not have to wait. Problem: This is not testable. Quantify how fast is acceptable? Problem: This is not testable. Quantify how fast is acceptable? The user must have Adobe Acrobat installed. The user must have Adobe Acrobat installed. Problem: This is not something our system must do. It could be in the constraints/assumptions or maybe operating environment sections, but is not a functional requirement of our system Problem: This is not something our system must do. It could be in the constraints/assumptions or maybe operating environment sections, but is not a functional requirement of our system

39. SRS Functional Requirements Checklist All start with “The system shall…” All start with “The system shall…” All have a unique identifier (R1, R2, R3, …) All have a unique identifier (R1, R2, R3, …) All do one and only one thing All do one and only one thing All are testable All are testable Have a source (who asked for it? make it up for the SRS – John Smith (Marketing), Nguyen Kim (sys admin), etc… Have a source (who asked for it? make it up for the SRS – John Smith (Marketing), Nguyen Kim (sys admin), etc… Says something YOUR software shall do Says something YOUR software shall do Are all labeld “F” in the chart Are all labeld “F” in the chart Coming up: SRS Non-functional Requirements Checkist 39 Check this when writing the SRS

40. SRS Non-functional Requirements Checkist Section 5 just categorizes items in the table: Section 5 just categorizes items in the table: 5.1 Performance Requirements 5.1 Performance Requirements See section 7 R11-R17, R29, R4 See section 7 R11-R17, R29, R4 5.2 Safety Requirements 5.2 Safety Requirements See section 7 R18 See section 7 R18 All the ones listed in section 5 should be marked “NF” in section 7’s table and be non-functional constraints All the ones listed in section 5 should be marked “NF” in section 7’s table and be non-functional constraints Intuition: Is this something I can assign to one developer and say “code this”… if so, it’s functional. (A constraint?) Intuition: Is this something I can assign to one developer and say “code this”… if so, it’s functional. (A constraint?) Coming up: The Result of Good Requirements 40 Check this when writing the SRS

41. End of presentation 41 The Result of Good Requirements I’m melting! Your wicked problems melt into small manageable problems ….