Professional Documents
Culture Documents
Dcp5521 Fyp Final Report Template Web Tri2210 - Group
Dcp5521 Fyp Final Report Template Web Tri2210 - Group
SESSION 2022/2023
MULTIMEDIA UNIVERSITY
JUNE 2023
ONLINE MANGA
BY
SESSION 2022/2023
MULTIMEDIA UNIVERSITY
JUNE 2023
DCP 5521
Copyright of this report belongs to Universiti Telekom Sdn. Bhd. as qualified by Regulation 7.2 (c) of the
Multimedia University Intellectual Property and Commercialisation Policy. No part of this publication may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of
Universiti Telekom Sdn. Bhd. Due acknowledgement shall always be made of the use of any material contained in,
or derived from, this report.
ACKNOWLEDGEMENT
The Acknowledgements page is where you thank all the people who have helped you
with the project, including your supervisor, if appropriate. You will also need to
acknowledge the contribution of others at different places in the body of the report.
ABSTRACT
It is a very brief but clear description of what the report is all about, summarising your
plan and your progress so far. Keep your abstract to 100 to 150 words or in one page.
LIST OF TABLES
If the table exists in Part 1, it should be referred as Table 1.x where x is an integer
based on the order of appearance.
LIST OF FIGURES
If the figure exists in Part 2, it should be referred as Figure 2.x where x is an integer
based on the order of appearance.
COPYRIGHT i
ACKNOWLEDGEMENT ii
ABSTRACT iii
LIST OF TABLES iv
LIST OF FIGURES v
TABLE OF CONTENTS vi
PART 1: INTRODUCTION 1
1.1 Overview 2
1.2 Project Objectives 3
1.3 Target User 4
1.4 Project Scope 5
1.5 Gantt Chart 2 6
1.6 Division of Work 7
PART 6: CONCLUSION 23
6.1 Conclusion 24
6.2 Further Enhancements 25
PART 7: REFERENCES 27
PART 8: APPENDIX 29
Appendix A: Minutes of Meeting 30
Appendix B: Website Samples/Questionnaire/Forms 30
Part I:
Introduction
1.1 Overview
This section focuses on outcomes of your project. State what you would like to
achieve from the system. The objectives must be measurable and achievable.
1. To reduce …
2. To improve …
3. To increase …
Example:
Target users are people who can interact with your system (e.g: E-Learning:
target user: students, lecturers). However, you may want to narrow down your
target users based on the accessability of your project.
Example:
1. Teenagers
State the reasons why you target teenagers to use your system.
2. Music lovers
State the reasons why you target music lovers to use your system.
Sellers will have the ability to manage and edit product details,
but any changes made after a product has been purchased will not
affect the corresponding order.
A Gantt chart outlines what aspects of the project has been compeleted. The
Gantt chart must show the duration taken from Design phase until delivering
the Final Report/Presentation for the entire project. You can create Gantt chart
in Microsoft Excel, MS Project, SmartDraw or other project management
software.
Division of work is very important make sure every member participates in the
project development. Some of the tasks such as preparing documentation and
background study must be done by all group members. However certain tasks
must be delegated to each group member by the group leader.
TASKS STUDENTS
Ali Chong Kumar
Preparing project proposal X
Overview X X
Objectives X
Target Users X
Project Scope
Gantt chart
Primary Study
Problem Statements
System Features
Hardware/Software Requirements
Data flow diagram & Context Diagram
Entity relationship diagram
Data dictionary
System Interface Design
System Coding
System Testing
Compilation of Final Report
Presentation and Demo
Meeting Minutes
Part II:
Primary Study/
Literature Research
Example
The example above shows how the registration section lists out all the errors
above the form, which then forces the user to scroll and scan down to the rest
of the form to fix the errors. This will be troublesome for longer forms and
frustrating as the user has to scroll up and down to fix each error. It would be
much easier if the errors could be seen next to the form field.
Objective:
To improve the visual design of online manga stores by striking a
balance between simplicity and visual interest.
Problem Statement:
Objective:
To improve the user experience of long-scrolling websites by
providing convenient navigation options.
Problem Statement:
Part III:
System Design
Faculty of Information Science and Technology 12
DCP 5521
List down all features of the proposed system for each type of user.
Example:
● Admin
● Member
This section lists the hardware components (if any), software or any
project. You may also include the price, how and where do you plan to
Example:
and MySQL web based systems. It is free to download and easy to use.
requirement for the user to run your new project. This information
Example:
Browser: The user will need any browser such as Internet Explorer,
This section describes in details the attributes and tables used in developing
the project. This section is for Web-based or Standalone project.
Sample:
Part IV:
System Previews
In this section, show and explain screen shots related to user type: Customer/
Member/Student and etc.
Example:
This is the Students Quiz List for students to select to answer quizzes. Students are
only allowed to this page if the students are one of the students for this subject. Once
directed, students have to just choose the subjects based on the lecturer and click on
Answer button.
In this section, show and explain screen shots related to user type: Admin/ Staff/ Front
Desk/ Lecturer and etc.
Example:
This is all the Quiz that already been created in the system. The quizzes will only
display if the lecturer is one of the lecturers in MMU. There are two sections in this
Quiz List. One is the Private Quiz and Public Quiz. Private Quiz is for lecturers who
decided for their own use and not for sharing. The public quiz is for lecturers who
decided to share the quiz with other lecturers.
Part V:
System Testing
generate and
show
3. customer registration:
Enter valid attributes.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Part VI:
Conclusion
6.1 Conclusion
This chapter should address any future system development. You may suggest
the system features to be included for future enhancements and it could be
based on your system limitations, e.g. SMS notifications were not
incorporated in your system and you can suggest this feature to be included
during future system development.
Part VII:
References
Books:
Anti, J.M. and Ryan, P.V.S., “Civil Engineering Construction”, 3rd Ed.,
Sydney, Angus and Robertson, London, 1967, 631 pages
Journal:
Monograph:
Body, D.M., “Flood Estimation”. Water Res. Board of Australia. No.4, 1959,
41 pages
Thesis:
Marques, J.L.G., “A Study of Anchorage Capacities of Confined Bentbar
Reinforcement”. Ph.D. Thesis, Rice University, Houston Texas May, 1988
Conf.
Lea, F.M., “Cement Research: Retrospect and Prospect” in Proc. 4th
Proceedings: International Symposium on the Chemistry of Cement,
Washington DC, 1960, pg 5-6
Web Page:
Smith, A. B., “Description of the Intel P6 Processor”, Intel Corp.,
http://www.intel.com/pentium/p6/description.htm
Working Paper:
Kuo, C and Sayer, P, “Education of Engineers in Marine Technology”,
presented at the World Conference on Education in Applied Engineering &
Engineering Technology Cologne German, 16-19 April, 1984
Standards:
British Standard Institute, “BS 6000:1972, Guide to the use of BS 6001,
sampling procedures and tables for inspection by attributes”, London, 50
pages
Part VIII:
Appendix
All meeting minutes must be included in the report in the appendix section.
Any website screen shots, questionnaires and forms used as reference to your
project will be included in this section.