Candidate: Experience in database design.
The successful candidate will be given access to an inventory management software to analyse and from there create the following:
1st - Database design is connected with application design.
The requirements and the collection analysis phase produce both data requirements and functional requirements. The data requirements are used as a source of database design. The data requirements should be specified in as detailed and complete form as possible.
2nd - Conceptual Design
Once all the requirements have been collected and analyzed, the next step is to create a conceptual shema for the database, using a high level conceptual data model. This phase is called conceptual design.
The result of this phase is an Entity-Relationship (ER) diagram or UML class diagram. It is a high-level data model of the specific application area. It describes how different entities (objects, items) are related to each other
3rd - Logical Design
The result of the logical design phase (or data model mapping phase) is a set of relation shcemas. The ER diagram or class diagram is the basis for these relation schemas.
4th - Normalization
Normalization is the last part of the logical design. The goal of normalization is to eliminate redundancy and potential update anomalies.
Redundancy means that the same data is saved more than once in a database. Update anomaly is a consequence of redundancy. If a piece of data is saved in more than one place, the same data must be updated in more than one place.
Designs Conceptual, Logical and Physical data models for scalability/flexibility/Extensibility.
Performs Data analysis/Profiling to evaluate data and underlying data structures.
Documents and publishes the data dictionaries/Metadata, data models to ensure their correct implementation