Applied Business Computing Requirements Specification Document Overview

Published Date: 02 Nov 2017

RTL SA is a company which develops bespoke solutions for the rubber industry. They produce quality rubber compounds, which other companies such as tyre manufacturers use to produce vulcanized products. The company also produces custom made moulded rubber products and rubber coatings according to customer specifications. The rubber products are for a wide variety of applications and thus there are a wide range of requirements for the properties of the rubber including elasticity, hardness and exposure to a range of chemicals, to name but a few. Thus the formulations need to be tailored to suit the customer’s needs.

This means that the company does not have a range of readymade but rather that there is a process where the customer makes an enquiry through telephone or in person at the office and the company needs to assess whether they can make a product to the customer’s specifications before producing some samples which the customer has to approve before an offer is made and the customer can order the products.

Customers inquire about a particular rubber product with the Operation officer, they note the customer’s contacts details and pass them to a Technician who checks for feasibility of the said product, then the customer is called for feedback, a file is opened for that customer who wish to place an order and full personal detail recorded manually. The files are kept in an unlockable cabinet. If it is a new product the details are also noted in new products file. Those who buy products in stock they pay cash and they are issued with cash receipt and their details are not kept.

The company has a Manager, two technicians and 2 Operation staff who all have access to the cabinet, each have a duplicate of an office door key. There are also ten casual workers. All employees have access to all office books like payments receipts books.

The company has only one telephone line which is used by all customers who wish to call the office. They operate from 0830 hours to 1600 hours during the week and from 0830 hours to 1230hours on Saturday, they close on Sunday and public holidays.

Whenever customers enquire about their accounts an officer has to go through all files one by one looking for their files and it takes time or they go missing. Their Payments are recorded in one manual receipt book which is also kept an unlockable cabinet. Currently the Company does not know how many customers they have because not all customers’ information is kept.

Product to be delivered to client

RTL SA Online Customer Service System where customers make inquiries and all order processing to the point where the customer can order company’s rubber products through the web, to be submitted on the 13th May 2013 together with complete system documentation and user manual.

Client requirements

Functional Requirements:

Customer

Log in to the system by using combination of username and password

browse through all rubber products within the interface

register into the system

post related queries

Place order online

View shopping cart list

View status of previous orders

Log out

Manager

Log in to the system by using combination of username and password

Print monthly statistical reports

View customer orders

Print Customer orders

View customer details

View customer’s queries

View Product details

Respond to customers queries

View stock level

Log out

Operation

Log in to the system by using combination of username and password

Forward new rubber products request to Technicians

Respond to customer requests

Respond to customer’s order

Log out

Sales

Log in to the system by using combination of username and password

Respond to customer’s order (reject or approve)

Respond to customer requests

Print invoices for customer

Log out

Technicians

Log in to the system by using combination of username and password

respond to customer’s request

respond to Customer’s orders

View Rubber products list

View New Rubber Products requests

Log out

System Administrator

Log in to the system by using combination of username and password

Promote User roles e.g. change user role from customer to Operation

Manage database: delete user, add user, update user details.

Back-up

Register product details

Edit product details

view all users’ accounts details

- update product specifications

Log out

Visitors

Visit the RTL SA website without registration

Non-Functional requirements

Security

The system shall not allow unauthorised access:

customers’ sensitive data shall be transmitted securely

Encryption of communication between system’s data server and clients

Availability

- The system shall be available whenever requested by customers: must be available 24/7.

Usability

- The system shall be easy to use and well-matched with major web browsers

- Clear and easy to understand manuals

- Well up-to-date graphical user interface

Performance

- The system should be sufficiently fast to accommodate various internet connection speeds.

- The system shall support multiple users at a time

Holding Capacity

- At least up to 50 000 customers can be stored

Supportability – the ease of provide support, maintainability and other qualities necessary to keep the system up-to-date after its release.

The system shall be able to handle numerous transactions at the same time.

Portability: the software can fit on all obligatory platforms on which it is supposed to run.

Integrity: precaution merits of the system, restrictive right of entry to information of certain users and protecting the privacy of information entered into the software.

Robustness: the system will be able to handle error conditions without malfunction. This includes a resistance of unacceptable data, software faults, and unforeseen functioning conditions.

Scalability: the system will have the ability to handle a broad range of system configuration sizes.

Future requirements to be implemented in future phases:

Inventory System - brings up to date inventory information for all items, monitoring inventory reduction, importation and exportation inventory information to and from outside systems of documentation. The Inventory System serves the wants of consumers, company managers, site administrators, and outside line-of-business systems that interface with Commerce Server.

Constraints

Poor internet connection and resource accessibility within BAC is unreliable

Time allocated to the whole project is too small

This is an academic Project so, there is no budget limit to observe

Despite the outlined above constraints this project remains valid as I will go to Internet Cafes whenever internet is down at BAC (between 0900 hours and 2000 hours). I will also sacrifice my time whenever I am free and continue working on the project so that I finish it within the agreed time.

Resources

Client – Mr Mandla Ndlovu: a client representing the RTL SA company

HP G62 Notebook PC with Windows 7

Printer – for producing the document’s hardcopy and user manuals.

MicroSoft SQL Server 2008 - to store and retrieve data as requested by Web application

ASP.NET - a development structure for building web sites and web pages with Visual Basic Programming language easily

MicroSoft Visual Studio 2010 - A client side scripting language used to create dynamic web content and user interface.

MicroSoft word 2010 – for typing documentation, spell check and grammar checking.

MicroSoft Project 2010 - a task-planning program which makes it simple to trail and chart project actions

MicroSoft Visio - for drawing business use-case and Activity diagrams.

Evaluation

The aim of evaluating of the artefact is the project’s success which covers the following; –

Client’s impact / satisfaction – it includes meeting the project’s technical and operational specifications

Fulfilling the Client’s need – actual use by the client, solving major operational problem of the client

This will be done by acceptance testing – Beta testing, which is the system in the environment where it will eventually be used; Two types of testing will be done. Unit testing which focuses on the code a developer had written, and function testing which is user oriented and checks the correctness of all functions.

The users will sign off on the system and accept it once they are satisfied with it.

Sponsor Sign-off

Signature ___________________________

Date______________