Requirements Elicitation Techniques and Strategies for Common Campus System

Task 1: Requirements elicitation.
1. Requirements gathering techniques and reason why choosing this techniques.
According to Mochal (2008) explained that requirement collecting is very important stage in
software development cycle and good gathering techniques have to be selected.
Interviews, Questionnaires, Prototyping, Brainstorming and Analyzing of document.
a. According to Sommerville (2016) explained that questionnaires are effectively cheap, easy to use
and very fast at collecting requirement that come from stakeholders. Interviews are made on one
on one with stakeholder this helps to get vital information. Analyzing of software requirement
specification and design specification documents of the current common campus system helps to
identify the gaps in the system and redesign. Prototype is the best way of understanding the
problem where a prototype is design and given to stakeholder to use while capturing requirement
this is very important because accurate requirements are capture at less cost. Brainstorming helps
to generate different ideas by coming up with solution of problems or gaps in system. For
example during brainstorming system analysists suggested user interface of Common campus
should have green color, sliding pictures and details on dash boarded should not be scattered or
congested on one point. According to Preece, Rogers and Sharp (2017explained that good user
interface should user friendly and able to capture attentions of users. The website shall be easy to
learn how to operate and to remember how to use after being learned due to the graphical
representation of some features (menu, event, order now, drinks, Dive right in or sign in to re-
order,) that makes them obvious and straight forward. It has catch names and images of food,
uses perceptual boundaries, color to capture customers’ attention and price of each food and
beverage is attached making it easier to buy. Select and buy icons shall be visible.
2. Strategies, Details of technics, data collected and justification.
Drafting questioners and distributing to student and staff.
Requesting appointment from student and staff for interview.
Forming groups to brainstorm.
Details of technics, data collected and justification.
After interviewing students, restaurant person and Delivery person. Questions from interviews
were answered .For example interviewee asked interviewer a question of if there is need of new
system as compared to existing one? Majority of students 90% answered there is need of new
and gave reason, for example reasons they gave was a lot of time was wasted during waiting for
order and student could get wrong orders during delivery so students prefer to order themselves.
This data helps in redesigning of the system. Analyzing of documents helped researcher to obtain
data about different important document required for system to operate well and be captured for
example data about payment details, food menu, order details all this data is vital and need to be
captured during designing.Reciepts and food menus were obtained at restaurant showing
payment details and type of food available at restaurant. After giving student questioners to

answer some answers and reasons were obtained. For example question of, if there is a problem
with existing system? .Majority of student 80% answered yes there is a problem and gave
reasons such as activity of student getting food orders and booking for event is long ,slow and
consume a lot of time .Getting what you want in time is difficult so redesign of system is
important.
3. Questions.
Do you eat, drinking and interact at campus?
Which kind of items do you order?
Do you attend for event at campus?
Do you book for events?
Do you prefer delivery or pick up of order?
How do you make payments for orders you do make?
Is there a problem with existing system?
Do you need new new CCS system at Campus?
Which kind of improvement do you suggest we make?

Task 2: Requirements specification.
According to Pressman (2018) explained that both functional and non-functional requirements
are important during design of system and so they are important to be implemented .Functional
are requirements which a system has to do or implement for it to functions well while
nonfunctional requirements are requirements which a system cannot implement but a system will
continues functioning example speed of system processing food order is low.
4. User scenarios.
CCS Delivery person registers on CSS as a delivery person, Registration details are validated
using MqAuthServer and a student can be a Delivery person. Delivery accepts orders and change
status as delivered.CCS manager manages booking, schedule conflicts, creates and cancels
booked events.
5. User stories.
CCs Member registers on ccs.
CCs Delivery Person can be a student and same time delivery person.
Ccs member makes payment through Css to the bank or MQ Budget Office system.
Restaurant is auto registered.
6. Functional requirements.
All CCS Members shall register to get an account of css.
CCs member shall make payment first before ordering, through Css to the bank or MQ Budget
Office system.
The manager shall manage all booked event.
7. Non-functional requirements.
Performance.
Time to process order shall be 15 mins and employees should not be overloaded with a lot of
work so there is need to employ more workers.
Time for responding to order should be real time. System can notify ccs member if order food is
available or no in real time. System shall process all orders of student a university.
Security.
The system shall only allow only registered, validated student and staff are the one to access
ccs features and use. Roles also shall be given according to level for example a student cannot
read or write on manger level.
Reliability.
The system shall be available any time ccs member need to make orders thus systems shall be
free from failure. For example shall have 5 mins of time it is down per month.
According to Fenton and Pfleeger (2017) explained that nonfunctional requirements’
limitations and constraints have to be considered during design of system. Example security,
reliability and performance requirement are important and should be put into consideration
during designing.

Task3: System Perspective.
8. Figure 1 below showing Context Diagram of Common Campus System.
The context diagram above demonstrates how external users interact with the common campus
system. The context has covered major stakeholders of the common campus system.