Create a Google document and a Miro board for other members to contribute sequence diagrams.
Leave feedback on people's work as they complete it to ensure that all contributions are consistent with one another.
Deliverable Requirements:
Sequence Diagrams (/35)
Pick 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.
About 7 - 15 analysis sequence diagrams plus 3 -7 design sequence diagrams.
If the number of analysis/design sequence diagrams is below 7 and/or 3 respectively, deduct -3 points per each. For example, if there are only 5 analysis SD, deduct -6 points.
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.
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
12 months ago
Create a Google document and a Miro board for other members to contribute sequence diagrams. Leave feedback on people's work as they complete it to ensure that all contributions are consistent with one another.
Deliverable Requirements: Sequence Diagrams (/35)
Pick 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.
About 7 - 15 analysis sequence diagrams plus 3 -7 design sequence diagrams.
If the number of analysis/design sequence diagrams is below 7 and/or 3 respectively, deduct -3 points per each. For example, if there are only 5 analysis SD, deduct -6 points.
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.
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.