System Design Specification Sds

System Design
Specification
for
Project Title: aaa
Project Code: aaannn
Version: x.x
Date: dd/mm/yy
Template Revised April 2013

System Design Specification for aaannnError: Reference source not found Version: x.xError:
Reference source not foundE
rror: Reference source not
found
Contents
1 DOCUMENT MANAGEMENT....................................................................2
1.1 Contributors.....................................................................................................2
1.2 Version Control.................................................................................................2
2 OVERVIEW................................................................................................3
3 DEVELOPMENT TOOLS AND STANDARDS...........................................4

3.1 Development Tools...........................................................................................4
3.2 Development Standards...................................................................................4
4 SYSTEM PROCESSES.............................................................................5
5 USER INTERFACE....................................................................................6
5.1 Transactional Interface....................................................................................6
5.2 MyEd Interface.................................................................................................6
5.3 Reporting Interface..........................................................................................6
6 APPLICATION SECURITY........................................................................7
6.1 Authentication..................................................................................................7
6.2 Authorisation....................................................................................................7
6.3 Business Objects...............................................................................................7
7 DATABASE DESIGN.................................................................................8
8 APPLICATION INTERFACES....................................................................9
9 DATA........................................................................................................10
9.1 Data Migration...............................................................................................10
9.2 Archiving Policy.............................................................................................10
10 IMPLEMENTATION..............................................................................11
Page 1of 11
found
1 Document Management
When completing this document, please mark any section that is not required as ‘N/A’. A brief
description of why the section is not required should also be included.
1.1 Contributors
Please provide details of all contributors to this document.
Role Unit Name

Systems Analyst
Designer
(Owner)
Business
Analyst
Project Manager
Project Sponsor
Business Area
Manager
Other document
contributors
1.2 Version Control

Please document all changes made to this document since initial distribution.
Date Version Author Section Amendment
Page 2of 11
found
2 OVERVIEW
Provide a general overview of the system design so that anyone reading this section is able to gain an
understanding of what functionality is provided and how this functionality will be technically
implemented.
Page 3of 11
found
3 DEVELOPMENT TOOLS AND STANDARDS
3.1 Development Tools

Specify which technologies will be used to develop the application, eg Oracle 9i, Cold Fusion MX,
Oracle Forms, Business Objects, Java, PL/SQL etc.
3.2 Development Standards
Tick the appropriate box to indicate the standards being followed for this application:
Standard √ indicates compliance

Database Design
Cold Fusion
Java
Uportal Development
Accessibility
Web Style Standards
Supported Web Browsers
Page 4of 11
found
4 SYSTEM PROCESSES
Take each process specified in the Business Requirements Document (BRD) and state how it will be
implemented technically (please make reference to the corresponding paragraph number in the BRD).
Where applicable, a specification of each screen which makes up a process should be provided (ie a
screenshot and descriptions of every data item displayed).
All paragraphs should be numbered to assist cross referencing in testing stages.
Page 5of 11
found
5 USER INTERFACE
5.1 Transactional Interface

Use this section to link to an application prototype built by a Designer. The screens should be built in
conjunction with the business partner.
If this section is not applicable then please state why.
5.2 MyEd Interface

Where a MyEd channel is being used to deliver some or all of the transactional interface, provide
design details here.
Note that a Channel Publishing Template (one per channel) should be completed and linked to this
document. The information in this template will form the basis of the channel publishing information
used in MyEd when building channels.
5.3 Reporting Interface

Where applicable, please state how reporting is to be delivered, eg Webi, HTML.
The design of any pre-written reports should be specified, and if Webi is to be used, the Universe
should be defined (ie classes/measures/dimensions and source data).
Page 6of 11
found
6 APPLICATION SECURITY
This section relates to application rather than physical security which is covered in the Technical
Architecture Document (TAD).
6.1 Authentication
6.2 Authorisation
Include application, menu and page authorisation and any application roles.
6.3 Business Objects

Include any specific object/row authorisation.
Page 7of 11
found
7 DATABASE DESIGN
Insert an Entity-Relationship Diagram of the system. If new tables have been added to an existing
system then highlight these in your ER Diagram (full diagram of existing system not needed).
Full specifications should be provided for all new tables/views/columns in the system (ie name,
datatype, mandatory, default values, constraints).
Page 8of 11
found
8 APPLICATION INTERFACES
Provide technical details of any inputs to the system from other applications and any outputs from the
system to other applications. Full data specifications should be included. Identify possible impact on
existing processes.
Page 9of 11
found
9 DATA
9.1 Data Migration

Include any mappings between existing systems and the new system
9.2 Archiving Policy
Page 10of 11
found
10 IMPLEMENTATION
Specify any implementation issues that should be considered when creating an implementation plan at
the Build stage.
Page 11of 11

System Design Specification Sds

Uploaded by

Copyright:

Available Formats

System Design Specification Sds

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Design Specification Sds

Uploaded by

Copyright:

Available Formats

System Design

Project Title: aaa

Project Code: aaannn

Template Revised April 2013

3 DEVELOPMENT TOOLS AND STANDARDS...........................................4

Role Unit Name

1.2 Version Control

Date Version Author Section Amendment

3 DEVELOPMENT TOOLS AND STANDARDS

3.1 Development Tools

3.2 Development Standards

Standard √ indicates compliance

All paragraphs should be numbered to assist cross referencing in testing stages.

5.1 Transactional Interface

If this section is not applicable then please state why.

5.2 MyEd Interface

5.3 Reporting Interface

6.3 Business Objects

9.1 Data Migration

9.2 Archiving Policy

You might also like