Software requirement specification(SRS)

SRS for Cool Ski Resorts Booking System
Page 1
Group 13
ASSIGNMENT COVER SHEET
SUBJECT NUMBER & NAME NAME OF STUDENT(s) (PRINT CLEARLY) STUDENT ID(s)
32569
Enterprise Business
Requirements
SURNAME FIRST NAME
MohammadEmon 12794121
Wei XXXX 9xxxxx
YeXXXX 12xxxxx
ASSESSMENT ITEM NUMBER
Assignment 2-SRS
NAME OF TUTOR:
Associate Professor Kaska
Musial-Gabrys
GROUP ID:
13
Tutorial day and time:
Wednesday and 3pm
☒ I confirm that I have read, understood and followed the guidelines for assignment submission and presentation.
☒ I confirm that I have read, understood and followed the advice in the Subject Outline about assessment
requirements.
☒ I understand that if this assignment is submitted after the due date it may incur a penalty for lateness unless I
have previously had an extension of time approved and have attached the written confirmation of this extension.
Declaration of originality: The work contained in this assignment, other than that specifically attributed to another
source, is that of the author(s) and has not been previously submitted for assessment. I understand that, should
this declaration be found to be false, disciplinary action could be taken and penalties imposed in accordance with
University policy and rules. In the statement below, I have indicated the extent to which I have collaborated with
others, whom I have named.
Signature of student(s) Date: 30-4-
2018
Signature of student(s) Date: 30-4-2018
Signature of student(s) Date: 30-4-2018
Signature of student(s) Date
Signature of student(s) Date

Group 13
Checklist
1
One Relevant model for the system (ERD & Class Diagram)
×
2
Full Software Requirements Specifications (SRS) using IEEE
template provided ×
3
One Traceability matrix using the template provided
×
4
All the use cases you submitted for your assignment 1
×
5
The Minutes of all three Stakeholder meetings using the
template provided ×
7
Individual contribution (One-page reflections by each group
member) ×

Group 13
Software Requirements
Specification
for
Cool Ski Resorts Booking
System
Version 8.0
Preparedby
Wei XXXXX 9xxxxx,
Yexxxxxx 12xxxx,
Mohammad Emon 12794121,
University of Technology,Sydney(UTS)
Date created: 25-04-2018

Group 13
Table of Contents
1. Introduction 7
1.1 Purpose 7
1.2 Document Conventions 8
1.3 Intended Audience and Reading Suggestions 8
1.4 Project Scope 9
1.4.1 Project boundary diagram: High-level use case diagram 9
1.4.2 In Scope 10
1.4.3 Out of Scope 10
2. Overall Description 11
2.1 Product Perspective 11
2.2 Product Features 12
2.3 User Classes and Characteristics 13
2.4 Operating Environment 14
2.5 Design and Implementation Constraints 14
2.6 User Documentation 15
2.7 Assumptions and Dependencies 15
3. System Features 16
3.1 Use Case Descriptions 16
3.2 Class Diagram 32
3.3 Entity Relationship Diagram (ERD) 33
3.4 User Story Map 34
4. User Interface (Non- functional requirements) 35
4.1 User Interface Samples 35
4.2 Hardware Interfaces 40
4.3 Software Interfaces 40
4.4 Communications Interfaces 40
5 Other Nonfunctional Requirements 40
5.1 Performance Requirements 40
5.1.1 Response time 40
5.1.2 Workload 40
5.2 Security Requirements 40
5.3 Compatibility requirements 41

Group 13
References 42
Appendix A: Issues List 43
Appendix B: Individual Reflection 44
Wei Joon Low 44
Mohammad Emon 45
Yeqian Zhu 46
Appendix C: Meeting Minutes Template 47
Appendix D: Traceability Matrix 54

Group 13
Revision History:
Name Date Reasonfor Changes Version
Low 13-04-
2018
Initial Draft 1.0
Low, Emon, Zhu 20-04-
2018
Re-edit use case description, Add ERD and
Class diagram
2.0
Emon 23-04-
2018
Add high-level priority to use case description 3.0
Zhu 25-04-
2018
Modify and add User story and user interface
design
4.0
Low,Zhu,Emon 27-04-
2018
Update reference 5.0
Low, Zhu, Emon 29-04-
2018
Final edit and fixed 6.0
Low 30-04-
2018
Edited for page separation and added traceability
matrix final version
7.0
Low 30-04-
2018
Final Cosmetic Changes 8.0

Group 13
1. Introduction
1.1 Purpose
The purpose of this document is to present and document the business requirements of the ‘Cool Ski
Resorts Online Management System’.The new online system will create a convenient and efficient
website for customers who can complete the booking process online.The Cool Ski Resorts
Company staff can easily handle the daily business, generate the reports and post advertisement via
the new system.Above all, the new system will improve the customers experience and work
efficiency to attract more regular customers in the future.
The system that has been designed consists of a website, a room booking system, equipment
bookings, ski class bookings, class scheduling, payments, equipment/inventory management,
feedback reports, financial reports as well as management of advertising material.

Group 13
1.2 Document Conventions
Requirement Priority indicators that were used in this document:
H = High. These requirements must be met before the project can be launched.
M = Medium. These requirements should be met unless there are compelling reasons for delays
L = Low. These requirements are not absolutely needed for project launch.
This document was organized in accordance with the Software Requirements Specification template
of the IEEE.
1.3 Intended Audience and Reading Suggestions
This document is intended to be read by stakeholders of the project to provide an overview of the
project plan as well as developers of the project. Stakeholders include the project sponsor (Owner of
Cool Ski Resorts Mary Smith), Resort Staff who will be the eventual users of this new System and
the business analyst team members.
This document is organized in accordance with the IEEE SRS template and will provide an overall
description of the project with regards to features, user classes, implementation constraints and
assumptions followed by details of the system features in the form of Use Case Descriptions and
Diagrams and closing with Non-Functional Requirements.

Group 13
1.4 ProjectScope
1.4.1 Projectboundary diagram: High-level use case diagram

Group 13
1.4.2 In Scope
This project is intended to fulfil the requests set forth by the owner of Cool Ski Resorts in the
documents provided to us as well as through past interviews.
This project will consist of an online room, class and equipment booking system, an inventory
management system, payment handling, class scheduling system, customer feedback management,
accounting system, as well as a social media advertising management system.
The new online system will be built to be accessed primarily through the Resort website. Some staff
only features will not be available unless via internal intranet. All secure access will be
authenticated either via staff login credentials or guest details.
1.4.3 Out of Scope
Processing of payments will not be handled directly by the website for security and privacy reasons.
Payment processing is out of the scope of this project and will be handled by the bank’s processing
system. The payments system of this project will hand off processing of payment to the bank and
receive and record an approved or denied message.
Actual accounting and financial management will not be handled by this system as it is not designed
to replace accounting staff. This accounts management system is intended to make it easier and
more efficient to gather and query accounting information such as payments and purchases made. It
is intended to be a digital alternative to the current paper only system.
This SRS does not take into account the mechanics of network security and management as well as
bandwidth requirements. These details are beyond the scope of the project requirements and can be
determined by network management staff or developers. While basic security is taken into account
such as hashing of stored passwords, actual security protocols should be implemented by qualified
security experts.
Creation of staff login credentials can be accomplished by the IT Manager or any other staff
member with administrative access, the process for this to be done is out of the scope of this project.

Group 13
2. Overall Description
2.1 Product Perspective
This product is intended to be built for a single resort within the Cool Ski Resorts chain as specified
by the Owner Ms. Smith.
In our previous meetings, Ms. Smith has specified that this project is required to interface with
online systems of the other two resorts in her resort chain. Taking this information into account, we
have designed the system to be more of a standalone system, reducing dependency to the other
resorts where it is not necessary. We understand that for the sake of accounting and financial
management, integration between the two resorts is required and as such, this has been included in
the project plan.
In accordance with Ms. Smith’s requests, this project has been designed to digitize the current
method of operations of the resort and move away from operations being ‘only on paper’.
Implementing this project will allow for the automation of mundane administrative tasks such as
record keeping and manual data retrieval. It also allows for new capabilities that were not feasible
with paper only systems such as guest logins and online bookings as well as credit card payments.
Overall, this system aims to improve productivity of resort staff, improve efficiency by reducing
time taken to complete administrative tasks and create an overall better experience for guests by
allowing them to have control over tasks such as payments and bookings.

Group 13
2.2 Product Features
The product will be primarily interacted upon by users through the webpage. This allows for guests
to access room, class and equipment booking information all through their preferred device, be it a
computer or mobile device.
Through this web page, users are then able to view information regarding the resort as well as view
social media posts, advertising material and a current weather report which they may click to visit
Google Weather forecasts for the Resorts exact location.
Furthermore, guests will then be able to view skiing class availabilities without a room booking in
order to better decide when they would like to book rooms for. Guests can then make reservations
for their rooms and pay by credit card after providing some personal information. This process can
also be accomplished at the front desk by staff using their staff login credentials.
Upon first login for guests, they will be presented with a prompt to set 2 security questions. This
will allow them to reset the passwords to their accounts while they stay at the resort. Customer
personal details not required for accounting and legal purposes will be removed 14 days after
checkout. This is due to the fact that customers will be given 14 days to leave feedback about their
stay using these account credentials to verify that the feedback is left by an actual resort guest.
While staying at the ski resort, customers may book skiing classes and/or hire skiing equipment
using the website and their login credentials. They will also be able to make payment via credit card
on the website. Booking of equipment is free if the guest has already booked a class.
The following features should be accessible only via local intranet where possible.
The system has also been designed to allow for staff to manage inventory and remind staff members
as to what equipment needs to be replaced and when. This allows for the inventory staff to operate
in a paperless manner, reducing waste and preventing the loss of documentation as well as allowing
for audit trails.
Besides that, accounting staff will be able to easily query and view financial records of the resort
and consolidate them with the other 2 resorts’ systems if required. This allows for the elimination of
paper records and increased efficiency when processing accounts and taxation information.
Administrative tasks such as customer feedback report and guest user account management can also
be accomplished by customer service staff using this system which is capable of collecting and
generating reports of customer feedback. To begin with, the Owner and IT Manager are by default,
allocated administrative privileges and have the ability to change and adjust any details within the
entire system such as fee waivers, password changes, account removal, etc.
Lastly, the system is also capable of allowing for marketing staff to upload social media posts with
marketing material to add to social media accounts and display on the website for the purposes of
increasing the resort’s social media outreach.

Group 13
2.3 User ClassesandCharacteristics
This system will be used by 2 primary groups of users which can be categorized into 3 skill levels.
The two groups are those of Resort Guests and Resort Staff. They can be sorted into 3 skill levels:
A. Completely unfamiliar with IT facilities or unwilling to use
B. Average user with basic knowledge on IT facilities
C. Skilled or professional knowledge and grasp of IT facilities
This system has taken into account for guests who are unable, or unwilling to use IT facilities while
staying at the resort or booking their stay. Hence, customer service staff will have access to be able
to accomplish any tasks that a guest may perform on their behalf such as booking a room or hiring
equipment. Having customer service staff perform these roles will increase the workload on the
staff members, but will not require any direct contact between the system and the customer,
allowing them to enjoy their stay without being forced to use a system that they are not able or do
not want to use.
We expect most guests and staff members to fall under the category of average user with experience
in some form of regular computer or IT facility use. The webpage will be designed to be intuitive to
navigate for most average users and they should not have any issues if prompts and notices are
followed. Training material will be provided for staff members to familiarise themselves with the
systems concerning their job roles before it is fully launched to the public. It is recommended that
staff members should be able or qualified to use and navigate common IT facilities.
Members of the IT management staff are expected to be skilled at navigating and using IT facilities
and will be given full administrative access to the system for the purposes of maintenance and
troubleshooting. Oversight of their privileges is at the Owner’s discretion. Detailed documentation
of the system will be provided as well as training material for their reference.

Group 13
2.4 Operating Environment
While actual details regarding the physical system is to be determined by developers due to the
limited scope of knowledge of the business analyst team, it can be stated that the new online system
will mainly leverage the existing facilities of the current website. While bandwidth and hardware
upgrades may most likely be required, the current architecture can largely be maintained.
The website is expected to be hosted on an Apache server that is in-house and resides on hardware
that will be maintained by the IT Management team. This can be executed in the form of a virtual
machine to allow for growth of website traffic in the next two years. Having the web server run on a
virtual machine will allow for extremely easy migration of the web server in the event that the
owner wishes to outsource web hosting to an external company. A database server is also expected
to reside on the virtual machine for the purposes of storing and retrieving data.
Due to the web-based nature of the system, it will be largely compatible with any device that is
capable of internet access and has a web browser. The website will be coded with industry standard
practices to keep compatibility issues to a minimum.
With Google Chrome being the most popular web browser in the world (Vaughan-Nichols 2017),
special care will be taken to ensure optimum compatibility. As such, Google Chrome will be the
recommended web browser for staff use.
Compatibility of the online systems of the 2 other resorts will also be taken into account with focus
primarily on database access as the accounting staff will require access to the accounting
information of the other two resorts. More information will be needed regarding the other two
resort’s systems to be able to conclusively state what needs to be done.
2.5 Designand Implementation Constraints
Current constraints will be that of the interface between this system and the existing systems of the
two other resorts. Developers will be required to implement support for accessing the other resorts’
database or system. More documentation is required at this stage for better analysis.
The other constraint is to digitize all existing paperwork to allow for a transition from hard copy
documents to an electronic system. While this is out of the scope of the operations of the project,
implementing a system to make this possible will likely be required. More communication is
needed to determine what if anything is required to make this possible.

Group 13
2.6 User Documentation
Training manuals for staff will be included that reflect the Use Case Descriptions below. These
manuals will include step by step instructions on how to perform each task and what can be
achieved. It is recommended that staff only be trained for systems that concern their positions as to
prevent and confusion. Detailed documentation on the development and deployment of the system
will be provided to the IT Management staff to hand-over operations.
Besides training manuals, training workshops will also be held to formally train and assess staff
members in the usage of the new system and to allow time for staff to familiarise themselves with
the online system. Staff members who have proven to be experts in the usage of their respective
systems may be designated to assist in the further training of other staff members.
2.7 Assumptions and Dependencies
1. All current payments are handled by cash.
2. All payments on the new system are electronic. No cash is to be accepted.
3. User login details will be created upon booking (customers) or upon the start of their
employment (staff).
4. Staff access control is predetermined. Staff cannot access systems that are not part of their
job.
5. All credit card processing is handled by the bank’s system and beyond the scope of the use
cases.
6. Google weather updates are controlled by Google and beyond the scope of the use cases.
7. CEO and IT Manager/Management staff has full administrator control of all internal systems
and may make edits to any details in any use case.
8. Financial management is done by qualified accountants, and accounting system and method
are industry approved.
9. IT management staff exist to conduct maintenance of the system (out of the scope of use
cases).
10. Accounting staff have access to financial information and payment invoices of all resorts.
11. Accounting will no longer be conducted in each resort separately.
12. Trainers have authority to enforce rules for child classes. (Children under 5 or
unaccompanied children will be denied service as agreed by the customer on the web page).
13. Any exceptions to use cases not listed in the exceptions list will be managed at CEO’s
discretion (override using CEO login credentials).
14. In the “Manage Advertisement” use case, plugins exist for marketing staff to have full
control over all social media accounts and marketing material.
15. Credential validation and cross use case validation is handled by the internal database.
16. All sensitive information is stored in a secure manner using industry standard encryption.
17. Network security and management is performed by IT staff
18. Only accounting information is required to be retrieved from the other two Cool Ski Resorts
19. All resorts are operationally independent
20. Staff are expected to be able to use IT facilities as part of hiring requirement.

Group 13
3. System Features
This section describes the system features in the form of use case descriptions. Use case
descriptions have been created to view the features and usage of the product from the user’s
perspective.
3.1 Use Case Descriptions
3.1.1 Use Case: Customer Service Staff: Check Room Availability
UC 1 Check Room Availability
Summary Customer Service Staff can Check Room Availability
Priority Rated High: H
Preconditions None
Success End
Condition
The staff member can see how many rooms are available/vacant (zero
or more).
Failed End
Condition
No result is shown. The error message is displayed.
Primary,
Secondary
Actors
Customer Service Staff (Primary)
DESCRIPTION Step Action
1 Customer enquiries customer service staff regarding room
availability.
2 Staff member logs into the internal system
3 A staff member can view the number of rooms available to be
booked
4 The customer is informed by a staff member about the results of
the query.
EXTENSIONS Step Branching Action
4a Customer wishes to book an available room. Proceed to UC2

Group 13
3.1.2 Use case: Staff and Customer: Reserving a room
UC 2 Reservation
Summary Customer Service Staff Can Reserve a Room on Behalf of Customer
Customer may book their room
Preconditions Rooms must be available to be booked
Success End
Condition
The room is successfully booked under the customer’s name.
The customer receives a booking confirmation email
Failed End
Condition
No result is shown.
Payment is Declined.
Primary,
Secondary
Actors
Customer Service Staff, Customer (Primary)
Bank (Secondary)
1 A staff member or customer (bundled as User) visits the website
2 The user enters customer details into booking field.
3 The user selects check in and check out date
4 The user enters payment details
5 Bank approves payment
6 Booking is reserved under the customer’s name, and a
confirmation email is sent to customer’s email address.
1a.
5a
5b
1-4
5c
5d
Staff member logs into the website using their staff login details
Bank declines the payment.
Website returns to payment information page to request for an
alternative form of payment.
User cancels booking process. Web page returns to home page.
Payment page times-out due to lack of activity.
Return to step 5b

Group 13
3.1.3 Use Case: Customer: Check Weather condition
UC 3 Check Weather Forecasts
Summary A customer checks local weather conditions
Priority Rated Medium: M
Preconditions Google Weather service must be available
Success End
Condition
The customer can view up to date weather forecasts for the local area
Failed End
Condition
No result is shown.
The error message is shown
Primary,
Secondary
Actors
Customer (Primary)
Google (Secondary)
1 Customer visits website
2 Current weather is displayed on the homepage
3 Customer may close the webpage
2a
2b
If the customer wishes to view more detailed weather
information and forecasts, the customer may click on weather
widget on the home page.
The browser loads Google Weather page with detailed forecasts
for the local area of the ski resort.

Group 13
3.1.4 Use Case: Customer: Check training class Availability
UC 4 Check Class Availability
Summary Customer checks availability of skiing classes
Preconditions None
Success End
Condition
The customer can view available classes with vacancies
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Customer (Primary)
1 Customer visits website
2 The customer can view times and dates for available classes
2a Customer wishes to book an available slot. Visit UC 5.

Group 13
3.1.5 Use Case: Customer and Staff: Book training class
UC 5 Book Class
Summary Customer or Customer Service Staff (on behalf of the customer) may
book an available class
Preconditions Classes must be available to be booked
Success End
Condition
The class is successfully booked under the customer’s name
Failed End
Condition
No result is shown.
Error message is shown
Primary,
Secondary
Actors
Customer (Primary)
Trainers (Secondary)
1 User visits website
2 User visits class booking webpage
3 The user provides login details (customer: Room number and
last name. Staff: Staff login details)
4 The user is presented with class options (Adult or Child Classes)
and trainer name.
5 The user is presented with a form to fill in number of attendees
and contact details
6 The user is taken to the payment page where payment can be
made for the selected class(es).
7 The class slot is successfully booked. The customer receives a
confirmation email.

Group 13
4a
5a
Customers who book Child Classes are required to acknowledge
that their child(ren) are over five years of age and will attend the
class accompanied by an adult. Failure to meet these
requirements will result in the service being denied.
If payment is cancelled or declined, an error is presented, and
the user is taken back to booking page where they may attempt
to make payment again.

Group 13
3.1.6 Use case: Customer and Staff: Check Inventory Availability
UC 6 Check Equipment Availability
Summary Customer or Inventory Management Staff may check for equipment
availability
Preconditions None
Success End
Condition
Available equipment to the book is displayed to the user.
Staff may be alerted to replace old inventory.
Failed End
Condition
No (non-zero) result is shown.
Primary,
Secondary
Actors
Customer (Primary)
Inventory Management Staff (Primary)
2 User visits equipment availability page
4 The user is presented with equipment list and corresponding
units available
5 The user may then exit the page
4a
4b
User logged in as staff will be presented with equipment list and
units available as well as dates to replace equipment and alerts
for any equipment that needs to be changed.
The user may acknowledge alerts or flag items as “replaced” to
reset the date to be replaced (pre-determined number of days)
for each equipment type.

Group 13
3.1.7 Use Case: Customer and Staff: Book Equipment
UC 7 Book Equipment
Summary Customer or Customer Service Staff (on behalf of the customer) may
book for equipment
Preconditions Equipment must be available to book
Success End
Condition
Equipment is successfully booked under the customer’s name.
Failed End
Condition
No result is shown.
Page is closed
Primary,
Secondary
Actors
Customer (Primary)
Bank (Secondary)
2 User visits equipment booking page
4 The user is presented with equipment list and may select
equipment to be booked and fill out customer details in a web
form.
5 The user will be presented with the option to enter class booking
details for class booked under the customer’s name or to skip
and proceed to next step.
6 User skips details and is taken to the payment page
7 Equipment is successfully booked under the Customer’s name,
and the customer receives a confirmation email.

Group 13
5a
6a
5b
6b
6c
Customer enters details of class booked under their name which
is verified.
Proceed to step 7
Class verification fails, return to step 5
Payment is declined. Return to step 5
Payment page times out. Return to step 5

Group 13
3.1.8 Use Case: Customer: Leave feedback
UC 8 Leave Feedback
Summary Customer may leave feedback via web form
Priority Rated Low: L
Preconditions Customer must have been a guest at a resort in the last 14 days
Success End
Condition
Feedback and customer contact details are recorded
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Customer (Primary)
2 User visits leave feedback page
3 The user provides Last Name, Room number and check-out
date.
4 If details are valid, the user is taken to a web page where they
may leave feedback in a text box and optionally enter their
contact details so that staff may respond to any complaints.
5 User clicks on a button to send feedback details
6 The user is prompted with a thank you message and may close
the webpage
4a
6a
If customer details are invalid, the user is presented with an
error message and may try again
If no data (all fields empty), an error message is prompted and
the user may return to enter data into the web form.

Group 13
3.1.9 Use case: Customer and Staff: Generate feedback reports
UC 9 Customer Feedback Reports
Summary Customer Service Staff or CEO can generate customer feedback
reports.
Preconditions None
Success End
Condition
The report is generated containing all customer feedback and any
contact details provided
Failed End
Condition
No result is shown.
The invalid file is generated
Primary,
Secondary
Actors
CEO (Primary)
Customer (Secondary)
1 User logs into the internal portal
2 The user selects date range required and selects the option to
generate customer feedback reports.
3 The file is generated with all customer feedback and contact
details within a date range.
2a
2b
Login details are incorrect.
The user is presented with an “unauthorised” error prompt and
may attempt to log in again.

Group 13
3.1.10 Use Case: Accountant Staff: Manage Finances
UC 10 Manage Finances
Summary Accountant Staff can view and sort financial information for all resorts
Preconditions None
Success End
Condition
Financial and taxation information is recorded, financial reports are
generated.
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Accountant Staff (Primary)
retrieve payment invoices from customer payments
3 The user may then proceed to process payment and taxation
details which are recorded in a ledger.
2a
2b

Group 13
3.1.11 Use Case: Accountant and CEO: Generate weekly financial reports
UC 11 Weekly Financial Reports
Summary Accountant Staff or CEO generates a summarised weekly financial
report
Preconditions Accounting and taxation work must exist in the ledger
Success End
Condition
Financial report file is generated.
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Accountant Staff (Primary)
CEO (Primary)
retrieve financial report(s)
3 The file is generated with summarised reports of the weeks in
which the date range is selected
2a
2b

Group 13
3.1.12 Use Case: Marketing Staff: Manage Advertisement
UC 12 Manage Advertisements
Summary Marketing Staff may manage advertising material for the website
Preconditions None
Success End
Condition
Advertising material is successfully uploaded or removed
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Marketing Staff
2 The user can view files that have been uploaded and shared
3 The user can upload and share new files, share existing files on
social media or remove existing files
2a
2b

Group 13
3.1.13 Use Case: Trainers: View class schedule
UC 13 View Class Schedule
Summary Trainers can view classes they are scheduled for.
Preconditions None
Success End
Condition
The timetable is displayed with classes that trainer is scheduled to
conduct
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Trainers
2 User is presented with a timetable of classes
2a
2b

Group 13
3.1.14 Use Case: Staff and Customer: apply Password Reset Process
UC 14 Password Reset
Summary Users are able to reset their password
Preconditions 1. Account must have been already created
2. Resort Customer must have already created 2 security questions
Success End
Condition
Password successfully changed.
Failed End
Condition
No result is shown.
Primary,
Secondary
Actors
Staff (Primary)
Customer (Primary)
IT Manager (Secondary)
1 User visits website for forgotten password
2 The user selects password reset for staff or Customer
3a
3b
4a
4b
4c
Staff will enter their work email address to receive a password
reset link.
Upon clicking the link in their email, staff will be presented with
a prompt to enter a new password twice to change it.
Customer will be presented with a prompt to answer their two
security questions.
If correctly answered, the Customer will be presented with a
prompt to enter their new password twice to change it.
If incorrectly answered, Customer will be presented with an
error message and will be allowed to re-attempt the questions.
Note 1: UC 5, UC 6 and UC 7 should be modified to include an extension for guests who are
logging in the first time to set 2 security questions to reset their account password.
This is to fulfil the requirement stated by Ms. Smith in the 3rd meeting.
Note 2: UC 14 has been added to allow for the fulfilment of password reset procedure as described
in the 3rd Meeting

Group 13
3.2 Class Diagram
Figure 2: Class Diagram for ‘Cool Ski Resorts’ booking system

Group 13
3.3 Entity Relationship Diagram(ERD)
Figure 3: Entity Relationship Diagram for ‘Cool Ski Resorts’ booking system

Group 13
3.4 User Story Map
As a customer, I want
to make payment
online, so I don’t have
to carry cash.
As a CEO, I want to query
customer feedback online
so that I can analyse
customer feedback data.
As a CEO, I want to
add social media
widgets on the
website, so that we can
attract more
Priority:
EST. 1 month
Priority: H
Priority:
EST. 1 month
Priority: H
customers.
Priority:
EST. 1 month
Priority: H
As an accountant, I As inventory staff, I want
to check the equipment
status so that I can keep
track of inventory
.
Priority:
EST. 1 month
Priority: M
As a customer, I want
to check weather
forecasts so that I can
decide whether I will
stay.
Priority:
EST. 1 month
Priority: M
want to check online
financial reports so I
can consolidate
accounting and
taxation details faster.
Priority:
EST. 1 month
Priority: M
As a trainer, I want to As a customer, I want to As a marketing staff, I As a customer, I want to
give feedback online, so it
is anonymous.
Priority:
EST.1 month
Priority: L
check training class check the equipment status want to add
schedules online so I so that I can book the promotional material
can manage my equipment. on the websiteand
timetable. social media so that I
Priority: can conduct
Priority: EST.1 month advertising.
EST.1 month Priority: L
Priority: L Priority:
EST.1 month
Priority: L
Table 1: User story

Group 13
4. User Interface (Non- functional requirements)
4.1 User Interface Samples
4.1.1 Homepage
With accordance to the requests of Ms. Smith, the homepage has been designed with a colourful
interface and intuitive layout for easy navigation which will allow customers and staff to check
room availability, log in to access their details as well as view weather forecasts for the resort.
4.1.2 Customer log in
At this page, customers are able to book rooms, ski classes and equipment, edit their information
as well as leave feedback about their stay.

Group 13
4.1.3 Check Room
On this page, customers are able to check room availability without having to log in.
4.1.4 Book Room
With this page, users are able to book a room online and make payment using their credit card via
the website

Group 13
4.1.5 Booking completion
4.1.6 Book Ski class
Customers are able to use this page to book ski classes and view ski class time tables sorted by
types: Adult and Child

Group 13
4.1.7 Book equipment
Customers using this page may check or book equipment online
4.1.8 Customer register
Upon first login, customers will be requested to create and set two security questions to their
account.

Group 13
4.1.9 Inventory adjustment
Inventory staff are able to check and adjust the quantity of equipment through this page.
4.1.10 Financial report
Financial reports can be generated online

Group 13
4.2 Hardware Interfaces
As this product is designed to be primarily web-based, the hardware on which it resides on will be
any machine that can have a Gigabit Ethernet connection or faster and can host a web server.
Besides that, this machine should also be able to run virtualisation software to host the web server
on a virtual machine to facilitate future upgrades and scalability as discussed in previous meetings.
4.3 Software Interfaces
This product will utilise various software components for its web-based functionality including
HTML, CSS, javascript, XML, JSP as well as SQL databases. An Apache web server will be
required to host the website.
4.4 Communications Interfaces
As part of its core functionality, this product will require HTTP or HTTPS communication
interfaces with client devices and be able to send automated emails to staff and customers alike. It
will also be required to communicate with remote SQL servers as well as read and write into XML
files.
5 Other Non-functional Requirements
5.1 Performance Requirements
5.1.1 Response time
The purpose of identifying the response time is to highlight the performance goal of new website
which is the minimum requirement from Cool Ski resorts CEO.
1. Normal customer response shall be less than 5 seconds for all the websites.
2. 5% bandwidth shall be given for booking regarding to the capacity of website shall be 100
people at any given time.
5.1.2 Workload
1. The new website must support 100 people at any given time and it might be double traffic
volume in 2 years.
2. The uptime goal for the new site should be 7 am to 12 pm and the daily maintenance time
should be 12 pm to 7 am. The system should be shut down during the public holiday (both
systems and operations).
5.2 Security Requirements
1. Two security questions shall be set when customers log in their account for the first time.
2. An email link shall be sent when staff want to reset their password.
3. IT manager shall have full authority over all the permissions.

Group 13
5.3 Compatibility requirements
The purpose of compatibility requirement is to emphasis the requirement of the separation system
for each resort which is developed by different companies with different systems. The new system
shall be integrated with the other two resorts.

Group 13
References
1202Performance, n.d., How to write performance requirements with example, 1202Performance,
viewed 25 April 2018,<http://www.1202performance.com/atricles/how-to-write-performance-
requirements-with-example/>
Vaughan-Nichols, S. J. 2017, Chrome is the most popular web browser of all, ZDNet, viewed 24
April 2018, <https://www.zdnet.com/article/chrome-is-the-most-popular-web-browser-of-all/>
Zowghi, D. 2018,Software Requirements Specification Part 1,UTS online Enterprise Software Requirements
subject 32569 ,Powerpoint Presentaion,UTS,Sydney,viewed 30 April
2018,<https://online.uts.edu.au/bbcswebdav/pid-2768149-dt-content-rid-22855294_1/xid-22855294_1>
Zowghi, D. 2018,Requirements Analysis & Modeling,UTS online Enterprise Software Requirements subject
32569 ,Powerpoint Presentaion,UTS,Sydney,viewed 30 April 2018, <https://online.uts.edu.au/bbcswebdav/pid-
2764208-dt-content-rid-21977952_1/xid-21977952_1>
Wiegers, K. & Beatty, J., 2013. Documenting the requirements (Chapter 10), Software requirements,3rd
edn,
Redmond, Washington: Microsoft Press, pp. 181 - 201.

Group 13
Appendix A: Issues List
The only issue we are currently unable to resolve is that of the interfaces between the two other
resorts. We are unable to provide definitive information regarding it at the moment due to lack of
information about the other two systems. However, we are confident that a solution can be
achieved and it is only a matter of getting the information required to complete the task.

Group 13
Appendix B: Individual Reflection
Wei JoonLow
Throughout this assignment, I have learnt about the importance of interviews in the requirements
elicitation process. Without speaking to someone who is the intended user or customer, it is nearly
impossible to get a true picture of what a project should be like. Building a project purely out of
assumptions will likely result in projects that end users will not enjoy, do not achieve the
customer’s intended tasks or one that users will outright refuse to use.
Interviews have hence helped build a baseline of current operations which helps analysts plan a
project that emulates current operations while still achieving the intended goals of the customer.
This allows for a reduced aversion towards the new project by users as the ‘logic’ of their tried and
tested old ways of working are emulated digitally into a new system. Apart from making it less
daunting, it also helps with training users on the new system as they can view the processes of the
new system in relation to the old.
I have also learnt the importance of good documentation practices and document handling. Proper
documentation practices allow for auditing of any mistakes as well as minimizing data losses
through having multiple versions throughout the process of developing the document.
With regards to this assignment, I have learned the importance of proper work delegation to group
members with regards to abilities and time. It is important to take into account a group member’s
strengths and weaknesses as well as availability when delegating work. Often, work is divided
equally amongst all group members with each member taking an equal share. While this method
may seem fair, it is often an inefficient method of dividing up work. I have found that in this
assignment, dividing up work by group member’s ability and experience is far better and has better
results. Even though one group member may appear to receive more work than another, a group
member who is better at writing than another who is better at developing diagrams will both feel
that they have the same amount of work as they are able to complete their assigned tasks faster and
with relative ease, allowing for an overall better-quality result and satisfied group mates.
Besides that, I have found that the interviews that were conducted for this assignment were quite
limited in scope and did not allow enough breadth for us to explore more into the case study itself.
The meeting schedule availability also proved to be an issue as 2 out of 3 of our group members are
employed and it is very difficult to adjust to fit the time slots available. Having only 1 person
(stakeholder) to interview was also hard as it did not allow for a range of information that would be
available from different perspectives and people. However, we did find that our questions often
were not specific enough or did not probe deeply enough into a particular topic. This fact was not
apparent to us until meetings were over and development of the written work began.
Overall, this assignment was a good learning experience, allowing for exploration into a topic I
have thus far been unfamiliar with and allowing my group and myself to explore different ways of
delegating work and completing the assignment effectively and efficiently.

Group 13
Mohammad Emon
Before doing this course, I have basic knowledge of the software design and elicitation
techniques.Although, the exciting part is meeting with the stakeholder which is a real practical
experience that is amazing. I learned how to express and ask a question and get the requirement
elicitation as necessary from the clients.This improved my communication skills which are lack of
nowadays as most of the student. Besides, this assignment helps me to go through the designing of
use case and data modelling technique which is an essential part of communicating with the
stakeholders.Before this, I have no experience with writing SRS document. I learnt the crucial skill
to be successful “business analyst ‘ for my future career by doing practical writing SRS and known
the rules and guidelines which I enjoyed my learning.However, I also learnt by consulting to tutor
and getting help from previous student work.
On the other hands, there are only a few factors to talk about the missing part of the course, which
can be improved for future work. For example, it will be great helpful the tutorial class be more
than 1 hour, which is now very limited only 1 hour. Besides, the meeting with stakeholder which I
like the idea is very short limited time.It will significantly help if we interview real-life case
industry scenario which will engage student more and a chance to get real industry level experience
form the clients for “requirement elicitation”.

Group 13
Yeqian Zhu
Individual reflection
Our case is about eliciting the requirement of Cool Ski resort company and analysing the user need
and documenting the whole process for stakeholders to understand the project. We formed a group
of three to breakdown the tasks for the whole project. I am mainly responsible for the quality
assurance for the meetings to make sure we have got all the answer we need and assist the whole
process.
Planning and process
At the first beginning, we analysed the information we had to identify the scope for the new system
which our customers would like and recorded the questions for the further information we need for
the first interview. We prepared the questions which involved in the general concept of the whole
project, for example the expected output and performance of current system.During the first
meeting, I recognised that the communication skills are very important for eliciting the
requirement. The interviewer sometimes could not understand our questions clearly which are too
complicated regarding the way we asked her and we also had to pay attention to the way we
organised the mins which should be clear and easy to understand by every stakeholder. We decided
to narrow down the questions for our second interview to get the specific requirement for the whole
new system and simply the questions for better understanding. We improved our interviewing skills
during the second meeting and finally we did a great job for the last one. At the end, we
documented all the requirements in the software requirement specification by description, use case
and ERD diagrams.
Reflective evaluation
According to this case study, I have learnt the whole process about eliciting the user requirement in
a practical way. In my perspective, understanding and delivering the user requirement is important
for initiating the project. It also requires the comprehensive skills, for example, the knowledge for
eliciting the requirement, the communication skills for talking to the interviewees, the technical
skills about use case and ERD diagrams. Overall, the whole case study helps me understand the
whole process and the skill we need in the real world and identify the skills I have to learn.

Group 13
Appendix C: Meeting Minutes Template
Meeting with Stakeholder - Agenda and Minutes 1:
Group ID: _13
Date/Start Time: 26/03/2018 2.55pm
Group Members Present
Names Roles played in this meeting
1. Mohammad Emon Administrative Assistance
2. Yeqian Zhu Quality Assurance
3. Wei Joon Low Group Leader
Agenda prepared before this meeting
List of agenda items/Questions Outcomes/answers
1.How does the current system work?
What is your view of success for the
project? What is your target for social
media/website outreach?
- Online system is limited and
customer checks availability of
training classes.
- Increase the number of customers
especially more regular customers.
- Twitter page, Facebook page to
introduce resort to more people.
Goal is to mainly have a presence,
no numerical goals at the moment.
2. How are payments currently handled?
What is the process? How would you feel
about a consolidated online booking
system? Do you have any
concerns/feedback?
- payments handled by hand right
now and would like to enable
online payments for customers.
- Improve the time for payment
process
- Current feedback from customers
via Emails and they prefer get the
feedback online. (refer to customer
service section)
3.What functionality do you need for hiring
and inventory management on the web
system?
- Equipment count numbers should
be adjusted every month. For other
equipment, for example, gloves and
clothes should be changed every 6

Group 13
months. Alert system should be
changed as well.
- Implement equipment hire/booking
system for customers, integrate
with training session booking.
4. How does the current reservations
system work? What do you want for an
online booking system? What input do you
have if such a system would be
implemented?
- Currently, they can check the room
and training class information
online.
- Put every function online for
customers and clerks. For example,
training classes can be booked
online for adults and the other for
children (over 5 years old with an
adult)
5.What difficulties are you currently
experiencing regarding website
maintenance? How would you feel about a
major overhaul of the website and
potentially increased traffic?
- Ask IT manager
6. What difficulties do customers usually
face? What do customers enjoy right now?
What is your opinion on things that can be
currently improved?
- Complaints by email or calls.
- Would like to implement an online
customer feedback system on
website
- Quality of the rooms and training
classes.
- Weekly/monthly/annual reports
with customer feedback is needed.
7. Could you provide us with a list of other
people that you think we should have a
chat with regarding this project? It would
be great to gather some information from
other perspectives as well.
- Janet from Accounts
- IT manager
Other problems, questions & issues discussed during meeting not in the agenda
Problems/issues/questions Resolution/outcome/answer
1. How to check the weather and snow
condition online?
- - Link to Google Weather

Group 13
2.
4.
5.
6.
Activities/Actions planned for next meeting
Activities/Action items Name of the individual(s)
responsible for this
activity
Due Date
1. Meet IT manager TBD TBD
2. Meet account staff - Janet TBD TBD
Meeting Ended At: _3.10 am/pm

Group 13
Group ID: _13
Date/Start Time: 05/04/2018 3.10pm
1. Mohammad Emon Administrative Assistance
2. Yeqian Zhu Quality Assurance
3. Wei Joon Low Group Leader
1. In the email you sent us last week, you
mentioned some problems with the details
that we sent you. Could you elaborate more
on those issues so that we may resolve
them?
- Can’t discuss specifics
2. We’ve developed a Use Case Diagram
from the information we have gathered last
week. What are your thoughts on it? Are
there any changes you would like to make?
3.Does booking a class require payment?
Does equipment hire require payment?
4.Would you like to allow trainers to be
included in this use case? Would you like
for customers to be able to view their
trainer’s name?
- No independent opinion regarding
diagram
- Yes. Class can be checked for
everyone without logging. When
customers want to book training
class, they log in. Class booking
system will be modified to include
payment options. Equipment is free
if signed up for class. Equipment
hire will be modified to check if
class is booked.
- Yes. Trainers are included and
allowed to check the classes. Have
the trainer’s name included in
booking process. (visible).

Group 13
5.Should customer service staff have
access to customer feedback? Or should it
be exclusive to the CEO (yourself)
- Staff should be able to see feedback
and respond to customers
complaints by email. Staff should
generate feedback reports for CEO.
Other problems, questions & issues discussed during meeting not in the agenda
1. Should the class booking should be
separate from equipment booking system?
- Equipment booking should be
separate from class booking (Adheres to
current plan)
2. Can trainers change the class schedule? - Trainers should not change the
schedule and they can only check
the class (No plans for this to be
implemented, process unchanged)
3. Should the weather interface comes with
more details on the website?
- No Only simple forecast for one or
two days.
Activities/Actions planned for next meeting
Activities/Action items Name of the individual(s)
responsible for this
activity
Due Date
1. N/A
2. N/A
Meeting Ended At: _3.18 pm

Group 13
Group ID: Group 13
Date/Start Time: 12.15PM
1.Wei Joon Low Administrative Assistance
2. Yeqian Zhu Group Leader
3.Mohammad Emon Quality Assurance
1.Do you have any specific hardware ofsoftware
requirementfor the system?
Now wants to integrate system with the online
system of other 2 resorts. 2 different systems
developed by different companies different
companies for each resorts. 3 systems in total.
2. Note that due to this new system, we expect
a very high increase of web traffic to your
website as many core functionalities of your
operations will be moving to the website (room
booking, class booking, payments, etc).How
much bandwidth will the website require?
5% for bookings. 100 people at any given time.
Scaleable in the future. Double traffic volume in
2 years.
3. What are your uptime goals for the website?
(98%, 99%, 99.9%?)
7am to 12am. 12-7am for maintenance daily.
System shut down on public holidays (Systems
and operations will be down)
4. Regarding user interface design,is there any
required screen format?
Attractive colors on home page. Some videos
and images. The general screen layout is ok.
5. What kind of diagram would you prefer to
communicate with stakeholders? Would ERD be
acceptable?
ERD is okay.
6. Do you have any response time requirements for
the website and it’s features?
Less than 5 seconds for a webpage to
respond.
7. How would you like to handle situations where
users require technical supportfor the website?
(forgotten passwords,etc).At the moment,we have
designed itsuch thatthe CEO has full authority over
all the systems and mayresetpasswords.
Staff should be able to reset their own
password via an email link.
Automated email whenever a system crashes.

Group 13
Other problems, questions & issues discussed during the meeting not in the agenda
1.Regarding data security any suggestion? Customers set 2 security questions on first
login and IT manager general manager will
have full authority over all permissions.
2.
3.
4.
5.
6.
Meeting Ended At: 12.30 am/pm

Group 13
Appendix D: Traceability Matrix
Software Requirements Specifications
Functional
Requirements 1
Functional Requirements 2 Functional Requirements 3
1.1
reserva
t ion
1.2
paym
ent
2.1
check
room
availabi
lity
2.2
check&B
ook
equipme
nt
2.3
Check
& book
training
class
3.1check
weather
forcast
3.2 manage
fiance&
weekly
reports
3.3 manage
advertiseme
nt
UseCases
Use Case
1
X X
Use Case
2
X X
Use Case
3
X
use cse 4 X
use cse 5 X X
use case 6 X

Group 13
use case 7 X X
use case 8 X
use case 9 X
use case
10 X X
use case
11 X
use cse 12 X

Group 13
use case
13
X
Use Case
14 X X
FunctionalRequirementsVS Non-FunctionalRequirements
Software Requirements Specifications
Non-
Functional
Requirements
1
Non-Functional
Requirements 2
Security Performance
FunctionalRequirements1
1.1
reservation
X X
1.2
payment
X X
Functional
Requirements2
2.1
check&roo
m
availability
X

Group 13
2.2
check&boo
k
equipment
X X
2.3
check&boo
k training
class
X
FunctionalRequirements3
3.1 check
weather
forcasts
X
3.2
manage
fianace
&weekly
reports
X X
3.3
manage
advertisem
ent
X X

Software requirement specification(SRS)

Recommended

More Related Content

What's hot (20)

Similar to Software requirement specification(SRS) (20)

More from Mohammad Emrul Hassan Emon (20)

Recently uploaded (20)

Software requirement specification(SRS)