SIT725 - Web Application Design: Assignment 2 Report (Trimester 2)

This assignment report details the design and analysis of a web application, focusing on the car renting feature. It begins with a product backlog, including story mapping, product features, and user stories. The design phase utilizes UML profiles to create content, navigation, and process class diagrams, along with sequence diagrams and functional design specifications. Product planning involves creating a product roadmap, market maps, and feature/benefit analyses. Sprint planning defines sprint goals, capacity determinations, and sprint backlogs, including user stories for viewing and renting cars. The report concludes with a summary of the work done, a conclusion on the effectiveness of the design, and identifies areas for future improvement, such as enhanced security and payment options. Diagrams are included to clarify the design features.

A website Investigation And
Analysis
Group Assignment 2
Page 1 of 17

Table of Contents
1 Product Backlog.......................................................................................................................4
1.1 Story Mapping...................................................................................................................4
1.2 Product Features and Acceptance Criteria........................................................................4
1.3 User Stories.......................................................................................................................5
2 Sprint backlog- Design............................................................................................................7
2.1 UML Profile for design class models:..............................................................................7
2.1.1 Content Class.............................................................................................................7
2.1.2 Navigation class.........................................................................................................7
2.1.3 Process class..............................................................................................................8
2.2 Design Class Diagrams using your UML profile:............................................................8
2.3 Sequence Diagram............................................................................................................9
2.4 Navigation and functional design:..................................................................................10
2.4.1 Navigation Design...................................................................................................10
2.4.2 Functional Design....................................................................................................11
3 Product planning....................................................................................................................12
3.1 Product Road Map..........................................................................................................12
3.1.1 Market Map.............................................................................................................12
3.1.2 Market Map, Market Event, Architecture Map, Feature/Benefit............................12
4 Sprint planning and sprint backlog........................................................................................13
4.1 Spring Planning...............................................................................................................13
4.1.1 Sprint Goal...............................................................................................................13
4.1.2 Capacity determinations:.........................................................................................14
4.2 Sprint backlog.................................................................................................................15
4.2.1 Feature: Car Renting................................................................................................15
Page 2 of 17

4.2.2 User Story 1: View the available cars......................................................................15
4.2.3 User Story 2: Rent a car...........................................................................................15
5 Summary................................................................................................................................15
5.1 What you have done for this report.................................................................................15
5.2 Conclusion......................................................................................................................15
5.3 Whether there are some problems to be solved in future................................................16
6 Bibliography..........................................................................................................................17
Page 3 of 17

1 Product Backlog
1.1 Story Mapping
1.2 Product Features and Acceptance Criteria
Product Features Acceptance Criteria
Car Renting The system should only display available cars.
User can select and search for cars to book.
Student/Disability Support Students and disable person must have separate
rental plans.
Customer Loyalty Program The system should accept valid discount
vouchers or coupon codes.
Warranty Service User can see the warranty program by entering
the car model and year of purchase.
Repairing Service User can book repairing services through the
site.
Inspection Service User can book inspection services through the
site.
Cart Service User can add item in cart.
Page 4 of 17

Payment Process The system should accept online payment.
Catalog The system must display catalog for spare parts.
1.3 User Stories
As a I want So that
As a Customer I want to rent a car So that I can fulfill my current
need.
As a Student I want to rent a car So that I can reach my college
on time.
As a Disable person I want some special offers So that I can often book a car
for myself.
As a Buyer I want to view the available
cars
So that I can choose one for
myself.
As a Marketing Manager I want a customer loyalty
program
So that customers keep on
coming back to the site
As a Buyer I want to have warranty
services
So that I can view my
remaining warranty time or
warranty criteria.
As a Buyer I want to search for cars by
name
So that I can find my required
car.
As a Buyer I want to edit my cart So that I can add or remove
items.
As a Buyer I want to add items in cart So that I can proceed later or
sooner when feasible.
As a Service provider I want to know the customer’s
requirement
So that I can reach them and
provide services.
As a Buyer I want to view spare parts
catalog
So that I can find the
appropriate spare part for my
Page 5 of 17

car.
As a Buyer I want to search for spare parts
by name
So that the spare part from all
manufacturers will appear in
the result.
As a Buyer I want to search for spare parts
by manufacturer name
So that only required
manufacturer parts appear.
As an Admin I want to view Cart Items So that I can remove them
when they are there for a
specific time limit.
As a Buyer I want online payment services So that I can pay online
remotely.
As a Buyer I want a secure web
environment
So that I can enter my
card/bank details for payment.
As a User I want the ease of access So that I can use the website
smoothly.
As a Supplier I want to view the orders for
spare parts
So that I can supply the
required items.
Page 6 of 17

2 Sprint backlog- Design
2.1 UML Profile for design class models:
2.1.1 Content Class
2.1.2 Navigation class
Page 7 of 17

2.1.3 Process class
2.2 Design Class Diagrams using your UML profile:
Page 8 of 17

2.3 Sequence Diagram
Page 9 of 17

2.4 Navigation and functional design:
2.4.1 Navigation Design
Page 10 of 17

2.4.2 Functional Design
Page 11 of 17

3 Product planning
3.1 Product Road Map
3.1.1 Market Map
Market Map Target Customers Business Values
Car Rental  Students
 Disabled
 Searching cars
 Apply discounts
 Loyalty programs
 View catalogs
Car Maintenance Service  Car owners  Warranty Services
 Repairing services
 Buy services
 Car Inspections
Spare Parts Purchase  Car owners  Payment Process
 Catalogs
 Search for parts
 View cart
 Checkout
3.1.2 Market Map, Market Event, Architecture Map, Feature/Benefit
Q1 Q2 Q3
Market Map Students, Disabled Car Owners Car Owners
Market Event Provide rental
services to the
customer
Improve the car
services which are
provided to the
The spare parts
required for the
clients would be sold
to them.
Architecture Map Ruby, Perl Php, Javascript iOS and Android
platforms
Page 12 of 17

Feature/Benefits  Searching
cars
 Apply
discounts
 Loyalty
programs
 View catalogs
 Warranty
Services
 Repairing
services
 Buy services
 Car
Inspections
 Payment
Process
 Catalogs
 Search for
parts
 View cart
 Checkout
4 Sprint planning and sprint backlog
4.1 Spring Planning
4.1.1 Sprint Goal
4.1.1.1 Goal 1
The main goal is to provide the users with the searching of cars. This goal is to be
fulfilled in the first sprint.
4.1.1.2 Goal 2
The system should be able to provide the users with the option to rent a car for
themselves. This goal is to be fulfilled in the first sprint.
4.1.1.3 Goal 3
The system should be able to check the warranty for a particular car. This goal is to be
fulfilled in the second sprint.
4.1.1.4 Goal 4
The system should be able to allocate services to the cars after the warranty check. This
goal is to be fulfilled in the second sprint.
4.1.1.5 Goal 5
The system should have an inventory where details of all the spare parts required by the
clients are shown to them. This goal is to be fulfilled in the third sprint.
Page 13 of 17

4.1.1.6 Goal 6
The product can be purchased by the clients in the system. This goal is to be fulfilled in the
third sprint.
4.1.2 Capacity determinations:
4.1.2.1 Server Capacity
The large amounts of data which would be generate in the business of the organization
would be stored in the severs and the servers would be used for handling large amount of
procedures.
4.1.2.2 Market Capacity
The clients of the organization would be very interested in the system as the system
would be helpful for them to obtain the services of the organization.
4.1.2.3 Design UI
The user Interface would be useful for the system as the User interface should be easily
accessed by the users of the system. The navigation options and surfing in the system should be
an easy process for the users.
4.1.2.4 Technology
The php language would be used for the development of the website of the company. In
the further system developments, the applications for the mobile versions would be developed
which would take place in the future.
4.1.2.5 Backend
The integration of backend would be done with the help of PHP which would connect the
cloud with the application.
4.2 Sprint backlog
4.2.1 Feature: Car Renting
4.2.2 User Story 1: View the available cars
4.2.2.1 Tasks
 Select preferences
Page 14 of 17

 Search cars
 View Availability
4.2.3 User Story 2: Rent a car
4.2.3.1 Tasks
 Select Car
 Opt for rent
 Make payment
5 Summary
5.1 What you have done for this report
The report has been developed for the purpose of understanding the feature of car renting
offered by the system. At first stage I have focused on developing a product features along with
the acceptance criteria. After that user story has been prepared so that it becomes easy to
understand the activities that will be performed by the system. Based on the features offered by
the system Sprint backlog design has been prepared. In addition to this I have also designed the
navigation design for the system for understanding the activities more clearly. Lastly the focus
was on planning the product. In the report I have focused entirely on outlining the designing
feature of the system so that it becomes easy to understand the functionality. It can be stated that
with the use of enterprise architecture it will become easy to outline the design of each
interphase. The report has included 7 diagrams for clearly understanding the features offered
with car renting.
5.2 Conclusion
Thus from the above report it can be concluded that with proper designing and analysis off
the system it will become easy to manage the car renting features. It is important to prepare the
market map for understanding the product details. With the help of the table it will become easy
for the users to identify the users and the business value of the designed system. In addition to
this the report has also highlighted the product features effectively so that it becomes easy to
determine the performance offered within the system. Thus with the help of the implemented
system and analysis it will become easy to identify the benefits that will be offered by the car
Page 15 of 17

renting feature. The system will be able to meet the needs of the customer by providing a better
environment towards the car renting system.
5.3 Whether there are some problems to be solved in future
After analyzing the features offered with car renting it can be stated that there is a need to
implement better security aspects so that each data can be restored effectively within the system.
In addition to this the system should allow the user to opt for offline payment system as this will
reduce the chances of fraud cases for the organization. The data of each customer should be
maintained effectively within the system so that it can ensure a better way of managing the data
within the system. The security aspect will ensure that each data has the potential to provide
better support towards the organization.
Page 16 of 17

6 Bibliography
Braude, E. J., & Bernstein, M. E. (2016). Software engineering: modern approaches. Waveland
Press.
Fitzgerald, B., & Stol, K. J. (2017). Continuous software engineering: A roadmap and agenda.
Journal of Systems and Software, 123, 176-189.
Mall, R. (2018). Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Page, C. (2017). Software Engineering. Larsen and Keller Education.
Page 17 of 17