03
Jan
Chapter 1: Object Technology between the development team
Chapter 1: Object Technology between the development team members as well as between them and the customer. Development team members can discuss their designs with the client to ensure they have fully understood his needs. Models can be layered and hence provide varying levels of detail. Abstract software models omit large amounts of fine-grained detail and permit us to gain a high-level view of the system and its architecture. These views permit us to focus on various parts of the system without recourse to the details of program code. Repeated refinement of these models can be used to progress them toward the final code. An architect when designing a building often constructs a number of diagrams that present it from a variety of perspectives. One view is, of course, the structure of the building and is vital to the construction company. This same view is also important to the customer since it reveals the details of the accommodation, its layout and the access to stairs, elevators, etc. However, electrical (or plumbing) contractors are more interested in the run of electrical circuits (water supplies and drainage pipes) and their supply to the building from the utility companies. Hence an architect would construct a number of blueprints highlighting these various facets. In a similar manner, the software architect can offer a range of UML diagrams that view the system from different perspectives. Some give a static view of the application with the architectural configuration of the objects as the primary focus. Other UML models emphasize the dynamic behaviour of the objects and their interactions. 1.1.2 UML The UML defines a diagrammatic notation for describing the artefacts of an OOAD. Through the UML we can visualize, specify, construct and document our software application. As our software systems become ever larger and ever more complex we need to manage that complexity and, in a sense, simplify it so we have a better understanding of it. Often, visualizing the software graphically is more appropriate than struggling to understand it in program code. By inspecting our models we can identify deficiencies in our designs as well as opportunities to enhance them. The UML acts as a specification language in which we can precisely and unambiguously capture our design decisions. Finally, from our UML diagrams we can derive programming language code. This is referred to as forward engineering the generation of code from UML models. This is an approach we advocate through this textbook. The models are at the core of our designs. The code is an outcome of that modelling activity and is itself a design document. The models dictate the code that we ultimately produce. 1.1.3 Analysis and design models An analysis model used in software development aims to document various facets of the real world problem that we are modelling. In an object-oriented system development this would typically involve identifying the significant application objects and the application processing to be performed.
If you looking for unlimited one inclusive web hosting plan please check unlimited web hosting website.