Applications Modelling and Development

This document discusses applications modelling and development, including requirement gathering techniques, user scenarios, functional and non-functional requirements, and use case diagrams.

Running head: APPLICATIONS MODELLING AND DEVELOPMENT
Applications Modelling and Development
Name of the Student
Name of the University
Authors note

1APPLICATIONS MODELLING AND DEVELOPMENT
Table of Contents
Task 1.........................................................................................................................................2
Answer to question 1..................................................................................................2
Answer to question 2..................................................................................................2
Task 2.........................................................................................................................................3
Answer to question 3..................................................................................................3
Answer to question 4..................................................................................................3
Answer to question 5..................................................................................................5
Answer to question 6..................................................................................................5
Task 3.........................................................................................................................................6
Answer to question 7..................................................................................................6
Answer to question 8..................................................................................................7
Answer to question 9..................................................................................................7
Answer to question 10................................................................................................8
Answer to question 11................................................................................................9
Answer to question 12..............................................................................................10
Task 4.......................................................................................................................................13
Answer to question 13..............................................................................................13
Answer to question 14..............................................................................................14

2APPLICATIONS MODELLING AND DEVELOPMENT

3APPLICATIONS MODELLING AND DEVELOPMENT
Task 1
Answer to question 1
Following are the 5 requirement gathering techniques which can be used for the
given scenario of the Campus common system
Brainstorming: This technique is helpful in gathering enough number of ideas from
the different group of people.
Prototyping: Through the use of prototypes of the proposed system this technique
enables the potential users to observe and use a potential solution to which the users may add
or amend functionality or the requirements.
Survey: As the potential customer base of the proposed system is very large in
number thus survey among the user base will be very helpful in gathering and elicitation of
the requirements of the system.
Focus group: Focus group is the collection representatives from the different user base
of the proposed system to gain feedback. These collected feedbacks are mainly related to
different opportunities, problems requirements for the system.
Interface analysis: In this technique, different interfaces with the multiple touch
points along for different tasks according to the requirement in order to verify the usability
from the different user perspectives.

4APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 2
In order to have better understanding about the requirements about the new system
following strategy can be used in which the first step will be survey, focus group,
brainstorming and lastly prototyping.
At the first stage, large number or users like the students, CCS staffs, potential
delivery boys and other stakeholders. From this stage with the most reasonable, feasible
functionalities will be selected. Next, interviewing the focus groups the selected
functionalities can be narrowed to have precise functionalities for the proposed system. In the
brainstorming stage the precise requirements will be refined in order to start the development
of the prototype that can be used for initial interaction with the potential user.
Task 2
Answer to question 3
User scenario from the CCS Delivery person’s perspective: The students at first
needs to register to the system which is to be validated through the MQAuth server. only
after the validation the boys will be able to pick the orders from the counter to deliver to the
customers. When the orders is picked from the counter then it will marked as “Picked” in the
system. The delivery will be rated by the customers through the system.
User scenario from CCS manager’s perspective: The managers are responsible for
proper management of different events. Whenever, a manager receives any call for
scheduling an event at first the manager will check for any available slots. If for the required
slot is available, then the manager will confirm the booking after taking the details of the
event. After this the manager will ask if the member wishes to use the bundle. If the “Add
Bundle” option is selected, then after confirmation the booking is completed and status is set

5APPLICATIONS MODELLING AND DEVELOPMENT
to book. In case the requested slot is not available then the manager will deny the request for
booking.
Answer to question 4
User story for manager
1. Manager will schedule and confirm the schedules of the event
2. Check conflicts with the other booked events
3. Cancel booking.
4. Check booking.
User story for Student member
1. Register in the system to be a member in CCS.
2. Order food and beverages from the CCS.
3. Register to be a delivery boy.
4. Deliver the order to the customer.
User story for Delivery person
1. Register to be a delivery boy.
2. Pick the order from counter.
3. Deliver the order.
4. Change the status for the order as delivered.
User story for staff member
1. Book for an event.
2. Check for availability for the slot for booking a event.
3. Pay for the booked event.

6APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 5
Functional requirements
For customers: The users should be able to view different available food and
beverages in order to select order from those options.
For Managers: The users must be able to check if requested slots by the customers
had any booking or not so that they can book the slot or cancel the booking.
For Delivery boys: The system must generate a unique order id in order to pick up a
specific order that needs to be delivered from CCS.
Answer to question 6
Non-functional requirements
Performance: The developed application should have minimal downtime in order to
provide better usability.
Security: As the payment for the order will be processed through the developed
system therefore providing a secure environment for the users is also important.
Usability: In order to provide better user experience, it is important to develop the
system in such a way that user will complete the task in minimal steps.

7APPLICATIONS MODELLING AND DEVELOPMENT

8APPLICATIONS MODELLING AND DEVELOPMENT
Task 3
Answer to question 7
Figure 1: Context level Diagram for CCS
(Developed by using Visio)

9APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 8
Figure 2: Use case diagram for the CCS case study
(Created by author using Visio)
Answer to question 9
Use case description for the order delivery
Actors: CCS student/Staff, Delivery boy
Precondition: The CCS member booked order through any method in CCS.

10APPLICATIONS MODELLING AND DEVELOPMENT
Description: The delivery by picks up the order from the counter and marks it as
picked. After the order is delivered to the member the order status is marked as delivered by
the delivery boy.
Post condition: The order status is changed to delivered.
Answer to question 10
Figure 3: Sequence Diagram for Event booking use case
(Created by author using Visio)

11APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 11
Figure 4: Entity Class Diagram for the Scenario of CS
(Source: Created by author using Visio)

12APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 12

13APPLICATIONS MODELLING AND DEVELOPMENT

14APPLICATIONS MODELLING AND DEVELOPMENT

15APPLICATIONS MODELLING AND DEVELOPMENT
Task 4
Answer to question 13
Figure 5: ERD Diagram for the First set of Entities
Source: Created by Author using Visio

16APPLICATIONS MODELLING AND DEVELOPMENT
Answer to question 14

17APPLICATIONS MODELLING AND DEVELOPMENT