02-introduction

02-introduction - CS4240 AaronBloomfield Introduction...

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 Principles of Software Design Aaron Bloomfield Introduction 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
22 So, what’s the point? n This whole class has one main goal: n “To  help  you  skillfully  assign  responsibilities  to  software objects”
Background image of page 2
33 Definitions n Object  oriented  analysis:  how  does  one  take  the  “things”  being  represented  and  make  them  into  objects? n Object oriented design: designing the software for  each of the classes identified in the analysis
Background image of page 3

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

View Full DocumentRight Arrow Icon
Analysis vs. Design n Analysis n Requirements analysis: what does the customer want? n OO analysis: investigating the domain objects n Focuses  on  finding  and  describing  the  concepts  in  the problem domain n Design n A conceptual solution that fulfills the requirements n Focuses  on  defining  software  objects  and  how  they collaborate to fulfill the requirements 44
Background image of page 4
55 Example: A dice game n Roll 2 dice n If a 7, player wins n Otherwise, player loses
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 Use cases n Just  a  prose  (i.e.  English)  explanation  of  what’s  happening n Play a dice game: player requests to roll the dice.   System  presents  results:  if  the  dice  face  value  totals seven, player wins; otherwise, player looses.
Background image of page 6
Click to edit Master subtitle style 77 UML
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 Domain models n Shows the important concepts (usually objects) in  a system, and how they interact Player name DiceGame Die faceValue Rolls Plays Includes 2 2 1 1 1 1
Background image of page 8
99 Interaction diagrams n Shows  how  the  objects  interact  with  each  other  over time :DiceGame play() die1 : Die fv1 := getFaceValue() die2 : Die roll() roll() fv2 := getFaceValue()
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 Class diagrams n Enumerating the methods, fields, etc. 2 Die faceValue : int getFaceValue() : int roll() DiceGame die1 : Die die2 : Die play() 1
Background image of page 10
1111 What is UML n Universal Modeling Language n Examples were the diagrams on the previous slides
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 Three ways to apply UML n As a sketch n For understanding n As a blueprint n For system specification n As a programming language n For fully writing a program
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 / 38

02-introduction - CS4240 AaronBloomfield Introduction...

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