Documente Academic
Documente Profesional
Documente Cultură
19-11-2011
Page 1
LLD
19-11-2011
Page 2
LLD
Table of Contents
1.
Executive Summary 1.1 1.2 1.3 1.4 1.5 Document Objective Document Scope Target Audience Functional Overview Document Organization
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
2.
Presentation Layer 2.1 Screens 2.1.1 Screen 1 2.2 Reports 2.2.1 Report 1
3. 4. 5.
Business Layer Database Layer Other Design Considerations 5.1 5.2 5.3 5.4 5.5 Backup and Recovery Design Security Architecture System Interfaces Performance and Response Time Considerations Other Modules
19-11-2011
Page 3
LLD
Executive Summary
Document Objective Document Scope Target Audience Functional Overview Document Organization
Presentation Layer
This section describes all the screens and reports needed to deliver all the functional requirements. Include screen descriptions, field level description, report descriptions and report fields. Screens Screen 1 Purpose of the screen Flow of Events Basic flow Alternative flows Pre-conditions Post-conditions Access level Input and output fields with description and business rule Field Description Business Rule
Reports Report 1 Describe the purpose of the report and access level List of fields in the detailed as well summary sections of the report.
Business Layer
Define all of the objects necessary to support the presentation layer. Please add the following diagrams here; a. A Static structure diagram or a class diagram. b. A Sequence Diagram
Database Layer
Define all of the tables/columns/views/stored procedures necessary to support the business layer along with an Entity-To-Relationship diagram.
LLD Security Architecture Describe how security will be enforced and at what level (or groups). If using NT, address the NT security model, IIS security, Secure Socket Layers, etc. if applicable. System Interfaces Describe how we will feed or receive feeds from other systems. This may be via replication, BCP, SQL Loader, etc. Describe the data that will flow between the systems, how often it will be updated, and who the system owners for each system are. Performance and Response Time Considerations Explain how we will design for maximum response time. This includes the use of Stored Procedures, de-normalized data (if applicable), server configuration (size, memory, etc), programming techniques, and the use of database tools such as Oracles Explain Plan and SQL Servers Show Plan. Other Modules Describe any other miscellaneous programs.
19-11-2011
Page 5