CSE360 Lecture 11

CSE360 Introduction to Software Engineering Lecture 11: Use Cases II
Javier Gonzalez-Sanchez [email protected] javiergs.engineering.asu.edu Office Hours: By appointment

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 2 Previously
child father base addition extension base << include >> << extend >>

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 3 Rules
for Use Cases • Titles begin with a verb – A use case models an action so the name should begin with a verb. • Make the name descriptive – This is to give more information for others who are looking at the diagram. For example “Print Invoice” is better than “Print”. • Highlight the logical order – For example if you’re analyzing a bank customer typical use cases include open account, deposit and withdraw. Showing them in the logical order makes more sense. • Place use cases to the right of the primary actor and to the left of secondary actors • Place inheriting use case below parent use case

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 4 Rules
for Actors • Give meaningful business relevant names for actors • Actors model roles (not positions) • External systems are actors • Actors don’t interact with other actors • Place inheriting actors below the parent actor

Test Yourselves

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 6 Test
Yourselves Draw car Draw Car with flower

Yourselves Draw car Draw Car with flower << include >> << include >> << extend >> << extend >>

Yourselves Draw Ghost Draw Ghost Red Draw Ghost Blue

Yourselves Draw Ghost Draw Ghost Red Draw Ghost Blue << include >> << include >> << extend >> << extend >> it is not because the color, but they behave different http://gameinternals.com/post/2072558330/understanding-pac-man-ghost-behavior

Yourselves Draw car Draw Car with flower Draw Ghost Draw Ghost Red Draw Ghost Blue

Yourselves Make Payment VISA payment PayPal Payment

Yourselves Drop a Class Search Class Enroll a Class

Yourselves Drop a Class Search Class Enroll a Class << include >>

Yourselves Make Payment VISA payment Drop a Class Search Class Enroll a Class PayPal Payment

Common Errors UC diagram for enrolling a class on MyASU

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 19 Case
1 • What about external systems? • unambiguous, and verifiable • Example 7 in Lecture 9

2 • Where is the user and/or the external systems? • unambiguous, and verifiable • Example 7 in Lecture 9

3 • unambiguous, and verifiable • Example 7 in Lecture 9

4 • unambiguous, and verifiable • Example 7 in Lecture 9

5 • UML notation • unambiguous, and verifiable • Example 7 in Lecture 9

6 • Example 7 in Lecture 9

7 • UML notation • unambiguous, and verifiable • Example 7 in Lecture 9

8

Common Errors UC diagram for a web project

1 • functional requirement: service, reaction, or behavior • functional vs non-functional • unambiguous, and verifiable • UML notation

2 • Where is the user? • functional requirement: service, reaction, or behavior • functional vs non-functional • unambiguous, and verifiable

3 • functional vs non-functional (quality, organization (technical) • unambiguous, and verifiable

4 • Who is the actor? User? • unambiguous, and verifiable • UML notation

5 • Who is the actor? User? • functional vs non-functional • unambiguous, and verifiable • UML notation

6 • functional vs non-functional (quality, organization (technical) • UML notation

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

8 • functional requirement: service, reaction, or behavior • functional vs non-functional (quality, organization (technical) • unambiguous, and verifiable • UML notation

Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 36 Homework
Chapter 4

CSE360 – Introduction to Software Engineering Javier Gonzalez-Sanchez [email protected] Summer
2017 Disclaimer. These slides can only be used as study material for the class CSE360 at ASU. They cannot be distributed or used for another purpose.

CSE360 Lecture 11

CSE360 Lecture 11

More Decks by Javier Gonzalez-Sanchez

Other Decks in Programming

Featured

Transcript