Software requirements and architecture training (2) Functional Model

PMT-II

Function Model

Deployment model

 

1. Maintain separation of concerns

High Cohesion and low coupling

2. Component Classification

Business process component: Business Process Model

Business Service Components: Methods

Technical components: struts, etc.

System software components:

Ø hardware components:

It also includes their responsibilities and dependencies.

Component Composition System.

A component is not a component in. Net/EJB in development.

3. components are combined into subsystems and combined into systems

4. How do I draw a component chart ??? Rose. Component diagram and class association. Multiple classes implement one component.

5. Why do we need to make a component model?

Big projects must be implemented.

 

6. In terms of functions, the focus is to map businesses to components.

7. three steps:

Identification component,

Component specification: The component meets the preconditions and can be started. The component ends normally if the prerequisite is met.

Component conversion:

8. Post Condition

9. pdei

10. Correspondence between the component trilogy and the RUP: initial (identification), refinement (specification), construction (conversion), and handover

11. Components

L TDD \ UDD \ DDD (mainly based on entity model, business model, similar to IRP)

L DCI model (similar to MVC, corresponding to each field)

L four-color model method (used for bidding): Generally, only four graphs are supported.

12. Component Reuse: The smallest component is a class.

13. white box testing methods:

Path overwrite method (loop, overwrite all)

Recognition:

14. Identify components and draw an interaction diagram (sequence diagram): How components interact.

15. High Cohesion: as many layers as possible.

16. Loose coupling: how to judge and look at layers. The fewer layers, the better.

17. Isolation: as many layers as possible, there is no relationship between some layers.

Conventions:

18. component specification: it refers to the call relationship between components (external interfaces provided), and hierarchical interface identification.

Conversion:

19. 4A: account, authorization, verification, and audit. Member Management/customer management module.

20. The core of component Modeling: Build the relationship between components, not inside the components.

21. components can be technical and business.

Run Model

1. functional model requirement-oriented component (componet), from usecase analysis.

2. Non-functional requirement-oriented Running Model

3. Several Concepts

L component into du

L release multiple du nodes to the node (the tape library is also a node)

L put node into location

4. Capacity Planning

L considering the capacity of existing data (structured and non-structured), that is, capacity planning.

Method: Estimate based on each component and consider the values in each component (d in pedi, that is, data ).

L structured data should be taken into account in temporary space

L 30% redundancy is reserved

5. Om: select the product (what product to use. Complete the OM during the outline design.

Reliability refers to try catch.

Scalability is the same as flexibility, that is, parameterization is achieved: The call between components must be flexible (XML ).

6. The architecture is irrelevant to the product and related to the technology.

7. CS has four types of components: presentation, execution, data, and installation.

8. VM and VMC (tools ). Virtual server environment.

9. Virtual Server Environment + file server environment: Online Editing of office, data must be uploaded to the server, and office is only edited.

10. For interface components, only E (executed)

11. Du: Deployment Unit, which is divided into PDU Edu IDU Ddu

12. ALOM: application login of Model

13. Logic OM: considering technologies, products, and hardware

14. SLA: requirements and expectations of the business department for the IT department.

15. For the data performance model, contact DBA

16. LL: logic location, logical location

17. a1: application loginc node.

18. E: refers to business processing rather than running.

19. Te: Technology execution

20. ALOM -- Lom -- and POM to guide the subsequent design.

21. physic node: PD

22. In ALM: Du is distributed to node, all of which are business aspects.

23. LM: The du node is less than the node, which involves technical products.

24,