"UML and Mode Applications" (US) Craig Larman Applying Uml and Patterns (An Introduction To Object-Oriented Analysis and Design)
It started in the 2 month ago, it took about 1 month to read, because it was still there. So I want to sum up some things to write down, and I don't think after reading.
The book is based on the development of a POS retail system, in detail the entire process of system analysis, design, and coding. With example the wizard, the process is the clue, and the number of knowledge-based integration is integrated in both the book is the organization. It is also the biggest feature of the book. The following is a summary of the points to summarize:
Point 1: Instance:
The POS machine terminal system involved in the book should be a relatively simple system, but because the book is not implemented throughout the system, but only choose a representative point in each development phase, so make This system is simpler. However, as a book introduced by a method, this is enough. And through simple examples, profound truth is exactly the style of academic circles abroad. I think this is why many people like to see the original book.
Key 2: Methodology:
RUP is divided into four phases of the Inconception Colaboration Construction Transaction. Although the presentation has not been described in the book (or the author does not emphasize the methodological problem), the main development process (establishing conditions and its classification and scheduling and repetition) from the book ( Establish a conceptual model and identify associations and properties, establish a collaboration map and use mode to assign assignments, establish a class diagram and determine its properties, and the image to the code is displayed.) The entire contour of RUP is displayed.
Point 3: Analysis:
The most important principles of the analysis phase are unrelated to the implementation, which is very clear in the book. First, in addition to the final use of the Java implementation, there is no specific implementation technique involved in realization; second, some terms of the specific computer have been involved in the establishment of a class diagram stage. At this stage, especially when modeling the concept model of the system, the author avoids the term in the computer, and models in the real system.
System sequence diagram and contract. First of all, I didn't get into contact with these two documents. When I first saw this part, I felt that I didn't work too much, but as it slowly, an important role was fully reflected in the book. System sequence diagrams and contracts are tools for modeling system behavior at system level. Its role of individuals have the following two points: First, it is possible to help analysts have more clear understandings for system boundaries and system behavior; the second is the collaboration maps of these two documents (especially contracts) to the design phase. Further, it is the most important work of the design phase - the duties of the class.
Key 4: Design
The core of the design phase is the assignment of responsibilities. The Book introduced the Grasp mode group as a model assigned as a responsibility. This mode group contains the following modes: experts, creators, low polymers, high coupling, controllers, polymorphism, pure fiction, intermediaries, "do not speak with strangers". Although there are many modes, and their respective effects are different, but the principles of these patterns are not complicated. Expert mode and creator reflect the single principle of duties; low-degree, high-coupling, intermediaries, "do not talk to strangers", etc. reflect the principle of low polymerization and high coupling between the class; polymorphism, pure fiction Reflect the openness and closed principles of class behavior. Further, these modes, and the object-oriented principles embody the engineering idea - how to better implement software multiplexing.
Key 5: Development Process Summary
Plan: Understanding Demand -> Determination -> Case Classification and Time Scheduling -> Start a development cycle
Analysis: Establishing a Concept Model -> Fill the Association -> Fill the Properties -> Recording Terminology -> Establish System Sequence Drawings and Contract Design: Describe Real Users -> Establishing a Collaboration Map (Interaction) -> Use the GRASP mode to assign duties -> Judgment visibility -> Design Class Diagram -> Deployment
Construction: Design to the code -> Enter the next development cycle
