Life Cycle Objectives (LCO) CSE 403, Spring 2006, Alverson

Size: px

Start display at page:

Download "Life Cycle Objectives (LCO) CSE 403, Spring 2006, Alverson"

Douglas Lee
5 years ago
Views:

1 Life Cycle Objectives (LCO) CSE 403, Spring 2006, Alversn

2 Readings Anchring the Sftware Prcess, Barry Behm, USC CSE 403, Spring 2006, Alversn

3 Outline Life Cycle Objectives Assignment 1 LCO review fr yur prduct idea CSE 403, Spring 2006, Alversn

4 Life Cycle Objectives Elements 1. Operatinal Cncepts What is it? high level scpe and bjectives 2. System Requirements What is it? lwer level actual planned deliverables 3. System and sftware architecture Hw technically? 4. Lifecycle plan Hw resurces? 5. Feasibility Ratinale Is this realistic? CSE 403, Spring 2006, Alversn

5 1: Operatinal Cncepts Tp level system bjectives and scpe What prblem are yu trying t slve? Why? Fr whm? User cmmunity, envirnment, majr benefits? Gals and nn gals set realistic expectatins CSE 403, Spring 2006, Alversn

6 1: Example Prblem: What: create a system fr displaying and playing musical chrds Why: Classrm demnstratins Fr whm: A music teacher User cmmunity: music teachers, music students Gals: Display musical chrds, mdify them interactively, save chrds fr use in future classes Nn gals: This is nt general music editing sftware. CSE 403, Spring 2006, Alversn

7 2: System Requirements Essential features f the system defined at a level apprpriate t the spin cycle capabilities, interfaces, reliability levels, appearance Easy t change early n, grws increasingly mre difficult Custmer s invlvement very imprtant they knw the dmain f interest far better than yu d what fits with their daily wrk and life patterns what might the future bring Neither yu nr the custmer knw everything try t build jint wnership f the prcess pen cmmunicatin can make change mre acceptable CSE 403, Spring 2006, Alversn

8 2: System Requirements (cnt.) The act f writing the spec describing hw the prgram wrks [frm user perspective] in detail will frce yu t actually design the prgram yu get a chance t see the pthles befre yu fall in The custmer can review it and sign ff quickly r cmplain early. If yu put it in writing, it s less ambiguus than if yu just say it. Frces yu t think f majr functinal areas, majr architectural defects A picture/diagram is (ften) wrth 1000 wrds. Scenaris/stries help, but dn't be verbse. Failing t write a spec is the single biggest unnecessary risk yu take in a sftware prject Jel Splsky HW tip: Yu d nt have t d a full spec fr this assignment. Yu will have a chance fr that in the LCA. CSE 403, Spring 2006, Alversn

9 2: Example The chrd visualizer will be used t demnstrate chrds in a music class. Users can input chrds by muse, external keybard*, r file+. The chrds will be displayed n a musical staff. A highlighted bx will indicate the currently selected chrd. Users can play back chrds* Users can save chrds t a file t be reladed later+. * User input + Develper input CSE 403, Spring 2006, Alversn

10 CSE 403, Spring 2006, Alversn

11 3: System and Sftware Architecture High level descriptin but with enugh detail t allw feasibility analysis Can this really be built with the available resurces? Architectural flaws will nly deepen as yu g frward, s cnsider alternatives while it s still early. This is necessarily a technical discussin (unlike the prir tw elements). HW Tip: Identify clients and servers and majr sftware cmpnents and interactins between them If attaching t 3 rd party sftware, verify the interface exists Pictures say 1000 wrds CSE 403, Spring 2006, Alversn

12 3: Example System will be implemented in Java File frmat will be in XML Challenge: Are the necessary XML parsers available? Is the verhead f XML necessary? Alternatives: Flat text file, binary file Input and utput will be MIDI Challenge: Des Jave supprt MIDI input and utput System will have a cncept f ntes, chrds, and chrd sets Alternatives: What ther frmats culd supprt this? Can this be extended if yu want t have multiple sets f chrds? CSE 403, Spring 2006, Alversn

13 3: Example Input file reads writes Chrd manager generates generates manipulates manipulates MIDI utput Visual display MIDI input CSE 403, Spring 2006, Alversn

14 4: Life Cycle Plan Identify stakehlders and their rles: Users, custmers, architects, develpers, etc. WWWWWHH: Why/What/When/Wh/Where/Hw/Hw Objectives Why is the system being develped? Schedules What will be dne, When? Respnsibilities Wh will d it? Where are they? Apprach Hw will the jb be dne? Resurces Hw much f each resurce? HW Tip: Yu nly need d a little nw. CSE 403, Spring 2006, Alversn

15 4: Example Stakehlders: client, teachers, students, develpment team Why is the system being develped? This system is being develped as an aid fr teachers t teach students abut chrds What will be dne, When? Ex. Chrd display by and input by week 4, file input and utput by week 6, etc. Wh will d it? Where are they? This can wait until there is a team Hw will the jb be dne? This can wait until there is a team Hw much f each resurce? 6 8 team members, 9 weeks, 1 MIDI input device CSE 403, Spring 2006, Alversn

16 5: Feasibility Ratinale Cnceptual integrity and cmpatibility What assumptins are yu making? Any unwarranted nes amng them? Identify risks CSE 403, Spring 2006, Alversn

17 5: Example Assumptins: Simple chrds sufficient fr teaching Java supprts MIDI input/utput Users want t be able t save/lad chrds Risks: Des the team have enugh musical knwledge? Des the team have enugh GUI prgramming knwledge? Unwarranted assumptins? CSE 403, Spring 2006, Alversn

Customer Upgrade Checklist

Customer Upgrade Checklist Custmer Upgrade Checklist Getting Ready fr Yur Sabre Prfiles Upgrade Kicking Off the Prject Create a prfiles prject team within yur agency. Cnsider including peple wh can represent bth the business and