Notes on advanced requirement analysis UML modeling design mode

1. REQ-> HLR Analysis System-> ad design context, BOM, conception2.req-> LLR analysis module analysis-> dd design + coding feature, BRM, UC, ucd3.dd design-> 30 functions in the code structure design module-> class/sequence diagram design, reflection/Inheritance/interface/design mode/entity class/Abstraction/configuration file code structure design: design goals: correctness goals-> functional requirements goals: code structure can meet all business requirements non-functional requirements goals: reusability: Avoid code redundancy and scalability: meets all business functions <-> feature variability requirements security: encryption, identity authentication, authentication, authorization, XSS performance: Computing in seconds, memory cache code stability: after the code structure is designed, the code is restructured on average every month; category-> encapsulation class based on business + single responsibility 30 featrue-> 30 class featrue-> class/public/private methods do not need to design domain models based on business: entity Data UC-> key KPC functions-> Public method Interface Design/base class design/abstract class/reuse design/Inheritance/delegate 1. interface Design Principles:. used for module function exposure, mostly used for inter-Module B. the interface definition is pure virtual. All implementations must be individually implemented. avoid using the basic data type D. use the domain model [object data] e. use the business name f. the interface definition should be defined by its own module, and cannot be determined by the caller. If you want to add an autonomous finddata (ID) finddata (ID, date), add the Date Parsing g by the caller. the interface is minimized/the interface is single, and the interface is called through combination reuse. 2. the Design of basic classes and inheritance: Class: The most common form of basic classes. It is impossible to force the sub-classes to achieve personalized implementation abstract class: class inheritance code reuse, defining pure virtual interfaces: Unable to reuse code, inheritance tree, completely exposed to external inheritance and authorization/reuse design: code reuse Use Commission code reuse scalable design: 1. analysis of featrue variability, commonalities 2. design baseclass. The common definition is in the base class, and the variability is defined in the subclass by pure virtual. design the inheritance system/inheritance tree. 3. all callers and base classes cannot directly call subclass 4. through polymorphism, the base class is called to subclass 5. define the factory to complete the polymorphism process. 6. the multi-state business logic is defined in the XML file Dependency inversion principle: the caller should call the abstract or base class, instead of calling the Child class's replacement principle: Check whether the extensibility inheritance tree is a valid Class Division: information expert: business logic service data entity: save data entity end Creator: extensibility design factory administrator: All classes in the management module, Manager/cache data entity) Boundary class: interface implementation imp Interface Class: View Controller: Control Practice Principles of detailed design: 1. analyze featrue and BRM (activity diagram) 2. analyze detailed requirements 3. based on the core design principles [encapsulation + single responsibility principle, from featrue-> class division] 4. analyze detailed requirements-> define methods 5. analyze BRM-> inter-class relationship definition 6. according to the GRASP design principles, classes are divided into seven categories 7. analyze the feature variability. according to the variable feature, the inheritance base class is formed by analyzing the commonalities and characteristics. The feature forms a subclass and completes the inheritance tree design. 9. modifies the caller's base class based on the Dependency inversion principle 10. define factory + XML for extension Design 11. verify whether there is any risk in the call process of the inheritance tree based on the Lee's replacement principle. 12. reusability Design 13. analyze featrue one by one and provide external access. The interface is designed based on [interface design practices and minimum interface principles] 14. improved design through design patterns 15. complete the class diagram design 16. complete the sequence diagram (sequence diagram) design 17. conduct detailed design review between teams 18. form detailed design document 19. in the future, we should constantly monitor design changes, resulting in design reconstruction [using 72 Reconstruction Methods for scalability reconstruction] standardized creation design mode: Abstract Factory model: the prototype mode for generating classes without new: builder mode: Singleton single-instance mode: structural mode panel mode: encapsulation of complex processes can call the adapter mode across classes: for external organization encapsulation, it is not allowed to call the decorator mode across classes: For calling different cleaning methods according to the configuration file proxy mode: a typical webserver call

Notes on advanced requirement analysis UML modeling design mode