Sie sind auf Seite 1von 2

<Project Name> Version: <1.

0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

<Project Name>
Software Requirements Specification

Version <1.0>

This document is to capture basic requirements based on project scenario offered or


selected by team and to propose a desired solution/ prototype. Innovation and creativity
of individual team members will help to prepare this document smartly. It’s always an
initial phase of any software project being planned for development and we need to
follow software engineering based concepts for the same.
According to the concepts of Software Engineering: The Software Requirements
Specification (SRS) captures the complete software requirements for the system, or a
portion of the system.

Please note following points when preparing this document.


• Information being submitted here must be precise & concise.
• Please use IBM Middleware and IBM Community Edition products only as
mentioned in the website..
• You can use appropriate colors as & when required.
• You should not copy information from any source instead provide reference in
References section.
• You can mention any specific problem faced or support required at the end of
document.

1.1 Overview & Scope


[Specify the purpose of this SRS. The SRS should fully describe the external behavior of
the application or subsystem identified. It also describes nonfunctional requirements,
design constraints and other factors necessary to provide a complete and comprehensive
description of the requirements for the software. Please don’t copy contents directly from
the project scenarios available on TGMC web. A brief description of the software
application that the SRS applies to; It may include number of users / type of users /
departments involved or overall scalability issues of the system..]

1.2 Assumptions and Dependencies


[This section describes any key technical feasibility, subsystem or component
availability, or other project related assumptions on which the viability of the software
described by this SRS may be based.For eg: A specific product may not be available on

<Company Name>, 2006 Page 1


<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

Linux if Linux is the OS you are using hence you can mention that. To know Linux
dependencies kindly visit www.ibm.com/linux/matrix]

1.3 Definitions, Acronyms and Abbreviations


[This subsection should provide the definitions of all terms, acronyms, and abbreviations
required to interpret properly the SRS. This information may be provided by reference to
the project Glossary.]

1.4 Technologies to be used


[This section mention all the technologies & products that you will be using as part of
your project like, (Java, J2EE- Servlets, JSPs etc and DB2, DB2 Express – C and WAS,
WASCE etc]

1.5 Specific Requirements


[This section of the SRS should contain all the software requirements to a level of detail
sufficient to enable designers to design a system to satisfy those requirements, and testers
to test that the system satisfies those requirements. You can use use-case modeling for
the same if you wish, even though it is not compulsory. If use-case modeling is not used,
the outline for specifications may be inserted directly here.]

1.6 Architecture diagram & database design


[Mention your application architecture diagram and database design schema here]

1.7 User Interface


[This subsection should provide some screen shots / layout of graphical user interface
being designed.]

1.8 References
[This subsection should provide a complete list of all documents referenced elsewhere in
the SRS. Each document should be identified by title, report number (if applicable), date,
and publishing organization. Specify the sources from which the references can be
obtained. This information may be provided by reference to an appendix or to another
document.]

1.9 Problems / Queries


[Please let us know any specific problem being faced or support required for submission
of this project solution.]

<Company Name>, 2006 Page 2