Software Requirements Specification

For

ORITECH APPLICATION

Prepared by :

MUHAMMAD SAAD

MUHAMMAD AHSAN ASLAM

ASIM RAZA FIRDOUSI

DATE CREATED :

20-7-2014

Software Requirements Specification for Oritech ApplicationPage ii

Table of ContentsTable of Contents....................................................................................................................... iiRevision History......................................................................................................................... ii1. Introduction.......................................................................................................................... 1

1.1 Purpose......................................................................................................................................11.2 Document Conventions..............................................................................................................11.3 Intended Audience and Reading Suggestions..............................................................................11.4 Project Scope..............................................................................................................................11.5 References..................................................................................................................................1

2. Overall Description.............................................................................................................. 22.1 Product Perspective....................................................................................................................22.2 Product Features.........................................................................................................................22.3 User Classes and Characteristics.................................................................................................22.4 Operating Environment...............................................................................................................22.5 Design and Implementation Constraints......................................................................................22.6 User Documentation...................................................................................................................22.7 Assumptions and Dependencies..................................................................................................3

3. System Features................................................................................................................... 33.1 System Feature 1........................................................................................................................33.2 System Feature 2 (and so on)......................................................................................................4

4. External Interface Requirements........................................................................................44.1 User Interfaces............................................................................................................................44.2 Hardware Interfaces....................................................................................................................44.3 Software Interfaces.....................................................................................................................44.4 Communications Interfaces.........................................................................................................4

5. Other Nonfunctional Requirements....................................................................................55.1 Performance Requirements.........................................................................................................55.2 Safety Requirements...................................................................................................................55.3 Security Requirements................................................................................................................55.4 Software Quality Attributes........................................................................................................5

6. Other Requirements............................................................................................................. 5Appendix A: Glossary................................................................................................................ 5Appendix B: Analysis Models.................................................................................................... 6Appendix C: Issues List............................................................................................................. 6

Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose

This is a web-based CRM application with customized admin panel that is meant to facilitate any business sector in Pakistan to build and strengthen its customer relationships by continuously keeping in touch with the customers.

Our purpose is to fulfill the following activities:1. Customer Order2. View Product3. Suggestion4. Feedback5. Query Solve6. Interact with company’s employee7. Inventory information

1.2 Document Conventions

While writing for SRS document we have made the following conventions and adopted the IEEE Standards Font used – Arial For main headings font size – 18 For subheadings font size- 14 For Normal Text- 11 Headings are highlighted in bold Document text is single spaced and maintains the 1” margin.

1.3 Intended Audience and Reading Suggestions

The document is intended for project guide, class coordinator and professor. The SRS document contains overall descriptions, specific requirements, and other non-functional requirements of the project.

1.4 Project Scope

Our project is made in PHP, HTML, CSS, Javascript as it is made at administrator level. Our objective is to maintain relationship with the customer in which we can solve the queries of the client such as providing the customer the information about the new products , solve various queries, take suggestions and feedback from customers.

Software Requirements Specification for <Project> Page 2

1.5 References

How to write software requirements specification at http://www.microtoolsinc.com/Howsrs.php

SRS Template at http://www.processimpact.com/process_assets/srs_template.doc.

2. Overall Description

2.1 Product Perspective

Customized CRM application will be a web service which is going to be hosted on a server which contains the CRM application and the database server.. Web service will be run on SQL.Application will be using open source language PHP which is also a web based language.All the coding will be created in PHP language. Application can be run through any browser like Mozilla, internet explorer. Google chrome etc. java script should be enabled in the pc. User must have the login and the password to use the application.

2.2 Product Features

The Customizable CRM application is designed for the “IT” industry which can develop good relations with their customers. By querying the customers to solve their problems . It is a customizable CRM that means the admin can restrict the user by accessing any forms which admin don’t want to show the customer. Different users can access different forms according to per user accessibility by the admin. Admin panel has the rights to do that. File uploading is also a very good feature of this project so that the user can easily upload the file he want to solve by uploading the file to the company.

2.3 User Classes and Characteristics

Oritech.com is the sophisticated and effective web site to deal with all the major aspects related to customer’s relation with the company that can help an individual to get all the information regarding new products with many other options that can used to solve their queries online.

2.4 Operating Environment

1.1. Software

The required software for the project are listed below :

Software Requirements Specification for <Project> Page 3

Photoshop Dreamweaver My SQL Operating system: Windows Xp, Windows Vista, Windows 7 Application tools: Internet explorer, Google chrome, Firefox, safari etc.

Languages:

PHP HTML CSS Javascript

1.2. Hardware

The required Hardware for the project are listed below :

PC with 800 mhz or above processor and 1 GB RAM

Storage media: not necessary

Windows XP/Windows7/ Windows8 with Internet Facility

2.5 Design and Implementation Constraints

CRM requires a web server connected to the internet; a programming language for describing the system’s logic; a server engine for generating the dynamic HTML content; and a database to provide a way of storing and retrieving large amounts of data. Only system administer has the right to change system parameters.The system should be secure and must use encryption to protect the databases.

2.6 User Documentation

User should know the details of the working being done in the software User should be comfortable with the working of the computer and how does that project

works.

2.7 Assumptions and Dependencies

All the hardware would function properly and all the information provided by the user should be correct to avoid any sort of problem regarding relationship with the customer.

The user should be login to the system

Software Requirements Specification for <Project> Page 4

Access is dependent on basis of level. Username and password is availability to the administrator. The user is an authorized one.

3. System Features3.1 System Features 1

3.1.1 Description & priority In this project, data access is given to the user on the basis of level of there designation. Higher the level, the more access is provided. At the highest level, the administrator supervises all the clients under him & he can access all the data.

3.1.2 Stimulus/Response sequence

Initially the user enters a user name & password. If it is among the one which are already saved then the user is an authenticated one. Else it will show the wrong user name & password.

On the basis of designation at which the person exists the access will be given.

The employee will perform the work or task for which he is being employed.

3.1.3 Functional Requirement

PC with 800 mhz or above processor and 1 GB RAM

Storage media: not necessary

Windows XP/Windows7/ Windows8 with Internet Facility

4. External Interface Requirements

4.1 User Interfaces

This project is made to be used by the Oil company. Client can not deal with this directly. Employers are going to get benefit from it. Earlier all this work was done manually. The clients had to visit the company’s service center. When the client, employee or the admin logins & if he enters wrong user name & password then it will prompt a message.

4.2 Hardware Interfaces

Pentium IV Processor, 1GB

Software Requirements Specification for <Project> Page 5

Minimum 128 MB RAM, Recommendable 512 MB Minimum 20 GB Hard Disk, Recommendable 80 GB

4.3 Software Interfaces

Photoshop Dreamweaver My SQL Operating system: Windows Xp, Windows Vista, Windows 7 Application tools: Internet explorer, Google chrome, Firefox, safari etc.

Languages:

PHP HTML CSS Javascript

4.4 Communications Interfaces

The Communication Between the client and the administrator takes place through E-mail. It requires a web browser at the client side and a web server at the Server Side. The communication standards that will be used, are as FTP or HTTP. Only system administer has the right to change pricing policy, reply to customer queries, assign the work to the employees according to their specialization and answer to the frequently asked questions etc. The system should be secure and must use encryption to protect the databases. Users need to be authenticated before having access to any personal data.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Response time of CRM for mycell.com will depend on the query made by the user to the employee. When the user will complain about his problem, the problems will be received by the employee and response will be given when the problem is solved. It may take some hours or days depending on the problem. Response time refers to the waiting time while the system accesses, queries and retrieves the information from the databases.(DB-user, DB-schedule etc) (A local copy of property database is maintained as DB-schedule to reduce this access time)

Software Requirements Specification for <Project> Page 6

5.2 Safety Requirements

CRM shall be available 24 hours a day, 7 days a week. CRM shall always provide real time information about available product information. CRM shall be able to recover from hardware failures, power failures and other natural

catastrophes and rollback the databases to their most recent valid state.

5.3 Security Requirements

Only system administer has the right to change system parameters, such as pricing policy etc. The system should be secure and must use encryption to protect the databases.

Users need to be authenticated before having access to any personal data.

5.4 Software Quality Attributes

Software quality attributes that need to be addressed are: Availability of space required to construct the project and upload it. Correctness of the information. Flexibility in operating the software from anywhere in the world. Interoperability that is introduced as the project is made using .net. Maintainability of the project. Reliability of the information and the software. Robustness of the software. Testability and usability of the software.

6. Other Requirements A database of a fixed large memory size would be required. All the legal formalities regarding the usage of internet space need to be addressed. All commercial and privacy policies need to be kept in mind during the development and

implementation of the project.

Software Requirements Specification for <Project> Page 7

USE CASE DIAGRAMS

Software Requirements Specification for <Project> Page 8

view advertisements

edit profile

view peoducts

give complaints

give feedback

place order

ask queriescustomer

give suggestions

Software Requirements Specification for <Project> Page 9

edit profile

view advertisements

view complaints

view feedback

read suggestions

solve queries

employee

view customer order

Software Requirements Specification for <Project> Page 10

Software Requirements Specification for <Project> Page 11

CLASS DIAGRAM