CaseStudy:Designing Memento databases:Photographic equipment: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Case Study: An initial photographic equipment database = ; Introduction : In this study, we set out to create a barebones design & implementation of a database for a photogr...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
= Case Study: An initial photographic equipment database = | = Case Study: An initial photographic equipment database = | ||
In this study, we set out to create a barebones design & implementation of a database for a photographic equipment inventory for an amateur photographer or for a solo or very small professional photographic enterprise.<br/>Our idea is to design a barebones but extensible database that will initially consist of a single library and will be able to grow to support several interrelated, linked libraries. | |||
== Nomenclature == | |||
Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology values from other [[Glossary#DBMS]] disciplines, notably relational DBMSes (or RDBMSes). The following table shows the equivalencies: | |||
{| class="wikitable" | {| class="wikitable" | ||
! Memento !! Relational !! Definition | ! Memento !! Relational !! Definition | ||
| Line 25: | Line 25: | ||
| The means by which libraries or tables are related to each other | | The means by which libraries or tables are related to each other | ||
|} | |} | ||
;Requirements (the need): | ;Requirements (the need): | ||
:;Intro: | :;Intro: | ||
| Line 34: | Line 35: | ||
:;Implementation: | :;Implementation: | ||
::;Intro: | ::;Intro: | ||
'''''The email''''' | '''''The email''''' | ||