Huazhong power grid project log: Minutes of the rational version 7.0 Technology Conference

1.: RMC

2. project portfolio: from the financial investment portfolio of Wall Street (portfolio) 3. field: Project/Program/portfolio3p project combination. The model does not mean a program. It means a large project and a change. 4. demand and System Analysis static analysis: code-level-such as dynamic analysis in RSA (Code Review): dynamic, code coverage, such as application server program servlet system-level analysis: automated tool performance analysis: concurrency performance tests should be considered, mainly for web5. Design and Construction 6. changes and configuration management changes are broadly defined as requirements, new improvement requests, bugs, and changes. Project managers and other roles need to consider and assign work based on changes -- form documents -- form versions -- generate different versions -- need Configuration Management! 7. Why not use rose when using RSA? A) rose does not support this standard and is only familiar with uml1.4uml2b) MDA development = model-driven software development model codec) Workload estimation: cocomo ⅱ d) tranteformatione) eclipse development tool integration F) whether to reuse the software asset specification. Patterm Design Pattern rasg) Cultural Support 8. Code can be made, Rad is a part of RSA. Built-in wasrsa9. automated documentation. Generate a document template based on the data in requesitepro. Benefits. If the data source changes, the document also changes. Soda (software of docutment authertion) 10. demand management a) current power situation: I. based on the document, requirement Survey II. information collection, Requirement Analysis Report III. summary design IV. maintain consistency. How to ensure consistency. V. Functional Perspective VI. design document VII. Automated Document generation tool VIII. How to see different changes IX. Data planning, similar to changes in CA Erwin X. Data planning. B): when using use case, the premise of using the demand questionnaire form is that you must have business logic capabilities. Such communication is based on job position and Demand Tracking. Many requirements from RD collection

How to filter requirements

Use the CQ change management platform to collect customer requirements

Use the modeling tools WBI, rose xde, RSM, and RSA to use an organic combination of the model (Use Case model) and the document to accurately describe the requirement Demo:

Business Requirements

Business features

Requesitepro provides different application interfaces:

MS word interface language. use requisitepro: requirement type, document type, attribute, contact, priority, source, stability, use case, supplemental conventions, outline design documents, detailed design documents, and tracking design documents. B. customer requirements, use cases, summary design, and supplementary provisions C. define the customer requirement document Suffix of the customer requirement questionnaire: CRD. define the use case e. define the outline design for the summary design document des. f. add attributes such as priority, source, stability, risks, and owner (you can change the name directly) g. import business documents in the fles menu to form the database documents imported to RQ. changed the document -- requirements in RQ have also changed === automatic synchronization I. method. wasexv6 is embedded in RQ: RWP. Later dB, webj. To handle changes, we need to create a view to reflect changes in the view. A) Do you have the permission settings such as CC public/parivate? Take offlineb) Can the modified comence be set to mandatory or not. C) whether multiple users make changes. No. D) install DB2 conflicts, port issues, and jdbce) secondary development issues. F) Rada is used for database modeling, similar to Erwin and new products. G) Is there a conflict with was installation? Port problem: Port 9060. 11. visual modeling a) when to use visual modeling I. communication and collaboration. language lb. graphical MC. communication between us and Unified Communication u ii. change III. normalization IV. management complexity. because of the complexity, we need to increase the Abstraction Level and height. B. Complex to simple v. Reuse A. File, header file HB., library FUNCTION libc. design mode d. frameworksa) How can the team quickly understand existing implementations or frameworks? Umlb) related training dev475: ooadc) can be deduced and formulated. OOAD

Pmuc

12. RSA

Requirement case

OOAD.

 

 

System definition

Analysis and Design 13. It is recommended to install the RUP/RMC Based on the role to collect the relevant presentation. We recommend that you copy the media and introduction documents of Ningde army RMC. 14. RSA demonstrates how to implement business use cases. It focuses on the relationship between entities and uses ca bpwin. Use RSA business model with business use cases as the core. The business use case comes from the business needs of the customer, and the business process is included. The entity has different lifecycles and States. How to describe the process in different stages. Try to implement the business process. Compile an effective use case to define the one-to-many and many-to-many relationships between object entities in a process based on the requirements of business processes. 15. The process of describing the meaning of drawing. In Huazhong electric power, data planning aims to generate business entities and form entity models in a certain business field. Abstract Based on the business field. 16. entity models are divided into layers. Data planning must do this !!! 17. What is the intersection of data analysis and modeling? Resolve the conflict. The sub-system/package/Steamed Stuffed Bun system focuses more on the nuances of 8 systems, one system and one package.

System

 

Function module

8 different systems

Subsystem

This concept is similar to the Mode Decomposition !!!! Workpiece-component

At the same time, a data dictionary is formed. This result not only includes the entity model, but also avoids data dictionary analysis and creates high-level views. Business Vision: Why is this project, Business Guide, and template. From the entity model to the vocabulary, we need to solve the iteration process and define the data expression specification. 18. How to define a business model, including attributes, methods, and application layers. The paradigm is not concerned with application design. You need to pay attention to the parameters in the iteration and check whether the object class is in the state. A state machine is required. 19. Find the automation part, extract the automation part to extract the use case, and then perform analysis. Generate the use case model and use it for requirements-related things. ---- Generate a view, which is a system view rather than a business view. 20. As is-to be = requirement analysis process. 21. What do we do after the use case model? A) the use case model consists of two use cases and documents, which can be linkb. There are two types of graphs: Static and Dynamic umlc.) The first thing to do after the use case model is: architecture Analysis d) extract key abstractions before Architecture Analysis. Extract entity Class E) and then perform Architecture Analysis. First, design the style. B/S, C/S, 3-laysf) and then perform case analysis. The case analysis focuses on functional analysis and other non-functional analysis, such as where the database exists? Data Reading Speed? What architecture mode and design mode are used. G) use case analysis-extract our analysis class. H) Time Sequence diagram. Generation method to generate attributes. I) Case Analysis-case design J) generation subsystem/generation interfacek) if the previous subsystem is generated, subsystem analysis is required. Also generate the interface l) static structure diagram, class diagram m) state machine, and extract the above. N) Select the persistence mechanism and deploy the deployment graph. O) mode: Collaboration diagram/class diagram with parameters. 22. Soda generate the relevant document a) display the relevant template B) display the model requirements for connecting to the server. C) PDF integration. 23. RSA instance description A) switch to the demand perspective, open the demand browser, open the demand analysis rsab) establish business analysis or system analysis. C) Establish a contract payment subsystem d) Create a case View package e) drag the Left demand diagram to the right of the use case diagram f) after the use case is completed, create an activity diagram g) Create a collaboration diagram H) create a mainstream/selected stream to generate user information. I) Use Case implementation j) Use Case implementation tracking diagram 24. the soda template consists of two parts. Static document: the original doc document. There is also a dynamic part: the dynamic part is connected to a domain source, such as the RSA source and Rose source. These dynamic parts are soda commands. When generating documents, collect these dynamic things to form documents. There are two ways to generate a file and a report. The report is static and is not associated with the database. Documents are dynamic and associated with databases. Such changes are the source of your domain.

Build

Test

Design

Requirement

Soda

25.

25. To what extent is modeling good? A) can clearly describe the business, even if it is good B) there is no definite pattern 26. The process we extract when planning data. Package package hierarchical tree of package. Divided by functional modules. 27. Because the business entity has a life cycle, you need to use the example diagram, activity diagram, status diagram (time, change), and class diagram in business modeling. 28. The status chart belongs to a certain entity. 29. Data Models only have class diagrams. Business System Subsystem use case diagram activity diagram function module class diagram use cases implement business entities | ---- system | ------ subsystem | ------ function module data dictionary (Vocabulary) | ------ key abstraction (commonly used word keywords) install RSA