Database Project Report: Design, Implementation, and Analysis

This database project report provides a comprehensive overview of the database project, encompassing requirements, design, and implementation details. The report's structure includes sections on the narrative, SQL coding standards, and a post-mortem analysis. The report includes an executive summary, clear project scope, and a detailed explanation of functional requirements. The report also covers the creation of ER diagrams, including attribute selection, and domain specifications. It also includes physical modeling, including data types and sizes, index selection, and transaction management. The report also covers application planning, including menus, reports, and environments for development, testing, and production. The report is designed to provide a detailed blueprint of database design and implementation.

DB Project Report Scorecard;
Outline of deliverables/criteria (with guidance for grade estimation):
1. Report text, (0-50)
Include in a zipped folder with relevant source/ files representing design and implementation information
1.1 Narrative, including executive summary
1.2 Project organization [consistent and clear]- team member roles explicitly defined and assigned
1.3 Scope [precise, concept of operation type with features]
1.4 Functional Requirements with scenarios
1.5 Future opportunities/alternatives and [current] project plans
1.6 Body of the report (see sections 2-6 below- each to be graded)
1.7 SQL Coding Standard (team guidelines- style manual)
1.8 Post Mortem – lessons learned incl. comparative analysis (Oracle/Java vs. SQL Server/C#(VB)
1.9 References; extra
1.10 Presentation .ppt completed
2 Questions/SQL or T-SQL queries PERTINENT AND TESTED (0-50)
2.1 Questions (minimum 10 queries): important, clear, non-trivial, and representative, comprehensive set
covering DB scope [in case of individual students in a team, scope fits meaningful portion/business
function/task]
2.2 T-SQL and SQL, PL/SQL queries written in consistent style, and tested for syntax, semantics and speed-
EXPLAIN plan, optimized [statistical etc.] if relevant, reports formatted and printed in a professional format;
sufficient test data prepared/generated for validity…
3. Logical Model(s) with related details (0-80)
3.1 ER Diagram, professional presence [standard ID text block, visual conventions, sizes etc.]
3.2 Attribute set rich, and names carefully chosen;
3.3. Standardized domains/independent attributes, with example sets of data values
3.4 Definitions, descriptions systematic, standardized ‘standardized’, based on use of a template checklists etc.
3.5 Referential integrity options, rationale specified within relationship definition/description
3.6 Extensive use of Erwin features and reports with primary key, alternate keys, secondary keys (IEs) etc.
3.7 Other including views, stored displays, subsystems-models, generalized templates [as app. domain and
independent design patterns], business rules for program logic etc.
4. Physical Model-Database with related details (0-80)
4.1 Data types and sizes carefully selected using independent attributes [domains] and volumetric calculated
4.2 Indexes and ‘file’ organization selected, encryption and compression evaluated
4.3 Lists of values (LOV) selected [for example: logical only entities, for physical LOV implementation!]
4.4 Transaction (isolation levels), Logical Access paths analysis, de-normalization suggested, plus physical
schema modifications and related integrity triggers etc.
4.5 specific design features, innovative solutions/capture of implied and unstated but desirable requirements
including in particular security concerns including access rights, encryption etc.
4.6. View Materialization if any, and other concerns, including an assessment of future architectural changes
[potential] , robustness, scale ability, distribution etc.
5. Application Planning (0-40)
5.1 menus, reports, transactions/data entry – updates etc.
5.2 environments [development, testing, production], security, DBA aspects, backups, etc.
5.3 GUI design layouts etc.
1