CIS020-2: Individual Coursework Assignment –1 Brief
CASE STUDY
You are individually required to develop and implement a database system for an application area in which you have experience and/or are familiar with/have an interest in. For example, it could be a booking type application or an order processing type system. Other examples include a system to book tickets for a theatre, a flight or a system to allow customers to hire or buy books, tools,a system to hire/buy cars and so forth. The scenario and the produced database system [up to 25 marks] will be judged by the tutors using the following criteria.
Example of minimum functionality:
??Browse product by category [up to 10 marks]
??Search product by a free-text keyword [up to 10 marks]
??Advanced product search [up to 10 marks]
??Product stock availability Check [up to 10 marks]
??Order one or more product(s) [up to 10 marks]
??Customer registration including validation checks [up to 10 marks]
??Product stock reduction on order [up to 10 marks]
??Order confirmation issuing a system generated unique number [up to 10 marks]
??Ability to cancel and/or amend order details [up to 10 marks]
??Add and update product stocks as an administrator [up to 10 marks]
The system element pass requires 40 marks
METHOD OF IMPLEMENTATION:
You may use back/front end environments of your choice to develop your system, as long as it is relevant/desirable to industry. Oracle APEX is advised as there are tutorial materials available on breo
Follow these STEPS carefully!
You are required to:
1. Identify what is required and produce a selection of relevant models using a mixture of SSM and UML
2. Produce an Entity Relationship Model (ERM)
3. Use the normalisation process to refine your ERM
4. Develop and implement the back-end of your DB system using suitable industry relevant platform
5. Implement the front-end of your DB system using suitable industry relevant platform
6. Demonstrate the DB system within a written report and how your system meets the minimum requirements.
7. Include example SQL code to demonstrate creating the relevant tables and querying the database. Extra marks will be awarded for a query which joins two or more tables. This SQL code should be included in the report and be in SQL*Plus format.
8. Provide documentation for the DB system including:
??User Documentation: this should provide instruction and reference to users as to the operation of the system.
??Documentation: this should provide sufficient information for maintenance andenhancement. It should also provide an overview of the system structure, code details and screen dumps.
??A copy of the whole DB system in a CD.
Deliverables
– Written report submission (70%)
o Submit report
o Submit a CD along with a hard printed copy of your individual assignment/ Alternatively, you can submit the zipped folder containing your system to a link online.
o Ensure an assignment top sheet is included at the start of both electronic and hard copies.
Full Documentation (70%): A paper-based report to serve as the documentation covering all
steps (1-7 inclusive). Any submission after the deadline will be treated as a latesubmission. Late submissions not approved by CAAS will receive a Fail grade.
An example structure for your written report may be as follows:
– An introduction/abstract describing the contents of the whole document and what the purpose of it is.
– A plan of work (perhaps in tabular form and/or a Gantt chart showing planned activity and a timescale and amount of effort that will be expended for these activities over the whole project.
– A textual description of your scenario
– Modelling of your scenario including a full Entity Relationship model, Soft Systems Methodology modelling and UML modelling.
– Step by step Normalisation of the ER model
– A final fully Normalised ER model
– Presentation of the database system developed from the ER model including implemented schema and presentation of the user interface
– Clear presentation of how the system meets the minimum requirements (as stated in the assignment brief above)
– Full user documentation for the system
– Documentation for maintenance of the system and enhancement if necessary
– A conclusion summarising the work presented in this document.
– An Appendix section including an overview of the system structure, code details and screen dumps.
The document should be no more than 20 pages in total length (excluding references and Appendices).
Pay very special attention to fomat your document consistently, and make sure that font sizes and styles are consistent, headings are consistent and the whole document is clearly structured and presented.
The System Itself (30%):
This will be assessed through your supporting report documents and the fully working system submitted on a CD/zipped folder as part of the full documentation submission. The more functions the better.
Marking Scheme – Individual Assignment 1 all parts
GP 14-16: An excellently detailed but concise individual report, providing a very clear introduction/abstract and plan of work, very clearly describing the problem scenario. A sufficiently complex scenario including SSM, UML and excellent Entity Relationship (ER) modelling of the conceptual schema which very clearly reflects the textual scenario presented earlier. The Normalisation process is carried out in a very logical and clear manner, very clearly and logically showing 1NF, 2NF and 3NF in logical steps. A final Normalised ER model clearly shows the logically presented tables including accurate optionality and all cardinality for all entities and relationships. Excellent SQL code for creating tables and querying database is included. Very clear and well thought out system functionality showing how all of the minimum requirements have been met as outlined in the assignment brief. The document also presents very clear and concise but detailed full user documentation for the user’s benefit.
GP 11-13: A detailed and concise individual report, providing a clear introduction/abstract and plan of work describing the problem scenario. A sufficiently complex scenario including SSM, UML and good Entity Relationship (ER) modelling of the conceptual schema which clearly reflects the textual scenario presented earlier. The Normalisation process is carried out in a logical and clear manner, clearly showing 1NF, 2NF and 3NF in logical steps. A final Normalised ER model clearly shows the logically presented tables including optionality and all cardinality for all entities and relationships. Good SQL code for creating tables and querying database is included. Clear and well thought out system functionality clearly shows how the minimum requirements have been met as outlined in the assignment brief. The document also clearly presents user documentation for the user’s benefit.
GP 8-10: A good individual report, providing an introduction/abstract and plan of work describing the problem scenario. A reasonable scenario including SSM, UML and Entity Relationship (ER) modelling of the conceptual schema which reflects the textual scenario presented earlier. The Normalisation process is carried out in a logical manner, showing 1NF, 2NF and 3NF in logical steps. A final Normalised ER model shows the resulting tables including some optionality and cardinality for entities and relationships. System functionality shows how the minimum requirements have been met as outlined in the assignment brief. SQL code for creating tables and querying database is included. The document also presents user documentation for the user’s benefit.
GP 5-7: An adequate individual report, providing an introduction/abstract and plan of work and covering the problem scenario. A scenario including SSM, UML and Entity Relationship (ER) modelling which to some extent reflects the textual scenario presented earlier. The Normalisation process is carried out, showing a progression through the logical steps of normalisation. Some optionality and cardinality for entities and relationships may also be included. SQL code for creating tables and querying database is included. System functionality shows how a selection of the minimum requirements have been met as outlined in the assignment brief.
GP 4: An inadequate individual report, providing a poor introduction/abstract and not covering the problem scenario adequately. The scenario SSM, UML and Entity Relationship (ER) modelling does not sufficiently reflect the textual scenario presented earlier. The Normalisation process is not carried out to an adequate level, and does not show a clear logical progression through the steps of normalisation. Optionality and cardinality for entities and relationships may also be included but are in the majority of cases inaccurate. System functionality does not show how a reasonable selection of the minimum requirements have been met as outlined in the assignment brief.
