CSE360 Lecture 13

Introduction to Software Engineering
Behavior Modeling
(201805)

Transcript

1. CSE360 Introduction to Software Engineering Lecture 13: Behavior Modeling Javier Gonzalez-Sanchez javiergs@asu.edu javiergs.engineering.asu.edu Office Hours: By appointment
2. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 2 Previously SRS (requirements) Use Case Diagram (functional structure) UC1 UC2 UC4 UC3 (non-functional) Use Case Template (functional details)
3. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 3 Previously Use Case Template
4. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 4 Introducing UML
5. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 5 Activities and States • Create a activity diagram when a use-case requires a graphical representation of the flow of interaction. • Create a state diagram when a use-case requires a list of the different states of a system. * they are not mandatory and they can be combined.
6. Activity Diagram
7. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 7 Test Yourselves • What is an activity? • What is the difference between activity and requirement?
8. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 8 Activity Diagram • A graphical representation of the flow of activities 1. Sequence 2. Conditions and Loops 3. Parallel or Concurrent 4. Actor (if there are multiple actors involved in a specific use-case) responsibility for the action described
9. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 9 Key elements • rounded rectangles represent actions; • diamonds represent decisions; • bars represent the start (split) or end (join) of concurrent activities; • a black circle represents the start (initial node) of the workflow; • an encircled black circle represents the end (final node). • Arrows run from the start towards the end and represent the order in which activities happen. • Swim lane or functional band helps to visually distinguishes job sharing and responsibilities
10. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 10 Example | Use Case
11. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 11 Example 2 ATM transaction
12. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 12 Example 3 (part 1/2) ATM transaction customer bank ATM machine
13. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 13 Example 3 (part 1\2/2)
14. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 14 Example | Astah
15. State Diagram
16. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 16 State Diagram State machine models show • states (as nodes) – a set of observable circumstances that characterizes the behavior of a system at a given time • Event (arc between nodes) —an occurrence that causes the system to exhibit some predictable form of behavior When an event occurs, the system moves from one state to another.
17. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 17 Example: MyASU
18. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 18 Example State machine diagram
19. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 19 Example State machine diagram
20. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 20 Test Yourselves • Requirement • Use case • Use case diagram • Use case document • Actor • Scenario • Activity • State
21. Pac-Man Video Game Case Study
22. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 22 Pac-Man • View Maze • View Characters • View Score • Move • Wall collision • Eat a dot • Eat power-up dot • Eat ghost • Pac-man dies
23. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 23 Pac-Man • http://gameinternals.com/post/2072558330/ understanding-pac-man-ghost-behavior
24. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 24 Pac-Man What about: • New • Hunter • Hunted • Eaten
25. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 25 Pac-Man
26. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 26 Homework • Review the Monopoly Requirements Specification • Review the Pac-Man Requirements Specification • Review the Course Registration System Specification * Documents available on Blackboard.
27. CSE360 – Introduction to Software Engineering Javier Gonzalez-Sanchez javiergs@asu.edu 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.