Monday, June 4, 2012

How To Prepare SRS for TGMC Project!

Posted by Shiva Gouraram | Monday, June 4, 2012 | Category: , , , , , |

Hi Folks,
This is an article exclusively for TGMCians who are in their first stage of TGMC Competition, i.e Preparing SRS for their selected projects.
As a TGMCian I faced a lot of problems while creating my first SRS in TGMC 2010,and me and vikas are here to explain about what is SRS and how to create it for TGMC projects.
Before starting your SRS I would like to let you know what SRS is and what tools are used to create SRS for TGMC projects.
SRS is a Software Requirements Specification is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform.
An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. A good SRS defines how an application will interact with system hardware, other programs and human users in a wide variety of real-world situations. Parameters such as operating speed, response time, availability, portability, maintainability, footprint, security and speed of recovery from adverse events are evaluated. Methods of defining an SRS are described by the IEEE (Institute of Electrical and Electronics Engineers) specification.
OK now I think you are aware of what SRS is and why it is used in software development.
Now I will let you know which tools are to be used for creating TGMC SRS for better points.
Always keep in mind that we have to use IBM tools in the entire project, so for creating SRS we use Lotus Symphony an IBM tool for documentation we can prepare Documents, Presentations, etc. using this tool.
It is just like Microsoft Word but it is developed by IBM and we have to use Lotus Symphony. We can even use Microsoft Word but we get more points if you use IBM tools for everything.

In SRS we have to design Models using UML Language to describe the flow of the project, use cases etc.
For designing UML Diagrams we can use Rational Rose or RSA(Rational Software Architect) or Rational Software Modeler, we use Rational Rose or RSA for modeling.
Download Rose

O.K. we have tools to create SRS for our project.
Well before start writing your SRS you have to analyze your project in a better way, i.e. you have to know what should you do and by which you should do and how should you do.
This makes creating a good SRS, good SRS is not good looking SRS, SRS is good if the content in SRS is good not its look.
Before Creating your own SRS have a look at few SRS’s already created, I am making available few SRS’s which are created for previous years TGMC projects.

Hmm hope this may help you out!
Ok now we discuss about a brief introduction of writing contents for SRS.

In this section you have to introduce your projects in your terms, do this after completely analyzing your project and make sure you give a good introduction to your project.

The name itself tells us to describe about the purpose of the project, describe why you have to going to develop this project. And if possible explain the older system for which you are going to develop a new system.

The scope of the project is to describe the basic features of the project going to be implemented in your project.

Definitions, Acronyms, and Abbreviations
In this section you have to mention the abbreviations ,definitions of the technologies and tools you are going to use in your project, for example see the SRS’s given above.


Mention the references from where you came to know about a project or something which helped you to do your may include links, books, authors, etc..!

Technologies Used

Describe the technologies which you have used and going to be used for project development.

Tools Used

Describe the tools which you have used and going to be used for project development.

Product Perspective

Describe the architecture used for project development or some limitations or protocols used for your project.

Software Interface

Mention the software requirements like what software is used to run your project for both client and server side like operating system, tools needed etc.

Hardware Interference

Mention the hardware requirements like what hardware is used to run your project for both client and server side. Which may include RAM, HARD DISK SPACE, and PROCESSOR etc.!

Product Functions

Briefly explain the functions and features of your project.

User characteristics

Describe the user characteristics like what types of users can access your system, what skills should users have and user interface used etc.


It can be limitations of your project.

Architecture Design

Give a pictorial Representation of architecture used for your project.

Use Case Model Description

It is a complete overview of total use cases of your project

Class Diagram, Sequence Diagram, Use case Diagrams, ER Diagram and other UML Diagrams are going to be discussed in other sessions with examples and how to use tools and etc.

Assumptions and Dependencies

The name suggests what you have to be described in this section.
Supplementary Requirements
Supplementary requirements include other requirements which are beyond functional requirements. This may include,

Server Configuration
Database Backups
User Friendly Interface
Safety Requirements
Security Requirements etc.

That’s all folks, hope it helped you to some extent!


Currently have 3 comments:

  1. Good tutorial.........nice work...:)
    Keep it up

  2. This comment has been removed by the author.

  3. Thanks for your detailed description and the links you have provided. Surely, it will be helpful for us to prepare our SRS.


Leave a Reply