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

2. Stellman&Greene – ch 10:1, 2 u Responsibility u Authority u Accountability 2 540f07tmproj6sep11

3. Stellman&Greene – ch 10:1, 2 u Visibility – how do we accomplish this for the team? 3 540f07tmproj6sep11

4. Lab Sep 11 and 12 u I will meet with each team individually u I will try to answer questions 4 540f07tmproj6sep11

5. Requirements Elicitation u Three types of questions –Context of system –Understanding of system –Effectiveness of the meeting 5 540f07tmproj6sep11

6. Context of System u Who is behind the request u Who will use the system u What will be the economic benefit 6 540f07tmproj6sep11

7. 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 7 540f07tmproj6sep11

8. 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 8 540f07tmproj6sep11

9. Requirements Tasks u Elaboration u Negotiation u Specification u Validation 9 540f07tmproj6sep11

10. 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 10 540f07tmproj6sep11

11. Software Process u a process model depicts the tasks that are done to achieve software development u process models usually depict –Actions (Tasks) –Artifacts (files,data,etc) –Actors –decisions (optional) 11 540f07tmproj6sep11

12. Process Segment 12 540f07tmproj6sep11

13. Purpose of Process Models u Understanding of what is (should be) done –training –management u Automation –clerical –analysis 13 540f07tmproj6sep11

14. Software Life Cycle (SLC) formalizing the process of software development 14 540f07tmproj6sep11

15. Software Crisis u Software is delivered over-budget, late, and not correct –software complexity –programmer productivity u DeMarco’s (IEEE Software Apr 94) –only too costly because they would like to pay less –only late because they want it sooner 15 540f07tmproj6sep11

16. Future of Software u increasing complexity u increasing criticality 16 540f07tmproj6sep11

17. How to achieve quality u Top-down –through software life cycle –through quality improvement –see Dilbert u Bottom-up –Personal Software Process 17 540f07tmproj6sep11

18. 18 reqelicit5 SLC Models Iterative Incremental Spiral 18 540f07tmproj6sep11

19. Journaling – due 11 am Tues, sep 18 u Write definitions of the major types of software life cycles: waterfall, spiral, iterative, incremental, and formal u The definitions should clearly distinguish between the major types u Additionally, identify characteristics of each. For example, when are requirements set, when is the first version delivered. 19 540f07tmproj6sep11

20. Team leader interviews u The team leader must meet privately with each team member. u The meeting should cover concerns, abilities, and anything relevant to the team participation. u The team leader must submit a report indicating when and where each meeting was held and a short summary of the discussion u This is due, via email, by Fri, Sep 21 20 540f07tmproj6sep11

21. Coming Soon u TL interviews due 9/21 via email u Reading for Thursday – S&G ch 6 Soft Req u No class or lab Tues, 9/18 (job fair), no lab wed, 9/19 u Upload by Tuesday, 9/16 – software life cycle assignment 21 540f07tmproj6sep11