1. Software Requirements The starting point of software development “He kept changing the requirements on us” 1 540f07reqelic4sep4

2. Journaling u Writing helps organize and clarify your thoughts u We will start with the reading assignment for Thursday, Sep 6. The assignment is to write an explanation for each subsection of the “Manage Your Team” in S&G pp 243-254. This is due 11am Thurs u The reading assignment for Tues, Sep 11 will also have an assignment. 540f07reqelic4sep42

3. Stellman and Greene – ch 2 u Understand the project needs –Drive the scope of the project –Talk to the main stakeholder –Write the vision and scope document 540f07reqelic4sep43

4. Stellman and Greene – ch 2 u Vision and scope –Problem statement »Project background »Stakeholders »Users »Risks »Assumptions –Vision of the solution 540f07reqelic4sep44

5. Stellman and Greene – ch 2 u Vision and scope –Problem statement –Vision of the solution »Vision statement »List of features »Scope of phased release (optional) »Features that will not be developed 540f07reqelic4sep45

6. Stellman and Greene – ch 2 u Create the project plan –Statement of work »Not standard def »Description of all work products –Resource list –Estimates and project schedule –Risk plan »Estimate risk »Mitigation plan 540f07reqelic4sep46

7. Stellman and Greene – ch 2 u Project Plan Inspection Checklist 540f07reqelic4sep47

8. Requirement Specification u The goal of a requirement methodology is to produce a good requirement specification. u The goal of a requirement specification is to be able to answer all the relevant questions about the behavior of the proposed system. 8540f07reqelic4sep4

9. 9 reqelicit5 Data Dictionary Object Model Use Cases State Models Grand View of Specification DD contains name, type,semantics of all data used or produced Use Cases shows functionality Object Model shows relations between data and functions State Models show behavior of system Not all methodologies use all parts 9540f07reqelic4sep4

10. Elicitation u Problems of scope – the boundary is ill- defined or too many details u Problems of understanding – user not completely sure what is needed, etc u Problems of volatility – requirements change over time 10540f07reqelic4sep4

11. Requirements Tasks u Elaboration u Negotiation u Specification u Validation 11540f07reqelic4sep4

12. Requirements Elicitation u Three types of questions –Context of system –Understanding of system –Effectiveness of the meeting 12540f07reqelic4sep4

13. Context of System u Who is behind the request u Who will use the system u What will be the economic benefit 13540f07reqelic4sep4

14. Understanding of system u How to characterize good output u What problems will the solution address u Describe the business environment u Any special performance issues or constraints 14540f07reqelic4sep4

15. Effectiveness of meeting u Are you the right person u Are my questions relevant u Am I asking too many questions u Can anyone else provide additional info u Should I be asking you anything else 15540f07reqelic4sep4

16. Quality Function Deployment u Normal Requirements u Expected Requirements u Exciting Requirements 16540f07reqelic4sep4

17. Playing roles u Divide team – one half users, one half software engineers u The users are not to “initiate” requirements, only to answer questions. u Elicit requirements for a robotic system to welcome guests to an engineering college reception 17540f07reqelic4sep4

18. Coming Soon u 9/4 and 9/5 Lab – rational rose – part 2 u Reading for Thurs – S&G:10(4 Manage your team) pp 243-354 u Reading for Tues, 9/11 – S&G:10(1,2) pp232-238 u There is a chance that class on Thurs will be cancelled – I will send email late wed u No class Tues, 9/18 (job fair) 18540f07reqelic4sep4