This assignment contributes 60% to your final module mark.
The following learning outcomes will be assessed:
1. Critical awareness of the current usage of database information systems for a variety of web based business solutions.
3. The ability to use database management systems and associated technologies in information and database systems development.
4. Ability to design, specify and implement a web based business information system using appropriate methodologies, tools and languages.
You are required to submit your work within the bounds of the University Infringement of Assessment Regulations (see your Programme Guide). Plagiarism, paraphrasing and downloading large amounts of information from external sources, will not be tolerated and will be dealt with severely. Although you should make full use of any source material, which would normally be an occasional sentence and/or paragraph (referenced) followed by your own critical analysis/evaluation. You will receive no marks for work that is not your own. Your work may be subject to checks for originality which can include use of an electronic plagiarism detection service. Where you are asked to submit an individual piece of work, the work must be entirely your own. The safety of your assessments is your responsibility. You must not permit another student access to your work. Where referencing is required, unless otherwise stated, the Harvard referencing system must be used (see your Programme Guide). Please ensure that you retain a duplicate of your assignment. We are required to send samples of student work to the external examiners for moderation purposes. It will also safeguard in the unlikely event of your work going astray.
Using the Oracle 11g Relational Database Management System, and PHP, you are required to design and develop a prototype web information system that satisfies the requirements below. To achieve this you must:
a.) Using an Entity-Relationship (E-R) Diagram, produce a design of the proposed system, correctly showing labelled relationships with optionality and cardinality constraints clearly indicated. You do not need to show attributes on the diagram, only entity names. Ensure that you state clearly any assumptions that you have made in creating your Entity-Relationship Diagram.
b.) Using a flowchart, create a design for the functionality described in part (e) below (i.e. you do not need to model the entire system) which clearly shows the functionality of your web information system and how the various PHP pages would interact, and how users would navigate between the screens. In your flowchart clearly annotate it by showing the filename of the PHP script file for each function A-D described in part (e) below.
It is strongly recommended that you check your design from task (a) and task (b) above with the module leader or your local tutor before moving on to the next task. c.) Using a data dictionary, specify a set of tables and appropriate attributes for your design from part (a) above. For each table, your data dictionary must specify: a.) table name; b.) for each attribute, its name, description, data type; c.) primary key and any foreign keys (indicating which table the foreign key relates to); d.) any further constraints on individual attributes. Ensure that each table is fully normalised to 3NF. To do this you must specify the functional dependencies and primary key for each table and provide a statement as to why each table is in 3NF, clearly resolving any tables which are not in 3NF.