Data Requirements and Conceptual Design The goal of the firs t part of your proj ect is to: 1. D efine a domain of your interest 2. Identify a...

profilekhaalm
Home>Homework Answsers>Computer Science homework help
Data Requirements and Conceptual Design
The goal of the firs
t part of your proj
ect is to:
1.
D
efine a domain of your interest
2.
Identify
a collection of sample queries
3.
Formulate data re
quirements for your application
4.
Draw an ER
-
diagram that captures these requirements.
For this part1, you will have an occasion to apply the material of the lectures on
Conceptual Modellin
g
.
In the following, is the description of the single steps in more detail.
D
o
main
of interest
Define a domain of your interest where you can
create
database
and do queries
.
Sample Queries
Spe
cify ten (10) example queries that you think are of interest in the
domain of your
application.
You need criteria to decide what to include into the data requirements and what not. A
good starting point for developing a database is to identify typical que
ries that users
will pose
—
either directly or via applications. These queries will be used to direct the
formulation of data requirements and to check them for completeness. Write up the
queries in plain English. Do not be concerned whether they can actuall
y be expressed
in a query language.
Data Requirements and ER Diagram
In reality, the formulation of requirements and the design of the diagram go hand in
hand. So, do both in parallel.
 
Your application should have a size that makes it nontrivial. As a g
uideline, aim at a
diagram of 15 (entities + relationships). The minimum size should be
•
13 (entities + relationships).
Write up which of your requirements could not be expressed in the diagram and
explain why that was the case.
Presentation
For the l
ecture on
02/03/2016
, each group will be asked to give a presentation with
slides on their work for this part1.
Deliverables
The deliverable will be a document consisting of three parts:
1. A collection of 10 sample queries;
2. A text with data requirements;
3. An ER diagram and a comment identifying the requirements that could not be
captured by the diagram.
    • 10 years ago
    • 10
    Report issue
    Answer(0)
    Bids(0)