Marking Criteria
1. Content (20%): Detailed and professionally well-written
2. Writing Expression (20%): Well-articulated with logical statements supported by
the scenario and by lecture materials
3. Presentation (30%): see the structure of the BI Project Design Document in the
next page
4. Solutions (20%): Logical and well-explained solution for client
5. Suggestions (10%): Excellent and well-explained suggestion for client
Note to read:
This template only gives you just guidelines on BI project design document layout.
Your submission is not restricted to this template, but must be related to the project
design document. Table of Contents, Headings, List of Figures, Tables, References,
and Appendices are highly recommended in your final submission.
BI Project Design
VERSION HISTORY
• Prepared by – The person(s) preparing project design document;
• Date/Control Number – The date the project design is finalized and the change or
configuration item control number assigned.
• Status/Notes – status of the document such as original or revision.
Table of Contents
1. EXECUTIVE SUMMARY
1.1 Purpose of this document
1.2 Scope of this document
1.3 Summarize the contents of this document
2. PROJECT OVERVIEW
Provide a general description of the BI Project including its goal, functionality
and matters related to the overall system and its design.
3. DESIGN CONSIDERATIONS
Describes issues need to be addressed before attempting to design a complete
solution.
3.1 Design Requirements
3.2 General Constraints – global constraints that impact on overall design
3.3 Development Method – used for the proposed model
3.4 Technical limitations
3.5 Assumptions and Dependencies
4 ARCHITECTURE DESIGN
Describe any design decisions that may affect the overall organization of the
system. It provides a high-level overview of the proposed model. The
architectural design provides information on the decomposition of the
system into modules (entities), dependencies between modules, hierarchy and
partitioning of the modules.
5 DATABASE DESIGN
The database design specifies how the data of the system is going to be stored.
5.1 Design Methodology
Describe any methodologies (logical or physical database design) during
database design.
5.2 Table schema
6 ETL design and Techniques
Describe used tools and techniques (if any) of ETL design for Data cleansing,
managing historic data, ensuring data integrity and implementing business rules.
7 Human-Machine Interface
7.1 Interface Design Rules
7.2 Inputs
7.3 Outputs
7.4 Navigation Hierarchy – screen layouts
8 Design Test Plan
Describe what the data combinations are and define what results are expected.
Decide how many test cases need to be built and include error checks. Also, look
at technical risk and include security.
9 Overall Design Process
• Discuss methodology used in the design phase.
• Design review process that your team used.
10 References
Provides complete citations to all documents and meetings referenced (Harvard
system)
11 APPENDIX
• Requirements Traceability Matrix
• Glossary of Terms – provides definitions, terms, and acronyms.