DEV475 Mastering Object-Oriented Analysis and Design with UML ...
Share Embed Flag
Download ePaper

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

DEV475 Mastering Object-Oriented Analysis and Design with UML ... DEV475 Mastering Object-Oriented Analysis and Design with UML ...

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UMLDefining Key AbstractionsDefining Key Abstractions• Define analysis class relationships• Model analysis classes and relationshipson class diagrams• Include brief description ofanalysis class• Map analysis classes tonecessary analysismechanismsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 30While defining the initial analysis classes, you can also define any relationships thatexist between them. The relationships are those that support the basic definitions ofthe abstractions. It is not the objective to develop a complete class model at thispoint, but just to define some key abstractions and basic relationships to “kick off” theanalysis effort. This will help to reduce any duplicate effort that may result whendifferent teams analyze the individual use cases.Relationships defined at this point reflect the semantic connections between thedefined abstractions, not the relationships necessary to support the implementationor the required communication among abstractions.The analysis classes identified at this point will probably change and evolve during thecourse of the project. The purpose of this step is not to identify a set of classes thatwill survive throughout design, but to identify the key abstractions the system musthandle. Do not spend much time describing analysis classes in detail at this initialstage, because there is a risk that you might identify classes and relationships that arenot actually needed by the use cases. Remember that you will find more analysisclasses and relationships when looking at the use cases.5 - 30

Module 5 - Architectural AnalysisExample: Key AbstractionsExample: Key AbstractionsProfessorStudentScheduleCourseCatalogCourseOfferingCourseMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 31Professor: A person teaching classes at the university.Student: A person enrolled in classes at the university.Schedule: The courses a student has enrolled in for a semester.CourseCatalog: Unabridged catalog of all courses offered by the university.CourseOffering: A specific offering for a course, including days of the week andtimes.Course: A class offered by the university.5 - 31

Module 5 - Architectural <strong>Analysis</strong>Example: Key AbstractionsExample: Key AbstractionsProfessorStudentScheduleCourseCatalogCourseOfferingCourse<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reserved 31Professor: A person teaching classes at the university.Student: A person enrolled in classes at the university.Schedule: The courses a student has enrolled in for a semester.CourseCatalog: Unabridged catalog of all courses offered by the university.CourseOffering: A specific offering for a course, including days of the week <strong>and</strong>times.Course: A class offered by the university.5 - 31

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!