cs427-12

cs427-12 - Analysis/Design in XP Similar to RUP except that...

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

View Full Document Right Arrow Icon
CS427 12-1 Analysis/Design in XP Similar to RUP except that everyone does it little written, more oral less is done up-front
Background image of page 1

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

View Full DocumentRight Arrow Icon
CS427 12-2 Analysis in RUP (and XP) Gather use cases from customer Make initial object model For each use case: step through use case,  note the objects it requires  note the operations it uses Clean up the model
Background image of page 2
CS427 12-3 Communication with customer XP does not require any written  requirements documents How do you make sure you are building  the system the customer wants? Customer is on the team Team writes code only for user stories
Background image of page 3

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

View Full DocumentRight Arrow Icon
CS427 12-4 User story User story equivalent to use case User story less detailed than use case usually just a sentence or two,  does not include detailed description How do developers know what the  customer meant by the user story?
Background image of page 4
CS427 12-5 XP timeline Developers Customer Write stories Estimate stories Pick stories Implement stories
Background image of page 5

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

View Full DocumentRight Arrow Icon
CS427 12-6 XP Timeline Startup Write stories Develop metaphor Estimate stories Normal Write stories, estimate stories, pick stories For each story write test write code refactor
Background image of page 6
CS427 12-7 Estimating stories Requires requirements talk to customer Requires design talk to other developers Requires experience
Background image of page 7

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

View Full DocumentRight Arrow Icon
CS427 12-8 Who is customer? Only one user of system Many users of system, all similar Many users of system, all different Mass-market software
Background image of page 8
CS427 12-9 XP does not necessarily Develop complete set of user stories Develop consistent model of system Develop documentation for “gold owner” for users for maintenance programmers
Background image of page 9

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

View Full DocumentRight Arrow Icon
CS427 12-10 XP Requirements What “Customer” does Talks with other customers Makes surveys Writes reports, position papers, specs, etc for  management and other customers Writes user stories
Background image of page 10
CS427 12-11 XP Analysis What the developer does Read user stories Talk to each other, play with the design, make  sure user story is understood Ask the customer questions Result: estimated user stories, developer who  thinks he understands what to do
Background image of page 11

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

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

Page1 / 42

cs427-12 - Analysis/Design in XP Similar to RUP except that...

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

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