Scribd
Upload
408 views6 pages

Software Design Document

This software design document outlines a project to create a software application. It includes sections on the system vision, requirements, system components and software design, and user interface design. The system vision provides an overview of the problem, system, and potential benefits. Requirements include user needs, software functionality, and use cases. The software design shows system components, including functions, data structures, and algorithms. Finally, the user interface design presents the information structure, navigation, and visual design of the interface.

Uploaded by

sadia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
408 views6 pages

Software Design Document

This software design document outlines a project to create a software application. It includes sections on the system vision, requirements, system components and software design, and user interface design. The system vision provides an overview of the problem, system, and potential benefits. Requirements include user needs, software functionality, and use cases. The software design shows system components, including functions, data structures, and algorithms. Finally, the user interface design presents the information structure, navigation, and visual design of the interface.

Uploaded by

sadia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Software Design Document

<Project Name>
Student Names
Table of Contents
1.0 System Vision.............................................................................................................................3
1.1 Problem Background.............................................................................................................3
1.2 System Overview...................................................................................................................3
1.3 Potential Benefits..................................................................................................................3
2.0 Requirements............................................................................................................................4
2.1 User Requirements................................................................................................................4
2.2 Software Requirements.........................................................................................................4
2.3 Use Cases...............................................................................................................................4
3.0 System Components and Software Design................................................................................5
3.1 System Components..............................................................................................................5
3.2 Software Design.....................................................................................................................5
4.0 User Interface Design................................................................................................................6
1.0 System Vision
1.1 Problem Background

1.2 System Overview

1.3 Potential Benefits


2.0 Requirements
2.1 User Requirements
In this section you detail how a user is supposed to interact with or use your program. What do they
need to be able to do? This should all be from the end users perspective. Can be a combination of
narrative text and listing of needs.

2.2 Software Requirements


In this section you detail what the requirements for the software are. What functionality will it
provide? This is usually a formal listing, with requirements often using the word ‘Shall’. IE:

R1.1 The program shall accept multiple file names as arguments from the command line.

R1.2 Each file name can be a simple file name or include the full path of the file with one or more
levels.

etc …

Can be primarily functional requirements, though you may include other types if you think of them.

2.3 Use Cases


In this section you provide some use cases showing how people may use your software.
3.0 Software Design and System Components
3.1 Software Design
A block diagram/flowchart of how your software might work

3.2 System Components


3.2.1 Functions
List of all functions in the software. For each function in the list the following information is
provided:

• a brief description of what it does (1 or 2 sentences);


• a list of the input parameters, and their data types, and what they are used for;
• a list of any side effects caused by the function (ie change global or member variables,
changes data passed by reference from calling function etc)
• a description of the function’s return value

3.2.2 Data Structures


List of all data structures in the software (eg linked lists, trees, arrays etc). For each data structure in
the list the following information is provided:

• Type of structure (tree, list etc),


• Description of where and how it is used
• List of data members, and what each one is for do
• List of functions that use it
•

3.2.3 Detailed Design


Pseudocode for all non-standard / non-trivial algorithms that operate on data structures
4.0 User Interface Design
This is your initial interface design. Describe the tools you used for this design stage and any key
findings that informed your design. This introduction is descriptive and should explain what you
have completed for the actual design work you will present in the sub-sections below.

4.1 Structural Design


Structural design refers to the navigational and information structure of your product – the structure
that supports the interface layout. How will you structure your product? How will you group your
information? How will you navigate through your product? Why? This can take the form of a
diagram showing structure and hierarchy, supported by a discussion and justification of your
choices. Why have you made these design choices? Describe and outline the structure of your
interface and of your information.

4.2 Visual Design


Detail your visual design: Layout, visual elements, icons, graphics, style, colour, fonts general screen
designs. This can be sketches, wireframes, mockups etc, supported by a discussion, explanation, and
justification of your choices.

You might also like