Chapter 4 - User Requirements Gathering and Analysis 2_v2.1

What is Requirements Gathering?

A process to collect and analyze user requirements for software development.

What are some methods for gathering user requirements?

User survey, user interview, review of existing documents, existing software review, study user-supplied documentation.

What is a User Survey?

A structured questionnaire distributed to a group of users for feedback and preferences.

What is one advantage of a User Survey?

Can be conducted easily and reach a large number of people at low cost.

What is a disadvantage of a User Survey?

Responses may not always be useful.

What is the purpose of a User Interview?

To gather detailed feedback through guided questions in one-on-one or small group settings.

What is one advantage of User Interviews?

Allows for guidance during the interview and encourages contact between developers and users.

What is a disadvantage of User Interviews?

They can be time-consuming.

What types of documents can be reviewed in Existing Documents Review?

Hardcopy or electronic documents such as reports, logs, meeting minutes, newsletters, and marketing materials.

What is an advantage of reviewing Existing Documents?

It is relatively inexpensive and a good source of background information.

What is a disadvantage of reviewing Existing Documents?

Information may be incomplete or inaccurate.

What is involved in Existing Software Review?

Verification of both functional and non-functional requirements.

What is an advantage of Existing Software Review?

Identifies design defects and highlights areas of the existing system for improvement.

What is a disadvantage of Existing Software Review?

Time-consuming and can increase project implementation costs.

What is the purpose of studying User-Supplied Documentation?

To analyze documents created by users to learn about procedures, regulations, and standards.

What is an advantage of studying User-Supplied Documentation?

No time commitment from users is required.

What is a disadvantage of studying User-Supplied Documentation?

Day-to-day work may differ from documented procedures.

What is a Software Requirements Document (SRD)?

An official document specifying what is required from the system developers.

What does an SRD specify?

It specifies WHAT the system should do rather than HOW it should do it.

What types of requirements are included in a URD?

User requirements and system requirements.

What is a User Requirements Document (URD)?

A document that describes what users expect the software to do.

What are the components of a URD?

Mandatory requirements, Desirable requirements, Optional requirements, and Possible future enhancements.

What defines Mandatory Requirements?

Features that must be built into the final system; failure means elimination from the tender process.

What are Desirable Requirements?

Features that should be included unless the cost is too high.

What are Optional Requirements?

Features that can be built into the system but are not required.

What are Possible Future Enhancements?

Features that may be added based on budget and timeline.

What is a Requirements Checklist?

A tool to ensure that requirements documents are correct, complete, unambiguous, consistent, verifiable, and approved.

What is an example of a Requirements Checklist step?

Check common language to ensure acronyms are defined in the glossary.

How can a Requirements Checklist support the requirements documenting process?

By providing tools to verify correctness and completeness of the documentation.