{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Lecuture 4 Requirement Engineering Process

Lecuture 4 Requirement Engineering Process - Lecture 3A...

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Lecture 3A: Requirement Engineering Process Teresa Xia Cai
Background image of page 1

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Software Engineering / 3A - 2 Outline The steps involved in the requirement engineering process U Feasibility studies U Requirements elicitation and analysis U Requirements validation U Requirements management
Background image of page 2
CUHK, Spring 2007 Software Engineering / 3A - 3 The requirements engineering process Four phases Output documents
Background image of page 3

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Software Engineering / 3A - 4 1. Feasibility studies A feasibility study decides whether or not the proposed system is worthwhile. A short focused study that checks U If the system contributes to organisational objectives; U If the system can be engineered using current technology and within budget; U If the system can be integrated with other systems that are used.
Background image of page 4
CUHK, Spring 2007 Software Engineering / 3A - 5 2. Elicitation and analysis Sometimes called requirements elicitation or requirements discovery. Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints. May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders.
Background image of page 5

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Software Engineering / 3A - 6 Example: ATM system stakeholders Bank customers Representatives of other banks Bank managers Counter staff Database administrators Security managers Marketing department Hardware and software maintenance engineers Banking regulators
Background image of page 6
CUHK, Spring 2007 Software Engineering / 3A - 7 Viewpoints Viewpoints are a way of structuring the
Background image of page 7

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

View Full Document Right Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 20

Lecuture 4 Requirement Engineering Process - Lecture 3A...

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

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