Chap06_Requirements&UseCase

Chap06_Requirements&UseCase - Requirements Capture...

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

View Full Document Right Arrow Icon
Requirements Capture Requirements Capture Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design Using UML, (2 nd Edition), McGraw Hill, 2002.
Background image of page 1

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

View Full DocumentRight Arrow Icon
In This Lecture You Will Learn: The distinction between the current and required systems When and how to apply the main fact finding techniques The roles played by users The need to document requirements
Background image of page 2
User Requirements Need to understand how the organization operates at present What are the problems with the current system? What are the requirements users have of a new system that are not in the current system?
Background image of page 3

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

View Full DocumentRight Arrow Icon
Current System Much of the current system meets the needs of people who use it Sections of the system no longer meet the needs of the organization Some aspects of the organization’s work are not covered by the current system The system can no longer evolve but needs to be replaced
Background image of page 4
Current System It is important to understand current system to carry functionality forward into new system It is also important to understand it so that shortcomings and defects can be corrected in the new system
Background image of page 5

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

View Full DocumentRight Arrow Icon
Reasons for Investigating the Current System Functionality is required in new system Data must be migrated into new system Technical documentation provides details of processing algorithms Defects of existing system must be avoided Parts of existing system may have to be kept We need to understand the work of the users Baseline information about the existing system helps set targets for the new one
Background image of page 6
New Requirements Organizations operate in a rapidly changing business environment Organizations operate in a changing technical environment Governments and supra-governmental organizations introduce legislation Organizations merge, demerge, take over and get taken over All this drives the need to replace systems and build new ones
Background image of page 7

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

View Full DocumentRight Arrow Icon
Types of Requirements Functional Non-functional Usability
Background image of page 8
Functional Requirements Describe what a system must do Include: processes interfaces with users and other systems what the system must hold data about Modelled with Use Case Diagrams. Later will be modelled with other kinds of diagrams that show the structure of the system (Class Diagrams) and its behaviour (Interaction Diagrams and Statechart Diagrams)
Background image of page 9

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

View Full DocumentRight Arrow Icon
Non-functional Requirements Concerned with how well the system performs Include: response times volumes of data security considerations Documented in Requirements List or in Use Case Model (for requirements that can be linked to specific use cases)
Background image of page 10
Usability Requirements Concerned with matching the system to the way that people work Sets measurable objectives Include: characteristics of users tasks users undertake situational factors acceptance criteria (user judgement for the delivered system) Documented in Requirements List. May be tested by Prototypes
Background image of page 11

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

View Full DocumentRight Arrow Icon
Fact Finding Techniques Background Reading Interviewing Observation Document Sampling Questionnaires
Background image of page 12
Image of page 13
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 01/04/2010 for the course MSC CP 1312 taught by Professor Ms.nireshfathima during the Fall '09 term at Unity.

Page1 / 62

Chap06_Requirements&UseCase - Requirements Capture...

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

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