architectural modeller Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > person or group > person > stakeholder > software developer > modeller > architectural modeller

architectural modeller comparison table

Subject make is a kind of is a subtopic of avoid perform apply use refine

modeller software developer 5.10 - Difficulties and Risks When Creating Class Diagrams the use of obscure features of technology because later versions of the technology might be changed in ways that are incompatible with how you have used it or the producer of the technology might go out of business or withdraw it from the market modelling a design pattern without understanding in depth the forces that need to be balanced, and if another pattern would better balance the forces

architectural modeller the interface of a package as simple as possible to simplify its use and testing modeller 9.4 - Software Architecture circular dependencies among packages architectural modelling design principles UML diagrams architectural model by following these steps iteratively:
Sketch an outline of the architecture, based on the principal requirements and use cases. Determine the main components that will be needed, such as databases, particular hardware devices and the main software subsystems
Refine the architecture by identifying the main ways in which the components will interact, and by identifying the interfaces between them. Decide how each piece of data and functionality will be distributed among the various components
Consider each use case and adjust the architecture to make it realizable
Mature the architecture as you define the final class diagrams and interaction diagrams

Subject	make	is a kind of	is a subtopic of	avoid	perform	apply	use	refine
modeller		software developer	5.10 - Difficulties and Risks When Creating Class Diagrams	the use of obscure features of technology because later versions of the technology might be changed in ways that are incompatible with how you have used it or the producer of the technology might go out of business or withdraw it from the market	modelling		a design pattern without understanding in depth the forces that need to be balanced, and if another pattern would better balance the forces
architectural modeller	the interface of a package as simple as possible to simplify its use and testing	modeller	9.4 - Software Architecture	circular dependencies among packages	architectural modelling	design principles	UML diagrams	architectural model by following these steps iteratively: Sketch an outline of the architecture, based on the principal requirements and use cases. Determine the main components that will be needed, such as databases, particular hardware devices and the main software subsystems Refine the architecture by identifying the main ways in which the components will interact, and by identifying the interfaces between them. Decide how each piece of data and functionality will be distributed among the various components Consider each use case and adjust the architecture to make it realizable Mature the architecture as you define the final class diagrams and interaction diagrams

Up: modeller