Satzinger_Ch05

Satzinger_Ch05 - 5 Chapter 5 Modeling System Requirements Systems Analysis and Design in a Changing World 5th Edition Learning Objectives x 5 x x x

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
5 Chapter 5 Modeling System Requirements Systems Analysis and Design in a Changing World, 5th Edition
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
5 Learning Objectives Explain why identifying use cases is the key to defining functional requirements Use three techniques for identifying use cases Write brief, intermediate, and fully developed use case descriptions Explain how the concept of things in the problem domain also defines requirements Identify and analyze data entities and domain classes needed in the system Read, interpret, and create an entity-relationship diagram Read, interpret, and create a domain model class diagram 2
Background image of page 2
5 Overview Document functional requirements by creating models Models created during analysis phase activity – Define system requirements Two concepts help identify functional requirements in the traditional approach and object-oriented approach Use cases and the events that trigger them Things in the users’ work domain 3
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
5 User Goals, Events, and Use Cases Use Case -- An activity the system performs in response to a user request Techniques for identifying use cases User goal technique Each goal at the elementary business process (EBP) level is a use case EBP – a task performed by one user, in one place in response to a business event, that adds measurable business value, and leaves system and data in consistent state CRUD analysis technique (create, read, update, delete) C Event decomposition technique 4
Background image of page 4
5 Identifying Use Cases Based on User Goals 5 Figure 5-1
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
5 Use Case Based on CRUD Technique 6 Figure 5-2
Background image of page 6
5 Event Decomposition Technique Event – an occurrence at a specific time and place and which needs to be remembered Business events trigger elementary business processes (EBPs) p EBPs are at correct level of analysis for use cases Identify business events to decompose system into activities/use cases 7
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
5 Types of Events External Outside system Initiated by external agent or actor Temporal Occur as result of reaching a point in time Based on system deadlines State Something inside system triggers processing need 8
Background image of page 8
5 Events Affecting a Charge Account Processing System that Lead to Use Cases 9 Figure 5-3
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
5 External Event Checklist 10 Figure 5-4 Temporal Event Checklist Figure 5-5
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 02/22/2010.

Page1 / 55

Satzinger_Ch05 - 5 Chapter 5 Modeling System Requirements Systems Analysis and Design in a Changing World 5th Edition Learning Objectives x 5 x x x

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online