HIGH LEVEL DESIGNRevision: 1.0 Version Date: 2015/07/09Contents1
Introduction31.1Why this High Level Design Document?31.2.
Scope31.3. Definitions31.4. Overview32. General Description42.1.
Product Perspective42.2. Tools used42.3. General Constraints42.4.
Assumptions42.5. Special Design aspects43. Design Details43.1. Main
Design Features43.2. Application Architecture43.3. Technology
Architecture43.3.1. Web Application Architecture43.3.2.
Presentation Layer43.3.3. Data Access Layer43.3.4. Tools Used43.4.
Standards43.5. Database design43.6. Files43.7. User Interface43.8.
Reports43.9. Error Handling43.10. Interfaces43.11. Help43.12.
Performance43.13. Security53.14. Reliability53.15.
Maintainability53.16. Portability53.17. Reusability53.18.
Application compatibility53.19. Resource utilization53.20. Major
Classes5
1 Introduction1.1 Why this High Level Design Document?The
purpose of this High Level Design (HLD) Document is to add the
necessary detail to the current project description to represent a
suitable model for coding. This document is also intended to help
detect contradictions prior to coding, and can be used as a
reference manual for how the modules interact at a high level.1.2.
Scope The HLD documentation presents the structure of the system,
such as the database architecture, application architecture
(layers), application flow (Navigation), and technology
architecture. This uses non-technical to mildly-technical terms
which should be understandable to the administrators of the
system.1.3. Definitions 1.4. OverviewThe HLD will: Present all of
the design aspects and define them in detail Describe the user
interface being implemented Describe the hardware and software
interfaces Describe the performance requirements Include design
features and the architecture of the project List and describe the
non-functional attributes like: Security o reliability
Maintainability Portability Reusability Application compatibility
Resource utilization Serviceability2. General Description2.1.
Product Perspective 2.2. Tools used 2.3. General Constraints 2.4.
Assumptions 2.5. Special Design aspects3. Design Details3.1. Main
Design Features 3.2. Application Architecture 3.3. Technology
Architecture 3.3.1. Web Application Architecture 3.3.2.
Presentation Layer 3.3.3. Data Access Layer 3.3.4. Tools Used 3.4.
Standards 3.5. Database design 3.6. Files 3.7. User Interface 3.8.
Reports 3.9. Error Handling 3.10. Interfaces 3.11. Help 3.12.
Performance 3.13. Security 3.14. Reliability 3.15. Maintainability
3.16. Portability 3.17. Reusability 3.18. Application compatibility
3.19. Resource utilization 3.20. Major Classes3
