Software Requirements Specification For CRM
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
seminar surveyer
Active In SP

Posts: 3,541
Joined: Sep 2010
03-01-2011, 03:45 PM

.docx   Software Requirements.docx (Size: 81.71 KB / Downloads: 339)

Monika Gupta
Neha Dahra
Neha Gupta


This is an online customer relationship management program as well as a groupware and a marketing tool also used for cellular company ‘Mycell’. The CRM module helps admin to identify and maintain their customers and employees. Customers can contact with the plan responsibles and add, edit or delete their own personal profile. They can view different products details, ask their queries, give suggestions and provide feedback for the product which they are using. Similarly employees can also add edit or delete their own profile and provide response to queries, suggestions and feedback of customers .

Purpose is a unique web site for all customers and employees using MyCell products. Now it’s easy for any user to search solutions for any kind of problem coming with his/her Mycell products. It will be easy for the company people to show details of their products.
Our purpose is to fulfill the following activities:
1. Customer Order
2. View Product
3. Suggestion
4. Feedback
5. Query Solve
6. Interact with company’s employee

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.

Intended Audience and Reading suggestions

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

seminar class
Active In SP

Posts: 5,361
Joined: Feb 2011
21-02-2011, 12:49 PM

.pdf   SRS-PeaZip-2.7.1-EN.pdf (Size: 770.69 KB / Downloads: 255)
Software Requirements
1. Introduction
1.1 Purpose

The present document is a software requirements specification document for PeaZip ,
version 2.7.1. PeaZip is a general purpose file and archive manager application for a computer
system, aiming to provide a cross-platform graphical interface for many Open Source archiving and
compression utilities, so that its user would be able to handle most of the available archiving
formats(indicatively: 7z,RAR,ZIP. Full list of the supported formats is provided in following
This document follows “Software Requirements Specification” template for software
requirements specification documents, by Karl E. Wiegers, with a few declensions.
1.2 Document Conventions
The present document concerns software engineers that would work on further
development of this piece of software, as well as clients/users of PeaZip.
This is the only document so far describing PeaZip’s software requirements. It should be
used by software engineers who will develop this piece of software and it should be used for
formalization of the software that is going to be delivered to clients/users. Every future change in
the requirements of this software should be made through a typical procedure of change and final
acceptance of this document.
Software engineers should ask for further explanation or clarification, if and wherever they
decide this is necessary and should not proceed to modifications without the approval of the final
1.3 Intended Audience and Reading Suggestions
This document applies to programmers of this project and implimentation, to software engineers that weal work
on its further development and, finally, to the end users of this application and it aims at displaying
the features of PeaZip version 2.7.1, as well as at providing information about the goals and the
proper use of the software.
Chapters that would interest users are: 3, 4 and 6, whereas the whole document would be
of interest for software engineers and programmers.
1.4 Project Scope
The piece of software to which the present document refers, is a file and archive manager
application for a computer system, that offers user the capability of archiving,compressing and
extracting (decompressing) files and archives.
In brief, the basic functions that PeaZip features are:
Creating compressed archives, updating compressed archives, extracting content of compressed
archives, file and archive management tools(robust copy, split and join, fast or secure deletion,
byte to byte comparison, calculation of a wide set of checksums and hashes over selected files),
append timestamp to archive name(useful for archiving and backup purpose) and two factor
authentication(password and keyfile) for the managed archives. All pre-mentioned functions’
parameters can be modified and adapted to user’s needs and preferences from a settings’ menu.
The initial goal of this application was creating a frontend for Pea archiving utility. However,
after completing PeaZip’s GUI, support to many mainstream archiving and compression formats
was added to PeaZip. In this way, PeaZip became an aggregate frontend GUI for a set of Open
Source archiving and compression utilities(full list of which is provided in following chapters). The
fact that this application is Open Source software, gives its users the chance to directly take part in
its development, as well as notice possible bugs or mistakes and make their suggestions on it.
2. Overall Description
2.1 Product Perspective

Peazip was created for file and archive management in a computer system. The initial goal
of the application was to function as frontend for Pea archiving utility(which was also developed by
PeaZip’s creator, Giorgio Tani). However, after completing the development of PeaZip UI, support
to more archiving and compression formats (full list of which is provided in following chapters) was
added to PeaZip, allowing it to function as a single, consistent frontend GUI, which exposes a list
of options of the underlying applications.
PeaZip works similarly to a large group of well-known applications, like WinRAR and
WinZip. PeaZip features, to a large degree, the same features with the applications of this group
and in addition, it supports a wide range of archiving and compression formats(superset of the
supported by each application of the pre-mentioned group set)as well as some file and archive
management tools(which are mentioned explicitly in following chapters), while at the same time it
offers its users the capability of executing its functions as command prompt commands(resulting
commands can be extracted and saved in a text file), allowing them to monitor any running activity
in real-time.
An important attribute of PeaZip is its self-standingness and its independency from the kind
of the Operating System of the computer system on which it runs. In no case is the installation of
any other program required for PeaZip to work, while for cases that no system integration is
preferred, PeaZip Portable is available as standalone application, not needing installation and not
modifying the host system.

download full report
seminar class
Active In SP

Posts: 5,361
Joined: Feb 2011
23-02-2011, 12:11 PM

.doc   srs_template-1.doc (Size: 54.5 KB / Downloads: 123)
Software Requirements Specification
1. Introduction
1.1 Purpose

<Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem.>
1.2 Document Conventions
<Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.>
1.3 Intended Audience and Reading Suggestions
<Describe the different types of reader that the document is intended for, such as developers, project and implimentation managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.>
1.4 Product Scope
<Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here.>
1.5 References
<List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.>
2. Overall Description
2.1 Product Perspective

<Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.>
2.2 Product Functions
<Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.>
2.3 User Classes and Characteristics
<Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy.>
2.4 Operating Environment
<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.>
2.5 Design and Implementation Constraints
<Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).>
2.6 User Documentation
<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.>
2.7 Assumptions and Dependencies
<List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project and implimentation could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project and implimentation has on external factors, such as software components that you intend to reuse from another project and implimentation, unless they are already documented elsewhere (for example, in the vision and scope document or the project and implimentation plan).>
3. External Interface Requirements
3.1 User Interfaces

<Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.>
3.2 Hardware Interfaces
<Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.>
3.3 Software Interfaces
<Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.>
3.4 Communications Interfaces
<Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.>
4. System Features
<This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.>
4.1 System Feature 1
<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.>
<Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.>
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.>
Active In SP

Posts: 1
Joined: Jul 2011
05-07-2011, 02:08 PM

plz send me the srs of CRM application
siddique ahmad
Active In SP

Posts: 1
Joined: Oct 2011
26-10-2011, 01:46 AM

Attached Files
.docx   CustomerManagementSystem-Synopsis.docx (Size: 182.8 KB / Downloads: 55)
seminar addict
Super Moderator

Posts: 6,592
Joined: Jul 2011
26-10-2011, 09:31 AM

to get information about the topic"Software Requirements Specification For CRM"refer the link bellow
seminar addict
Super Moderator

Posts: 6,592
Joined: Jul 2011
30-01-2012, 11:39 AM

to get information about the topic SOFTWARE REQUIREMENTS SPECIFICATION FOR LIBRARY MANAGEMENT SYSTEM full report, ppt and related topic refer the link bellow



seminar and presentationproject and implimentationsshowthread.php?mode=linear&tid=14645


seminar and presentationproject and implimentationsshowthread.php?tid=28145&google_seo=Fj5T++++++++++++++++++++&pid=61262#pid61262

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  microwind software free download jaseelati 0 284 23-02-2015, 12:47 PM
Last Post: jaseelati
  software reuse seminar ppt jaseelati 0 303 30-12-2014, 04:59 PM
Last Post: jaseelati
  Open Core Protocol ( OCP ) An Introduction to Interface Specification seminar projects maker 0 536 24-09-2013, 12:29 PM
Last Post: seminar projects maker
  Software Agents pdf seminar projects maker 0 394 13-09-2013, 04:55 PM
Last Post: seminar projects maker
  Seminar Report On SOFTWARE REUSE pdf seminar projects maker 0 587 12-09-2013, 04:18 PM
Last Post: seminar projects maker
  STANSYS SOFTWARE SOLUTIONS study tips 0 305 29-08-2013, 01:00 PM
Last Post: study tips
  A Beginner’s Guide To Software Defined Radios PPT study tips 0 294 28-08-2013, 04:55 PM
Last Post: study tips
Last Post: study tips
  FOUNDRY SOFTWARE study tips 0 273 20-08-2013, 03:02 PM
Last Post: study tips
  LOGISTICS AND SCM INFORMATION SYSTEM , SCM SOFTWARE ppt study tips 0 303 03-08-2013, 03:48 PM
Last Post: study tips