Ch05-_Understand_Requirement_Workflow

Ch05-_Understand_Requirement_Workflow - THE REQUIREMENTS...

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

View Full Document Right Arrow Icon
1 THE REQUIREMENTS WORKFLOW I
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 Chapter Overview Determining What the Client Needs Overview of the Requirements Workflow Understanding the Domain Initial Understanding of the Domain: Case Study Business Model Interviewing Other techniques
Background image of page 2
3 Chapter Overview (contd) Use Cases Initial Business Model: Case Study Initial Requirements Initial Requirements: Case Study Continuing the Requirements Workflow: Case Study
Background image of page 3

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

View Full DocumentRight Arrow Icon
4 Determining the Client’s Needs Consider the requirements workflow The primary task of the systems analyst is to determine what the client needs This may not be what the client says that he or she wants Information systems are complex Clients therefore often ask for the wrong information system
Background image of page 4
5 Determining the Client’s Needs (contd) It is hard for a systems analyst to visualize an information system and its functionality The problem is far worse for the client A skilled systems analyst is needed to bring out the appropriate information from the client The client is the only source of this information
Background image of page 5

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

View Full DocumentRight Arrow Icon
6 Determining the Client’s Needs (contd) The solution: Obtain initial information from the client Use this initial information as input to the Unified Process Follow the steps of the Unified Process to determine the client’s real needs
Background image of page 6
7 Overview of the Requirements Workflow First, gain an understanding of the application domain (domain, for short) (The specific business environment in which the information system is to operate) Second, build a business model Use UML to describe the client’s business processes Third, use the business model to determine the client’s requirements Then iterate (“repeat”) the above steps
Background image of page 7

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

View Full DocumentRight Arrow Icon
8 Understanding the Domain Every member of the development team must become fully familiar application domain Correct terminology is essential We must build a glossary That is, a list of technical words used in the domain, and their meaning
Background image of page 8
9 Flowchart of the Requirements Workflow
Background image of page 9

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

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 27

Ch05-_Understand_Requirement_Workflow - THE REQUIREMENTS...

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

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