Inspection of Software Requirements Specifications (srs)

ASSIGNMENT COVER SHEET
SUBJECT NUMBER & NAME NAME OF STUDENT(s) (PRINT CLEARLY) STUDENT ID(s)
32569
Enterprise Business
Requirements
SURNAME FIRST NAME
Mohammad Emon 12794121
Wei XXXX 99xxxx
YeXXX XXX 12xxxx
ASSESSMENT ITEM NUMBER
Assignment 3
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 extensionof timeapproved and have attachedthe writtenconfirmationof this extension.
Declaration oforiginality: The work contained inthis assignment,otherthanthat specificallyattributedtoanother
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: 20-5-2018
Signature of student(s) Date
Signature of student(s) Date

Checklist
1 The front page
×
2 Entry Criteria check list
×
3 Exit Criteria check list
×
4 A full description of the inspection process used
×
5 The result of the inspection exercise in the forms provided
×
6 A discussion of the lessons learnt from the inspection
exercise
×
7 The SRS document that you have inspected
×
Group 13 1

Inspection of Software Requirements
Specifications (SRS)
32569 Enterprise Business Requirements
Assignment 3 - Autumn 2018
Inspection Team Members:
Wei xxxxx x – 99xxxxxx
Yexxxx xxx – 12xxxxx
Mohammad Emon - 12794121
Group 13 2

Table of Contents
Entry Criteria. ...................................................................................................................... 4
Team Member Roles........................................................................................................... 5
Meeting Preparation............................................................................................................. 5
Inspection Meeting .............................................................................................................. 5
Issues Log .......................................................................................................................... 7
Exit Criteria........................................................................................................................ 13
Reflection .......................................................................................................................... 14
References........................................................................................................................ 16
Appendix A: Checklist for Requirements Specification Reviews .......................................... 17
Appendix B: Document Inspected ...................................................................................... 18
Group 13 3

Entry Criteria:
❑ The inspection team selected an inspection approach for the product being reviewed.
❑ All necessary supporting documentation is available
❑ Reviewers are trained in the peer review process.
❑ Documents to be inspected are identified with a version number. All pages
are numbered and line numbers are displayed.
Group 13 4

Team MemberRoles:
Wei Joon Low: Reader, Moderator/Inspector
Mohammad Emon: Reader, Inspector, Recorder
Yeqian Zhu: Reader, Inspector, Recorder
As we are a group of 3 team members, we have assumed multiple roles for the course of the
inspection of this document.
Each team member assumed the role of a reader before the inspection meeting to make
preparations and conduct preliminary inspections based on obvious flaws that were spotted
in the document.
While meeting was in session, Wei Joon assumed the role as moderator for the meeting
while conducting the inspection together with Muhammad and Yeqian. As moderator, Wei
Joon’s decision was the tie-breaker in the event of a disagreement on a flaw (or lack thereof)
within the document.
2 team members recorded the decisions made in the inspection meeting together using
Google Drive and Spreadsheets as a collaborative tool, allowing for team members to
update the same file in real time with changes visible by all.
Meeting Preparation
Team members agreed upon using a Checklist for the inspection process. The reason for
this was due to the fact that all 3 team members are inexperienced in conducting document
inspections and having a checklist to ensure no important factors and points are missed will
allow us to conduct a complete and adequate inspection. The Checklist that was used was
an altered version of the Checklist for Requirements Specification Reviews by Karl F.
Wiegers (2001). This Checklist allowed for team members to follow similar procedures in
their initial preparation for the document inspection meeting, allowing for the definitive
validation of any defects that are found by all 3 team members. By following the checklist,
each team member can be sure that they are inspecting every required aspect of the
document and not leaving out any important parts and missing critical defects.
As preparation for the meeting, each team member was instructed to read the entire
document and note down any flaws that they have found through their initial reading with
regards to the Checklist. Team members were also to prepare questions to be discussed in
the inspection meeting for any sections to which there was doubt about.
Inspection Meeting
The meeting was formally called to order at 4pm on Wednesday the 16th of May 2018.
Team members first compared notes on flaws that have been found during their own
preparation and discussed and debated on the relevance on what had been found. All points
Group 13 5

that were agreed upon were formally noted into the Issues Log. Next, each team member
presented their questions on potential, but unconfirmed defects for discussion and debate,
with defects that were agreed upon recorded into the Issues Log.
After that, the document was reviewed once again by all team members with reference to
the Checklist to ensure nothing else was missed, with some final points recorded into the
Issues Log.
In total, the document was reviewed as a whole a minimum of two times by each team
member and each defect recorded was discussed and agreed upon by all team members.
This was done to ensure maximum scrutiny of the document by every team member and
formal agreement of identified defects by 3 team members minimises the occurrence of false
positives and false negatives.
Once it was agreed by all team members that the document and defects had been fully
covered, the meeting was called to an end at approximately 6pm.
Group 13 6

Inspection Issues Log
Project Assignment 3
Inspection of SRS
Origin Requirements, Implementation
Meeting Date 16th May 2018
4:15PM
Type Missing, Wrong, Extra, Usability, Performance, Style, Clarity, Question.
Recorder Emon, Zhu. Severity Major, Minor.
Origin Type Severity Location Description
Implementation Wrong Minor page 3,line 36‐ 37 Spelling mistakes.
Implementation Style Minor page 3,line 39 Improper page management. Revision history stretches across table of
context which could be moved to next page.
Requirement Missing Major page 5,line 33 Explanation of priority ranking is missing.
Requirement Wrong Minor page 5,line 36 Spelling mistakes.
Requirement Missing Minor page 6,line 9‐ 11 Description missing.
Requirement Missing Major page 6,line13‐ 14 The details about stakeholders are missing. For example, the staff.
Requirement Missing Major page 6,line 29 Thefunctionalrequirement,feature and'outofscope'partinprojectscope
is missing.
Requirement Wrong Minor page 6,line 37 Grammars mistakes.
Requirement Missing Major page 6,line 38 Function description missing. ("Keeping track of supply and offer
notification" is mentioned as main intention regarding the first mins.)
Requirement Clarity Minor page 7,line16 Grammar mistakes lead to unclear statements.
Requirement Clarity Minor page 7,line 20 No detail descriptions for "AES" and "PCI" in document conventions.
Unclear statements for non‐ technical readers.
Requirement Style Minor page 7,line 34 Improper page management. (figure1 is shown between number 3 or
number 4 which is illogical)
Requirement Missing Major page 8,line 1, 'fig1
the product feature
model'
The function of "services" in figure is missing.
Requirement Missing Minor page 8,line 17‐ 23 Features cannot be found in the figure and the description is missing.
Requirement Clarity Minor page 9,line 5 Grammar mistakes lead to unclear statements.
Requirement Missing Major page 9,line 15 User role “assistant" is not described in the use case.
7
Group 13

Requirement Clarity Major page 9,line15 Grammar mistakes lead to unclear statements.
Requirement Wrong Minor page 9,line18 Spelling mistakes.
Requirement Missing Major page 9,line24 The description of system's environment for operation of web server is
missing.(no description for web hosting software or hardware)
Requirement Wrong Minor page 9,line37‐ 38 Thereasonforfont inItalic is notmentioned in thedocumentconvention.
Requirement Wrong Minor page 10,line13 Grammatical error
Requirement Clarity Minor page 10,line 15 Wrong expression for "Email ID"
Requirement Missing Minor Page 18 User interface visual demo example is missing
Requirement Question Major Page 18,line 22 Nocontextas towhathardwaretheserequirements arefor.Is itforserver?
User machine? What about CPU type requirement?
Requirement Clarity Major Page 18, line 32 This field should focus on used in development .they talk about the
database andwebprotocolusedbythesystem ratherthandevelopment
Requirement Clarity Minor Page 18, line 35 It’s confuse with the term name! Ambiguity issues
Implementation Wrong Minor Page 19, line 9&10 Redundant issues
Implementation Clarity Minor Page 19,line 27 Avoid to what extent?
Implementation Question Major Page 19, line 22 It is not mentioned in the case study or minutes meeting template
Implementation Clarity Minor Page 20,line1 This is an ideal scenario case which is not what should be discussing
Implementation Question Major Page 19, line 25 What algorithm and encryption will be used?
Implementation Clarity Major Page20,line11&12 System is not portable. It is unclear
Implementation Clarity Minor Page 19, line18 It’s ambiguous issue what if happen there is more than expected
requirement Question Major Page 19 , line 33 Whatredundancyis implementedinthesystem?Whatis donetoensure
the system is reliable?
Implementation Clarity Major Page 20, line 7&8 Unclear if data if corrupted, how can be retrieved from the server?
Implementation Missing Minor Document
conventions, line
9‐
11,page 6
Explanation is missing for HTTPS, AES, PCI
8
Group 13

Requirement Missing Minor Project scope, page
6
Out of scope is missing
Design Wrong
spelling,
Major Use case diagram,
line 2, page 22
Customer wrong spelling
Design Extra Major Use case diagram,
line 2, page 22
Thefunction“payfortheservice"isinconsistentintherequirement.It
shouldnotbeadded intheusecasebecauseitwasnotmentionedin
requirement.
Design Wrong Major Use case diagram,
line 2, page 22
Sarah is not actor, cannot put the name of the actor.
Design Missing Major Use case
diagram ,line 2,
page 22
In the “payment case” Doesn’t make any relationship between any “bank”
actor. It is not provided third party actor.
diagram ,line 2,
page 22
The relationship between the “pay for services” and other use case is
missing
Design Clarity Major Use case
diagram ,line 2,
page 22
The“managesupplier”usecaseisusedforbroadterm,sowhatmanage?
Design Clarity Major Use case
diagram ,line 2,
page 22
The “manage services” use caseis used for broadterm again. So what
manage?
Design Wrong Major Use case
diagram ,line 2,
page 22
The “pay for purchase” usecase doesn’t make any connection betweenany
actors.
diagram ,line 2,
page 22
inthe“processreport”usecasesaidthatthegeneralize relationshipuse
case there is two “process purchases report”, its wrong, redundant issue .it
should be one
Design Style Major Use case
diagram ,line 2,
page 22
In the “manage schedule” and “request change” include relationship is poor
formatting, one go inside each other.
Design Question Major Use case
diagram ,line 2,
page 22
How come the “pay for services” and “pay for purchase” same use cases use
for samefunction? Redundant issue?
9
Group 13

diagram ,line 2,
page 22
Inthe“checkAvailability” usecasethe“include”relationshipinothersideis
missing.
Design Clarity Minor Use case
diagram ,line 2,
page 22
Poor formatting relationship between “manage schedule” and “accept
roster” use cases
diagram ,line 2,
page 22
In “manage employees” use case should make generaliserelationship , not
“include’’ relation
diagram ,line 2,
page 22
The “update earnings” and“pay by card” use cases connection is poor
formatting
Design Question Major Use case
diagram ,line 2,
page 22
In “manage stock” and “pay for Purchase”use cases between them
“include” relation meantwhich way?
diagram ,line 2,
page 22
The “manage Employees “ use case the relationship between the actor is
confusing because of poor formatting
diagram ,line 2,
page 22
Poor formatting causeThe actor “Sarah”and use case “sendmessage
notifications” connection is conflictwith each other
Design Missing Major Class diagram, line
1, page23
In ‘”assistance”, “staff” and “owner” class did not add any operation
function
Design Wrong Major Class diagram, line
1, page23
The“bill’ class is notmeantintheusecaseandinconsistentwiththename
Design Clarity Major Class diagram, line
1, page23
Theservices classaboutwhat?Confusewiththename,theyusedbroad
term, and inconsistent with the name.
1, page23
The “customer” class there is no operation for “create or update” their
personalinformation andtheyonlymentionedaboutpayment whichisnot
linked to theattributes
1, page23
Thecardinality betweenthe“customer”and“Bill’class iswrongbecause
how come many customer have many bills?
Requirement Clarity Major Use case description In “manageemployees”usecasetheprimaryactoris given“admin”which
is inconsistent name with use case. It should me “Owner” actor
10
Group 13

Implementation Question Minor Page 25 Conflict with question 8 and 9 answer?
implementation Wrong Minor Page 26 Wrong number
Implementation Clarity Minor Page 27 Conflict with earlier meeting. Change should be reflected in SRS
Implementation Wrong Minor Page 30 Spelling mistake
Implementation Question Minor Page 31 What is meaning of the question?
Implementation Clarity Minor Page 36,line 13 Bad Page formatting
Implementation Clarity Minor Page 38, line 17 Bad page formatting
Requirement Clarity,
missing
Major Use case description “Login”usecaseinsideprimaryactornameisinconsistent.Itshouldbe
“owner”actor,not“admin”!Andthereisanotheractorismissingsuchas
“Sarah”
Requirement Clarity Major Use case description Check availability “use case inconsistent with the primary actor
name .Where is “Admin” actor come from?
Requirement Clarity Major Use case description In “manage rostering” use case secondary actor “employee” whereis come
from? There is no connection giving in the diagram between them.
Requirement Clarity,
missing
Major Use case description Inconsistentnamewith“Manage supplierdetails”.it Shouldbe“manage
supplier” and another actor “Sarah” is missing
Requirement Clarity Major Use case description “Process report” use case inconsistent name with the actor
Requirement Clarity Major Use case description In “schedule booking” there is no connection given in the diagram for
“customer” actor. So it’s wrong
Requirement Clarity Major Use case description In use case 6, inconsistent with the actor name.
Requirement Clarity Major Use case description In use case 5 primary actor name inconsistent again.
requirement Clarity Major Use case description In usecase7,secondaryactor“employees”butnoconnectiongivenfor
“employees” actor in the diagram.
Requirement Wrong Major Use case description Use case 9, secondary actor customer is wrong, they mention only oneactor
connection in the diagram.
Requirement Wrong Major Use case description Usecase11,secondaryactor“admin”iswrong.Thereis norelationship
given in the use case diagram and inconsistent with name.
Requirement Wrong Minor Use case
description
Use case 12, wrong spelling mistake for “PURCHASE”
Requirement Wrong Major Use case description Use case 12, actor “Sarah” no relation given in the diagram
Requirement Missing Major Use case description Use case 12, not talk about the ‘’process bank transfer” details
Requirement Wrong Minor Use case description Use case 10, in step 1,spelling mistake of “availability”
11
Group 13

Requirement Wrong Major Use case description Use case 10, step 6a, sub‐ use case: “update earnings”which is wrong, they
already mentioned “include” in the main function.
Requirement Question Major Use case description Usecase6,underExtension,insidesubusecase“placeorder”whereis
come from? It’s not mentioned in the diagram
Requirement Clarity Major Use case description Use case 5, the step provided, which is not mentioned in the diagram
Requirement Missing Major Use case description Usecase4,thesteps is provided,whichis notmentionedinthediagram
Requirement Missing Major Use case description Use case 3,in step 1a,6a both sub use case is missing on the diagram
Requirement Missing Major Use case description Use case 2, sub use case is missing on the diagram
Requirement Missing Major Use case description Almost half of use case description is not mentioned in the project.
Requirement Missing Major Traceability matrix,
page 39&40
Poor formatting, use cases and other requirement is missing
Requirement Missing Major Traceability matrix,
page 39
The “check availability “ use case there is no connection given in the
‘traceability matrix’
Requirement Wrong Major Traceability matrix,
page 39
Theusecasetablethereis two“manageemployees”usecaseis used.
Requirement Question Major Traceability matrix,
page 40
The “Functional requirement” table there is no connection is given. The
work is undone?
12
Group 13

Exit Criteria
❑ All of the inspection objectives are satisfied.
❑ Issues raised during the inspection are tracked to closure.
❑ All major defects are identified.
❑ Moderator has collected and recorded the inspection data.
❑ Moderator has delivered the completed Inspection Summary Report and
defect counts to the peer review coordinator.
Group 13 13

Reflection
This assignment allowed us to explore the steps involved in document inspection and
allowed us to experiment with the formal procedures of inspection and the preparation
involved.
The inspection was able to meet our teams objectives in the sense that all team members
were able to follow the procedures involved and were well prepared for the inspection
meeting. Allowing for the inspection to proceed and the meeting to be conducted smoothly.
Work was able to be spread well among our 3 team members. While we each ended up with
a higher workload than other teams of 4, our team was able to work effectively to complete
the task at hand.
While studying and exploring the formal process for document inspection using the Peer
Review Process Description, we found that the author of the document should be involved in
the document inspection process as well as a correction phase and reinspection phase. This
resulted in a bit of confusion and doubt about the procedure of the assignment as the
document author was not involved in our assignment process and neither was there a
correction and reinspection phase for the assignment. While it was understood that these
documents were meant to be used only as guides, the assignment should be tailored to be
closer to the actual process or documents altered to reflect the assignment more closely.
While reviewing the document provided to us, we realized that there were some significant
changes that could have been made to our original report such as a proper list of
requirements rather than classifying them as user stories. Using the method of listing
requirements and breaking those down would have significantly improved the clarity of the
requirements involved.
Through the preparation process, we used Wiegers Checklist as a reference to conduct our
preparation. The checklist allowed us to have a list of potential issues that we would need to
check for which let us conduct a thorough inspection of the document and avoid missing
important aspects of the inspection.
The time of the inspection meeting was formally agreed upon by all team members 1 week
ahead of time which allowed each team member enough time to prepare for the meeting by
conducting their own initial inspection based on the checklist. The only issue we had was
that by scheduling the meeting one week in advance, it did not leave us with very much time
for writing up the report. As most of our team members work part time through university, it
does not leave much time flexibility for work outside of the classroom.
The entry and exit criteria of the inspection meeting could not be followed completely as the
criteria included a more detailed procedure in which the author was involved and
reinspection was taken into account. Many of these steps had to be removed as they were
not within the scope of the assignment. We feel that this should be made clearer in the
assignment handout and in the tutorials as the assignment has greatly narrowed the scope
of a document inspection.
Group 13 14

The inspection meeting was conducted quite smoothly, despite being run on a tight schedule
due to team members having other obligations. The process of the meeting and things to be
discussed we established beforehand, as such, all team members were well prepared for the
meeting. Some of the meeting time had to be dedicated to allocation of work after the
meeting for the report, however, with regards to the assignment rather than the procedure of
document inspection, our actual document inspection could have been conducted over
conference calls and document collaboration tools rather than a face to face meeting. While
this was explicitly disallowed during our lectures, we did conclude that it would not be
impossible for the inspection meeting to be conducted over conference call. This was due to
the fact that with collaboration tools such as Google Docs or Office 365, all team members
would be able to make edits and view the edits and comments of other team members in
real time, allowing for similar efficiency to face to face meetings.
Much of our inspection meeting was the discussion of issues that had been identified during
our individual preparation phase. This involved each of us presenting the issues identified
one by one and all team members agreeing upon the issue and a description. We then
reviewed the document once again as a group following the checklist to ensure that we had
not missed any potential issues. Any new finds would be discussed as a group and agreed
upon before being added to the log.
Before the conclusion of the meeting, we discussed what would have to be written for the
assignment submission report. This reflection was particularly hard to designate as it is not
easy for 3 members to contribute writing it equally. As a result, the main points of the
reflection were discussed and it was left to the team member with the best command of
English to formulate. Shorter individual reflections would have been a better approach as it
would be a better distribution of responsibility for the team.
Overall, as an assignment, we felt that it was a good way to allow us to explore the actual
act of inspecting a document. However, it did not allow us to properly follow the formal
procedure of document inspection and did not allow us to follow through with a correction
and reinspection process. That being said, this assignment would allow us to learn about
mistakes that would commonly be made during the development of a Software
Requirements Specification which would prepare us to write better documents overall in the
future.
Group 13 15

References
Zowghi, D. 2018, ‘Lecture 7: Requirement Validation part 1’, UTS Online Subject 32569,
Powerpoint Presentation, UTS, Sydney, viewed 18 May
2018,<https://online.uts.edu.au/bbcswebdav/pid-2778237-dt-content-rid-
24733927_1/courses/32569-2018-AUTUMN-CITY/Week%207%20-
%20Requirements%20Validation%20part%201%281%29.pdf>
Zowghi, D. 2018, ‘Lecture 7: Requirement Validation part 1’, UTS Online Subject 32569,
Powerpoint Presentation, UTS, Sydney, viewed 18 May
2018,<https://online.uts.edu.au/bbcswebdav/pid-2781146-dt-content-rid-
25772516_1/courses/32569-2018-AUTUMN-CITY/Week%208%20-
%20Requirements%20Validation%20part%202%281%29.pdf>
Zowghi, D. 2018,Requirements Analysis & Modeling,UTS online Enterprise Software
Requirements subject 32569 ,Powerpoint Presentaion,UTS,Sydney,viewed 19 May 2018,
<https://online.uts.edu.au/bbcswebdav/pid-2764208-dt-content-rid-21977952_1/xid-
21977952_1>
Group 13 16

Appendix A: Checklist for Requirements Specification Reviews
Organization and Completeness
o Are all internal cross-references to other requirements correct?
o Are all requirements written at a consistent and appropriate level of detail?
o Do the requirements provide an adequate basis for design?
o Is the implementation priority of each requirement included?
o Are all external hardware, software, and communication interfaces defined?
o Have algorithms intrinsic to the functional requirements been defined?
o Does the specification include all of the known customer or system needs?
o Is the expected behaviour documented for all anticipated error conditions?
Correctness
o Do any requirements conflict with or duplicate other requirements?
o Is each requirement written in clear, concise, unambiguous language?
o Is each requirement verifiable by testing, demonstration, review, or analysis?
o Is each requirement in scope for the project?
o Is each requirement free from content and grammatical errors?
o Is any necessary information missing from a requirement? If so, is it identified as TBD?
o Can all of the requirements be implemented within known constraints?
o Are any specified error messages unique and meaningful?
Quality Attributes
o Are all performance objectives properly specified?
o Are all security and safety considerations properly specified?
o Are other pertinent quality attribute goals explicitly documented and quantified, with the
acceptable tradeoffs specified?
Traceability
o Is each requirement uniquely and correctly identified?
o Is each software functional requirement traceable to a higher-level requirement (e.g.,
system requirement, use case)?
Special Issues
o Are all requirements actually requirements, not design or implementation solutions?
o Are all time-critical functions identified, and timing criteria specified for them?
Group 13 17

Appendix B: DocumentInspected
Group 13 18

1 ASSIGNMENT COVERSHEET
2
SUBJECT NUMBER & NAME
32569
Enterprise Business Requirements
NAME OF STUDENT(s) (PRINT CLEARLY)
SURNAME FIRST NAME
STUDENT ID(s)
Daizy Balar 12849663
Anaika Deshpande 12835423
Sumin Joseph 12774042
ASSESSMENT ITEM NUMBER
Assignment 2 - SRS
Bhavi Chaudhari 12799223
NAME OF TUTOR
Professor Kaska Musial-Gabrys
GROUP ID
14
Tutorial day and time
Wednesday 3 pm – 4 pm
☒ 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) Daizy Balar Date 1/5/18
Signature of student(s) Anaika Deshpande Date 1/5/18 Signature
of student(s) Sumin Joseph Date 1/5/18
Signature of student(s) Bhavi Chaudhari Date 1/5/18
3
1

Page | 2
1 SOFTWARE REQUIREMENTS
2 SPECIFICATION
3 FOR
4 SALON MANAGEMENT
5 SYSTEM
6 Version 1.0 approved
7
8
9
10
11
12
13
14
15
16
17
18 Date:1/5/18
19
Approved By:
Daizy Balar: 12849663
Anaika Deshpande: 12835423
Sumin Joseph: 12774042
Bhavi Chaudhari: 12799223

Page | 3
1 Table of Contents
2 Table of Contents ii
3 Revision History ii
4 1. Introduction 1
5 1.1 Purpose1
6 1.2 Document Conventions 2
7 1.3 Intended Audience and Reading Suggestions 2
8 1.4 Project Scope 2
9 1.5 References 3
10
11
2. Overall Description 2
2.1 Product Perspective 3
12 2.2 Product Features 4
13 2.3 User Classes and Characteristics5
14 2.4 Operating Environment 5
15 2.5 Design and Implementation Constraints 5
16 2.6 User Documentation 5
17 2.7 Assumptions and Dependencies 6
18 3. System Features 3
19 3.1 System Feature 1 13
20 3.2 System Feature 2 (and so on) 13
21 4. External Interface Requirements 14
22 4.1 User Interfaces 13
23 4.2 Hardware Interfaces 14
24 4.3 Software Interfaces 14
25 4.4 Communications Interfaces 14
26 5. Other Nonfunctional Requirements 15
27 5.1 Performance Requirements 14
28 5.2 Safety Requirements 15
29 5.3 Security Requirements 15
30 5.4 Software Quality Attributes 15
31 6. Other Requirements 16
32 Appendix A: Glossary 16
33 Appendix B: Analysis Models 18
34 Appendix C: Minutes of meetings 27
35 Appendix D: Literature review..................................................................................................31
36 Appendix E:Tracibility matrix… ..............................................................................................34
37 Appendix F: Screenshoots… .....................................................................................................30
38
39 Revision History
Name Date ReasonFor Changes Version
Sumin Joseph 24/4/18 Initial Draft 0.1

Page | 4
Anaika Deshpande 26/4/18 External and nonfunctional requirements 0.2
Daizy Balar 25/4/18 System features 0.3
Bhavi Chaudhari 30/4/18 screenshots 0.4
Sumin Joseph 28/4/18 Use case diagram 0.5
Daizy Balar 27/4/18 Hardware & Software requirements 0.6
Anaika Deshpande 27/4/18 External interface requirement 0.7
Sumin Joseph 30/4/18 Consolidation, proofreading and spell checking 1.0
1
2
3 Check list
One Relevant model for the system (e.g. ERD, DFD, or from UML) ✓
Full Software Requirements Specifications (SRS)1 ✓
Quality of your last requirements elicitation interviews ✓
One Traceability matrix ✓
Quality of the Minutes of Stakeholder meetings ✓
Individual contribution (reflections by each group member) ✓
All the use cases you developed and submitted for assignment 1 ✓
4
5
6
7

Page | 5
1 1. Introduction
2
3 In today’s world, more and more people are investing money in improving their looks and
4 maintaining their beauty. To keep up with the growing demand, there is a steady increase in the
5 number of salons offering numerous services to cater to the needs of the customers. Moreover,
6 many salons are automating their systems and processes to keep track of their expenses and
7 earnings, in addition to their realization that to attract more customers and increase profits, salon
8 must not only provide services by professionally trained staffs but also employ a system that
9 facilitates efficient customer service and management.
10 Nancy Jones is the owner of Nancy’s salon, a thriving hair dressing shop near a university
11 where the business is currently running manually with no computer or automated system in place.
12 Currently in the salon, she uses books to keep record of all the aspects of operating a business
13 including customer appointments and employee schedule. While she uses another book to keep
14 track of supplies, a cashbook records the day’s taking, which she shares with the accountant to
15 calculate tax and track the revenue.
16 Nancy wishes to implement a system, so that she can automate the current mechanism of
17 book keeping and run her business more efficiently and economically. Furthermore, she wants the
18 system to offer a booking system to capture client’s appointments competently, improve the
19 process of scheduling and rostering of staff. In addition, she also expects the system to facilitate in
20 keeping track of supplies and notify her when running out. This Software Specification Document
21 will assist in developing a system that acts as an appropriate solution to Nancy’s requirements.
22
23 1.1 Purpose
24 The main purpose of this SRS is to define the requirements needed to develop and
25 implement a Salon management system (Nancy’s Salon Management System- NSMS) that caters
26 to the elicited needs of the client. Furthermore, this document illustrates the major specifications of
27 NSMS, which will help in running the salon and its business efficiently. The system aims at
28 providing an automated platform that completely overrides the existing manual processes in the
29 salon. Moreover, taking into account the client’s requirement, the NSMS will be an online system
30 which eligible users can access using the internet. This system can connect and integrate with an
31 external accounting software- FAST ACCOUNTS, reducing the hassle of revenue and tax
32 management.
33 1.2 Document Conventions
34 The entire document is justified. The contents of this document are in 11 point size in Arial.
35 The main heading are in Times New Roman size 18 while the subheadings are in size 14.
36 Furthermore, the document contains the requirements in a hierarchical manner. In most cases thee

Page | 6
1 detailed requirements inherits the priority set at the higher-level requirements but in some cases,
2 priorities are set at the requirement level.
3
4 The document contains the following conventions
5 ● ERD Entity Relationship Diagram
6 ● DB- Database
7 ● NSMS- Nancy’s Salon Management System.
8 ● SRS – Software Requirement Specification.
9 ● HTTPS -
10 ● AES -
11 ● PCI -
12 1.3 Intended Audience and Reading Suggestions
13 The SRS is intended primarily for the major stakeholders of the system, like the owner-
14 Nancy as well as the members of the development and testing team. The document captures the
15 requirements of the client providing a foundation for the development team to design and develop
16 NSMS fulfilling the needs of the client.
17 The document contains the details of the system like product features and the available
18 user classes their respective access conditions, expected requirements of the operating system,
19 software and hardware components, which facilitates the smooth functioning of the system.
20 The next section also contains the various features of the system that simplifies and assists
21 the client in the smooth running of business and processes of the salon.
22 Further to these specifications, the document also contains details of the external interface
23 requirements like software interfaces (discussing aspects such as the operating systems,other
24 commercial software integrated with the system), the various hardware interfaces (the supported
25 interactions with other devices) in addition to high-level sample user interfaces screen layouts.
26 The developers and testers can refer to section 3 for the requirements and functions
27 expected of the system, section 4 details external interface requirements and section 5 discusses
28 the functional and non-functional requirements.
29 1.4 ProjectScope
30 The scope of this project is to develop a salon management system for Nancy’s salon for
31 replacing and automating the book keeping functions. The new system- NSMS is expected to
32 perform primarily two functions: managing appointments and managing rosters. With the new
33 system, Nancy wishes to record customer appointments. During the booking process, the system
34 should also provide a provision to view the staff available.
35 Another function expected of the system is to generate reports such that the owner can
36 keep track of the busy times and roster sufficient staff to meet customer demand. Furthermore, the
37 system should keep track of the day’s to generate the reports of the earnings and expenses to aid
38 in keeping track of the revenue and calculate goods and services tax.
39 In addition, the system is to generate various other reports related to services opted by the
40 customers, peak business hours and purchase reports which will enable the owner to run the
41 business more efficiently with the information provided. The system primarily aims at improving
42 and efficiently running the current business and utilizing the reports that the system generates to
43 automate the revenue tracking and calculate the tax using an external software- FAST
44 ACCOUNTS, thus reducing the overhead on the accountant.

Page | 7
1 1.5 References
2 Christensen, M. & Thayer, R. 2001, ‘Software Requirements Specifications’, The Project
3 manager’s guide to software Engineering’s best Practices’, pp. 336 -339.
4 2. Overall Description
5 2.1 Product Perspective
6 The product is a salon management system, which aims at replacing and automating all the
7 salon related processes currently running manually. The product is an online portal, which the
8 employees and the salon owner can use to carry out various related business functions. The
9 product assists by providing provisions to manage appointments, schedule roster, view employee
10 availability, manage salon inventory and suppliers, in addition to managing various services it
11 offers. The system also provides a provision to the owner/ admin to set restriction to the details and
12 information the employees can view and access. The admin/owner has the privilege to create user
13 roles and assign the permissions and privileges for each role to control the accessibility of the
14 employees under the role.
15 The system will run on a web application server. NSMS utilizes the web server to display its
16 contents on the browser of user choice. A database will store all the details ranging from the
17 employee information, product and supplier details, rosters, services and other details related to
18 earnings and expense invoices. To keep the client data and related functions safe and secure, an
19 HTTPS connection carries out the functions online. Since the customer can make payments
20 through cards, the data is AES encrypted and gateways are PCI compliant.
21 2.2 Product Features
22 The system will perform the following functions:
23
24 1. User Roles
25 ● The user can create various roles and assign visibility and access privileges.
26 ● Each employee is assigned to the role.
27 2. Login
28 ● The employee can login into the system with the username and password provided
29 ● The functions and provisions of the system that are available to them varies depending
30 of the roles assigned against them.
31 3. Enter availability.
32 ● The employees can enter their availability in the system.
33
34 Fig1: the product feature model
35
36
37

Page | 8
1
2
3 4. Manage Employee
4 ● The admin registers the employee provides the login details to the employee to access
5 NSMS.
6 5. Manage Appointments
7 ● The assistant handles appointments
8 ● The customers of the salon can walk in or call over the phone to book appointments.
9 ● According to the customer, the assistant can update or delete an appointment.
10 ● A message is sent to remind the customer of the booking 1 day prior.
11 6. Rosters
12 ● The admin creates roster for the week depending on the availability provided by the
13 employees.
14 ● The admin can edit the roster and update the employee’s schedule if need be.
15 ● The admin publishes the roster once the employees approve the uploaded temporary
16 roster.
17 7. Manage Product
18 ● Products and product details can be added, deleted or edited.
19
20
21 8. Notify order
22 9. Generate Reports
23 10. Generate service invoices
24
25

Page | 9
1
2
3
4 2.3 User Classesand Characteristics
5 The NSMS has applied restriction to user accessibility of the various function the system offers.
6 Based on the roles of the employees, the information available to the employees varies on the basis
7 of the roles assigned to them. The user roles are as follows:
8
9 Admin/Owner: These users have complete access to the system features and information. There is
10 absolutely no restriction to this class of user roles. They are the storeowners. They have the
11 privilege to edit, add and delete data including that of the employees, products, services, suppliers
12 and generating necessary reports. Furthermore, they can create rosters depending on the employee
13 availability, after the approval of which the admin publishes the roster.
14
15 Assistant: The user a few restrictions of the accessibility of the features. The primary role is to
16 manage the appointments including booking, updating and deleting appointments. In addition to
17 which they can place orders and view stock, product, supplier and service details. They can also edit
18 the stock details if case of product purchase.
19
20 Staff: They have the least privileges. They can view their personal details and edit information.
21 They have the privilege to approve the created roster and send change request. They also have a
22 provision to enter their availability.
23
24 2.4 Operating Environment
25 The product is compliant and works on Windows operating system in its first version. As the
26 system is an online web portal, it is accessible through Google Chrome, Internet Explore and
27 Mozilla Firefox (Version 2.0 or later). It is works on IE 6.0 and any higher versions. The primary
28 requirement is uninterrupted internet connection.
29 2.5 Designand Implementation Constraints
30 1. The code with the system is built may become outdated.
31 2. User roles will aid in configuring user privilages, which provide access control to the
32 employees or staff members.
33 3. The finance- related reports generated may not capture all the details as required by the
34 FAST ACCOUNTING software. The system will give the admin a provision to add or
35 modify the fields as per requirement.
36 2.6 User Documentation
37 The system shall provide an online manual available to all users except those under the staff role
38 illustrating all the system features

Page | 10
1 2.7 Assumptions and Dependencies
2 Assumptions
3 1. The initial data to set up the data base will be provided by the owner
4 2. The payment can be made through cash and card. The assistant will handle the payment for the
5 services availed by the customers.
6 3. The online system shall be tested in the latest versions of the web-browsers.
7 4. The user accessing the system must ensure that relevant firewall is installed in the system prior to
8 accessing the system.
9 5. The user handles payment of purchases through banktransfers.
10 6. The user manually enters the purchase invoices into the system.
11 Dependencies
12
13 1. The free high-speed internet is required at least 30Mbps.
14 2. The salon owner provides all the relevant data to set up the DB.
15 3. The user selects the reports and their frequency to be sent to the configured email id. If email id not
16 provided, then the user generates the reports manually and sends the reports.
17
18 3. System Features
19 3.1 Manage Employees
20 3.1.1 Description and Importance:
21 This feature allows admin to register the existing employees and activate employee accounts
22 in order to provide default login details to the employees. Newley recruited employees get
23 the privilege to access NSMS based on their job roles. This feature is highest on priority
24 level, on a scale of 9.
25
26 Priority: 0 9
27
28
29 3.1.2 Stimulates/Response Sequence:
30 Employees get access to NSMS.
31
32 3.1.3 Functional Prerequisites:
33 REQ 3.1.3.1 The admin shall be able to register employee based on name, job role, email
34 address and assign employee id to each employee.
35 REQ 3.1.3.2 The admin should be able to generate initial login id and password for each
36 employee.
37 REQ 3.1.3.3 The system provides a feature to add or delete an employee.

Page | 11
1 REQ 3.1.3.4 The admin shall be able to assign role id to the employee during registration to
2 restrict accessibility to the system.
3 REQ 3.1.3.5 The admin should be able to edit the role id whenever required.
4
5
6 3.2 User Login
8 This feature will allow users to login to the system and get access it’s functionality. Without
9 this option user won’t be able to access any function at all therefore, this feature has priority
10 9 on the scale.
11
12
13
14 Priority: 0 9
15
17 ● The user enters login id and password in the login window.
18 ● System validates the details entered and logs in to the system on successful validation.
19 ● The user clicks on forgot password option to retrieve his/her password.
20
22 REQ 3.2.3.1 The system should give access to the user using login form.
23 REQ 3.2.3.2 The system should provide an option to the user to retrieve their password via
24 registered email account.
25 REQ 3.2.3.3 The system should not allow the user to log in to the system if the details are
26 not valid.
27 REQ 3.2.3.4 The system should have the facility, like system should lock the user’s account
28 if the user continuously login to the system for more number of time.
29 3.3 Check Availability
31 This feature provides admin to check the availability of the staff before generating the roster
32 so that shifts are assigned efficiently. Getting availability is a crucial feature as it is required
33 for generating a roster and hence it has a priority 9.
34

Page | 12
1 Priority: 0 9
2
4 ● Admin will enter the date and time for which they want to check availability of employees.
5 ● Admin clicks on the check availability option and can check the available staff for the
6 coming week.
7
8
9 3.3.3 Functional prerequisites :
10 REQ 3.3.3.1 System should verify the login details and if it valid only then access should be
11 granted to the admin to check availability.
12 REQ 3.3.3.2 System should allow the admin to enter period for which they want to check
13 availability of the staff.
14 REQ3.3.3.2 The system should show availability of the staff for the period specified by the
15 admin.
16 REQ 3.3.3.4 The system should notify employees if their availability is not displayed on
17 the availability charts.
18
19 3.4 Manage Services
20 3.4.1 Description and importance:
21 This feature provides the facility to view the most popular services of the current week, so
22 that the admin can assign more staff for that service. Based on the customer review and
23 needs, even a new service can be added to the list and we can come up with that information
24 using this feature.
25
26 Priority: 0 6
27
29 ● The admin login to the system.
30 ● Admin that come up with the most popular service of that week.
31 ● Busy hours and days are predicted based on demand chart generated.
32 ● Adequate staff is assigned for that particular period.
34 REQ 3.4.3.1 The system should allow owner/admin to view current services and their
35 existing rates.
36 REQ 3.4.3.2 The system must short list the most popular services.

Page | 13
1 REQ 3.4.3.2 The admin shall be able to add or delete particular service.
2 REQ 3.4.3.3 The System should provide accurate data for the particular period entered by
3 the admin.
4 REQ 3.4.3.5 System should provide admin an access to the option to view demand chart
5 for the service.
6
7
8
9
10 3.5 Manage Suppliers Details
12 This feature provides the facility to maintain the contact details of the suppliers. The
13 information regarding the stock, as in when the stock is almost going to be finished, this
14 feature helps in contacting the suppliers.
15
16 Priority: 0 5
17
19 ● Admin checks the availability of the stock.
20 ● The new supplier details is been updated.
21 ● An automated notification will be sent to the assistant/owner when minimal stock
22 amount is reached.
23 ● Purchase invoice is generated after placing an order.
25 REQ 3.5.3.1 Admin should be given access to update contact detail of the suppliers.
26 REQ 3.5.3.2 Assistant or owner must be notified once a product reaches its minimum
27 quantity.
28 REQ 3.5.3.3 The system shall display purchase invoice matching the supplier.
29
30 REQ 3.5.3.4 When admin login to the system it should display the list of products
31 and its supplier to the admin.
32 3.6 Manage Stock
34 This feature helps the admin or the handler regarding the ordering of the stock when it is
35 needed and even the admin is notified when the stock on hold reaches to the minimum
36 quantity.
37

Page | 14
1 Priority: 0 7
2
4 ● Admin sets the minimum quantity.
5 ● System notifies regarding the minimum stocks.
7 REQ 3.6.1.1 System needs to notify the user when SOH is less than the configured
8 minimum quantity.
9 .
10 REQ 3.6.1.2 Systems should allow the admin to set the minimum quantity.
11 REQ 3.6.1.3 System should allow admin to update the details of the products.
12 REQ 3.6.1.4 System should display the contact details of the suppliers with notification that
13 is been popped up on the screen about the minimal stock.
14 3.7 Manage Rostering
16 This feature helps the admin in making the roster of the staff 2 weeks prior based on the
17 availability of the staff.
18
19 Priority: 0 9
21 ● Admin grants access so that staff can enter their availability.
22 ● Admin selects ‘create roster’ option.
23 ● Admin enters date and time for which the roster is to be generated.
24 ● Staff enters their availability in the system.
25 ● Admin checks the demand chart report.
27 REQ 3.7.3.1 System should prompt asking about the time period for which admin wants to
28 generate the roster.
29 REQ 3.7.3.2 System should not give an access to the employee if the username or the
30 password is not valid.
31 REQ 3.7.3.3 System should have the report regarding the popular services based on the
32 feature of manage services so that admin can assign the staff for that service.
33 REQ 3.7.3.4 System should send the notification to the employee regarding the roaster
34 generated.
35 REQ 3.7.3.5 The system shall display roster upto next two weeks.
36 REQ 3.7.3.6 Admin must be notified if an employee rejects the roster.

Page | 15
1 3.8 ProcessReports
3 This feature provides facility to the owner/admin to generate and view report in order to get
4 a clear idea regarding the current business situation. This feature even provides the facility
5 to generate reports based on the revenue tracking and the facilitates accountant in tax
6 declaration as these reports will be emailed to the accountant.
7
8 Priority: 0 8
9 3.8.2 Stimulates/Response Sequence
10 ● Admin generate the reports related to the revenue and the tax calculation.
11 ● Admin enters the duration and type of report she wants to view.
12 3.8.3 Admin is notified once the report is sent to the accountant Functional Prerequisites:
13 REQ 3.8.3.1 System should grant an access to the admin to get all the generated reports.
14 REQ 3.8.3.2 System should give an option to the admin to select the type of the report.
15 REQ 3.8.3.3 System should provide the option regarding the time for which the
16 admin wants to generate the report.
17 REQ 3.8.3.4 System should just display the report for that period for which the admin has
18 requested.
19 REQ 3.8.3.5 System should notify the admin regarding the delivery status of that particular
20 report.
21 3.9 Scheduling Booking
22 3.9.1 Document and Importance:
23 This feature provides the employee the system which facilitate the bookings for the
24 customers who walks in to the saloon or book the appointment via calls.
25
26 Priority: 0 4
27 3.9.2 Stimulates/ Response Sequence:
28 ● Sarah confirms the appointment and blocks the slot for the requested services and the
29 employees.
30 ● Before assigning the service to the employee, Sarah first enter the name of the
31 employee and comes up with the roaster and check weather he/she is available or
32 not.
34 REQ 3.9.3.1 System should prompt the availability of the employees when assistant

Page | 16
1 enters employee name.
2 REQ 3.9.3.2 System should have up-to-date service list available.
3 REQ 3.9.3.3 System should show the available time slots of the employees when their name
4 is entered to check the availability.
5 REQ 3.9.3.4 System should send the booking notification to the employees and the
6 customers before 1 day just a kind of reminder.
7 REQ 3.9.3.5 If the requested service or the employee is not available on that particular date
8 Then the system should decline the booking.
9 REQ 3.9.3.6 If the Customer do not confirm the bookings then the system should
10 automatically cancel the bookings.
11 3.10 Pay for Services:
13 This feature provides the customer to do the payment online for the services provided to
14 them.
15 Priority: 0 3
17 ● Customer select the payment types.
18 ● Customers does the payment by cash or card.
19 3.10.3 Functional Prerequisite:
20 REQ 3.10.3.1 system should let the customer knows which the services are available or
21 should show the available services.
22 REQ 3.10.3.2 System should provide payment options to the customers.
23 REQ 3.10.3.3 system should provide employee with the option of update earnings as in
24 sometimes employees forgot to update the total earnings in the system which
25 generated the ambiguity in the database.
26 3.11 Manage Schedule:
28 This feature provides a provision to the employees to accept the created roaster so that the
29 admin is notified with availability facilitating efficient management of booking the
30 appointments. Even this feature also provides the mechanism for swapping the shift wit the
31 other Staff members.
32
33 Priority: 0 7
34 3.11.2 Stimulate/Response Sequence:
35 ● Employees login to the system.

Page | 17
1 ● Employee accept the shift.
2 ● Employee request for change in shift.
4 REQ 3.11.3.1 System should provide employees with the manage schedule option.
5 REQ 3.11.3.2 System should provide and option to the employee to view the roaster.
6 REQ 3.11.3.3 System should notify the admin if the employee accepts the roaster.
7 REQ 3.11.3.4 System should provide a Request Change option to the employee for the swap
8 of their shift.
9 3.12 Pay for Purchase
11 This Feature helps the system to provide a provision for keeping the track of the purchases
12 done in the saloon so that the accurate expense of the saloon is maintained properly.
13
14 Priority: 0 8
15 3.12.2 Stimulate/Resource Sequence:
16 ● The user should view the purchase order that is received.
17 ● The user processes the payment of the purchase
19 REQ 3.12.3.1 System should allow Sarah to logged in to the system
20 REQ 3.12.3.2 System should allow the user to view the purchase order that is received.
21 REQ 3.12.3.3 system should update the expense details of the saloon in correspond to the
22 entry done.
23
24
25
26
27
28
29
30
31
32
33
34
35

Page | 18
1 4. External Interface Requirements
2 4.1 User Interfaces
3 To enable the users to carry out the functions and the requirements, the following screen are
4 provided in the system.
5 1. Manage Employee- To add/ edit/ delete and register employees.
6 2. Login- To login to the system
7 3. Enter Availability- The employees enter their available time slots.
8 4. Manage Suppliers- The user adds, edits and deletes a supplier details.
9 5. Manage Stock- the products and their details are captured.
10 6. Manage Services- The user can add or modify the services and its details.
11 7. Generate Report- The user can generate the various reports with the given period.
12 8. Permission- The admin can create roles and assign the access rights for each role.
13 9. Manage Roster- The admin can create roster and manage employee schedules.
14 10. Manage Appointments- The assistant can take bookings.
15
16 High-level screen layouts are enclosed in the Appendix. They are subjected to change during the
17 design phase. All the interface will incorporate the company logo and the user information in
18 the header in addition to the footer which contains the copyright information.
19 The notifications for placing order and sending the finance reports will be a pop up which is
20 collapsible.
21
22 4.2 Hardware Interfaces
23 RAM
24 Minimum: 2GB
25 Recommended: 8GB
26
27 Disk Space
28
29 Minimum: 500GB
30 Recommended: 1TB
31
32 4.3 Software Interfaces
33 The software application will be developed using eclipse IDE. Eclipse provides a platform to
34 develop a web application using JSP and java code. Eclipse is supported by both windows and
35 MAC. The communication will take place using HTTPS and it will be stored in SQLdatabase.
36 Bootstrap will be used for designing the system. Various java libraries like java web toolkit and
37 SQL connectors will be used.
38
39 IDE: Eclipse oxygen

Page | 19
1
2 Database: SQL server
3
4 OS: MAC, Windows (7 and above)
5
6 Communication: HTTPS
7
8 4.4 Communications Interfaces
9 The communication channel is secured using HTTPS and SSL and various security algorithms
10 would be applied to ensure secure data transfer. Data will be encrypted before it is transferred.
11 5. Other Nonfunctional Requirements
12 5.1 Performance Requirements
13 5.1.1 System should be able to respond to any request within two seconds.
14 5.1.2 In case of report generation, depending on the volume of data maximum time tolerable
15 would
16 be 30 seconds.
17
18 5.1.3 The system should be able to save and retrieve huge data sets (>200GB).
19
20 5.1.4 The system must efficiently communicate with FAST ACCOUNTS software.
21
22 5.2 Security Requirements
23 5.2.1 The system shall use SSL which would act as a security layer for any transactions which
24 include sensitive customer information like bank details or personal details.
25 5.2.2 The system should use encryption and decryption algorithms as a precaution against theft and
26 data loss.
27 5.2.3 The system would avoid storing cookies for privacy of customer information.
28 5.2.4 The system shall lock the user after entering wrong password for 3 times.
29 5.2.5 The systems back-end servers will only be accessed by assigned administrator.
30
31 5.3 Software Quality Attributes
32 5.3.1 Reliability
33 5.3.1.1 The entire system shall be reliable if each component of the system works efficiently.

Page | 20
1 5.3.1.2 If the database is updated time-to-time then the system does not contain ambiguous data and
2 it is reliable.
3 5.3.2 Availability
4 5.3.2.1 The system shall be available 24 x 7 except for the downtime of the server on which the
5 system is dependent.
6 5.3.2.2 If the system faces hardware failure then an alternative page would be available.
7 5.3.2.3 In case where the system faces database corruption then data could be retrieved from the
8 server and the service would be available to use.
9
10 5.3.3 Portability
11 5.3.3.1 It is a web-based application hence built on scripting language and HTML so that it is fully
12 portable as you can access the application from any device like laptop, PC or mobile.
13

Page | 21
1 6. Other Requirements
2 Appendix A: Glossary
NSMS Nancy’s Salon Management System
SRS Software Requirements Specification
FAST ACCOUNTS Software used by accountant for tax and
accounts maintenance.
User Registered User in the system
Assistant Sarah is the assistant who is responsible for
appointment booking and supplies
management
Admin Owner is the admin of the system.
HTTPS Protocol used for secure data transmission.
GB Gigabyte
RAM Random-access memory is a form of system
storage
SSL (Secure Socket Layer)It is a standard security
layer for web browser and server.
SOH Stock on hand
Client Refers to the owner i.e. Nancy
3

Page | 22
1 Appendix B: Analysis Model
2 Use Case
3
4
5
6

Page | 23
1 Class Diagram
2
3
4
5 Appendix C: Minutes of Meetings
6 1. Meeting with Stakeholder - Agenda andMinutes
7
8 Group ID: 14

Page | 24
1
2 Date/Start Time: _29/03/2018 4:40 pm
3
4 Group Members Present
5
Names Roles played in this meeting
1. Sumin Susan Group leader
2. Daizy Balar Administrative assistant
3. Anaika Deshpande Quality assurance
4. Bhavi Chaudhari Interview summary preparation
6
7 Agenda prepared before this meeting
8
9
List of agenda items/Questions Outcomes/answers
1. What are the services currently offered? Haircut, Blow dry, Colouring, Washing,
Manicure, Facial.
2. Any fixed day for offering these services or
does it keep on changing?
There are currently no fixed days for any of the
services being provided.
3. Any additional services in the future? There is currently no intention to increase the
services being provided but there is scope for it
later in the future depending on the requests
from the customers.
4. For the services offered by part-time staff,
are you intending to employ full-time
employees to do them.
Not at the moment. But if there is any demand
in the future I would.
5. Is an online system for customer to book an
appointment your expectation?
No need for an online system for
booking. The main intention now is to
help in better rostering and the
following below points:
- Record of supplies and financial tasks
- Some part of customer booking
- Main task is rostering
- Scope for online system in the future
6. Currently how is the rostering done? Talk to them verbally about availability and
then roaster accordingly.
7. How many staff do you employ at the
moment?
12 employees, 8 full-time and 4 part-time
8. Should we provide a by-stander option in
case an employee calls in sick?
No by-stander option required as she would do
it manually. Main requirement is to have an
option to roster efficiently based on which day
is the busiest or which service is in most
demand.
9. Would you like to have a feature to notify if
the product quantity is over?
To avoid embarrassing situation like running
out or low in number of products. Notify/ remind
to order and also provide information about the
remaining quantity.
10. How many products are currently being
used?
Many products but the owner must be able to
add as many products as she wants.

Page | 25
1
Problems/issues/questions Resolution/outcome/answer
1. How ahead is the employee availability
details required?
1 week.
2. Do you want an option where employees
can swap their shifts?
Yes, that would be good.
3. When do you want the notify feature to be
triggered?
It depends on the product and she wants a field
to be added in the system where she can
specify the minimum quantity of the product.
4. Do you want a report being generated for
this and what is the frequency ?
- Weekly
- Number of clients being served and also the
peak hours
- Any additional report which we think would
help her in running the business efficiently.
2
3
4
5
6
7
8
9 Activities/Actions planned for next meeting
10
Activities/Action items Name of the individual(s)
responsible for this
activity
Due Date
1. Prepare interview questions. Address
and identify any gaps in the previous
collected information and interview the
stakeholder.
Anaika Deshpande 6/04/2018
2. Prepare interview questions. Address
and identify any gaps in the previous
collected information and interview the
stakeholder.
Sumin Susan 6/04/2018
3. Prepare interview questions and take
interview notes
Daizy Balar 6/04/2018
4. Prepare interview questions and take
interview notes.
Bhavi Chaudhari 6/04/2018
11
12 Meeting Ended At: 5:00 pm
13
14
15
16
17

Page | 26
1
2
3
4 Group ID: 14
5
2. Meeting with Stakeholder - Agenda and Minutes
6 Date/Start Time: 10:20am
7
8
10
1. Anaika Deshpande Group leader
2. Sumin Susan Administrating Assistant
3. Daizy Balar Quality Assurance
4. Bhavi Chaudhari Quality Assurance
11
13
1. Greet the stakeholder and build a rapport. Have a casual greeting with the stakeholder
about how she was feeling today and building a
good rapport with her.
2. Ask the stakeholder about the gaps in the
first stakeholder meeting.
a.In the first interview, Nancy mentioned about
John and Sarah.
b.If Nancy would manually enter the roster into
the system if she is provided with the
necessary reports.
c. Should the employees be given complete
privilege to edit their shift displayed in the
roster or would the stakeholder be willing to
include a request-approve process in
changing the shifts?
3. A summary of the current working of the
system from the earlier interview.
y agrees with the initial summary of the system.
4. Would you like to allow your employees to
have complete access to the system?
She wants her employees to have access to
the system. The features that are available to
them varies. As in, she wants the employee to
enter their availability. They need a provision to
accept the timetable shown as per the roster
and be able to send a request to change the
shift and see if the status of the request.
5. Who is Sarah and John? They are the employees. Sarah is takes care of
bookings and helps Nancy to keep track of
supplies.
John: - he is her accountant; he keeps track of
the financial data.
6. 3. Do you want to give provision to john,
where he can view the reports?
Access to the system is not given to John.
Either Nancy would personally provide John
with the necessary data or she expects the
system to send the report directly.
7. Is Sarah the only person who manages
appointments?
Yes, she is the one who takes the
appointments.

Page | 27
1
2
3 Other problems, questions & issues discussed during meeting not in the agenda
4
1. At the start of the second interview, Nancy
conveyed of an additional requirement to
The employees and the owner can access the
system. The features available for the
8. Would you like to set the roster a week
ahead?
Yes, a week or 2 weeks earlier.
9. If customers want to do bookings and if
the roster is not ready then will he/she be
able to do the bookings.
They have not come across such a situation in
the business until now and would most likely
not happen. The rosters are set at least 2
weeks in advance. But in case such a situation
arrives, the booking will not be taken.
10. What are the accessible features of the
system for the employees?
It is mainly the roster, in which they can enter
their availability. The employees should be able
to accept or reject the roster in addition to
being able to send a request for changing the
shift.
11. Would Nancy manually change the shift of
the staff, when the staff send the request
to Nancy?
Yes, she will manually change the shift.
12. what are the current problems that Sarah
is facing with bookings
Sarah uses reservation books to check the
availability of the staff at the time of customer
bookings. Every time she needs to check the
reservation book for the availability of the
employees and other features. This takes time
and the customer needs to wait.
13. How do you usually place and order for
supplies in inventory?
Nancy calls the supplier and ask him/her to
supply the product, which is running out of
supply.
14. Do you need a weekly or a daily report of
all the supplies that are overdue?
It is good to have a report regarding the supply,
but the main thing is she wants the system to
notify about the product, which is running out of
supply.
15. Would you manually place a call, or you
want system to order it for you?
No, she will be ordering by herself.
16. Do you want the system to keep details of
all the suppliers?
It would be good, if the system provides this
facility. When the notification pops up regarding
the minimum availability of stock, it is good if it
contains the details of the suppliers.
17. When you order the product, how is the
process done, do you want the system to
facilitate?
She wants the system to have the record of all
the existing products in numbers. Moreover,
when she receives new orders she wants to be
able to update the stock numbers as well.
18. Do you have any scanning machine to
scan the barcode of the product as it helps
in keeping track of the products efficiently?
No. she does not have one as she can identify
the products and is fully aware of the details.

Page | 28
the proposed system. employees depends on their job roles.
2. Are you intending to place the order every
time you are notified or at the end of the day
or after a week?
No, she cannot postpone it after a week
maximum to the end of day.
3. How do you distinct the product if barcode is
not attached?
She is aware about which kind of product she
ordered and can recognize it.
4. Are you planning to use the package fast
account externally or do you want software
to interact with our system to manage your
account?
It was just a suggestion, because it is easy to
use for those who do not have accounting
knowledge.
1
2
3 Meeting Ended At: 10:40am
4
5
6
7
8
9
10
11
12 3. Meeting with Stakeholder - Agenda and Minutes
13
14 Group ID: 14
15
16 Date: 13/04/2018 Start Time: 9.40am
17
18
19
21
1. Sumin Susan Administrative assistant
2. Daizy Balar Administrative assistant
3. Anaika Deshpande Group Leader
4. Bhavi Chaudhari Quality assurance
22
23
24
26

Page | 29
1. Build rapport with the stakeholder. A general opening question about how
Nancy is doing. In addition to whether she
expects a busy day today.
2. How do you calculate or set the wages
of the employees?
Each employee has a specific rate per
hour. Wages of the employees depend on
the number of hours they work at the
salon during the week.
3. Is the accountant notified about the
wages as it also involves calculation of
tax and maintaining pay slip.
Nancy expects the system to generate a
report so that John can carry out tax
calculations. The report should contain
number of hours, the rate and other
related information that are relevant to the
scenario.
4. So irrespective of the employment Nancy agrees. She also states that the
type, are the wages calculated on wages are not dependent on whether the
hourly basis? employee is under part time or full time
employment. Nancy also shares the
requirement in terms of how she expects
an interaction between the system and the
accounting software- Fast Account. The
accountant is currently working on the
software and she expects the reports
generated by the system to be compatible
with the software. As part of this change in
the requirement, Nancy expects an
integration of the salon management
system with the accounting software to
carry out the financial part of the business.

Page | 30
5. Stakeholder: John
Nancy mentioned about the decision to
use Fast Account software for
accounting purposes, what are the
basic reports, data and the format that
you want our system to provide to
facilitate the smooth operation?
Nancy wants the system to generate the
report in an excel format. In terms of type
of reports, she confirms that she requires
the report of all her incomes, expense and
the wages. For example, the information
regarding the expense would be the
money that Nancy earns during the week
by offering various services, bank interest
and the expense could be employee
wages, utility expense etc. Do research on
the basic data required for calculating the
tax returns.
In order to prevent any complications or
problems in the future, it better to provide
extra blank fields in the computer system.
This will provide Nancy an option to add/
update any extra information into the
report when required later on. In event of
any unexpected expense, Nancy can also
share this information into the system.
6. Therefore, we must provide extra user
fields in the database.
Yes. However, define the fields as
expense or income.
7. Currently you maintain all the data
manually by bookkeeping, but do you
expect the system to capture ad
maintain previous data in the system?
Nancy says that the data that is
mandatory in a system depends on the
type of the data. For example, the system
need not maintain the data regarding
previous appointments. At the same time,
she expects the system to store data
relevant to the supplies in salon.
8. So we were thinking of providing the
system with data inserted regarding
the customer, products, suppliers and
employees.
Nancy agrees.
9. The data like the earlier invoices and
the appointments made earlier would
not be included in the system.
Regarding the financial information, it is
better to incorporate the earlier financial
data into the system. Especially since the
different types of the financial data is of
importance during tax calculations at the
end of financial year.
10. So will you share the relevant financial
data?
Either Nancy or John would provide all the
relevant details required.

Page | 31
11. We believe that presently you do not
use a computer system. Do you have
any preference regarding the type of
system you want to buy?
Since the application runs on an internet,
the OS would not be an issue.
12. So just to clarify, you want and web
based system not a stand-alone
system.
Nancy wants the system to be web based
on the contrary to the previously agreed
terms, as she wants multiple users to
access the system. Hence, it is practical to
have an internet system so that multiple
users can access the system at a single
time.
13. What would be the must have
features?
Requirements mentioned as part of the
previous meetings are all the must haves.
Booking appointment keeping track of the
expense, supplies etc.
14. Would you require any additional fields
in the product descriptions apart from
these ones?
Nancy approves the product table layout
and reminds the need to display the
supplier details in the notification shown.
15. Another question is does the
customers have a provision to buy
items from the salon?
No. now there is no such facility. Nancy
buys the products only for using at the
salon.
16. Would you expect the system to keep
track of the customer data a well?
In some cases, she requires this facility.
Especially when the customer has booked
an appointment. It helpful in notifying the
customer of a cancellation of the
appointment due to unforeseen
inconveniences of the staff.
17. Nancy will be the admin. Do you want
the flexibility to modify accessibility
privileges of the employees at all
times?
Nancy says she should be able to edit the
assigned privileges of the staff at any time.
18. What is the preferred response time of
the system?
There were time constraints. Still Nancy
confirms that the response time can vary
depending on the task. However, she
expects the least response time-
maximum up to 2 seconds whenever the
situation directly involves a customer. On
the other hand, in the case of report
generation, depending on the volume of
data, up to 30s is permissible.

Page | 32
1
2
3
4
5 Other problems, questions & issues discussed during meeting not in the agenda
6
7
1. Do you want the system to be
accessible 24 *7?
Yes.
2. Do you want the system to send a
notification to the customer regarding
the appointment?
Nancy wants such a facility. Nevertheless,
she states that she does not want it to be a
confirmation process. A reminder, 24hr
before set appointment time via text
message would suffice.
3. Would you have an internet set up in the
salon?
Yes, Nancy confirms that the salon has an
active internet service.
4. We require some basic softwares for the
proper functioning of the system. Will you
install the same beforehand?
Nancy is of the opinion that while installing
the system; it is preferable to install the
necessary softwares that facilitates the
uninterrupted functioning of the salon
system.
8
9
10 Meeting Ended At: 10:40 am
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

Page | 33
1
2
3
4 Appendix D: Reflective Essay
5 Name: Daizy Balar Student Id: 12849663
6 The main motive behind this subject was to gather the business requirements. Firstly, we were
7 assigned with the case study named Nancy’s saloon. We were then told to come up with the
8 interview questions by playing various roles like:
9 ● Group leader
10 ● Quality assurance
11 ● Administrative assistance
12 Then we came up with the interview questions, user stories and use case description. Based on that
13 we did three interview sessions with the stakeholder or the shop owner named Nancy, the owner of
14 Nancy’s saloon in different time intervals. During the time of all the three interviews we came up
15 with her requirements. Based on this interview we were able to learn one of the skill that was
16 interviewing the stakeholders. We faced various problems during the time of those stakeholder
17 interviews, like in our first interview we were not sure what to ask and what not to ask. After the
18 first interview we came to know about what the actual requirement of the stakeholder is. During that
19 time span we came across various changes in the requirements of the stakeholders as well. Anyways
20 it was easy for us to keep track of all that interviews, as in after every interviews were told to make
21 the minutes of meetings to know what the question were asked to the stakeholder and what was the
22 requirement that we came up based on that. After that the next step was the Use Case Diagram and
23 that was the major twist, as in I was not sure about what and how the Use Case diagram is to be
24 made. So first we just went to some of the tutorials and came up with an idea. Use Case is basically
25 a list of the actions and the event steps which is typically defines the interaction between the roles
26 and the system for achieving that goal. Then we came up with the user stories and based on that
27 user stories we came up with the user description. This was the ultimate step where we got a glance
28 regarding the actual requirement of Nancy. Further SRS came in to the picture and that made our
29 work more complicated because no hints, no idea nor any kind of clarity about what to do and this
30 lead us into the deep research and we to come up with the best possible information regarding SRS
31 with the time span of two days. In this way we got cleared about what SRS is? SRS was the part of
32 the second assignment and it had many parts in it that leads us towards new areas and more and
33 more knowledge regarding something new. We made the class diagram and then the traceability
34 matrix. Many things in this case lead us with the deep research. There were many challenges that
35 we faced during our work hours for this topic. Finally, at the end we learned many things that
36 will be helpful for me in the future.
37 Taking this subject ended up with the bunch of skills that would be helpful to me in the
38 opportunities in the future. Starting with the interviews, research and ending up with group
39 coordinating skills and contacting myself to all the features and diagrams that would be helpful to
40 me in the near future.
41
42
43
44

Page | 34
1
2
3
4
5
6
7
8
9 Name: Sumin Susan Joseph Student ID:12774042
10
11 There were numerous issues we faced as a group and personally while approaching both the
12 assignments 1&2. Both the assignments challenged our abilities equally as it tests not just our
13 subject knowledge but also our ability to think critically and proactively. Completing the tasks in a
14 satisfactory manner proved to be a difficult task even though we managed to find a way to work
15 through this difficulty.
16 The primary obstacle was lack of experience in the software industry. Our group consists of
17 members who are straight out of under graduate courses, and lack of industry experience narrowed
18 their thinking. This was clearly reflected in our first stakeholder meeting were the number of
19 relevant and significant questions were very few. The ability to ask probing questions and thinking
20 beyond the normal flow was clearly absent, due to which the extra and new information we could
21 gather from the stakeholder was limited. Furthermore, the nature of the assignment also bought to
22 life various common issues concerning teamwork and planning. Due to these issues and the absence
23 of shared understanding of the requirement elicitation concepts and the case study, there was
24 substantial delay in completing the tasks.
25 After a difficult start, the team members made a conscious effort in planning the upcoming
26 interview session. More time was spent in practicing the art of questioning with group to develop an
27 ability to think critically and ask questions promptly. Personally, I felt that spending more time on
28 planning and collaborative team work assisted in gaining a better understanding about how to
29 approach the interviews and assignments efficiently and also how to utilize this opportunity to
30 develop the ability to ask challenging questions. One of the main approaches for improving
31 individual performance was to divide the sections of each assignment amongst the members for
32 completion. Later, other team members verified these sections. Adopting this method helped in
33 challenging the ideas of each individual and developed the idea better. This helped in transforming
34 the group works and assignment into more eventful and interesting experience.
35 In the future, more time should be spend on planning a strategy to approach the assignments
36 and group work. Rather than hurrying to solve the questions, time must be taken to assess the
37 understanding level of the group members and take approaches to not just complete the assignment
38 but also enhance the individual abilities. Another step that can be undertaken to improve the
39 individual and team performance is to, conduct collaborative reflection exercise.
40
41
42
43

Page | 35
1
2
3
4
5
6
7
8 Name: Bhavi Chaudhari Student id: 12799223
9
10
11 When first I read this subject outline, I found that this subject is beneficial and exciting. After that
12 when I attend the lectures and tutor, I see that this subject is constructive in future on this subject we
13 gain practical knowledge. That how to take a meeting? How to fulfil stakeholder or our customers'
14 requirements? In this, we have three meeting with our stakeholders based on our case study in this
15 meeting we gain a too much practical knowledge that how to ask the questions? How to prepare for
16 the meetings? After that in Assignment 1, we must describe the use case diagram, User Stories or
17 use case description based on our case study. In starting of this assignment, I do not know how to
18 start because I do not about the use case diagram and how to make a user description. After some
19 research and some help on the internet I learn about use case diagram, and then we start to make it.
20 In assignment 1 I have written 2 or 3 use case description based on use case and 8 to 9 user stories
21 based on our case study. In task 2 As per group discussion first, we studied the what ER Diagram
22 is? And How to make the ER Diagram? After that, we discussed in the group together about it and
23 shared knowledge with each other. We debated about salon specifications, and later we talked about
24 what to write in SRS. My contribution is in editing screens, i.e., login, registration, appointment,
25 etc., product features and made well presented in the document. If I talk about my group members,
26 they all are very supportive and helpful. If every problem on my part I ask them they always give
27 some solution to my problems. In this, I learn how an interview with the stakeholders takes? How to
28 prepare the question, how to make use case and stories based on the case study? All this part is
29 beneficial in our future life. In assignments in starting we have faced some problems regarding the
30 Use case and ER diagrams but after learning about that diagram in details we able to make it better.
31 If I do this subject related job in future than I must follow the things that I learn in this subject that
32 how to make a question? How to talk with the stakeholder? What type of requirements of their
33 business? All that things are most important to note on this subject that will be helped me in future.
34
35
36
37
38
39
40
41
42
43
44
45
46

Page | 36
1
2
3
4
5
6
7
8
9
10
11
12
13 Student name: Anaika Deshpande Student id: 12835423
14
15 Now that we are getting close towards the end of the semester, I realise that this subject has helped
16 me to enhance multiple skills like conducting elicitation interviews, negotiating with the
17 stakeholder, leadership skills and many more. At the beginning of the semester, we were told to
18 form a group of 4 and when I formed this group we didn’t know that we had different backgrounds
19 culturally as well as professionally. One of us had experience in the software development field
20 while others were fresh graduates from different backgrounds. Initially we had problems managing
21 our schedule for group meetings as all of us have different subjects. This somehow affected us in
22 the first elicitation interviews as we didn’t get time to plan and practice before the interview session.
23 All of us had various questions and as it was our first stakeholder interview we were not quite sure
24 what questions we should ask but the interview went surprisingly well. We got at least minimum
25 requirements of the stakeholder with which we could start working on our assignment.
26
27 With this experience we started watching videos on how to conduct meeting with the stakeholder
28 and this helped us in understanding what kind of questions we can ask stakeholder based on the
29 case study. At least I personally benefited from the video and lecture slides. At this point we needed
30 to dig deeper to get more specific requirements and hence we managed to arrange our schedule and
31 met a day before the interview and discussed what we should ask and how we should ask. We
32 decided our roles and all of us agreed that two of us will ask questions and others will take notes
33 during the interview. We also recorded the interview by taking stakeholder’s permission and that
34 was the best thing we did. When we got confused about certain things and what we were looking
35 for wasn’t available in the notes that’s when recording helped us. Our second interview was pretty
36 good as compared to the first one but we had many questions and couldn’t finish all questions
37 within the given time. After the second interview we had to make certain assumptions as we
38 couldn’t get answers to all our questions. We made a checklist of what we couldn’t cover in the
39 second interview so that we can ask that in the third interview. We had to submit the assignment
40 with those assumptions. Working in a group is not always easy, we faced schedule issue and due to
41 this we managed to submit our first assignment 5 mins before the deadline.
42
43 After our first assignment we arranged a group meeting for deciding the questions and doubts which
44 we needed to clarify with the stakeholder and the meeting went well and we managed to get
45 answers to most of our questions. It was good experience of having elicitation interviews.
46 Furthermore, when we started working on our assignment it was a challenging task to divide

Page | 37
1 sections for the assignment based on the capabilities of the individual. Work division is the best
2 approach to complete any task but timely integration of the task plays a major role. This helped us
3 complete our assessment tasks before the deadline.In future if given an opportunity to work on a
4 similar platform then I will definitely manage time and divide the work instead of making hasty
5 decisions. Overall, it was a good experience working in a diverse team.

Page | 38
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 Appendix E: Traceability Matrix

Inspection of Software Requirements Specifications (srs)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Inspection of Software Requirements Specifications (srs)

Similar to Inspection of Software Requirements Specifications (srs) (20)

More from Mohammad Emrul Hassan Emon

More from Mohammad Emrul Hassan Emon (20)

Recently uploaded

Recently uploaded (20)

Inspection of Software Requirements Specifications (srs)