Database application development, Database Management System

The database application project (DAP) for this assignment consists of the creation of a fully functional Microsoft Access database application for a real client. I recommend you select a potential client organization with which you have some familiarity, e.g. a bowling league, a small business, or a club. The application should not be complex. The final Access database application prototype must meet the following minimum criteria:

Tables: 

1.  A minimum of 5 tables, including intersection tables where necessary;

2.  Tables must have enough data (minimum of 8 records each) to fully demonstrate the functionalities of your database application (You may need to add some records to the baseline template);

3.  At least four table relationships, all of which must have referential integrity enforced.

 Queries:

1.  At least five queries (total) appropriate to the database requirements;

2.  Of these five, at least one query must prompt the user for input (i.e., parameter query) and use the input in the criteria for the query;

3.  Of these five, at least one query must use an aggregate function to calculate a summary statistic for an appropriate field in a table.

4.  Of these five, at least one query must retrieve data from multiple tables.

Forms:

1.  All the necessary forms for inputting and displaying the data in your database as required by your client. One form per table for data entry

2.  At least one form displaying data from a minimum of two tables. Reports:

1.  At least four reports (total) for data output;

2.  Of these four, at least two reports should be based on a multiple-table query.

3.  At least one report should display grouped data.

Menu:

1.  Provide a user interface to access the features of the prototype. See User Interface handouts.

Milestone 1: Write a memo to me describing your client, an initial analysis of the organization's problem, and what business process will be automated.

Milestone 2:

List of Interview questions

Milestone 3

Interview client

Milestone 4:

Draft of Requirements Analysis section

Milestone 5: 

Draft of Database Design section

Milestone 6:

Prototype Testing

Milestone 7

Draft of Implementation, Conclusions, and Lessons Learned sections

Milestone 8:  

Final Database Application Project Report and Database

Posted Date: 3/2/2013 12:15:38 AM | Location : United States







Related Discussions:- Database application development, Assignment Help, Ask Question on Database application development, Get Answer, Expert's Help, Database application development Discussions

Write discussion on Database application development
Your posts are moderated
Related Questions
Problem 1. Write the SQL queries using Data Manipulation Language (DML) statements. Insert values into student table with field names using insert command Display the

A file of employee have 10,000 blocks on a cylinder of a disk with characteristics r=8ms and btt=0.6ms I want to know the cost of read inthe file under following conditions for a q

The Proliferation of Object-Oriented Methods The first few years of the 1990s saw blossoming of around fifty various object oriented methods. This proliferation is a sign of g

Data Redundancy -A lot of information is being repeated in the relation. For instance, the information that MCS-014 is named SSAD is repetitive, address of Rahul is "D- 27, Main ro

What are shortcomings in structured approach? Structured methodology treats data and their behaviours separately, and this makes it harder to isolate changes. If changes are re

What are metrics for choosing the best algorithm? Matrices for choosing the best algorithms are as below: Computational complexity Ease of understand ability and im

Analyzing Association Traversal Till now, we have supposed that associations are bi-directional. But in the case of traversal, it is in only one direction in any application,

Extend your CREATE TABLE statement from problem 3 with referential integrity constraints. Updates and deletes on related rows are restricted. 6. From examination of the sample data


Conversion of entity sets: I)   For  every  strong  entity  type  E  in  the  ER  diagram,  we  make  a  relation  R containing all the easy attributes of E. The relation R pri