Professional Documents
Culture Documents
1
Topics Covered
• Project Flow Diagram
• Project Policy
• Chapter Submission
• GUIDELINES FOR REPORT
• Chapter:1
• Project Plan
2
Aim of Final Year Project
3
Time Duration
4
Flow Diagram
Start of FYP2
week1 activity
Plan to execute your
project
Complete project
chapters and submit to Complete Weekly Report
your supervisor (after Log
each 2 weeks)
Thesis Submission
5
Project Scope Statement
Final product must have 100 % complete system (must satisfy all
functional and non-functional requirement). Product and their
features or functions according to the defined scope.
6
Project Requirement:
a) Deliverables (chapters, Final report) must meet the schedules.
b) According to the stakeholder's requirements, the final product must be satisfied with
the proposed system's objective and scope.
c) The design or conceptual part must satisfy the system requirements.
d) Students must meet their supervisor once a week (defined schedule of supervisor).
Student in a group cannot entertain individually.
e) Each chapter must submit by the group in two weeks' time. The group must submit
the chapter to the supervisor in the first week; otherwise, the supervisor will not
accept to check the content. Next, the chapter must submit to the project
coordinator with the supervisor's signature by the end of the second week.
f) Coordinator will check the plagiarism and then notify the students.
g) The supervisor can entertain the other groups if the supervisor of that group sends a
request.
h) The supervisor must submit marks of chapters and log report on time.
i) The report is evaluated as a group, but the presentation and Demo are evaluated
individually.
7
Product Acceptance Criteria:
• Copy and outsourcing of the system are not
acceptable.
• Plagiarism is not acceptable.
• Must have proper referencing and format (APA
style).
• 100 %Complete system is acceptable.
• The product is acceptable after the scope
verification process
.
8
• Attendance Policies
• Students are expected to attend the FYP class/training session or meet their
respective supervisor(s) to discuss project status and project difficulties at least
once a week. The supervisor MUST fill in the student meeting form and signed the
document. The attendance will be a part of the continuous assessment (which
carries 5%) from the overall grading. If any group student is outside of Karachi, the
student must contact through Skype/Zoom at-least once a week.
9
Project Calendar
Seq. Activity WEEK
No. Active Role
1. Starting day of project Week1
1. Last day for submitting First Draft Week 14 Students, Supervisor(s), Examiner
10
Chapter Submission
Seq. No.
Chapter Week
1 Chapter1 Week-2
2 Chapter2 Week-4
3 Chapter 3 Week-6
4 Chapter 4 Week-8
5 Chapter 5 Week-10
6 Chapter 6 Week-12
7 Chapter 7 Week 14
11
1.1. Workshop due dates:
Seq. No.
Activity
Week
1. Very Short Guide to Good Writing REPORT Writing Style 2
2. UML Review 4
4. UX Design 10
5. 13
Final Report
12
GUIDELINES FOR REPORT
• The students of FEST are hereby directed to prepare their
final year project 2 reports according to the guidelines
provided in the following points.
• The project report should be hard bound
• The front cover of the report should be in printed form along-
with the university logo. The required print spacing on front
cover page is as follows:
• Top: 1.5 inches Left: 1.5 inches
• Right: 1 inch Bottom: 1 inch
• Note: For the front cover details contact your project
coordinator
13
GUIDELINES FOR REPORT
The font used should be Times New Roman, 12 points plain, with one-and-a-half
(1.5) spacing between two consecutive lines
For sub-headings, increase Two point and for main headings increase Two more
point.
The overall number of pages in the report must be a minimum of 60, Excluding the
appendix
All the pages should be properly numbered – preferably section-wise
The students should get their project reports cross-checked by their advisor before
submitting it to the FYPC. Marks will be deduced from the reports not complying
the prescribed format.
14
Chapter 1: INTRODUCTION
1. Introduction/Background
2. Problem Statement
3. Motivation
4. Project Objective
5. Challenges
6. Structure of the Report
15
Introduction
1. Start broadly and then narrow down
More general
More specific
16
• Genetic Programming based Feature Manipulation
for Skin Cancer Image Classification
• Introduction:
• Computer vision is an interdisciplinary field that deals with how “computers” can be made for
gaining high-level understanding from digital images or videos. From the perspective of
engineering, it seeks to automate tasks that the human visual system can do [28].
17
Problem Statement
18
Problem Statement
• Current techniques vary from applying standard machine learning algorithms to
medical imaging datasets for developing new approaches
adapted for the needs of the field [74]. A key limitation is that the size
of a medical image is often large, whereas the relevant information about
the disease is confined in a limited number of features in such images.
Hence, suitable feature selection and feature construction methods are required to
generate informative image features.
19
Motivations
• The ability of GP techniques to handle complex problems represents a key motivation for many
researchers to utilize it to perform different tasks such as object detection [9, 38, 183, 211, 212,
213], feature selection [10, 107, 131, 136, 198], feature construction
[11, 110, 138, 139, 198], image classification [15, 17, 20, 44, 58, 110, 143, 195],
regression [56, 83] and knowledge transfer [51, 90].
20
Project Objectives
• SMART
– Modelling and prediction of resource utilization for
Hadoop jobs using machine learning
21
Time Management
22
Thank You !