Software Engineering I
Activity – Use Case diagrams
– Computer Science and Software Engineering Department
Copyright By PowCoder代写 加微信 powcoder
• Understand the software requirements elicitation and specification activity.
• Use UML use case diagrams to represent requirements.
• Use wireframes to sketch the UI.
Understanding use case diagrams
• Objective:
– To identify what not to do when creating a use case diagram.
– Point out mistakes in the diagrams.
• Wrong extended actor.
• Incorrect associations.
• Extend/Include misunderstanding.
• Use cases that do not represent actions.
What is wrong in this diagram?
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
What is wrong in this diagram?
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
What is wrong in this diagram?
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
What is wrong in this diagram?
https://softwareengineering.stackexchange.com/questions/359486/how-to-model-two-step-login-in-uml-via-use-cases-and-sequence-diagrams-properly
What is wrong in this diagram?
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
What is wrong in this diagram?
By Kishorekumar 62, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=7880320
Understanding use case diagrams
• Objective:
– To determine the scope of your SENG201 project.
1. In groups, briefly discuss the project specification.
• What are the main features of your future system?
2. Complete the use case diagram for your SENG201 project.
Understanding use case diagrams
3. Monster Fighter
4. include
5. Go to sleep
6. Show number of monsters
7. View team’s properties
8. Purchase items
9. Enemy player
10. Steal a monster
12. Create a player
13. Upgrade a monster
14. extend
15. Visit the shop
16. Heal a monster
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com