Individual Project: Business Analysis for NoQueue - Spring 2019

This project presents a comprehensive business analysis plan for the NoQueue project, focusing on mobile commerce. It includes a feasibility report, business requirement specifications for a mobile application designed to address checkout issues at Big Bazaar in Oman, and software and hardware requirements. The analysis identifies potential risks, such as system failures, financial crises, and time shortages, along with proposed mitigation strategies. The project also incorporates a Gantt chart and work breakdown structure to illustrate the project timeline and task organization. The methodology used is the SDLC (Software Development Lifecycle) and it involves stakeholders like users, co-owners, managing directors, business IT managers, and developers. The project aims to provide a mobile solution for customers to scan product barcodes and make payments, ultimately saving time, costs, and increasing customer engagement. References to relevant literature support the analysis and recommendations.

Running head: BUSINESS ANALYSIS FOR NOQUEUE
BUSINESS ANALYSIS FOR NOQUEUE
Name of the Student
Name of the University
Author Note

1BUSINESS ANALYSIS FOR NOQUEUE
Table of Contents
Business Analysis Plan....................................................................................................................2
Feasibility Report.............................................................................................................................2
Business Requirement Specification...............................................................................................4
Software and Hardware requirements.............................................................................................4
Potential Risk...................................................................................................................................4
Gantt chart.......................................................................................................................................0
Work Breakdown.............................................................................................................................0
References........................................................................................................................................0

2BUSINESS ANALYSIS FOR NOQUEUE
Business Analysis Plan
Business Analysis Plan covers the analysis of the existing business of the Big Bazaar in
Oman, including gathering information about stakeholders along with their responsibilities and
roles. On the other hand, it will also cover the estimations for the development of the NoQueue
Project, timeline, and work breakdown plan with all the identified potential risks of the project.
An important part of the business plan is to set the objectives and aim of the company for the
project (Milani 2019). After developing the business plan, it needs to be monitored to reduce the
identified potential risks. The methodology used for the development of the project follows the
SDLC (Software development lifecycle). The stakeholders of the project are the users, Co-
owner, Managing director, Business IT manager, and Developers.
Feasibility Report
Feasibility report represents the consideration of the significant factors, problems, and
viability of them. It helps the decision-makers to identify options and select better options from
that. It also determines which task can be done or which cannot be done (Flora 2018). The main
aim of the feasibility report is to determine that the cost of the project is feasible for the company
or not. The Economic Feasibility report of the No Queue project is attached below:

3BUSINESS ANALYSIS FOR NOQUEUE
Figure 1: Economic Feasibility report
Source: created by author

4BUSINESS ANALYSIS FOR NOQUEUE
Business Requirement Specification
The Big Bazaar Company is facing issues in the checkout system of the customers where
they have to stand in a long queue at the counters. They want to provide a mobile application for
the customers having features of scanning product bar code self and payment system
collaborating with the banks. The requirement of the business is to save time, costs, and
increasing the number of audiences using Mobile Cloud Computing services.
Software and Hardware requirements
The Application based on mobile cloud computing will use the computational resources
to perform its processes. The services provided will be based on the PaaS (Platform as a Service)
and SaaS (Software as a Service) models (Kitanov and Janevski 2014). The Hardware
requirements for the project should be the Data centers, physical servers, Database servers,
Storage, and other networking devices. On the other hand, the software requirements will be IOS
or Windows-based Operating system and Amazon web services.
Potential Risk
Software Engineering projects require a high level of information and resources, where
the probability of arising the risks during the development is present (Abrahamsson et al. 2017).
To achieve the aim of the project, the potential risks must be identified before the development
phase. The potential risks for the NoQueue project are identified below in tabular form in terms
of technical, management, and external risk factors.

Running head: BUSINESS ANALYSIS FOR NOQUEUE
Ra
nk
Risk Description Category Root Cause Potential
Responses
Risk Owner Probabilit
y
Impact
3 System
Failure
During the testing
and integration
system crashes.
Technical System
hardware
requirements
not met.
Full fill the
technical
requirements
Developer
and project
manager
Less Critical
1 Financial
Crisis
The project is
costing more than
planned budget.
External Miscalculation
of the budget.
Replanning of the
budget from that
point.
Accountant
and Project
Manager
Moderate Critical
2 Time
Shortage
The Project is
running delayed.
Management Problems in
Project break
down.
Rescheduling the
project events
Project
Manager.
Moderate Critical
4 Quality
Issue
The Scope of the
project is not met.
External The project
work break
down is not
followed.
All breakdown
should be followed.
Project
Manager;
Less Moderate
Table 1: Risk Analysis for NoQueue project
Sources: created by author

Running head: BUSINESS ANALYSIS FOR NOQUEUE
Gantt chart
ID Task
Mode
Task Name Duration Start Finish Cost Resource Names
3 Identification of
hardware and software
requirements
3 days Wed 3/11/20 Fri 3/13/20 3,720.00 .ع .ر Tester,Designer
4 Usability requirement 4 days Mon 3/16/20 Thu 3/19/20 10,240.00 .ع .ر Managing
director,Co-owner
5 Identifying the risks of
the project
2 days Fri 3/20/20 Mon 3/23/20 5,440.00 .ع .ر Developer
,Designer
,Co-owner
6 Cost management plan 2 days Tue 3/24/20 Wed 3/25/20 3,040.00 .ع .ر Business IT
manager
,Designer7 Milestone 1 0 days Wed 3/25/20 Wed 3/25/20 0.00 .ع .ر Designer
8 Analysis 11 days Thu 3/26/20 Thu 4/9/20 35,320.00 .ع .ر
9 Creation of business case 1 day Thu 3/26/20 Thu 3/26/20 4,200.00 .ع .ر Developer
,Tester,Managing
director,Business10 Creation of business
analysis plan
1 day Fri 3/27/20 Fri 3/27/20 3,640.00 .ع .ر Developer
,Tester,Managing
director,Business11 Creation of feasibility
report
2 days Mon 3/30/20 Tue 3/31/20 8,400.00 .ع .ر Developer
,Tester,Managing
director,Business
IT manager12 Literature analysis 5 days Wed 4/1/20 Tue 4/7/20 15,000.00 .ع .ر Developer
,Tester,Business
IT manager
Tester,Designer
Managing director,Co-owner
Developer ,Designer ,Co-owner
Business IT manager ,Designer
3/25
Developer ,Tester,Managing director,Business IT manager ,Des
Developer ,Tester,Managing director,Business IT manager
Developer ,Tester,Managing director,Business IT manager ,De
Developer ,Tester,Business IT manager ,Designer
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Qtr 1, 2020 Qtr 2, 2020 Qtr 3, 2020 Qtr 4, 2020
Figure 2: Gantt chart Analysis of the NOQUEUE project
Source: Created by author

Running head: BUSINESS ANALYSIS FOR NOQUEUE
Work Breakdown
Figure 3: Work Breakdown Analysis of NOQUEUE
Source: created by author

Running head: BUSINESS ANALYSIS FOR NOQUEUE
References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Flora, H.K., 2018. Adopting an agile approach for the development of mobile applications.
Kitanov, S. and Janevski, T., 2014, May. State of the art: Mobile cloud computing. In 2014 Sixth
International Conference on Computational Intelligence, Communication Systems and
Networks (pp. 153-158). IEEE.
Milani, F., 2019. Business Analysis Plan and Monitoring. In Digital Business Analysis (pp. 111-
125). Springer, Cham.