Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Relational Databases, Modelling and Translation Example, Derived Attributes and Views, Object Diagram Test Case, Dr Mohammad Yamin, Ms Zoe Brain, Lecture Slides, Relational Databases, Australian National University, Australia.
Typology: Slides
1 / 35
This page cannot be seen from the preview
Don't miss anything!
Lecture 10: Modelling and Translation Example
Assignment 1 last year described a business problem and asked for a database design and queries to solve it. Today we work through the process of producing a complete solution.
See Assignment 1 from last year. http://cs.anu.edu.au/students/comp2400.2007/assignm it is based on a real business operating in Canberra (where Greg worked before discovering Australia Post)
See Assignment 1 from last year. http://cs.anu.edu.au/students/comp2400.2007/assignm it is based on a real business operating in Canberra (where Greg worked before discovering Australia Post) Greg also has the benefit of having seen many attempted solutions, some of which were very good Your first assignment will be similar, and is coming soon
Many problems resulted from people not reading what was asked.
Many problems resulted from people not reading what was asked.
Problem statements, and other relevant documents are a good starting point for modelling. nouns tell you the classes, eg product, order (unless there is only one instance, eg warehouse) underlining the nouns can be a good way to start
Many problems resulted from people not reading what was asked.
Problem statements, and other relevant documents are a good starting point for modelling. nouns tell you the classes, eg product, order (unless there is only one instance, eg warehouse) underlining the nouns can be a good way to start same thing will be described in different ways
Many problems resulted from people not reading what was asked.
Problem statements, and other relevant documents are a good starting point for modelling. nouns tell you the classes, eg product, order (unless there is only one instance, eg warehouse) underlining the nouns can be a good way to start same thing will be described in different ways choose good names (short, obvious, descriptive) look for properies of these things (attributes), and relationships between them (associations)
You don’t need to model everything mentioned in the document, you just need to solve the problem! models can easily grow out of control
You don’t need to model everything mentioned in the document, you just need to solve the problem! models can easily grow out of control get clear on the purpose of the model, and leave everything else out! (however, some allowance for future needs can be prudent)
You don’t need to model everything mentioned in the document, you just need to solve the problem! models can easily grow out of control get clear on the purpose of the model, and leave everything else out! (however, some allowance for future needs can be prudent) the specific requirements statements tell you what you must be able to produce
You don’t need to model everything mentioned in the document, you just need to solve the problem! models can easily grow out of control get clear on the purpose of the model, and leave everything else out! (however, some allowance for future needs can be prudent) the specific requirements statements tell you what you must be able to produce you can mentally “query” or navigate a UML class diagram, and see what’s missing do we need to model customers here?
You don’t need to model everything mentioned in the document, you just need to solve the problem! models can easily grow out of control get clear on the purpose of the model, and leave everything else out! (however, some allowance for future needs can be prudent) the specific requirements statements tell you what you must be able to produce you can mentally “query” or navigate a UML class diagram, and see what’s missing do we need to model customers here? no!
How should we model envelopes and boxes? a Packaging class?
How should we model envelopes and boxes? a Packaging class? an attribute of an Order class?
