Project Title

Software Design Document

Submitted by Your Name (Reg. No: XXXXXXXX) Sixth Semester, M C A Under the guidance of
Internal Guide Name Designation Department of M C A M.I.T, Manipal 576 104 External Guide Name Designation Company Address Line1 Place PIN

February 2013

Contents

Introduction 1.1 1.2 1.3 1.4 1.5 Document Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . Product Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . Denitions, Acronyms and Abbreviations . . . . . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 1 1 1 2 2 3 3 3 4 4 4 i

System Design 2.1 2.2 2.3 2.4 2.5 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Design and Description . . . . . . . . . . . . . . . . . . . Detailed Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Interface Design . . . . . . . . . . . . . . . . . . . . . . . . .

Bibliography

Chapter 1 Introduction
1.1 Document Purpose

Identify the purpose of this Software Design Document (SDD) and its intended audience. (Example : This software design document describes the architecture and system design of ......

1.2

Product Scope

Provide a short description of the pupose of software being specied and its purpose, including relevant benets, objectives, and goals. TO DO: 1-2 paragraphs describing the scope of the product. Make sure to describe the benets associated with the product.

1.3

Document Overview

Describe what the rest of this document 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

Project title

1.4

Denitions, Acronyms and Abbreviations

Dene all the terms necessary to properly interpret the SDD, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specic to a single project in each SRS. TO DO: Please provide a list of all abbreviations and acronyms used in this document sorted in alphabetical order

1.5

References

List any other documents or Web addresses to which this SDD refers. These may include user interface style guides, contracts, standards, system requirements specications, use case documents, or a vision and scope document.

Department of M.C.A

M.I.T, Manipal

Chapter 2 System Design

2.1 System Overview

Give a general description of the functionality, context and design of your project Provide any background information if any.

2.2

Initial Design

The above subtitle can be changed to Architectural/Structural design for OO approach The main purpose is to gain the general understanding of how and why the system was decompsed. Provide the major diagram showing the major subsystems. You may choose functional description or object oriented description. 1. For a functional description put a highlevel DFD(context-level data ow diagram) and structural decomposition diagrams as applicable. 2. For an OO description, put sub system model,use-case diagram, object diagram, class diagram, generalization hierachy diagrams(if any), aggregation hierarchy diagram if any. Discuss the rationale for selecting the architecture. Each diagram must be explained briey and must be refered in the description.

Project title

2.3

Database Design and Description

1. E-R Digram, schema diagram, table structure and data dictionary for function oriented design. 2. For Object Oriented design persistent or static data store, transient or dynamic data, external interface data and transformation data Each diagram must be explained briey and must be referred in the description.

2.4

Detailed Design

The above subtitle can be changed to behavioral design for OO approach. 1. For a function-oriented design you can present the Data-low data ow diagram, function/module description, data dictionary etc as applicable 2. For an object oriented design you can present general ow diagram,sequence diagram, state transition diagram,activity diagram, collaberation diagram, state chart any other relavent diagrams. Each diagram must be explained briey and must be refered in the description. Those who are using OO approach can have two sections as Structural Design and Behavioral design instead of Initial design and Detailed Design

2.5

User Interface Design

Any details pertaining to user interface design can be presented in this section

Department of M.C.A

M.I.T, Manipal

Bibliography
[1] Lee and Bae Keun, Video/Image coding method and system enabling region of interest, International Publication Number WO/2005/069634 A1, Samsung Electronics Co. Ltd., 28th July 2005. [2] Miled and Mohamed Khames Ben Hadj, Region of Interest tracking method and device for wavelet based video coding, International Publication Number WO 2004/044830 A1, Nokia Inc US, 27th May 2004. [3] Bae, et al, Multiple region of interest support in scalable video coding, ETRI Journal Volume 28, Number 2, April 2006.