Software Requirements Specification for CRM

This assignment provides a Software Requirements Specification (SRS) for a project titled 'CRM150'. It details the functional and non-functional requirements of the CRM system, including user roles, system functionalities, performance expectations, and security measures. The document adheres to industry standards and best practices for SRS writing, aiming to serve as a comprehensive guide for developers during the software development lifecycle.

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Software Requirements
Specification, SRS
For
The Australian Business Company, ABC
CRM150
“A Customer Relationship Management System”
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page i

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Table of Contents
1. SRS DOCUMENT INTRODUCTION ...................................................................................................... 1
1.1 P URPOSE OF D OCUMENT ........................................................................................................................... 1
1.2 DOCUMENT C ONVENTIONS ....................................................................................................................... 2
1.3 I NTENDED AUDIENCE AND R EADING SUGGESTIONS .................................................................................. 2
2. BUSINESS DOMAIN ................................................................................................................................. 3
2.1 T HE C LIENT ORGANIZATION ..................................................................................................................... 3
2.2 THE CLIENT ORGANIZATION PROBLEM ..................................................................................................... 3
2.3 P ROPOSED BUSINESS SOLUTION ................................................................................................................ 3
3. PROJECT INTRODUCTION ................................................................................................................... 5
3.1 P ROJECT S COPE ......................................................................................................................................... 5
3.2 P ROJECT A SSUMPTIONS AND C ONSTRAINTS .............................................................................................. 5
3.3 SYSTEM OPERATING ENVIRONMENT ......................................................................................................... 6
3.4 P ROJECT T ESTING APPROACH ................................................................................................................... 6
4. OUR SOFTWARE DEVELOPMENT METHODOLOGY .................................................................... 8
5. SYSTEM FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS ......................................... 9
5.1 S YSTEM FUNCTIONAL REQUIREMENTS ..................................................................................................... 9
5.2 S YSTEM N ON- FUNCTIONAL REQUIREMENTS ............................................................................................. 9
6. SYSTEM FUNCTIONAL DECOMPOSITION ..................................................................................... 11
6.1 FIRST S UB -SYSTEM (EXAMPLE , PEOPLE D ETAILS MANAGEMENT ) .......................................................... 14
6.2 S ECOND S UB -SYSTEM (EXAMPLE , SALES O RDER PROCESSING ) .............................................................. 17
6.3 T HIRD SUB - SYSTEM ( EXAMPLE , R EPORTS AND E NQUIRIES ) .................................................................... 17
6.4 AND SO ON… .................................................................................... ERROR ! BOOKMARK NOT DEFINED .
7. CANDIDATE SYSTEM CLASS DIAGRAM ........................................................................................ 26
8. System Database Modelling and Data Design
9. System User Inter Face
APPENDIX A: GLOSSARY...............................................................................................................................31
APPENDIX B: REFERENCES..........................................................................................................................2
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page ii

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Revision History
Name Date Reason for Changes Version
Team members 27 July 2017 First Version 0.1
Hoang Linh Nguyen 28 July 2017 Add Introduction 0.2
Shamima Akter and 28 July 2017 Add Project Introduction 0.3
Imran
Muhammad Umar 28 July 2017 Add Business Domain 0.4
Haral
Adel Aloqauli 28 July 2017 Add Software Development Methodology 0.5
Zheng Wu 28 July 2017 Add Business Problems 0.6
Hoang Linh Nguyen 28 July 2017 General review, combine and edit sections 0.7
Adel Aloqauli 28 July 2017 Add use case diagram for the development 0.8
methodology
Hoang Linh Nguyen 28 July 2017 Add 4.2 Testability (missing due to mistake) 0.9
and References
Hoang Linh Nguyen 09/09/2017 Improve Introduction 1.0
Shamima Akter and 09/09/2017 Improve Project Introduction 1.1
Imran
Muhammad Umar 09/09/2017 Improve Business Domain 1.2
Haral
Adel Aloqauli 09/09/2017 Improve Software Development Methodology 1.3
Zheng Wu 09/09/2017 Improve Business Problems 1.4
Hoang Linh Nguyen 09/09/2017 Add System Functional Decomposition 1.5
Diagram
Imran 09/09/2017 Add first Sub-system (Administration) 1.6
Adel Aloqauli 09/09/2017 Add second Sub-system (Sales Order) 1.7
Zheng Wu 09/09/2017 Add third Sub-system (Report and Enquiries) 1.8
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page iii

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Hoang Linh Nguyen 09/09/2017 Add Fourth Sub-system (Marketing) 1.9
Hoang Linh Nguyen 09/09/2017 Update Appendix A and Appendix B 2.0
Imran 09/09/2017 Add Candidate System Class Diagram 2.1
Muhammad Umar 27/09/2017 Improve Second Sub-system 2.2
Haral
Shamima Akter 27/09/2017 Improve Third Sub-system 2.3
Zheng Wu 27/09/2017 Add section 8 2.4
Imran 27/09/2017 Improve all the use case diagrams and section 2.5
class diagram (section 7)
Shamima Akter 28/09/2017 Improve Project Scope 2.6
Hoang Linh Nguyen 28/09/2017 Add Section 9: User Interface 2.7
Hoang Linh Nguyen 28/09/2017 Final review 2.8
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page iv

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
1. SRS Document Introduction
The introduction of the Software Requirement Specification (SRS) provides an overview of the
entire SRS including the purpose of document, document invention, intended audience and reading
suggestions [1]. The aim of this document is to fully define the complete Customer Relationship
Management 150 (CRM150) system and its functions which were built based on the requirements
required by stakeholders and their needs. Nevertheless, this document will present a number of
business issues that the client – the Australia Business Company (ABC) is facing caused by the
outdated software Sales Manager. The new CRM150 web-based system will be a perfect
replacement for the old system and also a powerful tool for the ABC to manage their relationship
with customers and to improve the business process.
The Unified Modeling Language (UML) will be used for visualizing, specifying, constructing
and documenting information about software-intensive system along with a number of use cases
to deliver a clear overview of the main system functional and non-functional requirements. The
use cases will mainly be used to describe the interactions between users and the system. All of the
collected requirements will also be listed fully in this document.
1.1 Purpose of Document
This Software Requirements Specification document specifically introduce and outline the
requirements for the CRM150 web-based system to the ABC senior managers and the executives
[1]. One of the main purpose of this document is providing a specific and objective view of the
CRM150 system, giving a good explanation of its complete functions. In addition, the main
concentration will be the requirements required by stakeholders and their needs of changes during
the testing process. This means that all the requirements made by stakeholders will be
documented and analyzed carefully and furthermore, any changing requirement during the testing
process will also be responded immediately. All of the requirements made by stakeholders will be
gathered, analyzed and listed fully in this document.
This SRS document contains seven main sections; each section is provided along with
its sub-sections.
Section 1, SRS Document Introduction
Section 2, Business Domain
Section 3, Project Introduction
Section 4, Our Software Development Methodology
Section 5, System Functional and Non-Functional
Requirements Section 6, System Functional Decomposition
Section 7, Candidate System Class Diagram
As a result, this document would be used as the central point of discussion among all the
interested stakeholders during the different phases of the system development lifecycle.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 1

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
1.2 Document Conventions
1. Business term’s first letters are Capitalised.
2. Abbreviations are CAPITALISED.
3. Important statements are bolded.
4. Text in italic needs to be confirmed or replaced.
5. The meaning of “must”, “should”, “must not”, “should not”, “may not”, “required”,
and “recommended” are defined as in RFC2119.
6. Text font used in Times New Roman with the size of 12.
7. Text font used for titles is Times New Roman - Heading 1 style (size 18) and subtitles
is Times New Roman - Heading 2 style (size14).
1.3 Intended Audience and Reading Suggestions
This document is intended for all the system stakeholders, it should be read and reviewed by:
1. The senior managers and executives of our client
2. The business analysts who are involved in the project
3. User and client representatives working in the subject area
4. Other reviewers who are experts in the subject area
Also, this document is to be reviewed and/or used by:
1. The project Team as a standard domain vocabulary for communication
2. System architect to create Solution Architecture
3. System analysts and designers for system design and modelling
4. Developers to implement the system
1. Testers for software inspections and testing against its principle and agreed-
on specifications
5. Client and end users for the continual testing and feedbacks
6. Documentation writers to create user’s and technical documents
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 2

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
2. Business Domain
Customer relationship management refers to the use of practices or strategies that are used by
companies for analysing the customer engagements [2]. The main involvement of this process is
the analysis of the various sales outlets like websites, stores or emails.
CRM helps in analysing the customer interactions and helps in predicting the sales growth. In
addition, it also helps in knowing the post engagement required in front of the target audience.
2.1 The Client Organization
The Australian Business Company, called ABC, is a noteworthy provider of electronic gadgets
and a vast supplier of specialized administrations built up in 1980 in Sydney, Australia. The
central mission of the organization is showcasing and offering diverse electronic gadgets as a
merchant/retailer for some global organizations, for example, Apple, Samsung, IBM, Sony, Group
and Xerox.
2.2 The Client Organization Problem
According the present situation, the company is using an old software application called “Sales
Management” which has raised problems due to it outdating that result to current system unable
to process insufficiently and functioning satisfactorily. This system could be isolation, non-
extensibility, and lacks openness. It will be hard for company to maintain the system due to the
expensive cost and the time for understanding internal workings of the system. Moreover, the
situation could be serious when the system has tis vulnerabilities that can result to security issues.
(1997, B. Wu, D. Lawless, J. Bisbal, J. Grimson, V. Wade, D. O'Sullivan, R. Richardson)
2.3 Proposed Business Solution
Although “Sales Management” unable working satisfactorily, it still can be improved by provide
a web-based interface through our service called “Customer Relationship and Business Processes
Manager” that convenient for people who are not familiar with software to use.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 3

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
3. Project Introduction
The Australian Business company which is a major supplier of electronic devices and a large
provider of technical services established back in 1980 in Sydney, Australia. Currently, the ABC is
using an old computer system. However, according to the present requirements and demands of
customer, the old system is no longer suitable. Additionally, in that case of updating this system, it
will be very expensive and unrealistic. According to that it has been decided by senior management
of ABC to create a new system. The project will only include the stages of system analysis and
design including modelling, database design and user interface.
3.1 Project Scope
The project includes a new software system analysis, design, modelling, database design and user
interface design. The need for new business requirements is mainly due to ABC's problem as the
existing system is no longer functioning adequately due to its age and insufficient and
unsatisfactory capabilities. In addition, the project includes an high-level description of a
potential solution to help the fundraising organisation to achieve their major objectives
3.1.1 Project Inclusive Aspects (Within the Project Scope)
The main aspects included in this project are the statement of the organization problem,
business drivers and technical constraints, functional Requirements, use case and
system class diagrams, non-functional Requirements, database design and model [3].
3.1.2 Project Exclusive Aspects (Out of the Project Scope)
The following aspects are out of the project scope:
1. Programming and coding
2. Unit testing
3. System environment setup
4. System hosting and deployment facilities
5. System configuration
6. System backup and restore facility
7. End users training
8. System maintenance and upgrade
3.2 Project Assumptions and Constraints
The main assumptions include licensing and general requirements for the business to use CRM
successfully. In addition, a remote sever set up which will provide sufficient security protection as
user’s personal information will be stored in the database. Moreover, staff will need to be
adequately trained in advance to easily transition from the old system increasing efficiency.
Furthermore, budget will be provided and managed by the client and storage of files will be
facilitated to fit government legislations of 6 years.
The various assumptions and constraints that needs adherence are included here. The software
must be accessible via a cloud based facility providing security and 24/7 access. In addition,
transactions and records must be stored to adhere to government legislations for a minimum of 6
years. The software must have compatibility features to enable user access from various platforms
and operating systems [3]. In addition, security of payments and information, like credit cards,
PayPal or bank transfer must be facilitated. Moreover, scalability to the client’s requirements and
Service Oriented Architecture Approach must be implemented.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 4

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
3.3 System Operating Environment
The system must be design as web-based set of applications that must be hosted in a cloud
facility for 24/7 availability. The reason for this is the flexibility and scalability cloud
computing provides. The Cloud computing technology helps to neglect the necessity for a physical
hardware by creating visual architectures. This helps the companies to work at a much faster rate.
1. Cloud computing technologies help to integrate software into the cloud where it can be used and accessed
from anywhere.
2. Almost all of the browsers allow access to the cloud architecture.
3. Reliability is another feature as access will always be guaranteed.
4. Security is also another benefit of this application.
5. According to the client, scalability is achieved.
3.4 Project Testing Approach
The development process will require the participation of the client company and their business
professionals at all time for monitoring the development progress of the project. Feedbacks and approvals
must be collected regularly at every stage of the development process changes will be made
accordingly before moving on to the next stage. The main focus of the system testing is to make sure
that the end result meets the business and user requirements. Additionally, the stakeholders will gain
their confidence by receiving a quality product. All of the components of the system will be evaluated
to ensure that they can work at the optimum level of working [3]. This process also includes the
reviewing of the process and this will be repeated continually until the system is successfully
implemented. Furthermore, customer's reviews, opinion, complain or additional requirements will be
documented to review for the next stages of project implementation.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 5

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
4. Our Software Development Methodology
The software development methodology used for this project management is the use of waterfall methodology.
This method is used making a sequential flow of the required steps to be integrated in the development phase of
the project [4]. These method resemblances a waterfall where the top layer is followed by underlying bottom
layer.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 6

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
5. System Functional and Non-functional Requirements
The introduction of the Software Requirement Specification (SRS) provides an overview of the
entire SRS including the purpose of document, document invention, intended audience and reading
suggestions [1]. In addition, the SRS report will be used to know about the main intentions of the
stakeholders as well as the software output.
5.1 System Functional Requirements
The first requirement of includes the presence of administrators to add new customer details or
delete them from the database. In addition, the administrators will also be able to create new orders
or delete them as well as track the order completion. Moreover, the administrator will also be able
to create system backup as well as edit sales report. The analysis report will also be made by the
administrators.
5.2 System Non-functional Requirements
The system is supposed to be in operations for 24 hours in a day and be responsive to the
authorities. In addition, the data will also be saved at regular intervals.
5.2.1 System Quality Attributes
The quality attributes are used to determine the attributes of the project management methods. This
includes the security, availability, maintainability and reliability [3].
5.2.2 Business Rules
The administrator should have full details of the user while a user is getting registered to the
system. Sales report will be generated weekly, quarterly or yearly [3]. The administrator should
have full access to sales reports.
5.2.3 Government legislations
While designing software plan, consideration of all the lawful necessities (that have been set by the
administration specialists to keep away from any business struggle or potentially wrongdoing) has
to be considered [4]. Software should retain the transaction of 5 years for company record and
Government audit. The transactions must contain all the records of receiving and sending
payments.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 7

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
5.2.4 Other Non-functional Requirements
It is necessary to keep backup of all data files and system in a separate directory / drive. In
addition, frequent auto-save of information to prevent loss of network connection and crashes of
browser and unexpected crash of the system is required [4]. Moreover, power supply should be
always on to assure the system is running all the time with no interruption.
6. System Functional Decomposition
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 8

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.1 First Sub-system (Administration Sub-System)
The purpose of this subsystem is to enable the client to manage the software on an Administrator
level [6]. They will have complete access to the software and will be able to customize the access
that their employees and users have when accessing the software.
6.1.1 Candidate Use Cases
The backup and restore is the first use case which will enable the administrator to
backup/restore the software if there are any major errors [5]. In addition, generate reports that
users may not have access to. They will also be able to edit customer accounts/details. They
can also customize what users can access and what level they can use the software.
Moreover, they can also update System and overwrite User Actions.
6.1.2 Sub-system Use Case Diagram
Fig: Administration sub system
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 9

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.1.3 Use Case Documentation
Identification
ID AD001 Package Administration
Name Backup & Restore Priority High
Description Administrator can back up the software and/or restore the system to an earlier
state.
Actors Admin User
Associated Use
Cases
Preconditions User has successfully logged in and has Administrator access
Post-Conditions System has been backed up or system has been restored successfully
Business Rules System registers that the backup has been processed
Non-Functional System should know which state of backup is being restored
Normal Flow
Actor Action System Response
This use case is enabled when an administrator System is
backed up
wants to “backup/restore” the system
Alternative Flows/ Exceptions
Condition System Action
No administrative
access System informs user they do not have access to perform
this action
Identification
ID AD007 Package Administration
Name Customize access Priority High
Description Customize what level of access users have when accessing the software
Actors Admin User
Associated Use Log in(include)
Cases
Preconditions User has successfully logged in and has Administrator access
Post-Conditions Users access has been altered to give more or take their access
Business Rules System updates users access
Non-Functional Refresh of the system now enabling the user their new access
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 10

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Normal Flow
Actor Action System Response
Change of user access level Changes in access level
Alternative Flows/ Exceptions
Condition System Action
No administrator access System informs user they do not have access to perform
this action
6.2 Second Sub-system (Sales Order Sub-System)
First introduce the main purpose of this sub-system showing all the client requirements that will be
fulfilled by developing this sub-system.
6.2.1 Candidate Use Cases
- Sign In / Sign Up: Sales clerks authenticates the user order and payment details
before processing the order
- Delivery Management: After authentication of the customer and his order the delivery staff
of the company processes the customer order and delivers it to the address provided by the
customer at login
- Order Management: Customer authenticates his account then orders for the product,
his order gets processed as soon as he provides his payment details and checks out.
- Check credit
- Check goods availability
6.2.2 Sub-system Use Case Diagram
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 11

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.2.3 Use Case Documentation
• Candidate Use Cases:
Identification
ID SS-001 Package Order Management
Name Customer Authentication Priority High
Description Customer authenticates his account then orders for the product, his order gets
processed as soon as he provides his payment
Actors User (primary)
Associated Use user login, payment, calculate total
Cases
Preconditions User has logged into the system and he is allowed to place order
Post-Conditions User has successfully added payment method and
Business Rules Order is processed when the payment details of the user is verified
System should prompt the user about payment details
Non-Functional
Normal Flow
Actor Action System Response
1. User enters the website and searches for
products
2.System displays the order page
3.User Chosen login, payment, calculate total
4. System gets accesses to database
5. System searches target data in database
6. System reads target data from database
7. User chosen the "Finish" option
8. System should prompt the user about
payment details when he checks out
Alternative Flows/ Exceptions
Condition System Action
3. we use case begins when the user 3.a we use case begins when the user logs into the
logs into the website portal and places website portal and places an order and the system
an order and the system displays the displays the order page
order page
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 12

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Identification
ID SS-002 Package Payment Management
Name Sign In / Sign Up Priority High
Description Sales clerks authenticates the user order and payment details before
processing the order
Actors Sales Clerk
Associated Use Customer authentication, payment details authentication, processing the order
Cases
Preconditions Authentication of user account and payment details
Post-Conditions Processing the order after authentication
Business Rules Order is processed when the payment details of the user is verified
System should prompt the user about payment details if they are incorrect
Non-Functional
Normal Flow
Actor Action System Response
1. The use case begins when the user has placed
the order and the sales clerk has verified his
account and payment details
2. System displays "payment details
authentication" interface.
3. User chosen Processing the order
4.System should prompt the user about payment
details if they are incorrect
Alternative Flows/ Exceptions
Condition System Action
User exits without placing the order or without adding
payment details the system will prompt the user to save
his details for a later session
Identification
ID SS-003 Package Delivery Management
Name Enquiry on Back Orders Priority High
Description After authentication of the customer and his order the delivery staff of the
company processes the customer order and delivers it to the address provided
by the customer at login
Actors Delivery Staff
Associated Use Order Verification, Order Processing, Order Delivery
Cases
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 13

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Preconditions After verification of the user details and order the order of the user is
processed
Post-Conditions The order is delivered to the customers address
Business Rules Order is processed when the user details and order is verified
If the order is not verified then it will not be processed for delivery
Non-Functional
Normal Flow
Actor Action System Response
1.he use case begins when the details and the
order of the user is verified and processed for
Delivery
2.System Display Order Verification, Order
Processing, Order Delivery
3. User chosen "Finish" option.
4.System Display Order is processed
Alternative Flows/ Exceptions
Condition System Action
If the details of the user and the order are not correct
then the order will not be processed for delivery
6.3 Report and Enquiries Sub-system
The purpose of this system is allowing user to collect target information from database
for documentation. Through the system, customer can search there back orders as well.
6.3.1 Candidate Use Cases
Produce Report – Get access to database to collect data and generate report.
Select Report Type – The content of report can be selected.
Format Report – Allow user to edit report.
Generate Chart – According the data from report to make chart.
Print Report – Allow report printed out.
Enquiry on Back Orders – User and check customers back orders, and customer can check
their own back orders.
Generate Enquiry form – Back orders are collected in a form.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 14

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.3.2 Sub-system Use Case Diagram
6.3.3 Use Case Documentation
Identification
ID RE001 Package Report & Enquiries
Name Produce Report Priority High
Description User produce a report with target data from database
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 15

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Actors User
Associated Use RE002 – Select Report Type (Include) – RE003 – Format Report (Extension)
Cases RE004 – Generate Chart (Extension) - RE005 – Print Report (Extension)
Preconditions User has successfully logged in and has right to produce a report
Post-Conditions System produce a Report with target data for user
Business Rules
Non-Functional System should generates report within one second
Normal Flow
Actor Action System Response
1. This use case begins when a user wishes to
produce a report. User chosen the “Produce
Report” option.
2. System displays the “Produce Report” page.
3. User chosen the "Report Type" option to select
the type of report.
4. System gets accesses to database
5. System searches target data in database
6. System reads target data from database
7. User chosen the "Finish" option to generate
report
8. System generates the report
9. System displays the report for user
Alternative Flows/ Exceptions
Condition System Action
1. User does not have accesses to 1.a System warns user needs accesses to produce report
produce report and displays method to get accesses
5. System cannot find target data in 5.a System displays option to exit produce report
database. interface or select other report type.
5.b If select other report type, system displays produce
report interface.
Identification
ID RE005 Package Report & Enquiries
Name Print Report Priority Low
Description User print the target report
Actors User
Associated Use RE001 – Produce Report
Cases
Preconditions User has successfully logged in, at least one report has been finished and a
printer is connecting
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 16

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Post-Conditions The report has been printed out
Business Rules
Non-Functional System should generate report
Normal Flow
Actor Action System Response
1. This use case begins when a user wishes to
print the report. User chosen the “Print
Report” option.
2. System displays "print Report" interface.
3. User chosen "finish" to print report.
4. System checks connecting with printer.
5. System checks state of printer.
6. System sends data of report to printer.
7. Printer prints out the report.
Alternative Flows/ Exceptions
Condition System Action
4. No printer is connecting with the 4a. System warns user to check connecting with printer.
system.
5. No printer is ready for print. 5a. System warns user to check the state if printer.
Identification
ID RE006 Package Report & Enquiries
Name Enquiry on Back Orders Priority Low
Description User/Customer get information of back orders of customer with order date,
product and payment
Actors User/customer
Associated Use Re007 – Generate Enquiry Form (Extension)
Cases
Preconditions User/customer has successfully logged in and has right to check back orders
Post-Conditions System displays the details of back orders
Business Rules Customer are not allowed to get others back orders
Non-Functional
Normal Flow
Actor Action System Response
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 17

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
1. This use case begins when a user/customer
wishes to check the back orders. User chosen
the “Check Orders” option.
3. User chosen time of back orders.
7. User chosen "Finish" option.
2. System displays "Enquiry on Back Orders"
interface.
4. System gets access to database.
5. System search target data in database.
6. System read the back orders.
8. System generates orders table.
9. System displays back orders.
Alternative Flows/ Exceptions
Condition System Action
5. Target order is not exist. 5.a System displays a warn that customer does not have
back orders in the period.
6.4 Fourth Sub-system (Marketing)
The main purpose of this system is to help the ABC to attracting new customers and expand their
market share. Also, it will improve the company image in the eyes of customer. Matching potential
customers with their products, maintain the relationship between them, therefore ensure the
profitability for the client.
6.4.1 Candidate Use Cases
- Create promotion: Allow the administration to create new promotion, product sales and
offer program
- Run campaign: Enable Administration to manage the ongoing campaign along with the
marketing employee
- Search for customers: Matching potential customers with the company products
by analysing and sorting market data
- Engage audiences: Allow customers to approach company products and service information
- Advertise products: Using advertising tools such as the Internet, television or newspaper to
advertise products and services
- Survey market: Collecting and analysing market data giving out and recollecting survey
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 18

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.4.2 Sub-systems and Use Case Diagram
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 19

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.5 Fifth Sub-system (People Details)
6.5.1 Use Diagram
6.5.2 Use Case Documentation
Identification
ID ID1 Package Manage People Module
Name Add person Priority Medium
Description Add the person into the system
Actors Administrator
Associated Use Search Person
Cases
Preconditions Administrator has logged in
Post-Conditions Person account is added successfully
Business Rules Administrator have to fill in all person details Non-
Functional Person account password should be auto-generated
Normal Flow
Actor Action System Response
1. Administrator clicks add person button
2. System display all fields of person
details to enter
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 20

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
3. Administrator enters all person details
4. Administrator click Submit button
7. Administrator confirms the message
5. System added the person account
to database
6. System display account added
successful message
Alternative Flows/ Exceptions
Condition System Action
1. Administrator enters the 2. System displays error messages
wrong username and
password
3. Administrator enters invalid 4. System displays warning message and asks
data into fields for trying again
Identification
ID ID2 Package Manage People Module
Name Update person Priority Medium
Description Update the person into the system
Actors Administrator
Associated Use Search Person
Cases
Preconditions Administrator has logged in
Post-Conditions Person account is updated successfully
Business Rules Administrator have to update in all person details
Non-Functional Person account password should be auto-generated
Normal Flow
Actor Action System Response
1. Administrator clicks “browse person
list”
2. System display all person accounts
3. Administrator select one person
account
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 21

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
4. System display the account detail
5. Administrator edit the data
6. Administrator click submit button
7. System asks for confirmation and
display
8. Administrator confirms the update
9. System updates the person account
Alternative Flows/ Exceptions
Condition System Action
1. Administrator enters the 2. System displays error messages
wrong username and
password
3. Administrator enters 4. System displays warning message and
invalid data into fields asks for trying again
5. Administrator enter person 6. System search accounts by person id and
id to search display results
7. Administrator click “Cancel 8. System abort update and return to person
update” list page
Identification
ID ID3 Package Manage People Module
Name Search person Priority Medium
Description Search the person account in the system
Actors Administrator
Associated Use Search Person
Cases
Preconditions Administrator wants to search the person account
Post-Conditions Person account existed and person account detail is displayed
Business Rules Administrator wants to search the person account
Non-Functional
Normal Flow
Actor Action System Response
1. Administrator clicks “search person”
2. System display the search bar for
entering
3. Administrator enters the person Id
4. System searches account by ID
5. System display the account result info
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 22

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6. Administrator browse the person
account detail
Alternative Flows/ Exceptions
Condition System Action
1. Administrator enters the 2. System displays error messages
wrong username and
password
3. Administrator enters person 4. Person account ID not existed
ID
6.6 Sub-system (Forecasting Payroll)
6.5.1 Use Case Diagram

Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 23

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
6.5.2 Use Case Documentation
Identification
ID FP-007 Package Forecasting Payroll Module
Name Transfer Payment Priority High
Description Managing Payment and Running Payroll
Actors Customer/employee
Associated Use FP-008-Run Payroll (Include), FP-009-Manage payment (Extension)
Cases
Preconditions User need to choose right transfer method
Post-Conditions process transferring after verifying
Business Rules Payment will transferred after verifying card
Non-Functional System should complete transfer method within one second
Normal Flow
Actor Action System Response
1. This use case will begin when
customer is ready for transferring
2. Select This use case will begin
when customer is ready for
transferring payment amount
Alternative Flows/ Exceptions
Condition System Action
1. Not have sufficient balance 1.a transfer cancelled
Identification
ID FP-004 Package
Name Run Payroll Priority
Description Transferring payment and calculating salary
Actors Administrator /accounting manager
Associated Use FP-005- Calculate salary(extension) , FP-006-Transfer Payment
(Include)Cases
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 24

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Preconditions Manager has successfully blogged in Post-Conditions Process
Payment method after verifying Business Rules Payment should be verified
before transferring Non-Functional System should complete transfer method
within one second
Normal Flow
Actor Action System Response
1. This use case will start when user is
ready for making a
payment
2. System displays “choose the
right amount
3. Payment successful
Alternative Flows/ Exceptions
Condition System Action
Identification
ID FP-001 Package Forecasting Payroll Module
Name Manage Payment Priority High
Description Verifying Payment and Transfer Payment
Actors User
Associated Use FP-002-Verify Payment (extension) , FP-003-Transfer
Cases Payment(extension)
Preconditions User has successfully logged in
Post-Conditions Finish verifying and transferring payment
Business Rules Payment will be approved after verifying
Non-Functional System should verify or transfer Payment within one second
Normal Flow
Actor Action System Response
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 25

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
4. This use case will start when
customer is ready for Payment
6. Customer choose card type
7. Select amount
5. System display “choose payment
method”
8. Payment or transfer approved
Alternative Flows/ Exceptions
Condition System Action
1. Customer put wrong pin 1.a Transaction declined
Number
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 26

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
7. Candidate System Class Diagram
This class diagram depicts the relationship among various objects of the project. In addition,
the attributes of them are also depicted to provide a clear view of the project method.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 27

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
8. System Database Modelling and Design
Database management is the use of a database in a system to store records pertaining to an
organization. As the traditional method of information storage is not sufficient to reference the
storage options, the databases are a most viable choice for such addressing.
8.6 Database Metadata (Data Dictionary)
Metadata is data that describes attributes of data in database. For example, metadata include
data name, length, format and requirement.
Table: User
Name Type Min Max Source
Leng
th
N
ull
? Value Value
System
CustomerID Unique ID Integer 7 No 1 9999999 generated
Alphanum
F_Name First Name Eric 20 No - - User entry
Customer
Name Alphanum
Last Name Eric 20 No ---- - User entry
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 28

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Customer
Gender Gender Option!!! -- No! -- -- User select
Customer
Email Email Text 30 No -- -- User entry
Phone
Phone
Number Number mobile 10 No -- -- User entry
Address
Customer
Address Text 60 No -- -- User entry
Table: Admin
Name Description Type Lengt Null Min Max Source
h ? Value Value
Integ System
AdminID Unique ID er 6 No 1 999999 generated
AdminPassw Second
ord Password Text 20 No -- -- User entry
Table: Report
Name Descriptio Type Lengt Null Min Max Source
n h ? Value Value
Integ 99999999 System
ReportID Unique ID er 10 No 1 99 generated
ProduceDa System
te Date Date -- No -- -- generate
ReportTyp Type of Optio
e Report n -- No -- -- User Choose
Table: Order
Name Descriptio Type Lengt Null Min Max Value Source
n h ? Value
Intege 9999999999 System
OrderID Unique ID r 12 No 1 99 generate
OrderDat System
e Date Date -- No -- -- generate
OrderTot Decim
al Total Price al 8 No 0.10 999999.00 User Choose
Table: Shipping
Name Description Type Lengt Null Min Max Source
h ? Value Value
Integ 999999999 System
ShippingID Unique ID er 11 No 1 99 generate
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 29

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
ShippingDat System
e Date Date -- No -- -- generate
ShippingSta State of Optio System
tus Shipping n -- No -- -- generate
TargetAddr
ess Address Text -- No -- -- User entry
Table: Payment
Name Description Typ Leng Nul Min Max Source
e th l? Value Value
Integ 999999999 System
PaymentID Unique ID er 12 No 1 999 generate
PaymentDat System
e Date Date -- No -- -- generate
PaymentMet Meothod of Opti
hod Payment on -- No -- -- User select
Table: Product
Name Description Type Lengt Null Min Max Source
h ? Value Value
Intege System
ProductID Unique ID r 5 No 1 99999 generate
ProductNa
Me Name of Product Text -- No -- -- User entry
ProductTy Optio
Pe Type of Product n -- No -- -- User select
Price of each Decim
Price Product al 7 No 0.10 99999.00 User entry
Intege
Stock Stock of Product r 5 No 0 99999 User entry
Table: OrderLine
Name Description Type Leng Null Min Max Source
th ? Value Value
OrderLin Intege 999999999 System
eID Unique ID r 12 No 1 999 generate
System
Product Name of Product Text -- No -- -- generate
Number of Intege System
Quantity Product r 2 No 1 50 generate
Price of Single Decim
Price Product al 7 No 0.10 99999.00 User entry
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 30

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
9. System User Interface Design
When software is created the design of it includes a complex analysis of the presentation of it. The
most basic requirements are the creation of a user interface [7]. This enables the software to
become visually attractive to its stakeholders. The main characteristics of an user interface is:
• Attractive
• Simple to use
• Responsive quickly
• Clear to understand
• Consistent on all interfacing screen
This project method includes the presentation of a simple and visually attractive user interface
designs.
- Simplicity: User can get their goal as fast as possible without going through complicate process
- Usability: Design the user interface to maintain ease-of-use and enhance the
users’ learn ability of the applications
- Consistency: Use the same or familiar layout for all screens
- Use Guidance: Provide users with as much as possible necessary information and
guidance about the system
In addition, Visibility, User Diversity, Customizability and other principles were also be considered
during the design process.
Lastly, in order to create a good system user interface, we consider all factors by answering
a number of questions:
- What is the purpose of your system?
- Who really are our users?
- What makes them tick?
- What are they hoping to accomplish?
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 31

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
9.6 Screen Specifications
This section includes the development of the screen of the software. In addition, the various pictures
of the intended developed software is also included in this section.
9.6.1 Sign In Page
Sign In page will be the first thing that will be used to interact with the users of the software when
they open up the CRM150 web-based application. The various stakeholders will be in charge of
interacting with the software of the company. The logo of the Australia Business Company will be
significantly highlighted to showcase the user interface. Users just need to type in their user name
and password [6]. Signing in of the system guarantees authentication which is used for security
enhancements. To summarize, our sign in page was designed to be as simple and familiar as
possible for users to have a good first impression with the system.
Element Type Format Null V & V Remarks
User Name Character Single Entry No Unique and
does not
contain space
Password
Character
Single Entry
No Must match
with the
database
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 32

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
9.6.2 Sign Up Page
When users want to create a new account, after clicking on the “Register” button, the sign-up page
will pop up. This is basically an application form for users to fill in necessary information to create
an account. The screen title is SIGN UP. This screen is designed for new users who not yet had an
account. In addition, there are two extended screens from the sign-up screen.
Firstly, the “Successful Sign Up” screen
Logging in message analyses the presence of an account. The here is integrated in the first page to take the users to
some other link. Submit is used to complete the logging process.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 33

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
This process is followed by a notification pop-up to inform users that their accounts haven been
successfully created. Furthermore, the system will also ask users if they want to receive news
about products, promotion or other via their email address. This pop-up will also come with a
thank you note to show the appreciation of the ABC to their customers. This screen is related to
sign-up use case. The main purpose of this screen is to welcome the new customers to the
CRM150.
The second extend screen is the “Sign Up Warning” screen.
This screen is also a pop-up that will appear during the registration. This screen informs the users that
all their data is not saved and they will have to fill in the data again. This screen is related to the sign
up use case. The warning sign will be extremely highlighted in red colour for attention and the YES
option will also be placed in a red box. Login is used to get user access whereas submit is used to
submit the credentials.
Element Type Format Null V & V Remark
First Name Free Text Single Entry Yes Proper Case
Entry Format
Last Name Free Text Single Entry No Proper Case
Entry Format
User Name Character Single Entry No Unique and Will become
does not unique
contain space
Password Character Single Entry No From 5 to 25 Will be save
characters on the system
for future
cross check
Email Character Single Entry No Must follow Cannot be
xxxxxx@.xxxx reused
Title
Text-
Tick box
No Must be from Admin will
one of the be able to add
existing value new value to
the existing list
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 34

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
9.6.3 Update account information page
After the user successfully sign up for a new account and sing in to the system, they will be able to
edit and update their private information. The screen title is UPDATE ACCOUNT
INFORMATION.
The “Update profile” will be placed at the bottom left of the screen and be highlighted in blue.
Element Type Format Null V & V Remark
First Name Free Text Single Entry Yes Proper Case
Entry Format
Last Name Free Text Single Entry No Proper Case
Entry Format
Email Character Single Entry No Must follow Cannot be
xxxxxx@.xxxx reused
Title Text- Tick box No Must be from Admin will
Predefined one of the be able to add
new value toexisting value
the existing
list
Phone
Number Numerical Single Entry Yes Start with +61
for references Must be
Australia
phone
Numbe
r, else it
will not
work
Address Text Single Entry Yes Must come
with postcode
Billing Text Single Entry Yes Must come
address with postcode
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 35

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
9.6.4 Create Campaign Page
The campaign creation page is the exclusive option for the system admin to access. Here they can
create a new advertisement campaign which will be activated and running following a schedule.
The screen title is CREATE CAMPAIGN.
Type Format Null V & V Remark
Campaign name Free Text Single Entry No Unique name NA
Entry and cannot
be reused
Type Text- Single Entry No Must be from Admin will
Predefined one of the be able to
existing add new
value value to the
existing list
Description Free Text Single Entry No NA NA
Entry
Start Date Date Single Entry No Must be on NA
or after the
creation day
End Date Date Single Entry No Must be at NA
least after
Start Date
Budgeted
Cost Numerical Single Entry No Positive NA
Amount
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 36

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Actual Cost Numerical Single Entry Yes Positive NA
Amount
9.6.5 Update Campaign
Active campaign lists those which are active. The status bar shows the campaign status, whether they are active or not.
This screen is for Administrator to access the campaign. The screen title is UPDATE CAMPAIGN.
This will be related to the use case Create Campaign and Distribute Campaign. The design was
kept consistent with the create campaign page. However, the summary of the running campaign
will be displayed on the right of the screen to assist user during the process of editing. This extra
display will help the administrator to make smart decision on the campaign. The “update” button
will be placed beside the “cancel” button. They will be highlighted in green and red and will be
placed at the bottom of the screen.
Element Type Format Null V & V Remark
Campaign Free Text Single Entry No Unique name NA
name Entry and cannot be
reused
Type Text- Single Entry No Must be from Admin will
Predefined one of the be able to add
existing value new value to
the existing
list
Description Free Text Single Entry No NA NA
Entry
Start Date Date Single Entry No Must be on or NA
after the
creation day
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 37

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
End Date Date Single Entry No Must be at NA
least after
Start Date
Budgted Cost Numerical Single Entry No Positive NA
Amount
Actual Cost Numerical Single Entry Yes Positive NA
Amount
9.6.6 Menu Side Bar
Menu Side Bar is a tool that used to minimize and hide all the tabs into one button. The button will
be located in the top right corner of the screen. When it is clicked, a side bar will appear on the right
of the screen with all the options that are available for users. The main purpose behind the using of
menu side bar in the CRM150 system is to simplify the user interface as much as possible. This will
also organise the layout of the screen and bring to the system a smarter look.
This menu side bar will relate to all the use cases because it will contain all the options
and available task for users.
9.6.7 Create Report Page
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 38

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Creating report assists business by convey and combine the essential information to support
decision making. The title of this screen is CREATE REPORT. This screen was designed to
allow administrator or staff to create a business report with recorded information. Most of the
information needed for the system to create a report will be predefined. Creator can preview the
report before saving and print the report.
The software can only access the visa or debit features of the banking details and hence the requirements.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 39

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
This section is used for submitting your payment details before you can proceed. On the right side
of the User Interface, there is an
Order Summary which basically gives brief information about the product(s) you are about to
purchase. It will display the product name, quantity, total price, estimated delivery date and your
delivery address. In summary, this payment method page is simple and clean designed to be easy to
use for all audiences.
Element Type Format Null V & V Remark
Name on Card
Text Single Entry No Must be the
same on the Data will be
secure
credit card confirmed
with the bank
Card Number Numerical Single Entry No Must be the Data will be
same on the secure
credit card confirmed
with the bank
CVV Numerical Single Entry No Must be the Data will be
same on the secure
credit card confirmed
with the bank
Expiration Month/Year Single Entry No Must be the Data will be
Date same on the secure
credit card confirmed
with the bank
9.6.9 Feedback Page
The rating page will appear once you finish using any service and will give you a few options of
rating. These options are Very Happy, Happy, Neutral, Sad and Very Sad. There is also an optional
comment box below the ratings to give feedback on the software. This allows further improvements
on the software from customer comments. Once you submit after you rate and comment, this data is
then collected in a database and then reviewed manually by a user. The comment box is for further
comments which will be reviewed and responded by the staff.
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 40

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150

Appendix A: Glossary
Here, you state all terms, abbreviations and any other standard words that used in this document
with their description or full names, for example…
SRS Software Requirement Specification
ABC Australia Business Company
CRM Customer Relationship Management
UML Unified Modelling Language
CRM150 Customer relationship management
UI User Interface
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 41

ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150
Appendix B: References
[1] Wiegers, Karl, and Joy Beatty. Software requirements. Pearson Education, 2013.
[2] Davis, Alan. Just enough requirements management: where software development meets
marketing. Addison-Wesley, 2013.
[3] Laplante, Phillip A. Requirements engineering for software and systems. CRC Press, 2013.
[4[B. Wu, D. Lawless, J. Bisbal, J. Grimson, V. Wade, D. O'Sullivan, R. Richardson, "Legacy
systems migration - a method and its tool-kit framework", Proc. of the Joint 1997 Asia Pacific
Software Engineering Conference and International Computer Science Conference
(APSEC'97/ ICSC'97), 1997-December.
[5] Software Testing Class. (2017). System Testing: What? Why? & How?. [online] Available at:
http://www.softwaretestingclass.com/system-testing-what-why-how/ [Accessed 26 Jul. 2017].
[6] Henning Gebert, Malte Geib, Lutz Kolbe, Walter Brenner, (2003) "Knowledge‐enabled
customer relationship management: integrating customer relationship management and
knowledge management concepts [1]", Journal of Knowledge Management, Vol. 7 Issue: 5,
pp.107-123, https://doi.org/10.1108/13673270310505421
[7] Henning Gebert, Malte Geib, Lutz Kolbe, Walter Brenner, (2003) "Knowledge‐enabled
customer relationship management: integrating customer relationship management and
knowledge management concepts [1]", Journal of Knowledge Management, Vol. 7 Issue: 5,
pp.107-123, https://doi.org/10.1108/13673270310505421
[8] Itinfo.am. (2017). Software Development Methodologies. [online] Available at:
http://www.itinfo.am/eng/software-development-methodologies/ [Accessed 30 Jul. 2017].
[9]Cs.utah.edu. (2017). Software Requirements Specification. [online] Available at:
http://www.cs.utah.edu/~drcannon/project/SRS.html [Accessed 28 Jul. 2017].
Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permission Page 42