![]() |
![]() |
![]() |
![]() |
![]() |
System Analysis
In the system analysis phase the system to be built is analyzed using an object-oriented method. The purpose of the phase is to describe the architecture of the system and identify the objects that are needed to implement the required functionality. The models used in this phase are:
- An analysis object model, to describe the architecture of the system and represent the objects in the system
- An analysis use case model where the interaction between some of the objects is described
- Textual analysis documents to document decisions and architecture related requirements not suitable to be expressed in the object models and use cases
The analysis object model is a conventional object model, consisting of class diagrams and possibly state charts, that forms the input to the object design phase. The analysts should in this model be concerned with identifying the objects that must be present in the system. These objects may come from the requirements object model produced in the requirements analysis, or they may be added in this phase for different reasons. For example, objects may be needed to represent the control logic described by the use cases from the requirements analysis. The differences between the object model in the system analysis phase and the object model in the requirements analysis phase are:
- The requirements analysis object model consists of objects visible on the border of the system and outside the system, e.g. users of the system, while the system analysis object model is focused on the internal object structure of the system.
- The purpose of the object model in the requirements analysis is different from the purpose in the system analysis. The purpose in the requirements analysis is to describe the problem that the system is to solve, while the purpose in the system analysis is to describe the system itself.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |