Object-oriented modeling: Difference between revisions

Revision as of 19:50, 7 May 2018

Revision as of 14:11, 28 September 2018

Line 3:

The software life cycle is typically divided up into stages going from abstract descriptions of the problem to designs then to code and testing and finally to deployment. Modeling is done at the beginning of the process. The reasons to model a system before writing the code are:

*Communication. Users typically cannot understand programming language or code area above all the others from one another the end. Model diagrams can be more understandable and can allow users to give developers feedback on the appropriate structure of the system. A key goal of the Object-Oriented approach is to decrease the "semantic gap" between the system and the real world, to have the system be constructedby using terminology that is the same as the functions that users perform. Modeling is an essential tool to facilitate achieving this goal .

*Abstraction. A goal of most software methodologies is to first address "what" questions and then address "how" questions. I.e., first determine the functionality the system is to provide without consideration of implementation constraints and then consider how to take this abstract description and refine it into an implementable design and code given constraints such as technology and budget. Modeling enables this by allowing abstract descriptions of processes and objects that define their essential structure and behavior.