04-elaboration

04-elaboration - CS4240 AdvancedSoftwareDesign...

Info iconThis preview shows pages 1–13. 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 Elaboration Domain Models 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 Elaboration
Background image of page 2
33 What is elaboration? n The building of the high-risk and high-value parts n A given use case is done over multiple iterations: 1 Use Case Process Sale 2 3 . . . Use Case Process Sale Use Case Process Sale Use Case Process Rentals Feature: Logging
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 Elaboration in one sentence n “Build  the  core  architecture,  resolve  the  high-risk  elements, define most requirements, and estimate  the overall schedule and resources”
Background image of page 4
55 A waterfall picture excuse… n If  elaboration  is  only  1  iteration,  then  you  are  doing  the  “waterfall” thinking
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 Artifacts started during elaboration n Domain model n Design model n Software architecture document n Data model n Use-case storyboards, UI prototypes
Background image of page 6
Incorrect ways to do elaboration n You know you don't understand elaboration when. .. n It's more than a “few” months n Has only 1 iteration n Most requirements defined beforehand n Risky elements not being tackled n Does not result in an executable after each iteration n Considered primarily design and/or requirements phase n Trying to do all the design beforehand n No early and realistic testing 77
Background image of page 7

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

View Full DocumentRight Arrow Icon
88 Planning the next iteration n What to include for the next iteration? n Consider: risk, coverage, complexity n Give things a priority: high, medium, low n Based on those factors
Background image of page 8
Click to edit Master subtitle style 99 Domain models
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 Definition n A domain model is a visual representation of real- situation conceptual classes (not software objects!)
Background image of page 10
1111 Conceptual classes n Can  be  represented by a: n Symbol n Intension n Extension Sale date time concept's symbol "A sale represents the event of a purchase transaction. It has a date and time." concept's intension sale-1 sale-3 sale-2 sale-4 concept's extension
Background image of page 11

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

View Full DocumentRight Arrow Icon
1212 Artifact relationships n Only  the  top  part  is  the  domain model! Process Sale
Background image of page 12
Image of page 13
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 / 42

04-elaboration - CS4240 AdvancedSoftwareDesign...

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

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