Scribd
Upload
31 views

Practical 4

This document discusses requirements gathering as the first part of any software project. It aims to collect all relevant information from stakeholders regarding the product to be developed. Requirements gathering involves understanding what is trying to be built and why through techniques like interviews, questionnaires, and use cases. It is a partnership between developers and users where users communicate needs and developers ask questions to identify requirements. The document provides examples of functional requirements, system users, and tasks for a library management system to illustrate requirements gathering.

Uploaded by

Naimish Sorathiya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
31 views

Practical 4

This document discusses requirements gathering as the first part of any software project. It aims to collect all relevant information from stakeholders regarding the product to be developed. Requirements gathering involves understanding what is trying to be built and why through techniques like interviews, questionnaires, and use cases. It is a partnership between developers and users where users communicate needs and developers ask questions to identify requirements. The document provides examples of functional requirements, system users, and tasks for a library management system to illustrate requirements gathering.

Uploaded by

Naimish Sorathiya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Introduction to Software Engineering

4340702
PRACTICAL - 4
AIM - Gather application specific requirements- Requirement gathering.
It is a process of collecting requirements from the stakeholders. It is usually the first
part of any software product.
Requirements gathering is the process of understanding what you are trying to build
and why you are building it.
The goal of the requirements gathering activity is – to collect all relevant information
from the customer regarding the product to be developed.
Requirements are an essential part of any software project and the foundation on
which all projects should be built. The gathering of and compiling of requirements for
a software project is very much a partnership between the user of the software and the
developer. Obviously, the customer or software user needs to communicate to the
developer what they need, but at the same time the developer needs to be able to
anticipate needs and ask the right questions during the requirements gathering phase
of a project.
Some techniques for gather requirements include
One-on-one Interviews
Sit down with the client and ask them what they need. Asking open-ended questions
and getting the client talking about their hopes for the project is a good way to
understand their needs.
Group Interviews
Similar to the one-on-one, but with a group of people, the same types of questions are
asked, but with more of the users in the room, they may pick up on other’s statements
and expand or correct them. This can be helpful, but too many cooks spoil the broth
and these meetings can stray from the goal.
Questionnaires
Providing questionnaires to the customer to fill out can be a good starting point or
supplemental approach to interviewing.
Introduction to Software Engineering
4340702
Use Cases
A use case if a story about how a certain process in the software should work, they
may be easier for users to communicate clearly. There are many more techniques and
methods of gathering good requirements the above are only a few.

TASK
1. Write down set of questions to collect functional requirements form
various stake holders for your system.
Functional Requirements
1. Allow the librarian to add and remove new members.
2. Allow the user to search for books based on title, publication date, author,
etc., and find their location in the library.
3. Users can request, reserve, or renew a book.
4. Librarian can add and manage the books.
5. The system should notify the user and librarian about the overdue books.
6. The system calculates the fine for overdue books on their return.

2. Write all the users of your system.


1. Administrator.
2. Librarian
3. Cashier

3. Write and analyze the task of the users of your system.


1. Administrator.
a. Can create users, modify permissions to users and all admin rights.
2. Librarian
a. Can issue books
b. Collect return books
c. Manage Stocks
d. Store and Manage all records
e. Print all records.
3. Cashier
a. Collect Fine
b. Store and Print Records

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy