ISYS324: Business Analysis of Parramatta Car Park System

This report presents a business analysis of the Parramatta City Council car park system, addressing the need for a new system to manage its seven car parks. The report begins by initiating the project, defining the system, identifying main issues (data management challenges), establishing the project scope (automating and streamlining car parking), and outlining stakeholders. It then analyzes the requirements, detailing functional requirements (customer data storage, payment details, entry/exit times) and non-functional requirements (24/7 operation, accessibility, security). The report further explores requirement specification validation and elicitation, focusing on the observation and prototyping techniques, and evaluates the RequisitePro tool for requirement elicitation. The analysis provides a comprehensive overview of the car park system, offering insights into its challenges and potential solutions through a structured approach to business analysis.

Running head: BUSINESS ANALYSIS
Business Analysis
Name of Student-
Name of University-
Author’s Note-

1BUSINESS ANALYSIS
Table of Contents
1. Initiating the project.....................................................................................................................1
1.1 System definition...................................................................................................................1
1.2 Main issues and problems......................................................................................................1
1.3 Project Scope and vision........................................................................................................1
1.4 Stakeholders...........................................................................................................................2
2. Analyzing Requirement...............................................................................................................2
2.1 Functional Requirement.........................................................................................................2
2.2 Non-functional Requirement.................................................................................................2
3. Requirement Specification Validation and elicitation.................................................................3
3.1 Requirement Elicitation Technique.......................................................................................3
3.2 Tool used for Requirement Elicitation Technique.................................................................3
Bibliography....................................................................................................................................5

2BUSINESS ANALYSIS
1. Initiating the project
1.1 System definition: The system that is being proposed in this report is capable of
handling the car parking system. The Parramatta City Council mainly works with seven car
parking areas that are situated in the city of Parramatta. The system that is being proposed in this
report will manage the parking system carried out in different car parking system. This system
will be capable of managing the data of tickers issues, the payment related data, as well as the
control barriers that are associated with the system. The system will also store data related with
the management problems in the system. The management problems includes recording
problems, issue season tickets as well as includes agreements of monitoring service.
1.2 Main issues and problems: The issues and the problems that are faced by the present
system is that they are not able to manage the huge amount of data that is generated by the
system. As the car parking system generates huge number of data including ticket data, payment
data as well as management problems in the system, it is very much difficult to store the data
manually or with some other forms of data storage. So, this new information system would help
to solve all these issues of the present system.
1.3 Project Scope and vision: The scope of the project is to develop an information
system that would help to automate the car parking system in all the centers of car parking and
would make the system more easier sand efficient. The project scope provides to develop an
information system that will make the car parking system an easy process to maintain all its data
and arrange parking efficiently.
1.4 Stakeholders: The stakeholders who are associated with the project are the owner of
the car parking system, the partners associated with the car parking and the shareholders of the

3BUSINESS ANALYSIS
company. The stakeholders who are associated with developing the information system for the
car parking system are project manager, subject matter experts, programmers, developers,
designers, testers and quality analysts. All these stakeholder are associated with the information
system development.
2. Analyzing Requirement
2.1 Functional Requirement: FR involved in the project are
1. This IS system will store two types of customers, ordinary customers and session ticket
customers.
2. The system will be able to store the details of the customers in the system.
3. The system will also store the payment details in the system as per the customer
payment for the season ticket. When the season expires, the customers get notification.
4. The system will also store the details of the payment that are made by the ordinary
customers in the system.
5. The entry time and the exit time of the car through the gate is stored in the system.
6. The record of the Video of the car parking are will also be stored in the system.
2.2 Non-functional Requirement: NFR involved in the project are:
1. The system will work for all 24 hours a day as because the car parking is opened all the
day long.
2. The system will be accessible to all the customer and many customers can access the
service at a particular time.

4BUSINESS ANALYSIS
3. The system will also be secured as the data stored in it will be secured through
encryption process.
3. Requirement Specification Validation and elicitation
3.1 Requirement Elicitation Technique: The requirement elicitation technique that is
used for data gathering in this system is observation technique and through prototyping method
(Nisar, Nawaz and Sirshar 2015).
In observation technique, the developer needs only to capture the existence of the system
and enables all the requirement tools that are needed to establish the use case scenarios in the
system (Carrizo, Dieste and Juristo 2017). It is needed for the analyst to observe the different
types of business process and as well as diagramming method to develop the information system
for the car parking system.
In the prototyping method, the system design can be analyzed using the prototyping
method of elicitation (Yousuf and Asger 2015). The analyst can design use case diagram, class
diagram, sequence diagram, activity diagram and even can develop a prototype for the system
that is being developed.
3.2 Tool used for Requirement Elicitation Technique:
The tool that can be used for requirement elicitation technique RequisitePro tool. This
tool is mainly used for making the requirement of the system easier. This tools makes the
requirement of the case model easy so that the team can focus on the software development
process of the application that is under process. The RequisitePro tool is used for improving the
development process and also helps to maximize the objective of the project that is undertaken

5BUSINESS ANALYSIS
(Garg, Agarwal and Khan 2015). This tool of elicitation helps to provide a high standard quality
product and is capable of handling the errors that comes while system development.

6BUSINESS ANALYSIS
Bibliography
Carrizo, D., Dieste, O. and Juristo, N., 2017. Contextual attributes impacting the effectiveness of
requirements elicitation Techniques: Mapping theoretical and empirical research. Information
and Software Technology, 92, pp.194-221.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), pp.7-13.
Khan, S., Babar, M., Khan, F., Arif, F. and Tahir, M., 2016. Collaboration Methodology for
Integrating Non-Functional Requirements in Architecture. the Journal of Applied Environmental
and Biological Sciences (JAEBS), 6(4S), pp.63-67.
Nisar, S., Nawaz, M. and Sirshar, M., 2015. Review analysis on requirement elicitation and its
issues. Int. J. Comput. Commun. Syst. Eng.(IJCCSE), 2(3), pp.484-489.
Yousuf, M. and Asger, M., 2015. Comparison of various requirements elicitation
techniques. International Journal of Computer Applications, 116(4).
Garg, N., Agarwal, P. and Khan, S., 2015, March. Recent advancements in requirement
elicitation and prioritization techniques. In 2015 International Conference on Advances in
Computer Engineering and Applications (pp. 237-240). IEEE.
Rafiq, U., Bajwa, S.S., Wang, X. and Lunesu, I., 2017, August. Requirements elicitation
techniques applied in software startups. In 2017 43rd Euromicro Conference on Software
Engineering and Advanced Applications (SEAA) (pp. 141-144). IEEE.