Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CSE563 Lecture 12

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

CSE563 Lecture 12

Software Requirements and Specification
Use Case Diagram Review
(202202)

Avatar for Javier Gonzalez-Sanchez

Javier Gonzalez-Sanchez PRO

August 27, 2021
Tweet

More Decks by Javier Gonzalez-Sanchez

Other Decks in Programming

Transcript

  1. jgs CSE 563 Software Requirements and Specification Lecture 12: Quiz

    Review Dr. Javier Gonzalez-Sanchez [email protected] javiergs.engineering.asu.edu | javiergs.com PERALTA 230U Office Hours: By appointment
  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.
  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
  4. 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
  5. jgs Spring 2022 | 00001100 Case 1 • functional requirement:

    service, reaction, or behavior • functional vs non-functional • unambiguous, and verifiable • UML notation
  6. jgs Spring 2022 | 00001100 Case 2 • Where is

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

    non-functional (quality, organization (technical) • unambiguous, and verifiable
  8. jgs Spring 2022 | 00001100 Case 4 • Who is

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

    the actor? User? • functional vs non-functional • unambiguous, and verifiable • UML notation
  10. jgs Spring 2022 | 00001100 Case 6 • functional vs

    non-functional (quality, organization (technical) • UML notation
  11. 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
  12. jgs Spring 2022 | 00001100 Case 8 • functional requirement:

    service, reaction, or behavior • functional vs non-functional (quality, organization (technical) • unambiguous, and verifiable • UML notation
  13. 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
  14. jgs Spring 2022 | 00001100 UC Diagram a) Actors b)

    Use Cases a) Relationships child father base addition extension base << include >> << extend >>
  15. jgs CSE 563 Software Requirements and Specification Javier Gonzalez-Sanchez, Ph.D.

    [email protected] 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.