System Design Standards



|[pic] | | |

| | |Ministry of Community Development and |

| | |Ministry of Tourism, Culture and the Arts |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | |System Design Standards |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | |Date: Oct 2008 |

| | |Prepared By: |

| | |Project: CAWS Standards Documentation |

| | |Harvest Package Name: |

| | |Harvest Version: |

| | |Contract: N/A |

Revision History

This section lists the various versions or releases of the document.

|Version |Details/Description |Distribution |Date |Author |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

Contents

Revision History 2

5

5

1. Introduction 6

1.1 Document Purpose 6

1.2 Audience 6

1.3 System Overview 6

1.4 References 7

1.5 Design Methodology 7

1.6 Quality Assurance 7

1.7 System Background 7

1.8 System Objectives 7

1.9 System Constraints 8

1.10 Measures of Success 8

1.11 Guiding Principles 8

1.12 8

2. System Architecture 8

2.1 Architectural Design 8

2.2 Decomposition Description 9

2.3 Design Rationale 9

3. Process Design 9

4. Data Design 9

4.1 High-level Data Interactions 9

4.2 Data Security 9

5. Human Interface Design 9

5.1 Overview 9

5.2 Screens 9

5.3 Reports 9

5.4 Help 9

5.5 Error Messages 9

6. Technical Requirements 9

6.1 Capacity 9

6.2 Software 9

6.3 Hardware 9

6.4 Communication protocols 9

6.5 Interoperability Requirements 9

6.6 Performance 9

6.7 Hardware/Software Interfaces 9

Sign-Off 9

Appendix A. Definitions, Acronyms, and Abbreviations 9

Appendix B. Screen Images 9

Appendix C. Report Layouts 9

Appendix D. Known Issues 9

Introduction

1 Document Purpose

This document describes the system design specifications for the . It describes how the application will be constructed by specifying the components to be used, how they will be organized in relation to each other, and the general principles of the application's internal construction.

This document also serves as a systems reference manual for the running system once it is implemented, and is the primary reference for application migrations, support and maintenance.

2 Audience

The intended audience for the document is technically proficient, but does not necessarily have specific knowledge of the business areas involved.

During application development and implementation, it will be used primarily by:

• Ministry staff responsible for approval of the specifications, presentation standards, intended architecture, security, and deployment context;

• Development staff responsible for developing, documenting, and delivering the application.

After implementation, it will serve as the authoritative description of the application as built, and will be used primarily by operations and maintenance staff.

3 System Overview

Any/all references to “the system” will relate to the contents of this section.

4 References

5 Design Methodology

6 Quality Assurance

7 System Background

8 System Objectives

9 System Constraints

10 Measures of Success

11 Guiding Principles

12

System Architecture

1 Architectural Design

2 Decomposition Description

1 Data Access Model

2 Application Security Model

3 Domain Model

3 Design Rationale

Process Design

Data Design

1 High-level Data Interactions

2 Data Security

Human Interface Design

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download