Software Requirements Specification
Software Requirements Specification
Software Requirements Specification
Specification
for
Prepared by
1. Akash Saxena(A00155793)
2. Hannah Ho (A00146832)
3. Adreana Fernandez(A00153773)
Group III
19 December 2017
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for <Project> Page ii
Table of Contents
Table of Contents .................................................................................................................. ii
1. Introduction .................................................................................................................... 1
1.1 Project Vision ............................................................................................................................... 1
1.2 Project Scope ............................................................................................................................... 1
2. Overall Description .......................................................................................................... 2
2.1 Product Perspective..................................................................................................................... 2
2.2 User Classes and Characteristics ................................................................................................. 2
3. System Features .............................................................................................................. 3
3.1 System Feature 1 ......................................................................................................................... 3
3.2 System Feature 2 ........................................................................................................................ 4
4. Data Requirements .......................................................................................................... 6
4.1 Logical Data Model ...................................................................................................................... 6
4.2 Data Dictionary ............................................................................................................................ 7
5. External Interface Requirements ...................................................................................... 9
5.1 User Interfaces ............................................................................................................................ 9
6. Quality Attributes .......................................................................................................... 11
6.1 Usability ..................................................................................................................................... 11
6.2 Performance .............................................................................................................................. 11
6.3 Security ...................................................................................................................................... 12
Appendix A: Glossary........................................................................................................... 12
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 1
1. Introduction
The beginning of this report is an overview of project’s vision and scope, and its content covers five main
sections of Software Requirements Specification. First, it starts by listing all the user classes and their
characteristics. Second, the two most important system features (Membership and Show Title
Management) are presented in user case diagram and functional requirements. Next, the data requirement
is documented by domain class diagrams and data dictionary. The second last topic is user interface of two
major processes which also plays a vital role in this document. Finally, some non-functional requirements
are written down to consider during the design phase.
Feature Release 1
FE-1, Create / edit New member can create account of one or more than one of 4 local art clubs
account A current member can change their personal information
FE-2, Pay annual fee Member can pay their annual fee by a valid credit or debit card of any bank
which has branch in Canada
FE-3, Manage Membership reports can be designed, displayed or extracted (include
membership information: Member ID, name, Art club, status, Start date, End date, show
titles, …)
FE-4, Post show title Create new show title(s) for an art show, and all mandatory fields must be
entered and validated.
FE-5, Manage show titles Show title reports of any art show shall be generated in standard or customized
view as Executive members require.
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 2
2. Overall Description
2.1 Product Perspective
The Art Club comprises of 50 to 200 local artists in each art club, who involves themselves in various shows
on a daily basis. They are working together to build a system to manage their work online as they currently
are managing them in Spreadsheets. A system, website, is a proper tool to manage their show titles,
members, and sales.
President and Vice Sponsor and approver for project as well as indicate the objects of project.
President Their expectation of new system is that it shall eliminate or reduce manual
workings and improve efficiency of management activities.
Treasurer, Secretary Take care of administrative activities of art clubs, and be key users to provide
business processes or requirements of their sections.
New system shall support them in ne member registration and mange income
from annual fee and sale commission more effective and systematical.
Managers (for Manage members and show titles, and be the vital representatives of project
Membership and who will participate in most of stages.
Show Titles) New and update information related to members or show titles shall be stored in
database of system in which they are more accessible and traceable.
Administrator This is the new role to support and train users get familiar to new system, and
reflect changes or updates into system as Executive members require.
Administrator has a full access to system.
Artist Members post their art pieces to system and view sale revenue of their art
workings.
The most important feature to this user class is to create show title and upload
image.
Project team (Business Create and monitor project plan, accomplish requirements elicitation, implement
Analysts, Developers, and maintain system in the sensitive time, and provide training for users.
Testers, Project
Managers)
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 3
3. System Features
3.1 System Feature 1: Membership management
3.1.1 Description
This feature shall provide some functions such as: creating member account, modifying member’s
information, changing member’s status (active, inactive, terminated), paying annual fee as well as viewing
and extracting reports related to members.
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 4
1. System shall display log in / sign in page for user to create member account
4. System shall create a member account for a valid set of input information
5. System shall show an error message if an invalid set of input information is entered
7. Member shall be able to pay annual fee by either debit or credit card
This feature shall provide some functions such as: creating and editing show title, posting the art piece
image, printing show tile, viewing historical and current show titles, emailing to ask for more submission
and generating reports related to show titles.
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 5
3. System shall generate a label of show title which is ready for printing
4. Member shall edit information of show title before the art show happens
5. System shall show an error message if a member attempts to edit show title of others
7. Member shall be able to create more than one show title for an art show
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 6
4. Data Requirements
4.1 Logical Data Model
Domain Class Diagram
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 7
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 8
+ Start Date Date 10 Not null The first day that member
(dd/mm/yyyy) joins art club
+ End Date Date 10 Accepted null The day that member leaves
(dd/mm/yyyy) art club
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 9
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 10
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 11
6. Quality attributes
6.1 Usability
The system shall provide a uniform look and feel between all the web pages. The system shall
provide a digital image for art work. The system shall provide use of icons and toolbars.
6.2 Performance
The product shall be based on web and has to be run from a web server. The product shall take
initial load time depending on internet connection strength which also depends on the media from
which the product is run. The performance shall depend upon hardware components of the
client/customer goals right with the corresponding functional requirements, rather than collecting
them in this section.
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 12
6.3 Security
All the security will be assessed by this roles and permission matrix.
Administrator
Coordinator
General Public
Managers
Management
Employee
Executive
Members
Artists
Employee
Membership
Non-
Show Title
Roles and Permission Matrix
System Operations
Creating User Account *
Membership Validation * * *
Sending notifications to Artists * *
Changing status from active to inactive
Change/Submit own Art Work * * *
Change/Submit art work on behalf of
others * *
Changing Roles of the members
Print Title report and labels of art for Art
Show * * *
View Confidential information * * *
Terminate membership * *
Can see/Buy Art Work *
View all entries of past and current Shows * * *
Accounts and Finance
Send Due payment notice * *
Accepting Art Work Payments *
Collect Membership fees * *
Change Account * * * *
Appendix A: Glossary
SRS – Software Requirement Specification
Client – Art Club
UI – User Interface
WebUI – Website User Interface
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 13
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 14
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Software Requirements Specification for Art Club Project Page 15
Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.