L4-Requirement Determination

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

Systems Analysis and Design

Requirements Determination

Chalani Oruthotaarachchi

2-0
Outline

▪Requirement determination.
▪ Requirement elicitation
techniques.
▪ Requirement analysis strategies.
THE ANALYSIS PHASE

2-2
THE ANALYSIS PHASE
▪ The basic process of analysis involves three
steps:
- Understand the existing situation (the as-is system)
- Identify improvements
- Define the requirement for the new system (the to-be
system).

▪ The final deliverables of the analysis phase is


the system proposal.

3-3
Relationship Between Information
Gathering and Model Building

4
What is a Requirement?
▪ A requirement is a statement of what the system must
do or what characteristics it needs to have.

▪ Requirements describe
- what the business needs (business requirements)
- what the users need to do (user requirements)
- what the software should do (functional requirements)
- characteristics the system should have (non-functional
requirements)

3-5
Requirements contd.

2-6
More about functional
requirements

2-7
Exercise
Requirements for Proposed System:
The system should…
1. Serve the web users. 11. increase market share
2. include the company logo and color scheme. 12. shorten order processing time
3. connect all the branches. 13. reduce customer service costs
4. include actual and budgeted cost information. 14. lower inventory spoilage
5. provide management reports. 15. improve responsiveness to customer
6. have 2-second maximum response time for service requests
predefined queries and 10-minute maximum 16. schedule a client appointment
response time for ad hoc queries. 17. place a new customer order
7. display information from all company 18. re-order the inventory
subsidiaries. 19. determine available credit of clients
8. print subsidiary reports in the primary language 20. look up account balances
of the subsidiary.
9. provide monthly rankings of salesperson
performance.
10. include sales information that is updated daily.

Categorize these requirements into business, user, functional, and non functional
2-8
requirements.
REQUIREMENTS ELICITATION TECHNIQUES

2-9
(1) Interviews
▪ Structured vs. unstructured interviews
▪ Basic steps:
– Selecting Interviewees
– Designing Interview Questions
– Preparing for the Interview
– Conducting the Interview
– Post-Interview Follow-up

3-10
Criteria for Selecting interviewees
▪ Who has the relevant information?
▪ Who is accessible?
▪ Who is willing to give relevant information?
▪ Who is most able to give the information?

2-11
Designing interview questions

3-12
Face-to-face or ‘remote’ interviewing?

2-13
Exercise
▪ Whom could you interview to find out more about following
programs/projects?

1. Recently there's been a great deal of concern over high school and
college students downloading past papers from "paper mill" websites.
Students then put their names on the papers and submit the papers
for course credit. You are conducting a research on this topic.

2. The CEO of your company has decided to fund a program for the arts
in the local junior high schools and has chosen you to lead the project.

3. Your team is assigned to build an information system for managing


figure-print based lecture attendance management system for a
university.
2-14
(2) Questionnaires
▪ A questionnaire is a set of written questions for
obtaining information from individuals.

▪ Good questionnaire design

3-15
Questionnaire practice
Organize yourselves into small groups. Have each person develop a short
questionnaire to collect information about any process the group prefers
(e.g., working on a class assignment, making a sandwich, paying bills, getting
to class). It should collect information about;
– the frequency in which group members perform process
– how long it takes them
– how they feel about the process
– opportunities for improving the process
Once everyone has completed his or her questionnaire, ask each member to
pass it to the right and then complete his or her neighbor’s questionnaire.
Pass the questionnaire back to the creator when it is completed.

QUESTIONS:
1. How did the questionnaire you completed differ from the one you created?
2. What are the strengths of each questionnaire?
3. What would you change about the questionnaire that you developed?
2-16
(3) Joint Application Development (JAD)
▪ JAD allows the project team, users, and management
to work together to identify requirements for the
system.

▪ It can reduce scope creep by 50%,


▪ JAD is a structure process in which 10 to 20 users
meet under the direction of a facilitator skilled in
JAD techniques.
3-17
JAD facility

2-18
(4) Document Analysis
▪Document analysis is used to
understand the as-is system.

▪Forms, reports, policy manuals,


organization charts describe the formal
system that the organization uses.

3-19
(5) Observation
▪ Observation – the act of watching processes being
performed.
▪ It is a powerful tool to gain insight into the as-is
system, and to check the validity of information
gathered from other sources.
▪ Nonetheless, people tend to be extremely careful in
their behaviors when they are being watched.

3-20
Activity for you…

▪Identify the pros and cons of each


requirement elicitation technique
discussed in the lecture.

2-21
Selecting the Appropriate Techniques
Comparison of Requirements Elicitation Techniques

3-22
Activity for you…
▪ Suppose that you are the analyst charged with
developing a new system for the university
bookstore with which students can order
books online and have them delivered to their
hostel and off-campus housing. What
requirements-gathering techniques will you
use? Describe in detail how you would apply
the techniques

2-23
End of the session

2-24

You might also like