03-inception

03-inception - CS4240 AdvancedSoftwareDesign AaronBloomfield

Info iconThis preview shows pages 1–14. Sign up to view the full content.

View Full Document Right Arrow Icon
Click to edit Master subtitle style CS 4240 Advanced Software Design Aaron Bloomfield Inception Fall 2009
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Click to edit Master subtitle style 22 Inception
Background image of page 2
33 Recall the four UP phases n Inception n Elaboration n Construction n Transition
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
44 Inception n Summarized:  “Envision  the  product  scope,  vision, and business case” n The problem solved: n “Do the stakeholders have basic agreement on the vision  of  the  project,  and  is  it  worth  investing  in  serious  investigation?”
Background image of page 4
Questions asked n What  is  the  vision  and  business  case  for  this  project? n Feasible? n Buy and/or build? n Rough  unreliable range of cost: Is it $10k-$100k or  in the millions? n Should we proceed or stop? 55
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
66 Buzzword alert: artifacts n An ‘artifact’ (as far as UP is concerned) is: n A document that defines some aspect of the development n Vision n Business Case n Use-Case Model n Supplementary Specification n Glossary n Business Rules n Risk List n Risk Management Plan n Prototypes n Iteration Plan n Phase Plan n Software Development Plan
Background image of page 6
77 “Waterfall” inception n Many people confuse  inception with the  waterfall requirements  phase n Dettifoss waterfall in  Iceland (via 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
You didn’t understand inception when… n … it’s more than a few weeks long n … you define most of the requirements n … estimates or plans are expected to be reliable n … you define the architecture n … there is no Business Case or Vision artifact n … all the use cases were written in detail n … none of the use cases were written in detail 88
Background image of page 8
Click to edit Master subtitle style 99 Evolutionary Requirements
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
1010 Evolutionary vs. waterfall requirements n 25% of requirements change on a software project! n Box Log Falls, Lamington National Park, Queensland,  Australia (via wikicommons)
Background image of page 10
1111 Category requirements n FURPS+ n Functional n Usability n Reliability n Performance n Supportability n The + can stand for: n Implementation n Interface n Operations n Packaging
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Click to edit Master subtitle style 1212 Use cases
Background image of page 12
1313 Use cases n An English description of using the system n Not diagrams!!! n
Background image of page 13

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 14
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/25/2009 for the course CS 4240 taught by Professor Aronbloomfiled during the Spring '09 term at UVA.

Page1 / 41

03-inception - CS4240 AdvancedSoftwareDesign AaronBloomfield

This preview shows document pages 1 - 14. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online