{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

1.2-Phases_of_Software_Life_Cycle_Design_2

1.2-Phases_of_Software_Life_Cycle_Design_2 - CMPT 225 Unit...

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

View Full Document Right Arrow Icon

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

View Full Document Right Arrow Icon

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

View Full Document Right Arrow Icon

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

View Full Document Right Arrow Icon

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

View Full Document Right Arrow Icon

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

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: CMPT 225 Unit 1 Software Life Cycle and Principles of Software Development Step 2 – Design Part 2 CMPT 225 UML Class Diagram 2 ClassName Attributes Operations Let’s not include our constructors, destructors, getters/accessors, setters/mutators because we shall assume that we will always develop these operations for all our classes. CMPT 225 3 UML Relationship • Generalization Relationship: is - a Example 1: Example 2: Account Saving Account Chequing Account Investment Account Student Person more general more specific We read the above class diagram as follows: Student is-a Person CMPT 225 4 Example: UML Class Diagram for our Banking Application • Using the principle of _______________ • Using the “name” and “verb” technique Customer Account account ID balance Bank deposit(amount) withdraw(amount) CMPT 225 5 UML Relationship • Association Relationship: has – a – Aggregation – Composition Example: We read the above class diagram as follows: CMPT 225 6 UML Relationship • Dependency Relationship: Example: We read the above class diagram as follows: CMPT 225 7 UML Relationship • Multiplicity Relationship: Example: We read the above class diagram as follows: 1) 2) CMPT 225 Using the Principle of Encapsulation • Purpose of – Account – Customer – Bank 8 CMPT 225 9 Example: UML Class Diagram for our Banking Application • Using the principles of _______________ Customer Account account ID balance Bank deposit(amount) withdraw(amount) CMPT 225 10 Observations about “noun” and “verb” technique Nouns: • bank • application • account • customer • $ • account ID • balance • operation • menu • name • first name • last name • example • account information • reason • amount of money Verbs: • want • handle • deposit • supply • withdraw • get the balance • belong • have • is • attempt • cancel • open • identify • close • exist • display • request • delete • state • ask CMPT 225...
View Full Document

{[ snackBarMessage ]}

Page1 / 24

1.2-Phases_of_Software_Life_Cycle_Design_2 - CMPT 225 Unit...

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

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