[Object-Oriented Analysis and Design] Reading Notes 4-Part 2 methods

Chapter 2 describes the representation-UML diagram, which is divided into two categories: the structure diagram describing the static structure and the behavior diagram describing the dynamic behavior. In this case, we can find out how to use the corresponding notation in practice. These representations do not remain unchanged once they are made. Instead, they need to go through the evolution of conceptual, logical, and physical models and use different models at different stages of project development. 

Question: 1. Do we need to draw so many representations in practice?

2. What representations should be used at different stages of project development.

For question 1, the answer is that you don't need to use all the representations. Just like the process theory of RUP, it strives to be a general theory, but in the actual project process, it is often a subset of theory. Question 2 will be analyzed in combination with actual practice.

Chapter 2 describes the software development process and describes the features of a successful project:Strong Architecture Vision(In essence, a good architecture should be object-oriented and composed of components );Well-managed application iteration and incremental development lifecycle. Pursuing a rational development process, understanding the key aspects of different development processes, and advocating the core concept is the key to understanding different practical processes. Processes are defined as macro and micro processes. Different from macro processes, they focus on the overall software development lifecycle, while micro processes focus on specific analysis and design technologies. We use the life cycle of RUP as the basic. For more information, see.

macro process, the macro process determines that the system will get the product system through continuous optimization in an evolutionary manner. The process can be described in two dimensions: Content and practice-what to do and when to do. The content dimension describes roles, tasks, and work products. You can also choose subject (requirements, analysis and design, implementation, testing, deployment + project management, configuration and change management, and environment) to describe and logically group the content. The time dimension describes the lifecycle of the process, from milestone (the scope is understood, the architecture is stable, the system is ready for end user testing, and the system is ready for deployment) , phase (initial, fine and iteration .

Micro process (that is, macroAnalysis and DesignFor example, if we describe the macro process from two dimensions, we will also describe the micro process from two key dimensions, that isAbstraction LevelAndContent(Activities and artifacts ). In the microscopic process, the traditional analysis and design stages are intentionally blurred. Instead, they are abstracted at different levels to Form Continuous spectra. The analysis focuses on behaviors rather than forms. Some elements are created during design, which provide the behaviors required by the analysis elements. The process of determining the architecture and components is of guiding significance for micro-iteration. Components have a lower abstraction level than architecture. SpecificActivityThis includes determining the collaboration between elements, determining the relationship between elements, and determining the semantics between elements. Corresponding artifacts are generated for each round of activity.

Chapter 2 focuses on object-oriented development practices, such as personnel management, release management, and quality assurance. These theme topics may be boring for technicians, but they are a reality that must be met to successfully build complex software systems.

1. Risk Management and Planning

2. Staffing. Object-oriented resource configuration is generally less than the traditional method, and a lot of work is not a big bang. The project has three main roles: Project Architect (complex evolution and Maintenance System Architecture), component Supervisor (initial abstraction of the project, the component supervisor is the final owner of a mechanism related to class aggregation, and is also responsible for testing and releasing the system during system evolution) and application engineers (usually fulfill one or two responsibilities ). In larger projects, different development roles are also required to complete the work.

3.Software Configuration Management (SCM) is a technology that identifies, organizes, and controls modifications. Software Configuration Management is applied throughout the software engineering process. Software Configuration Management can be refined into three aspects: version control, change control, and process support.

4. Establish a Reuse System.

...