Main Course Working Assessment Brief COMP1430-2024-2025 Academic session.

COMP1430 (2024/25) Systems Design and Master CRN: Contribution: 100% Coursework
Term A Development 11476
Module leader Title: Design and Deadline: 27-Nov-2024 by 23:30
Dr Solomon H. Ebenuwa Develop Web base
CRUD system for
event community
park.
Feedback and grades are normally made available within 15 working days of the coursework deadline
Learning Outcomes:
1. Demonstrate understanding of the importance of database normalisation and formulate normalised database
schemas.
2. Employ Structured Query Language to create, populate and manipulate relational database tables.
3. Acquire practical methods, techniques and tools for information modelling, management, and security issues
in relation to the design, development and the use of information systems and apply appropriate modelling
tools in the creation of static and dynamic software and web interface.
4. Analyse scenarios and design appropriate software solutions using industry standard modelling tools and
paradigms.

Plagiarism
Is presenting somebody else’s work as your own. It includes copying information directly from the Web or books
without referencing the material; submitting joint coursework as an individual effort; copying another student’s
coursework; stealing or buying coursework from someone else and submitting it as your own work. Suspected
plagiarism will be investigated and if found to have occurred will be dealt with according to the procedures set
down by the University. All material copied or amended from any source (e.g., internet, books) must be referenced
correctly according to the reference style you are using. Your work will be submitted for electronic plagiarism
checking. Any attempt to bypass our plagiarism detection systems will be treated as a severe Assessment Offence

Coursework Submission Requirements

An electronic copy of your work for this coursework must be fully uploaded by 11:30 PM. on the
Deadline Date of 27-Nov-24 using the link on the coursework Moodle page for COMP1430.
• For this coursework, you must submit a single Acrobat PDF document. One single ZIP file of your
content management system (CMS) must be uploaded on the COMP1430 Moodle page using the
appropriate submission link. Your developed CMS system should be a standalone (you don’t need to
host it on the university server)
• In general, any text in the document must not be an image (i.e. must not be scanned) and would
normally be generated from other documents (e.g. MS Office using "Save As .PDF"). An exception to
this is hand-written mathematical notations, but when scanning, ensure that the file size is not
excessive.
• There are limits on the file size. Please ensure that you meet that.
• Make sure that any files you upload are virus-free and not protected by a password or corrupted
otherwise they will be treated as null submissions.
• Your work will be marked online and comments on your work and a provisional grade will be
available from the Coursework page. The grade will be made available in the portal.
• You must NOT submit or mail any coursework to your or any tutor.

1
• All coursework must be submitted on the COMP1430 Moodle page.
Detailed Specification
This coursework is worth 100% of the total marks for this course. This coursework must be
completed individually. Please read this entire specification very carefully so that you are fully aware
of the requirements.
The University website has details of the current Coursework Regulations, including details of
penalties for late submission, procedures for Extenuating Circumstances, and penalties for
Assessment Offences.
This coursework must be completed individually.
Scenario Overview
Mellodian Community Park Authority is preparing for this year’s Christmas events ticket sale. They
really want to improve their services, particularly in safety. Upon analysing the previous year's events,
it was agreed that the rowdy crowds witnessed last year were because of too many people trying to
buy tickets at the gate, overselling of tickets, and the entrance gate being very close to the ticket
office. This coming year, they intend to ask customers to book and buy tickets online in advance. This
would enable the park authorities to monitor and supervise all events and avoid overselling tickets,
which is foreseen to improve safety.
You have been tasked to create a functional prototype of a web-based application to enable customers
Book and buy a ticket for Christmas events at “Mellodian Community Park”. The park has become
popular among young people and families. There are many activities and events that are attractive to
users of the park, this has made some events oversubscribed by customers. Whilst seating and
relaxing within the park is free, riding or going to some of the attractions is not free. The park has
some state-of-the-art attractions such as Sweeney, a private rail track with old steam engines and
carriages, different types of water sports, an indoor circus theatre and so many others. The evening
Christmas events are scheduled for the last two-week in December. The web application will record
information about:

I. Events.
II. Customers.
III. Event sales.
IV. Prices.
V. Others.

For all events, there are two types of seats: seats without tables and seats with tables. For some
events, there must be at least one adult seat purchased with every sale, to enable the adult to supervise
any children. For such events, a single sale cannot exceed eight tickets and the adult photo must be on
record for any sale for easy identification. The web application should enable the user to register and
log in to purchase a ticket. The admin should be able to log in as an admin user and see all users that
have booked tickets for events. The admin should be able to perform a Create, Read, Update and
Delete (CRUD) operation on any user. As this is a functional prototype, you are free to include any
real functionalities besides the CRUD or others that have been explained in the brief.

2
 Part 1 [Systems Design] [50 Marks]
(a) Using the above scenario produce a demonstration of the process of Normalization to 3 rd
normal form, to identify the entities that could be used to produce a backend database for
Create, Read, Update and Delete (CRUD) application, an appropriate explanation of the
processes is required.

(b) Using the identified entities in (a) produce the physical model of the Entity Relationship
Diagram (ERD). Ensure that the attributes, their values, and all entities’ metadata are
included in the model.

(c) Using the identified entities in (a) produce a Unified Modelling Language (UML) Class
Diagram. The diagram must include the various class names, attributes, data types and
methods. You must indicate if the methods are public or private in your model.

(d) Create and label Use Case diagrams for any activity based on the model from the above
scenario. You must include the main Use Cases and Actors, and the various relationships
between the Use Cases and Actors in the system.

(e) Draw some numbers of User Interface (UI) front-end forms that could be used to collect
data (input) to the backend system database, the UI should accommodate all necessary
interfaces to ensure adequate data inputs. The Interface design should incorporate
adequate security issues to manage the issues and ensure unauthorised access into the
systems.

You are to produce a report that contains all the tasks carried out in parts 1 (a) to (e) should be
captured fully as a screenshot with appropriate annotation and explanations in a word document and
saved in pdf format for submission, please see deliverables.

Part 2 [Systems Development] [50 Marks]

You must build or develop the front and back end of a web-based content management system (CMS)
system required to store and manage information in accordance with the design in part 1, the system
should allow users or clients to register before they could log in using username and password, after
logging in the user should be able to input their details to accommodate the scenario and should not be
able to delete or update his or other users information. The user login details and information should
be stored permanently in the backend database.
The admin login user should be able to see all registered users in a web interface and could perform
the Create, Read, Update and Delete (CRUD) operation on them. The number of web interface pages
to be developed to accommodate the application depends on you. In summary, the developed systems
should do the following among others
(a) Registration of user and admin.
(b) Input user details.
(c) Admin user’s login.
(d) Admin users can access all users’ information.

3
 (e) Admin user able to perform CRUD operations on all users and show that designed security
features are working.
(f) Other as you deemed necessary.

The web-based content management system (CMS) should be developed as a standalone, you are not
required to host it on the university server. The system and particularly the CRUD operations must be
fully tested and evidenced using clear screenshot annotation and explanation.
You are to produce a report that contains all the tasks carried out in part 2 (a) to (e) at least and should
be captured fully as a screenshot with appropriate annotation and explanations in a word document
and saved in pdf format for submission, please see deliverables.
Deliverables
One PDF or word document report submitted by the due date containing the report produced in part 1
and part2. The report should include.
 A cover page.
 Table of Contents
 All tasks in part 1 and part 2
Summary of Documentation of “Part 1 and part 2 – please refer to that part’s details above.
One single ZIP file of your created CRUD application should also be uploaded via Moodle
submission page. Be advised that you may be required to set up and run your applications on
your personal PC. You should therefore make sure that your work is tested well.
The documentation is suitably structured, written in your own words, and develops a clear narrative or
argument using appropriate language. All assertions are expected to be supported by references (using
Greenwich Harvard formatting) or otherwise justified. The discussion should be within 3,000 words
plus or minus 10% not including the title page or any preamble and not including the references.

4
 Marking Scheme Allocation and Rubric.

Coursework: Level 7
0 0-39% Fail 40-49% Fail 50-59% Good 60-69% Very Good 70-79% Excellent 80-100% Exceptional
D1 Knowledge No indication of any Did not Show any Demonstrate good understanding Demonstrate very good Demonstrate excellent Demonstrate exceptional
Demonstrate the knowledge of the meaningful and abilities to interpret the understanding and abilities understanding and abilities to understanding and abilities
knowledge of module shown. No understanding of the context Scenario and proposed to interpret the context interpret the context Scenario to interpret the context
proffering solution by meaningful answer context scenario. Unable some solution, able to Scenario and proposed and proposed excellent Scenario and proposed
system analysis of the provided. work to demonstrate any demonstrate the knowledge of good solution, able to solution, able to demonstrate solution, able to
context scenario and submitted almost empty. requirement elicitation scenario and case study analysis demonstrate the the knowledge of scenario and demonstrate the knowledge
Requirements techniques. Did not in other to use the relevant and knowledge of scenario and case study analysis in other to of scenario and case study
elicitations. demonstrate any correct techniques of case study analysis in use the relevant and correct analysis in other to use the
knowledge and skills in requirements elicitations. Able other to use the relevant techniques of requirements relevant and correct
context. No meaningful to capture some of the and correct techniques of elicitations. Able to capture techniques of requirements
answers provided. All meaningful requirements based requirements elicitations. most of the meaningful elicitations. Able to capture
answers are not correct on context analysis. Some Able to capture most of requirements based on context all meaningful requirements
significant errors. the meaningful analysis. No error based on context analysis.
requirements based on No error
context analysis. Few
errors
D2 Research Did not show any Did not Show any Showed good ability in Showed very good ability Showed an excellent ability in Showed exceptional ability
indication of research for significant ability in understanding and interpreting in understanding and understanding and interpreting in understanding and
Design based on design, no indication of interpreting the context the context scenario by interpreting the context the context scenario by interpreting the context
Requirements- requirements elicitation, scenario. Unable to producing a good design based scenario by producing a producing a comprehensive scenario by producing a
Synthesis the right no meaningful answer produce any meaningful on the case study. Produced comprehensive design design based on the case comprehensive design
solutions are clear provided. work designs based on the some evidence of proof of based on the case study. study. Produced more than based on the case study.
evidence of research submitted almost empty, case study. Did not knowledge and skills in the Produced more than enough evidence of proof of Produced more than enough
into the design demonstrate any interpretation of content case enough evidence of proof knowledge and skills in the evidence of proof of
paradigm and knowledge and skills in study to impact the design. Some of knowledge and skills in interpretation of content case knowledge and skills in the
requirements elicitation context. No meaningful skill in the usage of the tools and the interpretation of study to impact the design. interpretation of content
process based on the answers provided. techniques for system design, content case study to Able to use the proper tools case study to impact the
context. substantia errors. impact the design. and techniques for system design. Able to use the
Adequate skill in the usage design, ability to granulate the proper tools and techniques
of the tools and techniques design to the right levels for system design, ability to
for system design. Take granulate the design to the
the design to some levels right levels
of granularity, few errors

5
D3 Evaluation Did not show any demonstrated very poor demonstrated good demonstrated very good demonstrated an excellent Demonstrated exceptional
indication of interest, no implementation of the implementation in the implementation in the implementation in the implementation in the
Implementation, testing of any kind, no system. Unable to show development of various parts of development of various development of various parts development of various
Evaluation, and testing substantial knowledge of any substantial the system. Showed some parts of the system. of the system. Evidence of parts of the system.
the module shown. No developmental incremental developmental Showed incremental incremental developmental Evidence of incremental
meaningful answer processes. Did not processes. performed some developmental processes. processes with white box developmental processes
provided. performed any white box testing of some part of White box testing of some testing as an iterative process with white box testing as an
significant white box the system. Few final testing part of the system. Some in the development. Multiple iterative process in the
testing of the system. No evaluations of the final products. evidence of summative summative testing and development. Robust
meaningful effort testing and evaluations of evaluations of the final summative testing and
evidenced the final products. products. excellent evidence evaluations of the final
provided products. Clear provisions
of exceptional evidence
D4 Communication Very poor very poor Good documentation having Very Good documentation Excellent documentation Exceptionally excellent
communication did not documentation. Having some of the required pages and having all the required having all the required documentation having all
Documentation, show any interest, very no or few required some usage of the conventional, standard pages and usage standard contents pages and the required standard
Report, and poor usage of English pages. Few usages of technical terminology. Clear of conventional, technical usage of conventional, contents pages etc and
presentations. language. No meaningful terminology, totally screenshot and annotations, terminology. Clear technical terminology. Clear usage of conversional,
Proficiency in the use statement made unclear screenshot and presentations of clear evidence. screenshot and screenshot and annotations, technical terminology.
of English language annotations, evidence some good citation and Harvard annotations, presentations presentations of clear Clear screenshot and
provided is unclear or referencing, Significant omission of clear evidence. good evidence. Excellent citation annotations, Presentations
full of errors Showed no in the evidence provided. Good citation and Harvard and Harvard referencing, few of clear evidence. Excellent
or poor knowledge usage of English language, some referencing, some omissions in the evidence citation and Harvard
referencing. Evidence errors nothing serious. omission in the evidence provided. Excellent referencing, Exceptional
totally omitted. Poor provided. Very good usage proficiency in the used of proficiency in the used of
usage of English of English language, few English language English language
language, sentences are errors nothing serious.
gibberish.
D5 Referencing no meaningful Very poor citation and good citation and proper Very good citation and Excellent citation and proper Exceptional and clean
referencing, work referencing. Did not referencing using Harvard proper referencing. Clear referencing. Clear evidence of citation with the proper
submitted almost empty, demonstrate any referencing style, display some evidence of using Harvard using Harvard referencing referencing. Clear and
no substantial significant knowledge of knowledge of academic writing referencing style, style, documentation shows flawless evidence of using
knowledge of the Harvard referencing standards. Significant number of documentation shows evidence complying with Harvard referencing style,
module shown. Dis not style. The documentation errors. evidence of complying academic writing standards, documentation shows
indicate any knowledge complying with with academic writing very few noticeable errors evidence complying with
of referencing at all. academic writing standards. A few academic writing standards,
standards and full of noticeable errors. no errors
errors.
D6 Employability Very poor soft skills. Poor demonstration soft demonstrate good soft skills, like demonstrate very good demonstrate excellent soft demonstrate exceptional
Did not submit on time, skills, lateness timekeeping, working soft skills, like skills, like timekeeping, soft skills, like timekeeping,
Employability-Soft incomplete or empty submission, poor independently and in group. timekeeping, working working independently and in working independently and
skills, time work. timekeeping. etc Noticeable some lateness etc. independently and in group, complying to all in group, complying to all
management group, complying to all instructions and abilities to instructions and abilities to
independence and instructions and abilities to carryout individual research- carryout individual
ownership carryout individual etc. research-etc.

6
research-etc.

7
 Part 1 System Design
sn Assessment Criteria Mark Mark
Allocated Awarded
a demonstration of the process of Normalization to 3rd 9
normal form, to identify the entities that could be used
to produced backend database for Create, Read, Update
and Delete (CRUD) application,
b produce the physical model of the Entity Relationship 9
Diagram (ERD). Ensure that the attributes, their values,
and all entities metadata are included in the model
c produce a Unified Modelling Language (UML) Class 9
Diagram. The diagram must include the various class
names, attributes, data types and methods. You must
indicate if the methods are public or private in your
model.

d Use Case diagram to model the above scenario. You 9

must include the main Use Cases and Actors. You must
also include the relationships between the main Use
Cases and Actors
e Draw some numbers of User Interface (UI) 9
front-end forms that could be used to collect
data (input) to the backend system database,
the UI should accommodate all necessary
interfaces to ensure adequate data inputs. The
Interface design should incorporate adequate
security issues to manage the issues and
ensure unauthorised access into the systems.

f Documentation and presentation of this part of report,

usage of the English language and the right terminology 5
in context of design.
total 50

Comments:

Part 2: System Development

s Assessment Criteria Mark Mark
n Allocated Awarded
a Registration of user and admin. 9

b Input user details and information. 9

c User and Admin login. 9

d Admin user can access to all user’s information. 9

e Admin user able to perform CRUD operations on all 9

users and show that designed security features are
working.
Documentation and presentation of this part of report,
usage of the English language and the right terminology 5
in the context of the development.

8
 50

Comments:

sn Assessment Criteria Mark Mark

Allocated Awarded
Final total 100

End: