modelling Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

Next process: obsolescence Up: process Previous process: maintenance

modelling comparison table

Subject use follow do iteratively involve has definition be see also lead by perform by is a subtopic of have challenge

architectural modelling UML diagrams 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. Choose architectural patterns.
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. Determine if you can re-use an existing framework.
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
a particularly difficult skill process^2 architectural modeller 9.4 - Software Architecture is to produce a relevant and synthetic picture of a large and complex system

dynamic modelling formal languages representing such things as the states that the system can be in, the activities it can perform, and how its components interact A type of modelling used to represent the internal states of the software and their changes difficult because in a large system there are a very large number of possible paths a system can take, and because it is hard to choose the classes to allocate each behaviour process^2 skilled developers 1.7 - Activities Common to Software Projects

structural modelling formal languages representing such things as the classes and objects present in the domain or in the software A type of modelling used to represent the data or architecture of software a particularly difficult skill process^2 1.7 - Activities Common to Software Projects

use case modelling formal languages Representing the sequences of actions performed by users of software. a particularly difficult skill use case 1.7 - Activities Common to Software Projects

Subject	use	follow	do iteratively	involve	has definition	be	see also	lead by	perform by	is a subtopic of	have challenge
architectural modelling	UML diagrams	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. Choose architectural patterns. 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. Determine if you can re-use an existing framework. 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				a particularly difficult skill	process^2		architectural modeller	9.4 - Software Architecture	is to produce a relevant and synthetic picture of a large and complex system
dynamic modelling	formal languages			representing such things as the states that the system can be in, the activities it can perform, and how its components interact	A type of modelling used to represent the internal states of the software and their changes	difficult because in a large system there are a very large number of possible paths a system can take, and because it is hard to choose the classes to allocate each behaviour	process^2	skilled developers		1.7 - Activities Common to Software Projects
structural modelling	formal languages			representing such things as the classes and objects present in the domain or in the software	A type of modelling used to represent the data or architecture of software	a particularly difficult skill	process^2			1.7 - Activities Common to Software Projects
use case modelling	formal languages				Representing the sequences of actions performed by users of software.	a particularly difficult skill	use case			1.7 - Activities Common to Software Projects

Next process: obsolescence Up: process Previous process: maintenance