University of Dayton
School of Business Administration

MIS 385/MBA664
Systems Implementation with Database Management Systems

Team Project

This page was last modified on Monday January 12, 2015


In this team project your team will model an organization's data needs and will design and prototype a database application.  Expectations for quality of design, professionalism, appropriate use of E-R diagramming techniques and complexity will be fairly rigorous. The instructions will apply to each of the cases assigned.  The project will involve the conceptual, logical and physical development of a database system, with a final day for discussion and walk through of each team's efforts.  The specific deliverables are described below (due dates in syllabus). 

Part 1 - Executive Overview
15% of Team Project Mark

Write a 1.5 to 2.5-page description of your team's initial analysis of the business scenario provided as it pertains to designing a database application.  You should communicate clearly what it is you think the system you intend to develop will do in terms of specific functionality that your final system will offer.  Be as detailed as possible.  You may make some reasonable assumptions (in the early phases it is often the case that some things are a little fuzzy), but these must be reasonable and defensible within the context of your case.  Do not take the request for detail as a license to be overly verbose.  Executives tend to be busy people, and more than 2 pages or so will lose them.  

Part 2 - Conceptual Data Model (Entity-Relationship Model)
25% of Team Project Mark

Provide a conceptual data model for your proposed system using an entity-relationship diagram.  Show all relevant entities and the relationships between these entities, including the cardinalities of the relationships and participation requirements (i.e. is participation in a given relationship mandatory?).  Attributes of the entities must be shown using appropriate notation (including any derived, composite, or multi-valued attributes).  Attributes that serve as identifiers must be underlined.  M:N relationships may be resolved into associative entities as appropriate. 

Part 3 - Logical (and Physical) Data Model & Data Dictionary
25% of Team Project Mark

MySQL, prepare a logical data model that reflects the data relationships as they would be implemented in a RDBMS based on your ERD from Part 2.  Your schema should reflect relations normalized to 3NF.  Make sure that primary keys are identified, and include referential integrity constraints and designations of functional dependency (for functional dependency, comment these in the description in the data dictionary).  The data dictionary should define all fields used in the database, including field name, description, synonyms, data type, field size, format, constraints on allowable values (e.g. validation rules or required field settings) and any other field properties such as indexes deemed necessary.   

Part 4 - Application Prototype
35% of Team Project Mark

Obviously this is the most important part of the Team Project.  For this application, you are to create a working relational database prototype.  Your prototype should demonstrate your implementation of the work you have submitted in the earlier parts.  Your application must include at least 75 sample records in the largest table, and an appropriate amount of test data in each of the other tables.  You should demonstrate your command of tables, queries, forms and reports, using whatever features are available to make your prototype as professional-looking and functional as possible.  Be creative and ambitious, because the most functional and most professional-looking will receive the higher marks.  Having said this, temper your creativity with the realization that a modest application that works well is better than a flashy one that crashes.  As part of this assignment, the forms/reports/queries/modules you generate should be either suggested by the needs of the users in your cases, or be inferred from same.  You should also develop your forms and reports in such a way that they are intuitive and easy to use.  Each output report and input form should be created with an eye toward its purpose, recipients, and any user-definable parameters (e.g., data range for the data), any sorting/grouping/totaling used in reports, etc.