Chapter 6 Requirement Analysis Flashcards
Requirements Analysis
Also known as Fact-Finding Process and Requirement Elicitation.
PURPOSE: to find or gather requirements for a system to be developed
Fact-finding techniques
- Interview
- Document review
- Observation
- Sampling
- Research
- Surveys and Questionnaires
Interview
- a planned meeting which we can obtain information from another person
- skills are required to conduct an interview
- Do you think current system is secure?
- Which process takes the longest time to process
Steps to conduct an interview
Step 1: Determine the people to interview
Step 2: Establish objectives for the interview
Step 3: Develop interview questions
Step 4: Prepare for the interview
Step 5: Conduct the interview
Step 6: Document the interview
Step 7: Evaluate the interview
Document Review
Aims to find out the information requirements that people have in the current system
Including:
- Review existing system documentation
- Obtain copies of actual forms and documents
Observation
Aims to see what really happens not what people says
Includes:
- Seeing how people carry out processes
- Examine each form, record and report
Hawthorne effect
Productivity of the staffs seemed to be improve whenever workers knew they are being observed
Questionnaires and Surveys
Aims to obtain the views of a large number of people that can be analysed statistically
- open-ended and closed questions
- gathering opinions and facts
Example: On a scale of 1-5 how satisfied are you with the current system?
Sampling
- a sampling technique that is use to recruit participants who can provide in-depth information about the system
Techniques of sampling
Systematic sample- Select every 10th customer
Stratified sample- Select 5 customers from different locations
Random sample- any 20 customers or 10
Objective - to ensure representing overall population accurately
- May consider either Interviewing or questionnaires
Research
Such as Journals, periodicals, books
Recording facts
Keeping accurate records of interview, facts, ideas, and research is important to successful systems development
- Writing it all down
Software tools for recording facts
CASE tools - develop and maintain IS
Word processing - create reports
Spreadsheet - manage numerical data
Database- manage information about events
Presentation graphics- developing formal presentations
Personal Information Managers
- keep track of meetings, appointments
Types of Requirements
- Functional
- Non-functional
- Architectural
- Business
- System/technical
- User
- Security
- User interface
Types of Requirements definition
Functional - describe a what a system must do
Non-functional- specify criteria used to judge the operation of a system
Architectural- explain what has to be done
Business - High-level statements of the golas, objectives
- System - The infrastructure the new system needs to runs on
-User- Stakeholders
-Security- Types and levels of security the new system needs
-User interface- Specific design for user interface