Software Requirements

Specification

for

GBI

Version 1.0 approved

Prepared by Amer Akhtar

GBI Bicycles

25/07/2019

Table of Contents

Table of Contents.......................................................................................................................... ii

Revision History............................................................................................................................ ii

1. Introduction............................................................................................................................. 1

1.1 Purpose.................................................................................................................................. 1

1.2 Document Conventions........................................................................................................... 1

1.3 Intended Audience and Reading Suggestions........................................................................... 1

1.4 Project Scope......................................................................................................................... 1

1.5 References............................................................................................................................. 2

1.6 Company Research …………………..……………………………………………….......2

1.6.1 Employees Interviews …………………………………………………………………...2

1.6.2 Employees Requirements………………………………………………………………...2

1.6.3 User Stories. ……………………………………………………………………………..2

1.6.4 Problem Analysis. …………………..…………………………………………………..2

1.6.5 Solution ………………………………………………………………………………….2

2. Overall Description................................................................................................................. 2

2.1 Product Perspective................................................................................................................ 2

2.2 Product Features..................................................................................................................... 2

2.3 User Classes and Characteristics............................................................................................. 2

2.4 Operating Environment........................................................................................................... 2

2.5 Design and Implementation Constraints................................................................................... 2

2.6 User Documentation............................................................................................................... 2

2.7 Assumptions and Dependencies.............................................................................................. 3

3. System Features....................................................................................................................... 3

3.1 System Feature 1.................................................................................................................... 3

3.2 System Feature 2 (and so on).................................................................................................. 4

4. External Interface Requirements........................................................................................... 4

4.1 User Interfaces....................................................................................................................... 4

4.2 Hardware Interfaces............................................................................................................... 4

4.3 Software Interfaces................................................................................................................. 4

4.4 Communications Interfaces..................................................................................................... 4

5. Other Nonfunctional Requirements...................................................................................... 5

5.1 Performance Requirements..................................................................................................... 5

5.2 Safety Requirements............................................................................................................... 5

5.3 Security Requirements............................................................................................................ 5

5.4 Software Quality Attributes..................................................................................................... 5

6. Other Requirements................................................................................................................ 5

Appendix A: Glossary................................................................................................................... 5

Appendix B: Analysis Models...................................................................................................... 6

Appendix C: Issues List................................................................................................................ 6

Revision History

Name	Date	Reason For Changes	Version
Amer	25/07/2019	N/A	1.0

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the Web Software that we are going to build for GBI Company. The document will explain the purpose and reason of newly web-based software. It will explain the features, interfaces and working of the Web Software and under what circumstances this software will operate. This Software designated for the GBI users and stakeholders and being an open-source web application, it may be used by potential developers.

1.2 Document Conventions.

This document was created based on the IEEE template for System Requirement Specification Document.

1.3 Intended Audience and Reading Suggestions.

ü GBI Employees and stakeholders will use this Software for analysing and manipulating data.

ü This software will also be used by us authentically for further research purposes.

ü Programmers, researchers and students who are interested in this project will also use it for education and research purposes.

1.4 Product Scope Definition.

The Global bike incorporations are the legendary bike manufactures used for best competence. They offer zero defect and high quality and advance technology bikes in the market which makes them as one of the renowned producers of race bikes (Brian Mackay, 2008). The Global bike incorporation race bike manufacturing company has been used as a case study for this project management thesis. The Global Bike incorporation faces large tax issues associated with selling in the branch operations as the GBI is registered as U.S company and its headquarters are based in Dallas following US GAAP accounting standards. Now GBI has its subsidiary company in Europe under the name of “GBI Europe” and is based in Heidelberg and is subjected to IRFS accounting standards and German tax regulations so being an US registered company GBI is paying much more tax in Europe, at the same time GBI has very low internet sale as their internet usage is very limited. And the second important issue is exports. The reason behind this issue is limited manufacturing standards which only based on US standards while Europe has different manufacturing standards.

More related issues

1.5 References

1. Brian Mackay. (2008). ERP System Implementation Project Charter. AVP IT Services and CIO.

2. Kristian Jääskeläinen, a. f. (2009). ERP project’s Internal Stakeholder network and how it influences the project’s outcome.

3. Nagarajan, M. (2015). The 7 Prerequisites for an ERP Implementation.

4. Przemysaw Lech. (2016). Implementation of an ERP system. Journal of Management and Finance.

5. Sandeep Singhal, Dr Puneet Tandon, Sharma S K. (2011). Hardware and Software Requirements for Implementation of ERP in Technical institution. international journal of scientific research.

1.6 Company Research.

1.6.1 Employee Interviews.

As GBI is based in both US and Europe and has 2/3 of its employees in US and remaining 1/3 in Europe, so for interview purposes we used Email and skype as a mean of communication. We gave them a survey paper where they write the difficulties of the existing system which is obviously that excel sheet and also, they wrote about the requirements. Following are the questions that we have asked them in interviews.

Finance Department

Finance department needs a dashboard to generate sales reports weekly, monthly, yearly.

Finance department is also looking for a dashboard where they can monitor their cash flow and can generate cash flow statements. They also need a d feature in the dashboard so they can track all the smooth transactions made to the employees and other staff.

Sales Department.

Sales department also using the same typical MS Excel sheet to see the sales reports, so they need a dashboard where they can monitor sales reports and sales metrics, they want to transfer all their data from (CRM, Excel sheets, Google sheets) to a centralised database software where they can monitor track performance of their sales tax and manufacturing. They want graphical data of sales from country to country.

Marketing Department.

Marketing department needs dashboard so they can monitor and the conversion rates, geographic data. They need electronic media solution as their internet sales so they can market the products through social media, paid content, organic search, google search, sites and referrals. They also need built-in google adwords so they can advertise their products through google.

Administration department (CEO’s, Upper Management).

We also have interviewed Upper management and ask their needs and requirements and difficulties they are facing in using that spreadsheets. We separately conducted interviews with John and Peter (CEO’s of GBI). John is handing marketing, sales and financial departments and is looking for a Software where he can see the monitor the reports of each department. He needs financial transaction reports sales reports and Marketing reports in one screen. Whereas Peter is dealing with manufacturing, design and research departments. Peter needs to interact with other partner in US and Europe. He needs an interactive Software so he can have all the manufacturing branches at one place and also can share the latest designs and update all departments about the policy updates.

1.6.2 Problem Analysis.

We will perform a detailed requirement analysis process which will help us to identify the key business needs that the BI solution must address.

ü Step 1: Identify key stakeholders:

For this business requirement we have identified our key stakeholders as John, sales manager of GBI, Sales team, Marketing team, Finance team. Huge volumes of sales data is generated from day to day activities and this needs to be managed and analyzed efficiently by these stakeholders for developing effective sales and marketing strategy for Global Bike Inc.

ü Step 2: Capture Stakeholder’s Requirements:

In this step we identified that our stakeholders require a holistic view of data from multiple sales organizations within Global Bike Inc. which would give them access to clean, concise, coherent, non-redundant, de-duplicated data. This data will be used by the stakeholders to meet key business objectives by performing descriptive analytics, prescriptive analytics and predictive analytics.

ü Step 3: Categorize Requirements:

In order to make the analysis easier we have broadly grouped the stakeholders into 4 categories:

1. Functional Requirements: We require a Business Intelligence solution which will address the needs of the stakeholders for easy access of summarized data along with the capability to slice and dice the data across multiple dimensions like product category, region etc.

2. Operational Requirements: We will integrate the data from multiple operational source systems into our Software through Extraction, Transformation and Load of data. The data from the data warehouse can be divided into multiple data marts to cater to specific business areas. Business Intelligence tools and analytical tools will be employed to perform end user capabilities such as data mining, reporting and creation dashboards.

3. Technical Requirements: We will utilize Web Software to implement the Business Intelligence solution for Global Bike Inc. We will be additionally using T Caspio 9.2, ZOHO Analytics to perform visual analytics on our sales metrics.

4. Transitional Requirements: Data should be completely migrated from our legacy systems into our Software. We should plan and schedule the frequency of our ETL process based on the various factors like the volume of data, end user requirements etc. Since we are recording day to day sales transactions, daily load of data should be ideal for GBI. Regular data reconciliation process should be performed to validate the data with the source systems. We also have to plan for effective change management process which would include documentation update, cross training of staff etc.

1.6.3 Proposed Solution.

Based on our market expertise, we decided to implement the Web Software platform in conjunction with the Caspio Database as a solution for the GBI sales organizations.

There are a number of advantages of using the Web Software platform, some of which are listed below:

ü Performance and Scalability

ü Integration with Business Objects

ü Development Efficiency

ü Simplified configuration and Operations

ü High ROI

ü Cross-Application Visibility into Business Process Performance

ü Permanent data storage

ü Improved Customer Service Levels

ü Increased Capacity Utilization Rates

ü Proactive Decision Making Enabled by Real-Time Data

ü Compatibility with Caspio, Zoho and Tableau databases (Real time analytics)

ü Bad data is Quickly Identified through a built-in feature.

GBI Software solutions provides industry leading and historically proven BI user-friendly applications that help manage Enterprise Reporting requirements. It supports business requirements like report formatting, ad-hoc querying and analysis on relational or multi-dimensional data sources, or data visualizations and KPIs, our Software solution provides a single BI platform that enables business users to make effective data centric business decisions.

Business users have the ability to easily create ad-hoc queries and manage powerful data analysis to obtain business insight regardless of the database platform complexity.
Our Software solutions reduces BI TCO (Total Cost of Ownership) by providing a single, integrated, scalable, highly available, business intelligence enterprise platform.

Our Web Software provides a framework of data extraction and analysis that will help improve the bottom line and maintain operational stability and efficiency over the long term.

2. Overall Description.

2.1 Product Perspective.

This Web Based Software is developed for GBI company in order to facilitate the company in reducing the cost and deliver best technology to all divisions globally. The Web Software will also provide GBI an advanced business platform under a highly controlled environment. The Software will also help company to get competitive edge over its rivals in market.

The Web based Software is integrated with online database (Caspio) that is designed to develop the company's production, control, finance, customer complaints sales and inventory. The web Software will allow company to handle tax issues as it connects both headquarters together and will update employee’s data and tax information. The Software will also allow employees/users to see the sales reports, Revenue generated, Customers information and cost of goods. The Software will also allow the employees to add or change the data accordingly as we have integrated forms for different categories.

2.2 Product Features

This Web based Software provides the safe protection over the loss of data and thereby reduction in risk of business. It also improves the control over finance, making accessibility very easy to top management. It also benchmarks the previous operations in the business and gives ideas to the Cross functional team to analyze the bench mark and work on it to improve the business efficiency and to increase sales and cut cost.

2.3 User Classes and Characteristics.

GBI Employees and stakeholders will use this web Software for analysing and manipulating data.

GBI’s CEO’s and managers will use this Software to monitor marketing and financial activities.

GBI Suppliers will also be able to use this Software to see their orders dispatched, older data of their products.

GBI Partners and vendors will also use this Software.

2.4 Operating Environment

ü Web Software can be operated through any internet browser.

ü Caspio online database software for storing database.

ü MS Access for data compiling.

ü Windows XP

ü Windows 7

ü Windows 10

ü Mac OS X

ü Linux/Unix

2.5 Design and Implementation constraints.

The implementation of this Software solution for the Sales Organization has equipped GBI with the ability to make business decisions with more confidence since the decisions will now be backed by data. Thus, the Sales Organization stands to benefit a lot from this implementation. We propose to extend this solution to other departments in GBI like procurement, HR and supply chain. This will provide GBI with the ability to make data driven business decisions and thereby result in optimized and cost-effective operations.

We propose that GBI extend the current implementation of hub-and-spoke data warehouse architecture to include data marts from other departments.

Thus, Internet is required to operate this Software so network failure could lead to shut down the system, moreover failure of server or if the server is down the Software will be unavailable. Overload of server could slow down the Software.

Some features of this Software require ID and Password to login, adding wrong data multiple times could block the Software.

Clients must have ID number to login into the Software and must keep their passwords confidential.

2.6 Product Functions.

Reports.

ü Home is a welcome page or landing page on GBI’s Software which has 6 tabs on it.

ü Search From Data:

This tab is embedded with form on it where an employee can search a customer’s data by adding his name, ID, year, country.

ü Sales Reports:

This tab is featured with bar chart diagrams, where an employee can visualize the data in the form of bar charts, graph charts. Employee can compare the Revenue and cost of goods in through graphs and charts.

ü Sales Reports:

This tab shows the sales reports by country wise, material wise and yearly. This tab also has the feature to show the brief description of revenue generated from different countries with cities.

ü Country Wise Sales:

This tab shows the total revenue generated from each country in geographical form for the better understanding of employees.

ü Revenue vs Cost of Goods:

This tab shows comparison between Revenue and cost of goods, so employees would be able to compare if they are spending more on goods and not generating the enough revenue from that product so they can change the supplier or go to the cheaper supplier.

ü Revenue Analysis Reports

Revenue analysis shows the revenue generated from different countries in graphical form.

ü Cost of Goods Analysis Reports

This shows the overall spending on goods that are purchased from different suppliers.

Dashboard.

ü Cost Of Goods Analysis.

Cost of goods Software has precise and detailed description of cost spend on goods in different regions. It gives the MAX cost of goods in different countries.

ü Discount Analysis Software.

Discount Analysis Dashboard shows the discount on different bikes and also shows whether discount became costly for the company and it also shows the comparison between sales and discount.

2.7 User Documentation.

https://gbibicycles.blogspot.com/p/blog-page.html

2.8 Assumptions and Dependencies.

It is assumed that the user is familiar with an internet browser and also familiar with handling the keyboard and mouse.

Since the application is a web-based application there is a need for the internet browser. It will be assumed that the users will possess decent internet connectivity. The Software is highly depends on Web server and Internet connectivity so server down could lead dysconnectivity or slow process.

3. Systems Features.

Below are some of the features of Software.

3.1 System Features 1.

Pie Chart Visualization.

Form is integrated into web page where a user can add customer name, year, month, ID etc to visualize data.

3.2 System Feature 2.

Sales Dashboard.

3.3 System Feature 3

Sales Reports.

4. External Interfaces.

4.1 Hardware Interfaces.

Minimum hardware requirement for Software is 500-Megahertz CPU and 128 MB of RAM. As Software is web based so online server with 500 MB of Ram is also required to support it. The software doesn’t need any pre-built machine to run it instead a computer system with functional Keyboard and mouse is required to operate. As it web based software so 24/7 physical web server is required to operate the website.

4.2 Software Interfaces.

Our Web Based Software is an open-source platform and hence doesn’t require any special software from user to run it. A minimum system can run this software. Updated version of Java should be installed on the system. The Software is coming with built-In Caspio and ZOHO databases.

Software requirements for the Software are given below.

ü Java (version 8 and above).

ü MS Access.

ü Caspio and ZOHO Online Database.

ü Blogger (Googles Website developer Tool).

Project Constraints

ü We have fixed time to complete this project according to the timeline given to us.

ü We have to keep in mind the budget of this project and we shall not exceed the budget limit.

ü Communication gap among various stakeholders should be minimal.

ü The staff of GBI company should be friendly and cooperative while explaining the GBI’s existing system.

ü Again, cooperation is required while training the employees.

Product Success Criteria.

ü Satisfies GBI team’s demands including meeting client needs.

ü Meet the schedule goals, completing everything on time with no delays.

ü Keeping budget in mind while completing the work.

Project Requirement

ü Office/Library.

ü Software. (Windows Operating System, chosen database software).

ü Hardware.

ü Internet Services.

Impact Matrix:

LIKELIHOOD	CONSEQUENCES
	INSIGNIFICANT	MINOR	MODERATE	MAJOR	SEVERE
ALMOST CERTAIN					software fails to meet expectations of GBI bicycle company
LIKELY			The software is not successful In multiple system
POSSIBLY		The software will not be ready to use for outsourcing	Requirement for software will not be provided completely
UNLIIKELY				Fully tested software not available by the end of may
RARE	Benefits are not realized with the time and money invested in this project			Project completion will be delayed due to worker issues	GBI decides not to undertake this project or abandons the project

Low

Medium

High

Extreme

Risk Factors:

Risk involves the possibilities of occurrence of failure that has to face during the implementation of the project. The challenge is to manage the risk and continue the obstruction caused due to risk and focus on successful completion of project. Risk may occur at the startup of the project or during the entire cycle the team member can identify all type of risk during the ongoing of process it may include power failure, login issues, system error, unconfigured system, error in installation of software.

ü Software will not available on time for outsourcing

ü Fully tested software will not available by the end of May 2019

ü Software fails to meet the requirement and expectation of GBI bicycle team

ü Benefits could not be realized or measure according to the time and money invested in this project

ü Equipment or requirement provided to build the software is not of sufficient quality

ü Project is not ready due to workers issues.

Risk management

To overcome the risk, we took following steps to manage or minimize the risk

ü We set up a team who follow the process and control the worker issues

ü This team would do meeting on a regular basis to monitor the progress and to update and following through the risk register

Risk Response.

Avoid Possibility for the risk occurring.

Identify and migrate the risk, this will reduce the effect of the risk.

Stakeholders:

Name	Expectations	Internal/External	Type of communication	Interest
Shareholders	Receive profit from investment.	Internal	Financial Statements	High
Board of Directors	Decisions makers	Internal	N/A	High
Employees	Develop the Software,	Internal	In person	Medium
Lenders	Interested in company status	External	In person, Fax	High
Media	Receive and Publish feedback	External	Press release	Low
Government	Receive taxes	External	N/A	Low
Potential customers	Looking for software	External	Regular In Person Meetings	Medium

Work Breakdown Structure.

Work breakdown structure (WBS hereafter) breaks down the project into various stages, deliverables and actions (Kerzner & Kerzner, 2017). WBS prepared as a hierarchy defining different stages of the project and sub-sequent actions to perform. Referring to figure 1, WBS initiates from project management and the project further breakdown into different actions considering the size of the project, timeliness and responsibility that leads to completion of the project. This project has four stages (figure 2). The first stage is more related to paper work which includes planning of the project. In second stage software for bike design will develop. In this stage integration with dashboard will perform. The fourth stage tests the system whether it is performing proper and as per the client’s requirement. Lastly, the new system will deploy.

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Print this post

Global Bikes INC(GBI) Software Requirements Specifications (SRS)