Convert the two use case descriptions you worked on for deliverable 2 into Scenario Tables, then Sequence Diagrams.
Sequence Diagram Requirements:
ick a few of the main features of your application and draw the sequence diagrams based on those. Prioritize drawing ones with the highest priority.
For each of the sequence diagrams, start by writing a table describing the steps/messages, with columns for subject, subject action (a verb), parameters, and object acted upon. See class/slides for more information and examples.
See this example of sequence diagrams. Analysis sequence diagrams can be less formal (not showing method calls and formal types for arguments). Design sequence diagrams show message arguments and types (e.g. function call arguments and types), as covered in the class lecture.
https://docs.google.com/document/d/16aZE4B08wakokbiZmZOn2_nkfWlb59rq
Each diagram needs to have correct variables, methods, and parameters.
For any mistake, deduct -2 points.
For each diagram you need to write a description of the steps.
For each description that is missing, deduct -5 points.
For each incomplete description, deduct -2.5 points.
Dymonkeys
commented
1 year ago
Convert the two use case descriptions you worked on for deliverable 2 into Scenario Tables, then Sequence Diagrams.
Sequence Diagram Requirements: ick a few of the main features of your application and draw the sequence diagrams based on those. Prioritize drawing ones with the highest priority.
For each of the sequence diagrams, start by writing a table describing the steps/messages, with columns for subject, subject action (a verb), parameters, and object acted upon. See class/slides for more information and examples.
See this example of sequence diagrams. Analysis sequence diagrams can be less formal (not showing method calls and formal types for arguments). Design sequence diagrams show message arguments and types (e.g. function call arguments and types), as covered in the class lecture. https://docs.google.com/document/d/16aZE4B08wakokbiZmZOn2_nkfWlb59rq
Each diagram needs to have correct variables, methods, and parameters. For any mistake, deduct -2 points.
For each diagram you need to write a description of the steps. For each description that is missing, deduct -5 points. For each incomplete description, deduct -2.5 points.