Journal and self reflection

Ahmad571

forreference.docx

Home >Literature homework help >Journal and self reflection

Software Requirements Specification for GBI information system development project Page 7

Software Requirements Specification for

GBI Information System Development Project

Prepared by;

Muhammad Ahmad	AUK3021
Hafiz Muhammad Ahmad	AEG3028
Saim Altaf	VSS32156
Lovepreet Singh	DMA3351
Ranga Herath Mudiyanselage	PRT3133

Holmes Institute

HOLMES INSTITUTE

FACULTY OF

HIGHER EDUCATION

UNDERGRADUATE PROGRAM

Table of Contents ii

Revision History iii

1. Introduction 1

1.1 Purpose 1

1.2 Document Conventions 1

1.3 Intended Audience and Reading Suggestions 1

1.3.1 Overall Description: 1

1.3.2 System Features: 1

1.3.3 External Interface requirements: 1

1.4 Project Scope 2

1.5 References 2

2. Overall Description 2

2.1 Product Perspective 2

2.2 Product Features 2

2.3 User Classes and Characteristics 3

2.3.1 Customer 3

2.3.2 Co-CEO 3

2.3.3 Products 3

2.3.4 Employees 3

2.4 Operating Environment 3

2.5 Design and Implementation Constraints 3

2.6 User Documentation 3

2.7 Assumptions and Dependencies 3

3. System Features 4

3.1 Product information 4

3.1.1 Objective: 4

The purpose is to determine the functioning that is provided with each bikes globally. This will help the employees to check the details regarding each bike and the components associated with the system. 4

3.1.2 Priority: 4

3.1.3 Source: 4

3.1.4 Actor: 4

3.2 Customer details 4

3.2.1 Objective: 4

3.2.2 Priority: 4

3.2.3 Source: 4

3.2.4 Actor: 4

3.3 Order details 5

3.3.1 Objective: 5

3.3.2 Priority 5

3.3.3 Source: 5

3.3.4 Actor: 5

3.4 Report generation by employee 5

3.4.1 Objective: 5

3.4.2 Priority: 5

3.4.3 Source: 5

3.4.4 Actors: 5

3.5 Stock determination 5

3.5.1 Objective: 5

3.5.2 Priority: 6

3.5.3 Source: 6

3.5.4 Actor 6

3.6 Employee monitoring 6

3.6.1 Objective: 6

3.6.2 Priority: 6

3.6.3 Source: 6

3.6.4 Actor: 6

4. External Interface Requirements 6

4.1 User Interfaces 6

4.2 Hardware Interfaces 6

4.3 Software Interfaces 7

4.4 Communications Interfaces 7

5. Other Nonfunctional Requirements 7

5.1 Performance Requirements 7

5.2 Safety Requirements 7

5.3 Security Requirements 7

5.4 Software Quality Attributes 7

6. Other Requirements 8

Appendix A: Glossary 8

Appendix B: Analysis Models 8

Appendix C: Issues List 9

Revision History

Name	Date	Reason For Changes	Version

Software Requirements Specification for GBI information system development project Page iii

Introduction

Purpose

The purpose of the system is to provide an information system that would be containing all the procedure to make the business efficient for the organizations. This document is used for the

Collection and analysis of the data required for the system. The system requirements of the system are to identified in this system. A detailed overview of the software development for the GBI organization has been described in this document.

Document Conventions

The Harvard conventions have been followed in this document. The Bold-faced text has been used as an indication of the Headings and the sub headings in the document. Italicized texts have been used for the normal fonts in the document

Intended Audience and Reading Suggestions

The Document has been intended for the project team to read. In addition to this the marketing group in the organization would also be reading this document. The main stakeholders of the GBI organization would be reading this document to understand the system which has been developed for them. The management committee would be reviewing this document to check if all the functionalities in the system has been developed as per expectation or not. The specificity of the project that has been conducted by the project is to be provided from the SRS. Other features needed to be review by this document is:

Overall Description:

The Staffs in the GBI organization are required to get accustomed to the processes that are being followed currently in the organization and for the system.

System Features:

The scope of the system which is being designed for the organization are being provided from this SRS document.

External Interface requirements:

The hardware developers would be able to get knowledge about the software that is being developed. This would help them in making efforts to acquire the hardware interface required to support the software interface for the organization.

Project Scope

The Information system developed for the organization would be providing them with the details of all the required aspects of the system. The customers would be able to view a wide range of bike in the system and make their purchase options significantly easier. The system would also be able to store the details of the orders and prepare the reports accordingly.

References

For the references please refer to the project plan document for the schedule and budget of the development of the system. The system database development and the interface development of the GBI information system has been done in the Access file attached to this document.

The .accdb file attached here contains the details of the all major functionalities in the system dashboards.

The Entity relation diagram has been provided in the appendix section of this document and the dashboards have been included in the dashboard file.

Overall Description

Product Perspective

The development of the information system is done for the GBI organization so that they would be able to maintain there data in the information system database instead of performing the tasks manually. The software that is to be developed with would be incorporated with the developed system. The reports and the forms for the database would aid the organization maintaining their business data efficiently. The marketing and financial data for the organization would be derived from the system very efficiently and the results would be beneficial for the future development of the system.

Product Features

The main features of he developed dashboard project are listed below:

· The system would be able to store a huge amount of data that would be useful for the business of the organization. The details of the materials used by the organization for the products. The details of the products in the system are to be stored in the dashboards.

· The details of a new customer being enrolled in the system is also required to be stored in the system.

· In addition to this, the system should be able to store the details of the products in the system and the details of all the orders done on the system and the provide reports that are relating to the ordering and purchasing of the products from the systems.

· The staffs of the organization should be able to fetch business results with simple queries for the system.

· The data storage would also be proving excellent insights on the development and operations aspect of the business for the organization.

User Classes and Characteristics

Customer

The customers in the system would be able to login to the system and store their details. They would be able to view the details of the products in the system and make an order according to their preference.

Co-CEO

The co-CEO would be having a number of employees under him and the Co-CEO would be monitoring the employees in the organization.

Products

The product details would be stored in the system. The stocks of the products would also be stored in the system so that orders in the system can be placed accordingly.

Employees

The employees in the system would be storing their details in the system and each of the employees would belong to a certain co-CEO and would be handling the customer orders.

Operating Environment

The software designed would be operated as an windows application in a windows operating system and it is recommended that operating system versions above windows OS 2007 is used.

Design and Implementation Constraints

The software would not be made available outside the region as the organization does not support the delivery of the products at home of the customers and hence the application would only be available within the scope of the organization and not beyond that.

User Documentation

The user’s documentations are the Project planning document, the SRS document, the Dashboard document and the Database file. These documents would be helpful for the user in understanding the system effectively.

Assumptions and Dependencies

It is assumed that the system would be running on the windows operating system. The Microsoft office software is used for the development of the system.

System Features

Other Nonfunctional Requirements

Performance Requirements

· The database should load within 30 sec after sending request to view data and should display the required data as requested

· Database of the inventory system should be scalable across different platform

· Database integrated with the inventory system should not crash when there is increased traffic

Safety Requirements

Database should be fault proof. It should have option for automatic data backup so that data is available when the inventory system crash due to some system faults. Database should show warning message when someone tries to delete data which might be intentional or non-intentional.

Security Requirements

Database should integrate strong encryption so that it is not easy to exploit the inventory system and steal important data without proper authorization. Password should be encrypted with 256-bit encryption so that it is not easy to execute SQL injection process, a common and popular method for stealing password for acquiring access to the system.

Software Quality Attributes

There should not be any issues while exporting the database system to another platform and offer same level of performance and control over the database system. Along with that, it should be easy to access and easy to maintain as well to ensure optimum performance from the inventory system designed.

Other Requirements

There are other requirements of the project such as the user interfaces and the hardware procurement requirements for the project which has not been included in this SRS document. The networking requirements have also been omitted from this report.

Appendix A: Glossary

GBI – Global Bike International

SRS – System requirement specification

Dashboard – the Dashboard is the project which has been implemented for the GBI organization.

Appendix B: Analysis Models

Entity Relationship Diagram has been

Appendix C: Issues List

The main issues in the system are regarding the security of the database.

· Data access: The access to data is to be further restricted.

· Security: The system lacks the password feature which is to be implemented for the system.

978820_GBI1.accdb

ID	CEOName	CEOContact	CEOAddress
1	Kvein Hart	45512151	9A denver Lane
2	Durell Roy	45514593	32 greenway lane
3	Yan Valery	67489202	33 vinice road

CustomerID	CustomerName	CustomerContact
1	Henry	4568862
2	Matt	1458958
3	Gary	4851551

EmployeeID	EmployeeName	EmployeeSalary	CEOID
1	Becky	1000	1
2	Leroy	1200	1
3	Kelly	1300	2
4	Brock	1100	3
5	David	1100	2

OrderID	ProductID	CustomerID	EmployeeID	OrderDate
1	1	1	1	4/17/19
2	1	2	1	4/8/19
3	2	1	2	5/15/19
4	3	3	3	4/16/19

ProductID	ProductName	ProductPrice	ProductStock
1	GMX345	¤ 1,000.00	true
2	GHT112	¤ 1,200.00	true
3	YTM234	¤ 900.00	true

SELECT DISTINCTROW * FROM Co_CEO;

SELECT DISTINCTROW * FROM Employee;

SELECT DISTINCTROW * FROM Customer;

SELECT DISTINCTROW * FROM Product;

SELECT DISTINCTROW * FROM Order;

SELECT Customer.CustomerName, Count(Order.OrderID) AS CountOfOrderID FROM Customer INNER JOIN Order ON Customer.CustomerID=Order.CustomerID GROUP BY Customer.CustomerID, Customer.CustomerName;

SELECT Employee.EmployeeName, Sum(Product.ProductPrice) AS SumOfProductPrice FROM Employee INNER JOIN (Product INNER JOIN Order ON Product.ProductID=Order.ProductID) ON Employee.EmployeeID=Order.EmployeeID GROUP BY Employee.EmployeeID, Employee.EmployeeName;

SELECT Co_CEO.CEOName, Count(Employee.EmployeeName) AS CountOfEmployeeName FROM Co_CEO INNER JOIN Employee ON Co_CEO.ID=Employee.CEOID GROUP BY Co_CEO.ID, Co_CEO.CEOName;