CHAPTER 5OBJECT

MODELINGKEVEN MAYFIELD

ITP251

To Rick,I did some searching around and talked to a

few of my other friends in the business about object-oriented analysis and design and apparently it’s the way to go. It lets you use objects to model the requirements for a project. It can be used from start of design to the projects deployment and can help solve problems. I also learned that it can be used with Java and C languages. I hope I have given you the information you need to make a good presentation.

Keven MayfieldInformation Systems Analyst

LET ME SHOW YOU HOW TO DO THIS!!!

Organization is Key2. Make sure every Class has correct Objects3. Check to ensure Objects in class have similar Attributes4. Make sure the Inheritance of objects is correct5. Check that Messages flow correct and produce correct

Method6. Once all is well we can move on to create the diagram of

choice.

1,2,3 It’s Cardinality It’s a matter of two separate classes having the

same outcome.

DIAGRAM BREAKDOWNCLASS ACTIVITY

SEQUENCE STATE TRANSITION

CLASS DIAGRAM Detailed look of single use case Shows classes that are participating Documents the relationship among classes Class = Rectangle Lines = Relationships between classes

SEQUENCE DIAGRAMS Dynamic model of use case Shows interaction between classes for period of

time Show messages and timing of message Classes = Rectangle Lifelines = Dashed Lines Messages = Line in Direction Focuses = Narrow Vertical Line

STATE TRANSITION DIAGRAM

Shows how objects change State = Rounded Rectangles Initial State = Small Circle Action = Lines Left to Right Final State = Circle w/ Hollow Border

Activity Diagram Flow chart showing action and events as

they occur Classes = On Vertical Bars Actions = Horizontal arrow