Seventh jobs
1. System FIG sequence
2. Modeling Exercises
FIG Example 2.1 using
2.2 Activity Diagram
2.3 domain model
2.4 Status FIG.
S = {register, log in to view the notes list, select the format, edit notes}
E = {open to know notes, failed to register, complete the registration, cancellation of registration, login fails, the login is successful, cancel the registration, the new notes, quit, select the format, save}
2.5 System operation sequence diagram and the protocol
System FIG sequence:
Operating agreement:
Contract CO1: regist
Contract CO2: login
- Operation: login(username: string, password: string)
- Cross References: Use Cases: Make Notes
- Preconditions: There is a corresponding account
- Postconditions: none
Contract CO3: addNote
- Operation: addNote(title: string, date: Date, content: content)
- Cross References: Use Cases: Make Notes
- Preconditions: User has signed in
- Postconditions:
- A note instance ni was created
- ni was associated with the current account
Contract CO4: editNote
- Operation: editNote(noteId: noteId)
- Cross References: Use Cases: Make Notes
- Preconditions: User has signed in
- Postconditions: none
Contract CO5: saveEdit
- Operation: saveEdit(noteId: noteId, content: content)
- Cross References: Use Cases: Make Notes
- Preconditions: User has signed in
- Postconditions:
- note[noteId].content was changed
3. Evaluation team members do not answer
The theme of our group of
modelers answer
Evaluation:
- With the use of the embodiment of FIG embodiment needs a verb begin, in FIG modeler does not meet this requirement with multiple
- Activity diagrams did not draw a branch node
- 领域图中,收支类型、备注信息等都可以作为收支条目的属性
上一篇
原文:大专栏 Homework 7