COIS 2240H Study Guide - Final Guide: Object Diagram, Activity Diagram, Sequence Diagram
25 May 2018
School
Department
Course
Professor
Static diagrams:
- Class Diagram
- Object diagram
Dynamic diagrams:
- Activity diagram
- Sequence diagram
- State chart diagram
What is the difference between static and dynamic uml diagrams
- Static UML diagrams are utilized to outline the different software components,
and outline certain relationship between software components. However, it
does not show you all the possible interactions between software
components,
- it does not show how different software components interact at all. Static
UML diagrams are not stochastic, that means they are stagnant and do not
include what the software will do after time has passed.
How do we use them differently?
- Dynamic UML diagrams are the exact opposite, they are utilized to model
the functionality of the system, and they are also utilized to model how the
different software components are supposed to interact.
Why do we model
- 1-It is cost efficient
- 2-It ensures that we have a template to follow and that we are not coding
blindly
- 3-It allows us to map out interactions between software components
- 4-It allows a software development team to be more organized, and gives
us the ability to effectively delegate tasks
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
What is the difference between static and dynamic uml diagrams. Static uml diagrams are utilized to outline the different software components, and outline certain relationship between software components. However, it does not show you all the possible interactions between software components, it does not show how different software components interact at all. Uml diagrams are not stochastic, that means they are stagnant and do not include what the software will do after time has passed. Dynamic uml diagrams are the exact opposite, they are utilized to model the functionality of the system, and they are also utilized to model how the different software components are supposed to interact. 2-it ensures that we have a template to follow and that we are not coding blindly. 3-it allows us to map out interactions between software components. 4-it allows a software development team to be more organized, and gives us the ability to effectively delegate tasks.
