Object oriented analysis and design focus on what the system does and how it does it. It is a very helpful tool in software engineering, and teams have been using it for years. It will continue to be used as it is very versatile and can be adjusted to the changing trends. Team Task 1
I will take things one step at a time. I will gather all of the objects I will need first and put them in a list. I will then determine what role each object has and how it performs the tasks needed. Team Task 2
Cardinality refers to the relationships between different entities (objects). Team Task 3
The first is an object relationship diagram. This provides a brief overview. Next comes the use case diagram, which is a visual summary of several related use cases within a system or subsystem. Class diagrams represent a detailed view of a single use case, shows the classes that participate in the use case, and documents the relations among the classes. A sequence diagram is a dynamic model of a use case, showing the interaction among classes during a specified time period. State transition diagrams show how an object changes from one state to another, depending on events that affect the object. Activity diagrams resemble a horizontal flowchart that shows the action and events as they occur. Team Task 4
Explain how O.O.A. can be used to describe an information system. Define the terms and concepts. Explain object relationships and inheritance. Identify the actors. Draw a use case diagram. Draw an object relationship diagram. Describe UML. Explain CASE tools. Explain how to organize an object model. Review the diagrams and object relationships. Manage the SWL 1.a.
Concurrent: (1a) Define terms and concepts, (1b) explain object relationships and inheritance, (1c) describe UML, (1d) explain CASE tools, and (1e) review how to organize an object model. Sequential: (2a) Explain how O.O.A. can be used to describe an information system, (2b) identify actors, (2c) draw a use case diagram, (2d) draw an object relationship diagram, and (2e) review the diagrams and object model. Manage the SWL 1.b.
Task 2c cannot be completed until task 2b is completed. Task 2d cannot be completed until task 2c is completed. Task 2e cannot be completed until task 2d is completed. Manage the SWL 1.c.