AUBURN COMP 7700 - The Unified Modeling Language (36 pages)

Previewing pages 1, 2, 17, 18, 19, 35, 36 of 36 page document View the full content.
View Full Document

The Unified Modeling Language



Previewing pages 1, 2, 17, 18, 19, 35, 36 of actual document.

View the full content.
View Full Document
View Full Document

The Unified Modeling Language

146 views


Pages:
36
School:
Auburn University
Course:
Comp 7700 - SOFTWARE ARCHITECTURE (3)
Unformatted text preview:

Chapter 3 The Unified Modeling Language COMP 7700 Unified Modeling Language 1 Process Phase Affected by This Chapter Requirements Analysis Design Framework Architecture Detailed Design Implementation COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 2 Classes at Detailed Design wafer canister Visible from without Canister numCanisters int numWafers int size float display getNumOpenSlots setStatus Responsibilities describes each canister undergoing fabrication Class name Attribute type Operations Place for comments COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 3 Key Concept Representing a Class in UML UML represents a class with a rectangle containing the class name We display additional information within the rectangle as needed Variables methods etc COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 4 UML Notation and Typical Implementation package of classes MyPackage package MyPackage abstract class MyAbstractClass abstract class MyAbstractClass inheritance package MyPackage class MyDerivedClass extends MyAbstractClass int att void myFunction ReferencedClass r MyDerivedClass att int attribute myFunction operation COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 5 Interfaces UML Notation Typical Java Implementation interface MyInterface myMethod realization interface MyAbstractClass class MyClass implements MyInterface MyClass myMethod COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 6 Key Concept Representing Inheritance in UML UML represents inheritance and interface realization with an open triangle COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 7 Aggregation UML Notation and Typical Implementation MyClass att int myFunction aggregation ac 1 MyAggregatedClass class MyClass MyAggregatedClass ac int att composition ac Composed object exists only in the scope of owner object COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 8 Key Concept Representing Aggregation in UML Class A aggregates class B if A objects require B objects in a structural sense typically with an instance variable UML symbol is an open diamond COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 9 Dependence UML Notation and Typical Implementation MyDependentClass att int myFunction MyReferencedClass dependence reference to a class class MyDependentClass void myFunction1 MyReferencedClass r parameter MyReferencedClass myFunction2 void myFunction3 MyReferencedClass m or return type or local variable type COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 10 Key Concept Representing Dependency Class A depends on class B if A objects require B objects for their definition In practice this means that B appears in at least one method of A UML representation a dotted arrow COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 11 Association UML Notation and Typical Implementation Employer 1 3 employs is employed by 1 n Employee class Employer Employee employees class Employee Employer employers COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 12 Customer Mail Application CustomerMailApplication generateMail getCustomerTypeFromUser main DelinquentCustomer createMail customer MountainCustomer createMail Customer createMail 1 RegularCustomer createMail COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 13 Key Concept Use Cases a sequence of actions taken by an application and its user The user takes one role COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 14 Use Cases For Video Store Application Activate 1 Actor hits any key 2 Application displays main menu 1 Check in clerk Check out Add video stocker Precondition Application has been activated 1 Actor clicks check out 2 Actor swipes bar code 3 Application prompts for rental duration 4 Actor enters duration 5 Application stores record 6 Application prints customer s account status 1 COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 15 Use Case Generalization Usage A Application displays main options B User selects icon Perform warehouse transaction Warehouse worker uses ControlApplication extends Modify Stock i Application displays logo Dispatcher ii Perform warehouse Transaction use case iii Application displays farewell screen iv Application shuts down A Application displays main options 1 User moves cursor to stock icon B User selects icon 2 Application displays stock window COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 16 Beginning of Sequence Diagram for Check Out Use Case Note 1 Clerk MainScreen BarCodeReader CheckoutOptionDisplay doCheckout Note 0 Checkout read Note 2 Step 3 of use case order Step 2 of use case initiate Note 3 show COMP 7700 Unified Modeling Language Adapted from Software Design From Programming to Architecture by Eric J Braude Wiley 2003 with permission 17 Beginning of Sequence Diagram for Check Out Use Case User MainScreen BarCodeReader CheckoutOptionDisplay doCheckout 1 read Checkout Account 2 1 initiate 2 2 create 2 3 show 3 setDuration Use case 1 User swipes bar code 2 Application prompts for rental duration 3 User enters duration 4 Application stores record 5 Application prints customer s account status 4 store 5 print COMP 7700 Unified Modeling Language Adapted from Software


View Full Document

Access the best Study Guides, Lecture Notes and Practice Exams

Loading Unlocking...
Login

Join to view The Unified Modeling Language and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view The Unified Modeling Language and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?