Department of Computer Engineering / Information Technology

Instructions for IV B.E students doing project work

Following instructions are to be strictly followed while preparing SDS

failing which the SDS is likely to be rejected.
Do’s: -
Number of copies of SDS = Number of students in the group+1
One copy to be submitted before due date in Lab B203 to Mr Amol Dighe/Mr
Arpit Agrawal otherwise group would be unregistered in exam record.

1. [FONT TYPE: Times New Roman]

Main heading size=14, sub heading size=13, All text size=12
Alignment should be justified for all paragraphs.

Line Spacing - 1.5 between running text.

2 between two paragraphs.
2 between title and text.
In all pages leave left margin more then right margin otherwise there will be
problem when you will put pages in strip file.Use strip/plastic file for SDS.

2. Page number should be there on bottom of each page centrally aligned.

The first page of the chapter should include Chapter number and Chapter Name
centrally aligned. A Chapter should start with new page.

Utilize the full page space with text or figures i.e. don’t leave half or more then
half page empty in a chapter.

3. All figures and tables should be named and numbered.

4. Spacing should be uniform between paragraphs throughout the

SDS.Paragraphs should be justified.Utlilize each page fully.

5 Index should be prepared with appropriate numbering.

6 For all diagrams standard conventions should be used

For conventions Rational Rose Modules may be referred

7 Name of the guide and their post can be seen from their name plate outside the
cabin. Write it correctly in your SDS.
Don’ts:-
1) Using University logo is not allowed.
2) Don’t assign a chapter no. to bibliography and appendix.

3) Don’t write any abbreviations anywhere write the full form.

4) No page border and shading on any page of SDS.

5) Don’t put section / subsection as last line of the page.

 [Times new roman, size=20 and text bold] for the title
Title of the project
(WRITE ONLY THE FIRST LETTER OF EACH WORD IN CAPITAL WHEN
WRITING TITLE)

Times New Roman [size=14] for the below detail

Software Design Specification
(Session 20 -20 )

Times New Roman [size=14] for the below detail

Guided By: Submitted By:

Name of Project Guide Name of Students (Roll No)
(In alphabetical order)

Instruction for writing Name of the Branch/Department Name follow this everywhere
in the SDS.
(**** If group contains a mix of Computer and IT students then each student should
write the Name of the Branch / Department name as his own branch/Department in
which he is studying in his copy and not as Department of Computer
Engineering/Information Technology)
[size = 16] for the below detail
Department of Department name
Institute of Engineering & Technology
Devi Ahilya Vishwavidyalaya, Indore (M.P.)
(www.iet.dauniv.ac.in)
Month Year
 Revised Format
Students are required to maintain the following sequence of contents in the
respective order as indicated below:-

TABLE OF CONTENTS Page No

Chapter-1 Introduction
Chapter-2 Literature Survey
Chapter-3 Analysis
Chapter-4 Design
Chapter - 5 Implementation
Chapter – 6 Conclusion
Bibliography.

Chapter-1 Introduction
1.1 Overview and issues involved 1
1.2 Problem definition 2
1.3 Proposed solution

Chapter-2 Literature Survey

2.1 Methodology will include the steps to be followed to achieve the objective of the project during
the project development also include the Description of all Conceptual
Requirements(Terms,Concepts,Algorithm if any) that any body will need for understanding your
project for example What is a Web service? , Requirements for a Web Service etc.
2.2 Technologies and Tools to be used with a very short description and justification of using them.
2.3 Existing Solutions (Clearly describe all the solutions that are existing in the market in a detail manner
paragraph wise that cover your problem definition exactly or partially it may be study of websites
that may be related to your project or any other studies. It should be as exhaustive as possible but
related to your work.. Summarize the literature that you have read. Rather than literally copying the
texts that you have read, you should present your own interpretation of the theory. The last part of
this section must contain a brief mention of the gaps in the literature and a justification for
undertaking your study/project. For example If you are preparing a website in this section give
description of at least five related websites that you visited what functionalities were included in
them ,what were their advantages ,their drawbacks.)

Chapter-3 Analysis
3.1 Software Requirements
3.2 Hardware Requirements
3.3 Use Case Model
3.4 Use Case Description(See from the sample format of use case description from the pdf file of use
case description posted at your group .Any other format except the sample format uploaded is not
allowed)
Use case description of each use case in the use case model must be there and it must be properly
numbered and according to the format. In a particular use case description don’t simply write the
Preconditions, Post conditions and Special Requirements as none before analyzing the particular
use case in detail.

Chapter-4 Design
4.1 Technology Selection (Clearly specifying the reasons behind choosing a particular
technology used in your project)
4.2 Sequence diagrams(The names of classes and names of functions in the sequence diagrams should
match with names of classes and names of functions in class diagrams)

4.3 Packaging (Name of each package with name of classes it contains)

 It must also include the System Overview explaining how various stakeholders of the system
interact to make the application functional, description of architectural strategy adopted with block
diagram of architecture used in the project .
4.4 Database Design (Complete E-R diagram with cardinalities and relationships, It must also include
the name of each table structure with all its fields and a short description of the content of the
table under it .)

Chapter – 5 Conclusion
It should include your learning from the project that you will develop, limitations of the project that you
will develop
Bibliography.
Appendix ( Glossary and other relevant material)