Requirements Gathering Techniques and Stages

Cover page

Contents
Task 2..........................................................................................................................................................3
Q3) Scenario............................................................................................................................................3
CCS Manager.......................................................................................................................................3
CCS Delivery person.............................................................................................................................3
Q4) user stories.......................................................................................................................................3
Q5) Functional requirements...................................................................................................................3
Q6) Non-Functional requirements...........................................................................................................3
Task 3..........................................................................................................................................................4
Q7) Context diagram (Level O DFD).........................................................................................................4
Q8) Use case diagram..............................................................................................................................5
Q9) Use case description.........................................................................................................................5
Q10) Sequence diagram..........................................................................................................................7
Q11) Entity-class diagram........................................................................................................................8
Q12) State diagram..................................................................................................................................8
Task 4........................................................................................................................................................10
Q13) ER Diagram...................................................................................................................................10
Q14) Tables with primary keys..............................................................................................................10

Task 1
Q1) Requirements gathering techniques
The best requirements gathering techniques that can be used are;
 Observation- Observation technique involves observing the normal flow of activities in the
university to understand what is expected of the system. To gather data using observation, the
requirements gathering team would have to visit the university and engage in the normal
activities while observing and taking notes on how different activities are conducted. This can be
done by 3 or 4 people. Later on the requirements gathering team meets up and compares notes
to come up with a requirements document. This technique is ideal for finding more about the
problem because it is cheap and easy to implement. Observation technique does not require a
lot of preparation and resources to implement as the requirements gathering team only needs
to visit the business premises to find out more about the problem. Analysis of the results is also
easy as it only requires meeting up and comparing the requirements gathered to come up with
the requirements document.
 Questionnaires- This technique involves preparing questionnaires which are distributed to test
subjects that are expected to be the end users of the system or are stakeholders in the system.
The set of questions in the questionnaire should be structured to make it easy for the subjects
to fill in the questions easily. This technique is ideal for this problem because it’s cheap and easy
to implement. Preparing questionnaires does not require a lot of resources and analyzing the
data from the questionnaires is easy especially when structured questions are used.
 Interviews- This technique involves performing interviews on users or stakeholders of the
system. There are three types of interviews that can be administered; structured interviews,
unstructured interviews or semi-structured interviews (Dehra, 2017). Semi-structured
interviews is the ideal technique as it a combination of unstructured and structured where the
questions administered to the interviewee are predetermined but both the interviewer and the
interviewee are allowed to deviate from the structured questions. Performing interviews is ideal
for this problem because the data obtained using this technique is accurate.
 Document sampling- Document sampling involves analyzing documents containing information
on the requirements of the system. The documents can contain case studies regarding the
problem. The requirements gathering team analyses the documents and comes up with a set of
requirements that is used to prepare the requirements document. This technique is ideal for this
problem because it does not require a lot of resources to implement.
 Background reading- Background reading or research is a technique that involves analyzing the
case study of the problem to come up with the requirements document. This technique is the
easiest to implement as it only requires the requirements gathering team to go analyse the case
study.
Q2) Requirements gathering stages
The stages involved in requirements gathering are;
 Planning- This stage involves coming up with a plan on how the research will be conducted. In
this stage, a schedule and budget are prepared. All resources required for use in the research
process are determined including the techniques to be used to gather the requirements.

 Research- This stage involves conduction the actual process of requirements gathering using the
resources and techniques specified in the planning stage. The requirements gathering team is
supposed to follow the schedule specified in the planning stage while ensuring the resources are
used accordingly. At the end of this stage, the requirements gathering team presents documents
containing the research data.
 Analysis- This stage involves performing analysis on the data obtained on the research stage to
come up with the requirements document. For example the requirements gathering team can
go through the set of questionnaires to get the requirements. At the end of this stage, the final
requirements document is presented.
Task 2
Q3) Scenario
CCS Manager
The CCS manager accesses the system and checks if there are any new event booking requests made by
members. The manager checks the details of the events and creates the event. Later on a member files
a claim and the manager checks the details of the claims and manages the claim by solving the schedule
conflict. A member who had previously booked an event cancels the event. The manager sees the cancel
booking request and updates the status of the event.
CCS Delivery person
CCS delivery person accesses the system and checks if they are new orders waiting to be delivered to
customers. The delivery person accepts to deliver the order and goes to the restaurant to pick the items
comprising the order. The delivery person makes the delivery to the member and updates the status of
the order.
Q4) user stories
 As a CCS manager I would like to use the system to create events from booking requests made
by customers.
 As a CCS delivery person I would like to use the system to view available orders waiting to be
delivered and accept the orders for delivery.
 As a student member I would like to use the system to place an order.
 AS a staff I would like to use the system to register a new group of a department.
Q5) Functional requirements
 A student should be able to register as a member
 A Delivery person should be able to see orders that are waiting to be delivered so that he can
take on the delivery of the orders
 A CCS manager should be able to create events based on the members booking requests.
Q6) Non-Functional requirements
 Performance- The system should maintain high performance at all times ensuring that all actions
use the least time. For example placing an order by a member should take not more than 3
seconds.
 Robustness- The system should be able to continue in case of system errors. The system should
have mechanisms that prevent a system crash if the system encounters an error.