Description
The First Aid Brigade (FAB) is a non-profit, UN funded organization that has the unique authority, under international humanitarian law, to protect lives and provides aid to victims of wars, epidemics or natural disasters. To date, it has lead and organizes, in close cooperation with national societies in various countries, over 1800 relief assistance missions responding to large scale human crisis.
Due to the rapid expansion of the scope and size of its operations, there is an urgent need to re-look at how data is being tracked and maintained. The Director of IT services has appointed you to examine and analyze its current data needs / usages, and revamp its data model, which is to be used in its implementation of a new database a few months from now.
- The bulk of FAB's human resources comes from big-hearted volunteers from all over the world. These individuals volunteer their time to carry out the tasks of the organization. For each volunteer, their name, address, and telephone number are tracked.
Each volunteer may be assigned to several tasks during the time that they are doing volunteer work, and some tasks require many volunteers. It is possible for a volunteer to be in the system without having been assigned a task yet. It is possible to have tasks that no one has been assigned.
When a volunteer is assigned to a task, the system should track the location (i.e. Country, City, State, Address, etc) as well as the start time and end time of that assignment.
- For each task, there is a task code, task description, task type, and a task status. For example, there may be a task with:
- task code "101", with a description of "answer the help-lines," a type of "recurring," and a status of "ongoing."
OR, there could be another task with
- a task code of "102," a description of "prepare 5000 packages of basic medical supplies," a type of "packing," and a status of "open."
- For all tasks of type "packing," there is a packing list that specifies the contents of the packages. There are many different packing lists to produce different packages, such as:
- water purification packages,
- shelter/clothing packages,
- basic medical packages,
- child care packages,
- food packages, etc.
Each packing list has a packing list ID number, packing list name, and a packing list description, which describes the items that ideally go into making that type of package. Every packing task is associated with only one packing list. A packing list may not be associated with any tasks or may be associated with many tasks. Tasks that are not packing tasks are not associated with any packing list.
- Packing tasks result in the creation of packages. Each individual package of supplies that is produced by the organization is tracked. Each package is assigned an ID number. The date the package was created and total weight of the package is recorded.
A given package is associated with only one task. Some tasks (e.g., "answer the phones") will not have produced any packages, while other tasks (e.g., "prepare 5000 packages of basic medical supplies") will be associated with many packages.
- The packing list describes the ideal contents of each package, but it is not always possible to include the ideal number of each item. Therefore, the actual items included in each package should be tracked. A package can contain many different items, and a given item can be used in many different packages.
- For each item that the organization provides, there is an item ID number, item description, item value, and item quantity on hand stored in the system. Along with tracking the actual items that are placed in each package, the quantity of each item placed in the package must be tracked too.
For example, a packing list may state that basic medical packages should include 100 bandages, 4 bottles of iodine, and 4 bottles of hydrogen peroxide. However, because of the limited supply of items, a given package may include only 10 bandages, 1 bottle of iodine, and no hydrogen peroxide.
The fact that this package includes bandages and iodine needs to be recorded along with the quantity of each that is included. It is possible for the organization to have items donated that have not been included in any package yet, but every package will contain at least one item.
Task
1) You are to write all applicable business rules necessary to establish entities, relationships, optionalities, connectivities, cardinalities and constraints. If a many-to-many relationship is involved, state the business rules regarding the bridging entities after breaking down the many-to-many relationship. An example business rules format can be found in Appendix A of this document.
2) Based on these business rules, draw a fully labeled and implementable Entity-Relationship Diagram (ERD). Include all entities, relationships, optionalities, connectivities, cardinalities and constraints. You must use Crow's foot notation and MS Visio to create the ERD. A Hand-drawn ERD will NOT be accepted. A sample ERD can be found in Appendix A of this document.
3) A data dictionary is to be created to provide the details related data type, data domain, constraints, primary keys, and foreign keys. The data dictionary needs to be presented in a table format as shown Appendix B of this document.
4) Use MS ACCESS to implement the database as specified in the data dictionary. Include validation rules, input masks and indexes where appropriate. You need to input some text data in the database. Include appropriate testing data to illustrate the relationships of constraints.
5) A summary to describe the major justifications, assumptions and limitations related to your database design. For example: assumption / justifications for optionalitiy, connectivities, constraints data type and data domain; and special cases or data integrity issues that cannot be handled.
Attachment:- Instructions.rar