|Complete a short survey and get free Brand Name samples from QualityHealth.com!|
Some use case diagram
1. The relationship between use cases; use cases and the relationship between Actor; Actor relationship between
a. Participants are located outside the system boundary, the participants to complete a use case. Actor and two-way between the use case the communication mechanism. Pay system on the external Pos computer system interface between the systems should be considered, not the Actor.
b. there is no communication between the use case relationships. That a complete operation. Although the use case does not exist between communication relationship, but considering the use cases Include case, extracted from the sub-use cases there must be some return value, that is, use cases either failed or successful outcome value for the primary use case to the judge for further action .
for Example: in the reserve a seat and check the seat details of two between use cases, reserve a seat Include a check seat details of the use case, then reserve a seat on the Executive Check-seat use cases, check the seating of the use case there must be a return to the results of value for the scheduled seats to deal with.
c. Include the use cases are more events in the stream exist, is extracted in the development process, non-business use cases extracted from the build process, separately does not make sense. Customers generally do not care. The nature of a check should be more use cases.
d.Extend use cases and the relationship between the base use case. the base use case is independent of the expansion of existing use cases, extended use case is independent of the base use case exists. Extended event flow is defined by the user. Somewhat similar to the program’s ease of use features. For example, when doing document editing services to provide the function of a dictionary.
c. participants are users outside the system, only a generalization of the relationship between participants and can not communicate. The existence of such a situation, the role of A after the operation sends a notification to the role of B, on the surface the relationship between the communication should be completed a role in A single use case, the role of B also completed a separate use case.
d. use case, then if there are size, depending on business processes and division of tasks. User through the use case is a valuable operation, is a completion of the operation.
e. system operations (CRUD) and the business name meet, is a very dangerous signal. At this point the analysis of use cases have adopted the latter part of the development process of thinking, a way should be taken are: first, after the person’s way of taking the appropriate thing finished, complete their connections. It should be said at this time CRUD operations will be assigned to specific business scenarios.
Areas of data requirements
a. field (attribute) information
The format and rules of the field (data type), calculation rules (non-direct input fields derived property, by the expression data representation); structure rules (the composition and format of data)
b. the demand for the use case of organizational behavior
Flow of events, related requirements and functional point of interface prototypes, rules and constraints
a. into behavior (functions, business) rules, structure (data) rules, the interface rules
b. rules of conduct: and the business logic, business process-related rules. More than 500 yuan XXXX.
c. structural rules (rule data): and business entities, attributes, derived attributes related rules. Maximum length of SMS XXX, sales performance is valid in the month month paid the total amount of all orders together.
d. Interface rules: the rules and user interface related. Different colors show different levels.
e. the rules of conduct be regarded as macro-rules, structure, interface rules be micro-rules.
f. level of sub-rule exists. Is actually divided into global and local rules. Rules of different levels of organization structure, hierarchy is divided into areas of influence between classes, field classes, the field. Areas between classes: a single physical package and the physical examination can be components of the single medical examination but the composition and the physical examination can not be a single project The physical examination included package items repeat. After the domain model
Within the field of class: Package price is not derived medical field, but in line with the rules a little: physical package price “= Price * 0.75 a variety of medical items on the field. Field: In this use case to show only the name of medical packages and prices.
After the computer to modify the process to consider changes caused by, considering the history of the problem (historical data query, data, etc.).
Sorry, the comment form is closed at this time.