Escolar Documentos
Profissional Documentos
Cultura Documentos
Specification
For
ORITECH APPLICATION
Prepared by :
MUHAMMAD SAAD
DATE CREATED :
20-7-2014
SoftwareRequirementsSpecificationforOritechApplication
Pageii
TableofContents
TableofContents...........................................................................................................................ii
RevisionHistory.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5
Purpose...........................................................................................................................................1
DocumentConventions..................................................................................................................1
IntendedAudienceandReadingSuggestions.................................................................................1
ProjectScope..................................................................................................................................1
References......................................................................................................................................1
2.1
2.2
2.3
2.4
2.5
2.6
2.7
ProductPerspective........................................................................................................................2
ProductFeatures.............................................................................................................................2
UserClassesandCharacteristics....................................................................................................2
OperatingEnvironment..................................................................................................................2
DesignandImplementationConstraints.........................................................................................2
UserDocumentation.......................................................................................................................2
AssumptionsandDependencies.....................................................................................................3
2. OverallDescription..................................................................................................................2
3. SystemFeatures.......................................................................................................................3
3.1 SystemFeature1............................................................................................................................3
3.2 SystemFeature2(andsoon)..........................................................................................................4
4. ExternalInterfaceRequirements...........................................................................................4
4.1
4.2
4.3
4.4
UserInterfaces................................................................................................................................4
HardwareInterfaces........................................................................................................................4
SoftwareInterfaces.........................................................................................................................4
CommunicationsInterfaces............................................................................................................4
5.1
5.2
5.3
5.4
PerformanceRequirements.............................................................................................................5
SafetyRequirements.......................................................................................................................5
SecurityRequirements....................................................................................................................5
SoftwareQualityAttributes............................................................................................................5
5. OtherNonfunctionalRequirements.......................................................................................5
6. OtherRequirements................................................................................................................5
AppendixA:Glossary....................................................................................................................5
AppendixB:AnalysisModels.......................................................................................................6
AppendixC:IssuesList.................................................................................................................6
SoftwareRequirementsSpecificationfor<Project>
1.
Introduction
1.1
Purpose
Page1
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 Order
2. View Product
3. Suggestion
4. Feedback
5. Query Solve
6. Interact with companys employee
7. Inventory information
1.2
DocumentConventions
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
IntendedAudienceandReadingSuggestions
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
ProjectScope
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.
SoftwareRequirementsSpecificationfor<Project>
1.5
Page2
References
Howtowritesoftwarerequirementsspecificationat
http://www.microtoolsinc.com/Howsrs.php
SRSTemplateathttp://www.processimpact.com/process_assets/srs_template.doc.
2.
OverallDescription
2.1
ProductPerspective
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
ProductFeatures
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 dont 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
UserClassesandCharacteristics
Oritech.com is the sophisticated and effective web site to deal with all the major aspects related to
customers 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
OperatingEnvironment
1.1.
Software
SoftwareRequirementsSpecificationfor<Project>
Page3
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
2.5
DesignandImplementationConstraints
CRM requires a web server connected to the internet; a programming language for describing the
systems 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
UserDocumentation
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
AssumptionsandDependencies
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.
SoftwareRequirementsSpecificationfor<Project>
3.
Page4
SystemFeatures
4.
ExternalInterfaceRequirements
4.1
UserInterfaces
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 companys 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
HardwareInterfaces
Pentium IV Processor, 1GB
Minimum 128 MB RAM, Recommendable 512 MB
Minimum 20 GB Hard Disk, Recommendable 80 GB
SoftwareRequirementsSpecificationfor<Project>
4.3
Page5
SoftwareInterfaces
Photoshop
Dreamweaver
My SQL
Operating system: Windows Xp, Windows Vista, Windows 7
Application tools: Internet explorer, Google chrome, Firefox, safari etc.
Languages:
4.4
PHP
HTML
CSS
Javascript
CommunicationsInterfaces
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.
OtherNonfunctionalRequirements
5.1
PerformanceRequirements
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)
5.2
SafetyRequirements
SoftwareRequirementsSpecificationfor<Project>
Page6
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
SecurityRequirements
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
SoftwareQualityAttributes
6.
OtherRequirements
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.
SoftwareRequirementsSpecificationfor<Project>
Page7
SoftwareRequirementsSpecificationfor<Project>
Page8
view advertisements
edit profile
view peoducts
give complaints
ask queries
customer
give suggestions
place order
give feedback
SoftwareRequirementsSpecificationfor<Project>
Page9
edit profile
view advertis ements
view complaints
view feedback
employee
s olve queries
view cus tom er order
SoftwareRequirementsSpecificationfor<Project>
Page10
SoftwareRequirementsSpecificationfor<Project>
CLASS DIAGRAM
Page11