03
Jan
4 Object-Oriented Design with UML and Java Development
4 Object-Oriented Design with UML and Java Development methods that pre-dated object technology often deliberately delineated between the analysis phase and the design stage. Commonly, they would also use a linear or waterfall model for the development process in which the design stage only follows after all the analysis has been completed. Further, these separate analysis and design stages often resulted in a conflict between them, especially where different models and notations were deployed. Object-oriented methods are characterized by using the same modelling concepts throughout the software lifecycle. This way, the solution that emerges during analysis is carried through into design and finally to code. Objects identified during analysis should also be present in the final code. This offers a seamless integration of the stages, not otherwise found with other approaches. The design models augment the analysis models with additional detail and, perhaps, introduce further low-level system objects required in the implementation. 1.1.4 Development process The UML is a modelling language. It has no notion of a development process, which must accompany a method. The dictionary defines a method as a systematic or orderly procedure. The authors of the UML understood this distinction and deliberately sought to separate the language used to document a software design from the process used to develop it. They recognized that processes are influenced by many considerations such as the nature of projects and the culture of organizations. Object-oriented design is usually conducted within an iterative process. This is vital to ensure that we can revisit earlier decisions when corrections or modifications are necessary. This is not unreasonable. After all, initial design decisions may require revision, especially in new projects or in those that are less well understood by the development team. The iterative process continues until the full system is developed. In common with many object-oriented developers, an iterative process is also accompanied by an incremental style of development. Each increment introduces some additional functionality on to the previous stage. Often, the new increment only adds a small feature so that we can fully test it and its effect on the existing system and its architecture. Each iteration needs to be accompanied by an objective that can be checked. Otherwise, there is a danger of the process degenerating into undisciplined hacking. An iterative approach is further enhanced when the customer is closely involved in the system development. Each new iteration can be presented to the customer to obtain feedback and to ensure his active participation throughout the project. 1.2 Using the UML The next chapter presents a detailed discussion of the UML. Here, we simply consolidate our earlier discussions by considering the more important elements of an object-oriented software system. This will act as an introduction to the more detailed discussions that follow.
If you looking for unlimited one inclusive web hosting plan please check cheap web hosting website.