System Requirements Specifications

This document provides an overview of the system requirements specifications for the mobile repair system. It includes information on user interfaces, hardware interfaces, software interfaces, functional requirements, use cases, classes/objects, non-functional requirements, and design constraints. The document also outlines the logical database requirements and other system requirements. References are provided for further reading.

1System Requirements Specifications
HS3052 Capstone Project Group
Assignment-1: Project
Management
System requirements
specifications
Group:M1-01
INT3324 Sukhdeep SIDHU
CU3074 Xinjia FENG
INT3325 Yogesh SINGLA
SEC2103 Zhiqiang YAO

2System Requirements Specifications
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
Below are the system user interfaces.
i. The system login interfaces.
ii. The system data capture interfaces.
iii. The databases backend interfaces.
3.1.2 Hardware Interfaces
The below are the hardware interfaces that will be used in the mobile repair system to enable the
users to interact with it who includes the staffs and the clients.
i. Computer system.
ii. The network system.
iii. Internet access devices.
iv. External hard disks and flash disks.
v. Server system.
3.1.3 Software Interfaces
The below are the software applications that will be used in the mobile repair system to enable
the interaction and interfacing the users and the system hardware.
i. Windows operating system.
ii. Computer antimalware application.
iii. Web browsers.
iv. The server applications.
v. Database server software.
3.1.4 Communications Interfaces
The following are the communication interfaces for the mobile repair system.
i. Network cables.
ii. Network switch
iii. Network routers

3System Requirements Specifications
3.2 Functional Requirements
The following are some of the functional requirements.
i. System should enable user to capture client’s details.
ii. The system should enable users to capture the mobile phone details.
iii. The system should enable the user to capture the repaired phones.
iv. The system should enable the users to capture the technician details.
v. The system should enable users to capture the repair parts stock details.
vi. System should enable the users to capture the used repair parts.
3.3 Use Cases
Below are the mobile repair use cases.
3.3.1 Use Case #1: Record clients details
This is where the staffs record the details of the client with fault device in the system.
3.3.2 Use Case #2: Record technician details
This is where the staffs record the details of the technician in the system.
3.3.3 Use Case #3: Record fault phone details
This is where the staffs record the details of the fault phone devices in the system.
3.3.4 Use Case #4: Record repaired phones details
This is where the staffs record the details of the repaired phones in the system (Tycho, 2014).
3.3.5 Use Case #5: Record used repair parts details
This is where the staffs record the details of the used repair parts in the system.
3.3.6 Use Case #6: Record repair parts stock details
This is where the staffs record the details of the repair parts stock in the system.
3.3.7 Use Case #7: Record repair charges details
This is where the staffs record the details of the repair charges in the system.

4System Requirements Specifications
3.3.8 USE CASE diagram
PHONE REPAIR SYSTEM USE CASE DIAGRAM
Record client’s details
Record technician details
Record fault phone details
Record repaired phones details
Record used repair parts details
Record repair parts stock details
Record repair charges details
CLIENTS STAFFS
TECHNICIAN
ACCOUNTANT

5System Requirements Specifications
3.4 Classes / Objects
Below are the various classes that will be used in the mobile repair system to keep record of all
phones repair details, these classes has various names ,elements and operations as shown below.
3.4.1 Clients class
3.4.2 Mobile phone class
3.4.3 Technician class
3.4.4 Repair parts class
CLIENTS
+clientid:int
+fullname:string
+address:string
+town:string
+telphonephone:int
+addclients():void
+editcleint():void
Mobile phone
+phoneid:int
+model:string
+serialno:string
+manufacture:string
+clientid:int
+addphone():void
+editphone():void
Technician
+technicianid:int
+fullname:string
+telephone:string
+specialization:string
+department:int
+addTechnician():void
+editTechnician():void
Repair_parts
+partid:int
+name:string
+description:string
+cost:string
+remainingstock:int
+addparts():void
+editparts():void

6System Requirements Specifications
3.4.5 Payments class
(Dick, 2018).
3.5 Non-Functional Requirements
Below are the mobile repair system non functional requirements.
3.5.1 Performance
The system should be able to do various functions within a short period of time and therefore the
system execution period should be shortest possible.
3.5.2 Reliability
The system is required to be able to reliable in that it will support all functions and operations
and the executions within the shortest time possible (Michael, 2017).
3.5.3 Availability
The system should be always available wherever the system users require to perform some
operations, therefore during the system design system will be fully tested to ensure the system
uptime is high.
3.5.4 Security
The system is required to be highly secure such that there will be no unauthorized access to the
system, this will be implemented through the use of the security features and passwords
(Specialist, 2018).
Payments
+payid:int
+description:string
+amount:string
+date:string
+remainingstock:int
+clientid:int
+phoneid:int
+addparts():void
+editparts():void

7System Requirements Specifications
3.5.5 Maintainability
The system should be easy to maintain in that if the owner require adding or removing some
features can be able to do it easily without affecting the normal system operations (Paige, 2015).
3.5.6 Portability
The system should be easy to move from one computer system to the other this is through the use
of portable and installation devices.
3.6 Inverse Requirements
Below are some inverse requirements of the proposed system.
i. System should not be installable in other form apart from executable format (Stephen,
2014).
ii. System should not be accessible by unauthorized persons.
iii. The system should not be accessible by un-registered users.
iv. The system should not be accessible without username and passwords.
v. System should not allow registration of persons with weak username and passwords.
vi. The system should not be installed in computers without strong passwords.
3.7 Design Constraints
Below are the various system constraints that will be required during the entire system
implementation.
i. The system will be developed using asp.net language.
ii. The system will be linked to SQL server software.
iii. The system will be installed in the computers systems.
iv. The computer systems should be in a network system (Thomas, 2013).
v. All computer system should be installed with windows 7/8/10 operating system.
vi. All computer system should be installed with antimalware applications.
3.8 Logical Database Requirements
The mobile repair system will be linked to the database system that will be used to store the
information, however below are the various database requirements.
i. The database will store various types of information in form of numbers and texts.
ii. The database will require to be used and accessed any time while storing and
retrieving records (Shamkant, 2015).

8System Requirements Specifications
iii. The database will be accessed through usernames and passwords through the system
interface.
iv. The database will have various entities including clients, mobile phone, payments,
technicians, and repair parts tables.
v. The various entities will be having a relationship that will be established using the
foreign keys.
vi. The database tables will have the integrity constraints which includes the primary and
foreign keys.
vii. The database will be able to retain the records saved unless they are modified or
removed by the authorized users.
3.9 Other Requirements
Below are some other system requirements.
i. Organization should have the computer systems before system is installed.
ii. The organization should install the network before the system is installed.
iii. The system users should be registered by the system admin with unique username and
password (Dick, 2018).
iv. The system user should change their passwords after initial login.
v. The system users should frequently change the passwords of their accounts.
vi. The system users must logout after using the system (Elmasri,2013).
vii. The computer system software should be updated regularly (Ramez, 2015).
viii. The computer antimalware applications should be updated regularly.

9System Requirements Specifications
Reference
Dick,B.(2018) IT Project Management Essentials: Information Systems Project Methodology
Kindle Edition.1st edn.New York:Amazon Digital Services LLC.
Elmasri,E.(2013) Database Systems: Models, Languages, Design and Application Programming.
2nd edn India: PEARSON EDUCATION.
Ramez,E.(2015) Database Systems: Models, Languages, Design and Application Programming
- International Edition Paperback.2nd edn. India:PEARSON EDUCATION.
Shamkant, B.(2015) Fundamentals of Database Systems (7th Edition).India:pearson.
Thomas,C.(2013) Database Systems: A Practical Approach to Design, Implementation and
Management: WITH Success in Your Project.1st edn. USA:Addison Wesley.
Stephen,H.(2014) Management Information Systems with student CD and MISource.3rd edn.
New York:McGraw-Hill.
Paige,B.(2015) Business Driven Information Systems with MISource 2007 and Student CD.1st
edn New York: McGraw-Hill.
Specialist,I.(2018) CISSP Certified Information Systems Security Professional Study Guide
2018. 1st edn.New York:Independently published
Michael,J.(2017) Human Resource Information Systems: Basics, Applications, and Future
Directions. 5th edn.New York :SAGE Publications, Inc.
Dick,B.(2018) IT Project Management Essentials: Information Systems Project Methodology
Kindle Edition. 1st edn.New York:Amazon Digital Services LLC.
Tycho,p.(2014) Personal Finance Simplified: The Step-By-Step Guide for Smart Money
Management Paperback. 2nd edn.New York:Tycho Press.