Introduction to OOAD (Object-Oriented Analysis and Design)
1. OOAD method Theory Answer: 1) Object-oriented is a system modeling technology; 2) describe the relationship between the system as many interactions; 3) Objects in the system are organized; 4) oo Methodology is composed of the following three parts: one process. A symbol. A series of rules 2. In an OOAD software development process, we have to complete two different work: A: 1) Analysis stage we mainly:. Create a clear business The view of the problem; outline the task that the system must perform;. Establish a general vocabulary described by business issues; outline the best solution for business issues. 2) Design stage we mainly:. Solve business issues;. Define "how" instead "what"; introducing the support element for system working;. Define system implementation strategy.
3. Object: 1) is a single, uniquely confirmed entity or project; 2) As an object-oriented building block is used; 3) There is identity, data and behavior; 4) may be simple or complex; 5) It is real or imagined; 6) There is an attribute and operation; 7) is a dynamic instance of a class; 4. Category: A number of abstractions of multiple identical objects, objects create self
5. Amazing: 1) Abstract (abstraction):. Ignore the details of the details, handle objects or entities; simplify features and information; help users and object interactions; 2) ENCAPSULATION: hide Object data; handle two views handle each object: a. External view: Display an object what to do; b. Internal view: Show object how to complete its task; 3) Association. Mode inter-object interaction An object uses another object or another object, which is associated with each other. 4) AGGREGATION. Define an object is an component of another object; it is a relatively strong association; it can be confirmed by "HAS A" relationship. A car has a wheel, a seat, and a door, which is an integral part of a car. If you remove any part of the time, the car has no corresponding function, but it is still a car. 5) Composition. An object contains another object ;. is the strongest association form;. Confirmation can be confirmed through the "Contain" relationship. Assume that the part does not exist, the object does not exist. 6) Inheritance (inherited). It is a mechanism to define a new class according to the existing class;. Confirmation can be confirmed by "IS A" or "Kind of" relationship; allowing you to organize related classes, so these classes can be managed together And reuse. 7) Cohesion and Coupling (coupled). Cohesion: One or set of measures for a single function contribute to the system; COUPLING: Two or more types of metrics to contact tightness; 8) Polymorphism (Polymorphosity). Different objects completed the same semantic results; based on inheritance;. The implementation of polymorphism is dependent on its objects; for example: football - throw - need two hands, tennis - throw - only one Only hands, it is also throwing, there are different implementations. When you bring different balls to a child, he knows that it is a hand or two hands. Children know the polymorphism.
6. Development process preview: 1) Traditional development process: waterfall development: demand -> analysis -> design -> implementation -> test. Each step is completed and documentation will enter the next stage. It is difficult to return to the previous stage in the later stage. The members of the project team spend a lot of time and effort to ensure that it is correct. The symbols and terms used in each phase change. Although the completed software is correct, it is very related to the business logic it. 2) OOAD development process. Typical processing method is to use a project as a series of small items; UML (Unified Modeling Language) is a symbol, not a processing process; USDP (Unified Software Development Process) is an iterative increment The USDP and RUP (Rational Unified Process) are all popular OOAD processes. 7. Iterative Incremental Project Life Cycle Answer: 1) "Iteration" refers to every step in the life cycle; 2) The result of iteration is a step growth completed throughout the project function; 3) In each iteration, You should:. Select and analyze the relevant use case; use the selected architecture to create a design;. Use the component to implement the design;. Test component satisfies the use case.
8. Iterative Incremental Life Cycle The main phase Answer: 1) Inception phase:. This stage is concentrated in: a. Start project; b. Establish business principles for this project; c. Define a business problem; d. Identify potential risks; e. Define the scope of better understanding of problems; f. Creating documents for business issues. Each cycle includes one to more repetitions, and the completion result of each stage is a milestone. 2) ElaBoration stage:. In this stage, the growth is concentrated in: a. High level analysis and design; b. Establish a baseline of a architecture system for the project; c. Monitor potential risks; d. Create a project objective Construction plan; 3) The construction phase:. The growth of this stage is concentrated in software projects; 4) The Transition phase:. The growth of this phase is: a. Publish products to customers; B Complete BETA test; c. Implement performance adjustment, user training, and acceptance test. 9. Working steps during the stage: 1) Each stage consists of the following five working steps:. Requirements. Analysis. Design. Implementation. Test 2) Different repetitions are different to each work step; 3) Early Repeatedly covered the first working step in the depth, and later overlays the last work steps over the depth. 4) 8/2 Principle: If you have completed 80%, you can enter the next repetition.
10. Repeated and work steps: 1) In each repetition process, you can include any one of the five working steps as required. 2) Early repetition processes focus on the proceeding steps, and later repetition processes focus on post-releared work steps. 3) When you find that some errors in the earlier work steps should be modified, you can:. Continue and correct them in the next repetition process; continue and add a new repetitive process correction problem; if the time allows, return to the current Repeat and correct this problem. 4) Different repeated execution each work step is different. 11. Benefits of iterative incremental life cycle Answer: 1) Reduce costs; 2) A better guarantee for project progress; 3) Faster development in development teams; 4) Adaptation to user needs;
UML (Unified Modeling Language)
1. UML definition Answer: 1) UML is a graphical language for:. Description;. Construction; naked observation;. Documentation system prototype; 2) In the analysis phase, you create class diagrams to help you understand business concept (Nothing has not been implemented); 3) In the construction phase, we increase additional details for the same class diagram - realize business details;
2. The relationship between UML and blueprint Answer: Develop OOAD program --uml build room - blueprint
3. UML Graphics Answer: 1) Static Model: The basic structure of the software system you are modeling; 2) Dynamic model: emphasizes the behavior of the system;
4. Static model Answer: 1) Construction and documentation of a system static aspect; 2) Reflecting a basic, stable framework; 3) Creating a representative of the main elements; 4) Compose by the following graphics: use case Figure. Class diagram. Object map. Component, deployment diagram
5. Dynamic dramatically: 1) Build a graphic of the display system behavior; 2) consist of the following graphics: time chart. Collaboration map. State diagram. Activity diagram
6. Use example: 1) Show no one or any system and its characteristics; 2) A user using the characteristics of the example is called "ACTORS"; 3) Use an elliptical expression; 4) Easy to model, use case The figure needs to distinguish the order in order;
7. Category: 1) Represents a series of objects containing normal attributes and features; 2) Structured graphs show a series of collaboration and relationships between classes, interfaces, objects; 3) by one to more describe the following The rectangle of information:. Type (class name). Optional properties. Operation section
8. Objective A: 1) Represents a clear object 2) Structured graphic shows a series of objects and the relationship between them
9. Component Agree: Displays the relationship between software components
10. Deployment A: Displays physical devices that can be used to deploy software applications
11. Time series: 1) Messages that have occurred in different objects; 2) emphasize the time order of the message
12. Collaboration A: 1) Displayed collaboration between objects during the message period; 2) emphasize the structured organization of sending and receiving messages;
13. Status conversion graphics: Emphasizing the order of object behavior
14. Activity Agic: 1) Describe a process of activities to another one, emphasizing a process to another.
15. Symbols of the package: 1) means a way to organize the project; 2) Top-domain space commonly used to control classes; 3) Using package organization classes, software components, hardware components, other packages, and you in UML Anything related to the model
2004-11-5 Friday Yin
Demand and initialization analysis
1. Start development process Answer: 1) Analyze the initial workflow; 2) Collect information; 3) Creating a question of a question; 4) Creating an example; 5) Introduction components and deployment diagrams; 2. Collect information Answer: You can The information is collected in many resources including:. User's initialization demand details. Industry experts. Customers and users. Managers. Market. Previous similar projects
3. Avoid habitual hypothesis: 1) You must avoid habitual assumptions, including:. Users are true, developers are the clearest. The demand is static. I can establish a correct solution 2) Remember the project The development and customer needs are changed. 3) In order to avoid these assumptions, we should:. Clear user needs. Make sure your model can adapt to changing needs. Make sure you can modify your model 4. Industry expert A: 1) Refers to an expert in a particular business 2) can be roughly divided into:. General industry experts. Specific application industry experts and current business sector experts. Similar business sector experts 3) There is no industry expert, from other fields abstract general elements difficult
5. Question Answer: 1) Documentation clearly describes customer and system requirements? 2) User Enter For Documents Very important 3) Using Customer Familiar Language Vocabulary 4) Syringe Clear, Unexpected 5) Detailed Description Problem 2) Detailed Description Problem 8) The problem declaration provides constraints regarding business background, scope, and computer terms. It is used as a basis for confirming the scope of the problem. 6. Object and class candidates: 1) Determine from the question declaration 2) Give the noun phrase in the question declaration to decline the line to build objects and class selection list 3) In the next analysis phase, you need Determine the list of objects and classes you need in your system
7. Data Dictionary A: 1) Document 2) Document 2) Document 2) Pass and User Communication Accumulation Proceed 3) Applying for the entire project and system 4) will continue to join new term during the entire project 5) Help Elimination Ambiguity 6) It is important to use 7) Data Dictionary for all project groups. At this time, it is both a business document and a system document.
8. Creating an example: 1) A use case is a graphical expression of user and system interaction; 2) is a tool for defining and understanding system requirements and background; 3) is a simple impression of any system. When you collect all impressions in a piece, you have the entire description of the system; 4) The graphic is specifically manifested as an ellipse of the solid line.
9. Include "and" Extend "Answer in the example: 1)" Include "is set in the included relationship, and you must use another module before completing a module; 2)" extend "is concentrated in extended relationships, may or Maybe not based on a module, not mandatory;
10. The plot hypothesis in the case: 1) Use examples to display the software from the user's angle. There may be more than one way to complete a specified function. 2) A example of a hypothetical example - a logical path from the beginning to the end. 3) The plot hypothesis does not include conditional declarations - because they describe one of the plurality of possible paths of the user. 4) All plot assumptions start from the same way, but the result is different. 5) One of the successful or unsuccessful paths in use - in an ATM, you must consider that some plots such as the user's personal identity number is not ordered. 11. Use examples: 1) Summary of each use case 2) The use case form is not UML content, but it is recommended to complete it. 3) In this form, include the following items: use case name. Participant. Priority. State. Extended content section. Prerequisites / hypothesis: Submitted conditions. Event stream. Optional path. Execution. Frequency 12. Event map A: 1) After creating an example, you can use graphical instructions or workflows 2) graphically graphically all use of the case of falsehood plots 3) display activity, process or workflow
13. Risk Assessment: 1) It is necessary to risk assessment of the project 2) Use case can be the starting point of risk assessment 3) High-risk use cases should be developed in early iterations 4) The risk can appear in the following:. Risk. Technical risks. Skill risk. Resource risk. Policy risks
14. Demand risk Answer: 1) Demand risk refers to customer requirements 2) You should make all users and managers working in the system to participate
15. Technical risk A: Remember that the proven technology is less risky than the unconfirmed technology
16. Skill Risk Answer: Confident, you have all the skills you need.
17. Resources and Policy Risk Answers: 1) Resource Risk Refers to Excessive Time and Fund Budget 2) Political Risk refers to conflicts with current political rules
18. Package A: 1) There is a symbol in the UML to package any logic related UML element (class, object, use case, etc.); 2) Like Java, the related class is organized into a different package; 3) This symbol Like a folder icon; 4) helps reduce complexity; 5) There is a dependency between the inter-package; 6) Package helps: View the big picture without too many details; check the separate part of the independent;. Create a part A small portion;. Display the dependence between components; component map shows the form of physical organization, can be a class file, Java source file, jar file, package, shared library, object code, RDB, etc. in Java, Shared library, object code, RDB, etc. When a component changes, it can affect other-dependencies; component should have a good interface so you can use other components that implement the interface to replace it.
19. Deployment Diagram: 1) The physical relationship between hardware components is displayed; 2) Each symbol represents some hardware devices: server, workstation, personal PC, sensor, clock, telephone switch, etc. 3) When you get information, you can add and correct at any stage. 4) The connection between the symbols is displayed along with the protocol.
System object and class analysis
1. Analysis of the analysis: 1) What must be done in the system; 2) Avoid the problem of describing and implementing; 3) Focus on the system's components; 4) What is the correct function to ensure the correct functionality ; 5) After the analysis phase, after the demand collection phase and the use case phase, before the system design phase; 6) When it is a class and object, you should answer the following questions:. What object constitutes this system? What is possible Class? What is the responsibility of each object or class? How does the object and the class associate? 7) Remember to add all new projects to the data dictionary; 2. Micropline Answer: 1) When you define an object of the constituent system, you should create a list of system function objects; 2) The object is called Object Hou Selection; 3) Then you can prepare a sub-list for the most important objects in this list; 4) The keyword represents the main or first object in the system;
3. Use UML to indicate objects and classes: 1) The object model shows the statistical view of the logic and theft; 2) The object model has two pictures:. Class diagram: Show you must create a class required to create a system. You can create many objects with a class when you are running. Class diagrams must have a possible relationship between the display. Object map: Represents real objects in the system, describes the relationships outside of specific cases. 3) You can use the primary key to create class diagrams and object maps. 4) Class maps are updated and corrected throughout the analysis phase.
4. Properties and Method Answers: 1) Objects contain attributes of the defined object state; 2) The method defines the operations that the object can perform; 3) So the classes must define these properties and methods; 4) Before class execution, you must define All attributes and methods; 5), but many attributes and methods know the design phase, plus all you can add first; 6) Attributes and methods in the design phase are sufficient, but their types and parameters are not enough.
5. Properties and Method Answer: Two types of properties: normal property: is a variable or constant that exists in an object. A normal attribute will store some meaningful values in the object. Derivative attribute: Not stored in the system, calculated by other information in the system.
6. Joint and Links: 1) Joint - For class. The relationship is expressed in line with straight lines in the specification;. The line can be level or vertical; can be given to a logical name on the relationship Relationship; 2) Link - For objects. Refers to the relationship between two objects in the object map;
7. Joint and Diversity Answers: 1) Diversity shows the possibility of object contacts in a class object and another class; 2) In the class diagram, there is only one rectangle of each class, so the coupling will determine a class. How many objects are linked to another class object; 3) The end of the coupling line has a tag; 8. Validity of diversity: 1) 2: Just two; 2) *: 0 to multiple; 3) 5..15 : 5 to 15; 4) 2, 4, 6: 2, 4, 6; 5) 10 .. *: At least 10; 6) 0..10: Up to 10;
9. Complex joints: 1) Diversity tag "*" appears at both ends of the coupling; 2) After all the coupling in the class map, after the diversity is assigned, it is time to re-examine them and try to solve the complex join. . A coupling class or conformity can be used.
10. Database (similar to the database center index table) A: 1) This means that the coupling itself must be encoded as a class, this class has an attribute that resolves conflicts; 2) This technology is used in the analysis stage to solve many more relationship;
11. Conditional coupling: 1) Solve multiple problems by using attribute values; 2) Assign a unique attribute value;
