Course: ICT

Deadline:

PROJECT GUIDELINE

You need to divide into groups of 3 students and develop the website according to
one of the topics from the list below:
1. Doctor appointment
2. Online courses
3. Restaurant reservation
4. Travel agency
5. Recruitment service
6. Real Estate agency
7. Clothing store
8. Electronics store
9. Delivery service
You will need to submit two documents (one submission per group) in Moodle: a
preliminary report and a final report. No late submissions will be accepted.
Your report needs to be in pdf format. Please use 12 size of the “Times New
Roman” or “Arial” fonts and 2.5 cm in margins. Please refer to
https://owl.purdue.edu for formatting styles.
The report should be original work. Detecting cheating is automatically penalized
as a failure. Plagiarism rules cover all types of cheating work including using
someone concept, design, ideas, part of the text, approaches, source code, etc.

PRELIMINARY REPORT

Assessment: marked 25%

By the end of week 7, students have to submit a preliminary report of approx. (3-5
pages long). This document should be a first draft of your final report. The
preliminary report is a reference for the project's aims, objectives, challenges, and
time plan. The student should describe them by investigating background material
and related work/literature. Project's aims, objectives, and challenges must be
clearly stated and presented. It is also necessary to design a viable work plan,
which might be updated as work progresses.
– Contents in the preliminary report can be reused (and polished)
The preliminary report must include:
1. A brief discussion on project relevance/motivations (why is it worth doing it?)
and its main challenges;
2. Analysis of the existing websites: advantages and disadvantages of existing
products with similar functionality;
3. Technical specifications of the project: description of all the technical solutions
that are going to be used in your project;
4. Background material section: investigating background material and related
work/literature;
5. A detailed timetable and plan for achieving the objectives of the project,
including the milestone of the project.

MILESTONE: MEETING WITH THE TEACHER

Assessment: marked 25%
After the preliminary report, students should identify and experiment with the
theory, tools, and technologies that are needed to achieve the goals of the project.
This step is crucial to acquire confidence in the conceptual and technical
background that is needed to develop the project. In addition, new potential risks
might be identified and the project may have to be updated accordingly.
This milestone is a meeting with the teacher in week 9. During the meeting, the
student should start describing the project as follows:
1. Introduction and aims/challenges of the project.
2. Description of the skills the student has acquired so far to full the project stated
in the preliminary report.
3. A detailed specification and design of the core functionality of the project and a
detailed description of what the project is supposed to provide.
4. A clear description of the progress that has been made towards the project
objectives, discussing the artifacts that have been developed (e.g., a website
design, a partial implementation, views generated by some tool).
5. 60-70% implementation of your product.
6. Plan and work that remains to be done.

Table1. Milestone 1 grading criteria

responsibilities clear division of responsibilities of team 30%
members
acquired skills description of the skills the student has 30%
acquired so far
implementation 60-70% implementation of your product 40%
 PROJECT DEFENSE (FINAL REPORT AND DEMO)

Assessment: marked 100% (together with demo)

During the project defense students demonstrate the final product and graded
according to the criteria in the table 2
7-10 pages of the final report including important code areas, screenshots
Structure of the final report:
1. A brief discussion on project relevance/motivations (why is it worth doing it?)
and its main challenges;
2. Analysis of the existing systems: advantages and disadvantages of existing
products with similar functionality;
3. Differences and advantages of your system (why your product is better than
others?);
4. Technical specifications of the project: description of all the technical solutions
that are used in your project;
5. Background material section: investigating background material and related
work/literature;
6. Product description: a textual description of the main features and functionalities
of your product providing screenshots;
7. Important areas of source code with description. You should explain what each
piece of code does. You should also state what the technical contribution of each
piece of code is;
8. Description of the steps performed during the development of the project
providing screenshots from the process of it development (if no-code development
project);
9. Reflection. Description of the core aspects of your contribution and your own
experience (Each team member);
10. Conclusion. A critical appraisal of the project results (what has been done?)
This discussion should cover aims that were part of the project;
11. Appendices (Optional).
Table 2: Final project grading criteria

Functionality of your Functions, tasks, or activities for the 25

product benefit of the user

Visual Hierarchy of Elements of the product arranged in 10

your product such a way that visitors naturally
turn first to the most important
elements and the elements should not
overlap.
Navigability of your Planning out intuitive navigation on 10
product your product to help users find what
they're looking for. Ideally, a user
should not have to think extensively
about where to click next. Moving
from point A to point B should be as
frictionless as possible.
Consistency of your the overall look and feel of your 10
product product should be similar across
all of your forms. Backgrounds,
color schemes, typefaces, and even
the tone of your writing are all
areas where consistency has a
positive impact on usability and
UX.
Content of your report A clear description of the project 10
aims, objectives and challenges, full
description of all the functionality of
the product
Writing Style & Document is well-formatted. 5
Communication of Scholarly style. Writing is flowing
your report and easy to follow.
Conclusion of the Description of achieved results and 5
report their evaluation
Project demo Present your work in class, Delivery: 15
displays enthusiasm during
presentation, Team is well prepared
Report structure Followed the report structure 10
 The list of useful links

1. https://www.hostinger.com/tutorials/how-to-make-a-website
2. https://www.hostinger.com/tutorials/best-website-builder
3. https://www.websitebuilderexpert.com/website-builders/free/
4. https://medium.com/@Scofield_Idehen/how-to-create-a-website-for-
beginners-5ab256760d4b
5. https://tilda.education/video/
6. https://www.wix.com/learn/library/tutorials