Specifications
for
Prepared by RASHMI R
12 NOVEMBER 2010
1. Introduction
1.1 Purpose
<Identify the product whose software requirements are specified in next chapter, describe the
need for development of the product. State Very abstractly what the system does to fulfill the
needs of the end user. >
1.2 Motivation
<Describe the rationale behind development of the project and selection of the theme of
project.eg. tell about what inspired you to select the topic. And what is the idea.>
<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.
specify the role the project would have after implementation. The possibility of using the project
in solving real world problem eg. Understanding the practical design and implementation issues
of web applications, consolidating various web technologies and integrate these to develop
innovative Rich internet application>
< After selecting the a relevant topic (project theme), review information from various sources
(books, journals, conference proceedings, web sites, product literature, etc.), and formulate a
coherent report about that topic. Add reference numbers wherever relevant.>
2. Overall Description
Provide the product perspective here. <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.>
<Summarize the major features the product contains or the significant functions that it performs or
lets the user perform. Details will be provided in Section 2.3, so only a high level summary is
needed here. Organize the functions to make them understandable to any reader of the SRS.
REQ-1:
REQ-1: Select suppliers to whom the RFP(REQUEST PROPOSAL) will be submitted. These
suppliers should be on the list of qualified suppliers. If they are not, there should be some evidence that
they would be appropriate candidates for performing the work to be subcontracted. See Appendix H,
Guidance for Selecting Suppliers.
REQ-2: Contact suppliers to determine whether they wish to receive the RFP. If so, identify the
individual at the supplier’s site to whom the RFP is to be submitted.
REQ-3: If necessary, execute a nondisclosure agreement with suppliers who wish to receive the RFP.
REQ-4: Deliver the RFP to the suppliers by the most expeditious route, confirming receipt by each
supplier.
REQ-5: Record the list of suppliers to whom the RFP was submitted in the proposal evaluation report.
REQ-6: Respond to questions submitted by suppliers. Communicate clarifications or
corrections concurrently to all suppliers who received the RFP. Revise the RFP as necessary
according to the project’s change control process.
<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.>
<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 may be documented in a separate user interface specification(manual )
and added in appendix .>
<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.>
<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.>
DBI
<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.>
<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.>
Reference :BEST PRACTICE TO IMPROVE PERFORMANCE:http://developer.yahoo.com/performance/rules.html
<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>
HINT
TAKING BACKUP
<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>
ENCRYPTION
AUTHENTICATION
AUTHORIZATION
<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>
Portability
3. Design
<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).>
Hints
The presentation layer/ web site is designed to work efficiently on Particular browser ( either IE or
Firefox)
The Apache web server being used is not connected to the external network.
<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 could be
affected if these assumptions are incorrect, are not shared, or change. Also identify any
dependencies the project has on external factors, such as software components that you intend
to reuse from another project, unless they are already documented elsewhere (for example, in the
vision and scope document or the project plan).>
<This section should provide a high-level overview of how the functionality and responsibilities of
the system were partitioned and then assigned to subsystems or components. Don't go into too much
detail about the individual components themselves (there is a subsequent section for detailed
component descriptions). The main purpose here is to gain a general understanding of how and why
the system was decomposed, and how the individual parts work together to provide the desired
functionality.>
Write architecture diagram - A simple diagram that shows the major components of the overall
system, subsystem interconnections, and external interfaces.
Reference:
http://support.novell.com/techcenter/articles/nc2000_09a.html
http://www.ibm.com/developerworks/ibm/library/it-booch_web/
http://www.15seconds.com/issue/011023.htm
http://www.exforsys.com/tutorials/client-server/n-tier-client-server-architecture.html
CLIENT ______________INTERFACE_______SERVER_______INTERFACE________DATABASE
4. Detailed Design
<Describe all important modules in client and server side. Elaborate the architecture diagram to
depict navigation of web pages, mapping of request document with specific server side
program.>
Web diagram
Reference:
http://publib.boulder.ibm.com/infocenter/radhelp/v6r0m1/index.jsp?topic=
%2Fcom.ibm.etools.web.diagram.doc%2Ftopics%2Fcwebdia003.html
or
Figure 27. Sample process flow diagram for a web-based J2EE application
<This section should provide detailed description of what module does. >
<This section should provide detailed description of what module does. >
So on……………………
5. Implementation
5.1 Platform
<Describe the platform on which the project will be deployed(eg. Fedora, windows etc.>
<List the languages used with few characteristics of programming languages that are
implemented in the project >
So on……
WRITE ONLY SIGNIFICANT CODE USED IN YOUR PROJECT OTHER THAN WRITING
PRESENTATION LAYER AND DATABASE ACCESS.
DESCRIBE SPECIFIC BUSINESS LOGIC (highlight of the project) USED IN YOUR PROJECT
TESTING
6.1 Unit Testing
Unit testing is done to verify and validate whether individual units of source code are fit for use. A
unit is the smallest testable part of an application. The smallest unit of the Education Loan
Management System may be an insert, delete or update operation.
Table 6.7 Integration Test Case1 for Education Loan Management System
6. Results
<Describe the result of project.>
6.1 Observation
<summarize the process and results obtained. Also specify the limitations in
technology/organization/guidlines which affected the implementation/realization of the product
features >
<summarize the process and results obtained. Also specify the limitations in
technology/organization/guidlines which affected the implementation/realization of the product
features >
7. Conclusion
<one /two paragraph.>
REFERENCE