CSE563 Lecture 12

Software Requirements and Specification
Use Case Diagram Review
(202202)

Transcript

1. jgs
   CSE 563
   Software Requirements and Specification
   Lecture 12: Quiz Review
   Dr. Javier Gonzalez-Sanchez
   javiergs@asu.edu
   javiergs.engineering.asu.edu | javiergs.com
   PERALTA 230U
   Office Hours: By appointment
   

   View Slide

2. jgs
   Spring 2022 | 00001100
   Quiz 3
   § Quiz 3 is open. It is due in a Week as usual.
   § It is all about Requirement Engineering Roadmap – the paper you read
   reviewed on our lecture 8.
   

   View Slide

3. jgs
   Spring 2022 | 00001100
   Assignment 03
   § Create a Use Case diagram for the functional requirements that you listed in
   your Assignment 02
   § The software is described in the video (minute 26:00 to 54:40)
   § The functional requirements for the Pac-Man video game. All of them. A set
   that describes everything.
   § The functional requirements for the Game of Life. All of them. A set that
   describes everything
   § The functional requirements for the Space Invaders Game. All of them. A set
   that describes everything
   

   View Slide

4. jgs
   Examples
   Canvas
   

   View Slide

5. jgs
   Spring 2022 | 00001100
   Case 1
   🤔
   

   View Slide

6. jgs
   Spring 2022 | 00001100
   Case 2
   🤔
   

   View Slide

7. jgs
   Spring 2022 | 00001100
   Case 3
   Dragan Bogoevski (dbogoevs)
   👍
   

   View Slide

8. jgs
   Test Yourselves
   UC diagram for a Java Weather App
   

   View Slide

9. jgs
   Spring 2022 | 00001100
   Java App
   Include a button or icon that when clicked
   show a dialog box to select a city. Then map
   and weather for that city is shown
   show 10
   cities
   https://api.darksky.net/forecast/
   http://maps.google.com
   

   View Slide

10. jgs
    Spring 2022 | 00001100
    Case 1
    • functional requirement: service, reaction, or behavior
    • functional vs non-functional
    • unambiguous, and verifiable
    • UML notation
    

    View Slide

11. jgs
    Spring 2022 | 00001100
    Case 2
    • Where is the user?
    • functional requirement: service, reaction, or behavior
    • functional vs non-functional
    • unambiguous, and verifiable
    

    View Slide

12. jgs
    Spring 2022 | 00001100
    Case 3
    • functional vs non-functional (quality, organization (technical)
    • unambiguous, and verifiable
    

    View Slide

13. jgs
    Spring 2022 | 00001100
    Case 4
    • Who is the actor? User?
    • unambiguous, and verifiable
    • UML notation
    

    View Slide

14. jgs
    Spring 2022 | 00001100
    Case 5
    • Who is the actor? User?
    • functional vs non-functional
    • unambiguous, and verifiable
    • UML notation
    

    View Slide

15. jgs
    Spring 2022 | 00001100
    Case 6
    • functional vs non-functional (quality, organization (technical)
    • UML notation
    

    View Slide

16. jgs
    Spring 2022 | 00001100
    Case 7
    • Actor represent 1 user in 1 rol
    • functional requirement: service,
    reaction, or behavior
    • functional vs non-functional
    (quality, organization (technical)
    • unambiguous, and verifiable
    • UML notation
    

    View Slide

17. jgs
    Spring 2022 | 00001100
    Case 8
    • functional requirement: service,
    reaction, or behavior
    • functional vs non-functional
    (quality, organization (technical)
    • unambiguous, and verifiable
    • UML notation
    

    View Slide

18. jgs
    Test Yourselves
    UC diagram for a Pac-man
    

    View Slide

19. jgs
    Spring 2022 | 00001100
    From a Student’s Homework – Thoughts?
    

    View Slide

20. jgs
    Test Yourselves
    MyASU Enrrollement in a Course
    

    View Slide

21. jgs
    Spring 2022 | 00001100
    😣
    

    View Slide

22. jgs
    Spring 2022 | 00001100
    Case 1
    😔
    

    View Slide

23. jgs
    Spring 2022 | 00001100
    Case 2
    😔
    

    View Slide

24. jgs
    Spring 2022 | 00001100
    Case 3
    

    View Slide

25. jgs
    Spring 2022 | 00001100
    Case 4
    

    View Slide

26. jgs
    Spring 2022 | 00001100
    Case 5
    

    View Slide

27. jgs
    Spring 2022 | 00001100
    Case 6
    😔
    

    View Slide

28. jgs
    Spring 2022 | 00001100
    Case 7
    

    View Slide

29. jgs
    Spring 2022 | 00001100
    Case 8
    

    View Slide

30. jgs
    Spring 2022 | 00001100
    Case 9
    

    View Slide

31. jgs
    Spring 2022 | 00001100
    🤔
    

    View Slide

32. jgs
    Spring 2022 | 00001100
    Case 10
    😔
    

    View Slide

33. jgs
    Spring 2022 | 00001100
    Case 11
    

    View Slide

34. jgs
    Spring 2022 | 00001100
    Case 12
    

    View Slide

35. jgs
    Conclusion
    Review as needed
    

    View Slide

36. jgs
    Spring 2022 | 00001100
    Storyboarding
    storyboard
    Who? What (What if)?, why?,
    time
    

    View Slide

37. jgs
    Spring 2022 | 00001100
    INVEST in good requirements
    § Independent – loosely coupled with one another
    § Negotiable – Stories are what and why , not how ( 99% ).
    § Valuable – for the customer!
    § Estimatable – Effort/Cost of design, build, and test.
    § Small (sized appropriately)
    § Testable – pass or fail
    

    View Slide

38. jgs
    Spring 2022 | 00001100
    UC Diagram
    a) Actors
    b) Use Cases
    a) Relationships
    child father
    base addition
    extension base
    << include >>
    << extend >>
    

    View Slide

39. jgs
    Spring 2022 | 00001100
    Include vs Extends
    

    View Slide

40. jgs
    Spring 2022 | 00001100
    Questions
    

    View Slide

41. jgs
    CSE 563 Software Requirements and Specification
    Javier Gonzalez-Sanchez, Ph.D.
    javiergs@asu.edu
    Fall 2021
    Copyright. These slides can only be used as study material for the class CSE563 at ASU.
    They cannot be distributed or used for another purpose.
    

    View Slide