USA: +1(669)289-8683 
Sign in
Graduation project Application
Table of Contents
S.No
4
Item
Page Number
1
Acknowledgements
5
2
Introduction
5
3
Course Learning Outcomes
5
4
Student Outcomes
6
5
Overview
7
6
Assigning Students to Supervisors and Projects
7
7
Project Supervision
8
8
Project Evaluation
9
9
Deliverables
15
10
Appendices
17
1. Introduction
The Graduation Project (GP) provides the opportunity to the students to showcase the talents
through their learned skills and practices. The project is mandatory for all the students enrolled in
the programmes. As such, students should regard their graduate projects as an ideal opportunity to
implement the concept learned in most of the courses and gain hand on experience.
2. Course Learning Outcomes
i
ii
iii
iv
v
Ȉ Solid understanding of the theory and concepts underlying computer and
information sciences.
Ȉ Find and integrate the needed resources for a given/chosen problem.
Ȉ Understanding the problem more deepy by performing extensive
literature analysis.
Ȉ Analyse, design, and implement a solution by considering the software
engineering life cycles and best practices of software project
management.
Ȉ Demonstrate the outcomes of the graduation project by means of oral
and written skills.
3. Student Outcomes
a. An ability to apply knowledge of computing and mathemat ǯ
student outcomes and to the discipline[CS&IT].
b. An ability to analyze a problem, and identify and define the computing requirements
appropriate to its solution[CS&IT].
c. An ability to design, implement, and evaluate a computer-based system, process, component,
or program to meet desired needs[CS&IT].
d. An ability to function effectively on teams to accomplish a common goal[CS&IT].
e. An understanding of professional, ethical, legal, security and social issues and
responsibilities[CS&IT].
f. An ability to communicate effectively with a range of audiences[CS&IT].
g. An ability to analyze the local and global impact of computing on individuals, organizations,
and society[CS&IT].
h. Recognition of the need for and an ability to engage in continuing professional
development[CS&IT].
5
i.
An ability to use current techniques, skills, and tools necessary for computing
practice[CS&IT].
j.
An ability to apply mathematical foundations, algorithmic principles, and computer science theory
in the modeling and design of computer-based systems in a way that demonstrates comprehension
of the tradeoffs involved in design choices [CS].
An ability to use and apply current technical concepts and practices in the core information
technologies [IT}.
k. An ability to apply design and development principles in the construction of software systems of
varying complexity[CS].
An ability to identify and analyze user needs and take them into account in the selection,
creation, evaluation and administration of computer-based systems[IT].
l.
An ability to effectively integrate IT-based solutions into the user environment [IT].
m. An understanding of best practices and standards and their application [IT].
n. An ability to assist in the creation of an effective project plan [IT]..
Relationship between CLOs and SOs
CLO #
SO
a
1
b
c
d
X
4
5
f
g h
I
j
k
l
X
X
m
n
X
X
X
2
3
e
X
X
X
X
X
X
X
X
X X
4. Overview of GP Process
The GP is carried over in the last two semesters (9th and 10th semesters), called Semester 1 and
Semester 2 (Graduation Project 1 and Graduation Project 2). Both semesters will be graded
independently according to the work carried out in each semester. Work assessed will include
deliverables submitted and final presentation. The general purpose of Graduation Project 1 is
for the students to give a presentation showing their project proposal including management
plan, feasibility study, requirement document. At the end of their Graduation Project 2, the
students are evaluated on their presentation of the final project deliverables and a project
report.
6
5. Assigning Students to Supervisors and Projects
x
Graduation projects supervisors are asked to submit project preliminary ideas one semester in
advance to the departmental coordinator (GP Coordinator) for the students to start groups
formation.
x
Students can choose from ideas published by the supervisors or offer their own ideas to the
supervisors for adoption.
x
For a faculty member to supervise a graduation project, he/she must be a full time faculty
member. He/she could have assistants from external supervisor in case of an industrial project
or project from other colleges inside Majmmah University. In case of assistance from joint
supervisor, the following points are applicable
a. Need of joint supervisors are initiated by the Supervisor and submitted to the GP
coordinator.
b. The GP coordinator analyses the case and recommend to HoD for approval.
c. The joint supervisor is expected to work closely with the supervisor
d. The supervisor and joint supervisor will divide the responsibilities in order to avoid
conflicts.
e. The joint supervisor is the part of evaluation committee as a member outside the college.
x
An orientation session will be conducted to final year students to raise their awareness of the
graduation project handbook and the necessary information related to projects registration and
assessment.
x
Students must register during the first week of Semester 1 for their graduation project. Once
registered, they must form teamwork of at most 4 students, depending on the nature of the
ǯǤ
a. The supervisor is responsible to divide the project work among the team members and
follow up regularly.
b. In case of conflict among the team members in carrying out the assigned task, the
supervisor is responsible to solve it.
x
The GP Coordinator, is responsible to prepare a list of the proposed projects, list of students in
each project, and supervisors.
7
6. Project Supervision
a) Students are expected to submit a formal project proposal under the supervision of supervisor
in the 3rd week (see Appendix H)
b) In the 4th week of the Semester 1, students should submit final project proposal to the GP
Coordinator.
c) It is mandatory for every project group to submit project deliverables to their respective
supervisors (see Section 9 for detail on project deliverables).
d) It is mandatory for every project group to complete project proposal, project management
plan, project requirement specification, and prepare an oral presentation at the end of the
semester 1.
e) To keep track on weekly student-supervisor meetings and to monitor student progress, the
students are required to fill a Regular Supervision Record Form (see Appendix I) that contains
the meeting minutes and submit it to the respective supervisor after the meeting to ensure that
it is accurate. Finally, copies of the meeting minutes will be stored in the GP course file.
f) To keep track of all the projects in the department GP coordinator will ask supervisor to submit
a monthly report. (Appendix J)
g) It is mandatory for every project group to submit project report containing project details,
design, modeling and execution plan by the end of 15th week of Semester 1 to their respective
supervisor.
h) GP Coordinator releases project evaluation schedule for Semester 1 to be conducted in the
16th week of the semester 1. Every group presents a detailed oral presentation using
PowerPoint slides of the work done in Semester 1 to the evaluation committee and the final
grade of Semester 1 will be decided by the evaluation committee in consultation with the
Ǥ ʹͲͳͲǯ
question and answer session.
i) By considering the comments and suggestions given by evaluation committee after the oral
presentation the project work should be adapted, in consultation with the supervisor, at the start
of Semester 2.
j) It is mandatory for every project group to submit Final GP Report containing project details,
design, modeling, execution plan, implementation and testing by the end of 15th week of
Semester 2.
8
7. Project Evaluation
x The GP coordinator in consultation with the HoD is responsible to form an evaluation committee
comprises of a maximum three senior members within/other department of the college which
Evaluation Committee
includes the supervisor as a member.
x
Supervisor
Senior Member within
the Department
Senior Member outside
the Department or Joint
Supervisor
The GP Coordinator is responsible for scheduling final project presentation, which is a public
event where students of the last semester(Level 8) before GP should also be encouraged to
attend the event.
x
The table IV contains a minimal set of GP deliverables along with the purpose and the deadline
of submission. Each submitted deliverable must be duly signed by the supervisor. The
ǯval will not be considered. The evaluation committee will
carry out the evaluation according to the mark allocation policy.
x
ǯ
from the online integrity checker as decided the competent authorities and will be
communicated to the students/supervisor during the beginning of the semester 1.
9
Evaluation Criteria
Following table explains a guideline for the criteria to be used for GP evaluation/assessment
along with description and evaluation authority (s).
Table I: GP Evaluation Criteria
Criteria
Semester 1 Project
Proposal
(Initial
Evaluation)
Semester IProject
Proposal Midterm
Evaluation
Semester 1
Project
Presentation
(Final
Evaluation)
10
Description
The students are expected to provide
the following information convincingly
during this phase:
x Background of the project
x Motivation for the project
x Problem statement
x Scope of the project
x Project baseline requirements
x Expected outcomes
x Identified tasks and a tentative
work plan
The students are expected to provide
the following information during the
second phase:
x Comprehensive analysis
of
related work
x Detailed project requirements
x Identification of alternative
solutions/approaches
and
justification of selecting a
solution/approach
x Identified tasks and a realistic
work plan
Students are expected to present and
defend a comprehensive project proposal
during the final proposal evaluation
containing the following information:
x Background of the project
x Motivation for the project
x Problem statement
x Scope of the project
x Comprehensive analysis of related
work
x Project requirements
x Identification
of
alternative
solutions/approaches
and
justification
of
selecting
a
solution/approach
x Discussion of tools and techniques
used during project proposal
x Appropriate analysis
Evaluation
Authority(s)
Due Date
Week 6
Supervisor
Week 11
Supervisor
Week 15
Evaluation
Committee
x
Description of tools and techniques
to be used during project
implementation
x Identified tasks and a realistic work
plan for project implementation
Students are expected to provide the
following information during the midterm
project evaluation:
x Background of the project
x Problem statement
x Appropriate analysis
x Details of partial implementation
Semester 2
conforming to the design/proposal
Project
x Tools and techniques being used
Implementation
– Midterm
during project implementation
Evaluation
x Details of design conforming to the
problem statement
x Preliminary outcomes/results
x Remarks on preliminary results and
intermediate conclusions
x Identified tasks and a realistic work
plan for next phase
Week 9
Supervisor
Week 15
Semester 2
Demonstration
& Presentation
Final Evaluation
11
The students are expected to provide the
following information by the end of final
phase:
x Background of the project
x Motivation for the project
x Problem statement
x Scope of the project
x Comprehensive analysis of related
work
x Project requirements
x Identification
of
alternative
solutions/approaches
and
justification
of
selecting
a
solution/approach
x Appropriate analysis
x Details of project implementation
conforming to the project proposal
x Mastery of tools and techniques
being
used
in
project
implementation
x Overall
project
outcome/achievements
x Analysis of overall result through
comparison/validation/verification
x Comprehensive remarks on overall
project outcome and achievements
x Conclusions and future work
Evaluation
Committee
Semester 1 and
Semester 2
Project Report
To assess the structure of the project
report. Student(s) are required to show
planning and progress in an organized way
with emphasis on the interpretation of the
information gathered during the project.
Project reports have to be submitted in both
Semester 1 and Semester 2.
Week 16
Evaluation
Committee
Criteria for Mark Allocation Policy
Out of 100% marks, the supervisor will award the project for 65% marks and the evaluation
committee will award for 35% of marks. The criterion is shown in the following table:
Table II: Criteria for Evaluation
Criteria Ȃ Project 1
Initial Evaluation
Midterm Evaluation
Final Evaluation
Report
Criteria Ȃ Project 2
Midterm Evaluation
Project Demonstration & Presentation
(Final Evaluation)
Report
12
Graduation Project-I
Assessment Form (Final Evaluation)
Project Title:
Course : PROJECT 1
Literature review
Identify similar projects in the literature
Observe and list modern tools, simulators, advanced techniques that are used
in the literature for similar target project
Demonstrate an understanding towards the computing profession
responsibilities through literature review.
Find information relevant to problem solution without guidance
Literature Analysis
Ability to interpret and discuss any solution given in the literature
Use of various approaches of self-learning during literature review and
analysis
Assess the effect of constraints and specifications on an computing problem as
being practiced in the literature
Identify the cu1rrent critical issues confronting the discipline
Observe and list ethical issues that are related to the target project
Problem Formulation
Articulate and relate the computing issues with problem physical variables
Express the problem mathematically
Analyze the problem and divide it into component
Define/identify a problem constraints
Select and justify a solution to a technical problem.
Identify missing knowledge in seeking problem solution, then self-learning the
missing knowledge
Importance of the project to the society
Project Requirement Specification (PRS)
Requirements Analysis
expected feature
constraints, interface
Project Management Plan (PMP)
Project development approach
Associated milestones
Deliverables
Team Work
Researches and gathers information
Fulfill duties of team roles
Shares in work of team
Attends the team meetings and contributes in the discussions
Communication Skill
Write a technical report
Use language (grammar, spelling, expressions, vocabulary
Listen and respond to question
Use audio-visual equipment.
Communicate Effectively
Total Marks
13
Examiner 2. (E2)
Semester :
Examiner 1 (E1)
Student ID:
Supervisor (S)
Student Name:
Average (0.5 S+0.25
E1+0.25 E2)
Total
Student-Score
Graduation Project-II
Assessment Form (Final Evaluation)
Project Title:
Course : PROJECT II
Student Name:
Literature review & Analysis
Identify similar projects in the literature
Observe and list modern tools, simulators, advanced techniques that are used
in the literature for similar target project
Ability to interpret and discuss any solution given in the literature
Find information relevant to problem solution
Assess the effect of constraints and specifications on an computing problem as
being practiced in the literature
Project Design
Follow the design principal
System Design & Modeling, Fulfill the basis for implementation and unit test
Describes the rationale for design decisions taken
Coding, Testing & Implementation
Follow the Coding principal, use latest tool ,language etc
Use /Design Test cases for Testing of the Project
Implementation of the Project (Are the result is evaluated according to the list
of requirements that was created in the definition
Importance of the Project in Society
Future Work
Team Work
Researches and gathers information
Fulfill duties of team roles
Shares in work of team
Teammate listens to other
Attends the team meetings and contributes in the discussions
Communication Skills
Write a good technical report
Listen and respond to question
Communicate & Present the Work Effectively
Total
14
Examiner 2. (E2)
Examiner 1 (E1)
Semester
Supervisor (S)
Student ID:
Average (0.5 S+0.25 E1+0.25
E2)
Total
Student-Score
Deduction Rules
Supervisor continuously assesses students on a process criterion during the project. Late
submissions and irregular meetings may result in deduction of marks depending upon the
ǯǤ
Table III: Criteria for late project report submission
Marks
Deduction
1 day
(1/3marks)
2 day
(2/3marks)
3 day
(0 marks)
No Oral Presentation without report
submission
Report Delay
8. Deliverables
Table IV Ȃ GP Deliverables
Deliverable
Purpose
Student
Information
Due
Start of Semester 1
Project
Proposal
Mid-term
report
Project
report
Final
Presentation
To finalize and submit the problem
statement, motivation of the project,
project scope and expected outcomes
ǯ
their
proposed project
To submit project deliverables
(including the recommended
documents of Semester 1 shown in
Table II)
in the form of a single report
An evaluation committee is invited to
ǯ power
point presentation
Submit to
supervisor
4th week of
semester 1
Submit to
supervisor
8th week of
semester 1
Submit to
supervisor
15th week of
semester 1
Submit to
supervisor &
Examination
15th week of
semester 1
Grading of Semester 1 and End of Semester 1
Start of Semester 2
15
Mid-term
Report
ǯ
in execution plan,
implementation (coding) and
testing of their project
Submit to
supervisor
8th week of semester 2
Final Report
A single report containing all
project deliverables (including
the recommended documents of
Semester 2 shown in Table III)
in the form of a single report.
Submit to
Supervisor
14th week of Semester 2
Final
Presentation
& demo
An evaluation committee is
ǯ
projects
15th Week of Semester 2
Present to
Supervisor,
Examiners
Grading of Semester 2 and End of GP
TABLE V Ȃ Documents recommended and can be part of the deliverables shown in Table I and Table II
Deliverable
Project
Management
Plan (PMP)
Project
Requirement
Specification
(PRS)
Purpose
Start of Semester 1
To document the motivation for the
project, need of the project, project
development approach, milestones of
the project, agreed deliverables and
dates of deliverables
To document the requirements,
expected outcomes, constraints,
Graphics User Interfaces and system
design and modeling
Start of Semester 2
Student
informat
ion
Due
Submit to
superviso
r
10th week
of
Semester
1
Submit to
superviso
r
13th week
of
Semester
1
Project Design
Document
To document the design of the project
for detailed implementation and for
unit testing
Submit to
superviso
r
Test Document
To document how the project will
implemented, tested, and record the
results.
Submit to
superviso
r
3rd week
of
Semester
2
13th week
of
Semester
2
Grading of Semester 2 and End of GP
End of GP Submission
x Two copies of the bound report (one for the student and one for the college archive)
x
A CD in each report comprising the following folders:
o Report (soft copy of the final report, and power point presentation)
o Code (complete source code of the project)
o Demo (the executable in working order and a readme file containing the information
about the software requirements (tools) and hardware requirements for the GP as well
as the instructions or the steps (soft copy of the user manual) for running the GP
executable).
16
Appendix A
Overview of GP Process
Semester 8
Semester 9
Semester 10
`
GP Coordinator &
HoD
Project Scope
& Benefits
Project Design
Document
Project
Management Plan
Project Test
Document
Assign
Supervisor
Project
Requirements
Specification
17
Choose Project /
Propose Project
Final Presentation
Initial Meeting
Evaluation
Committee
Final
Presentation &
Demo
Appendix B
Cover Page
[DOCUMENT TITLE]
[PROJECT NAME]
Document History:
Version
(Draft/final)
Author
Description of
Version
Date
Signature
Reviewers:
Team
Members
1
2
3
Supervised by:
Student
Name
Registration
No
Date
Signature
Approved by:
[Project Team]
Dept. of ____________________________
Faculty of Computer and Information Sciences
.
18
Appendix C
< Project Name >
Project Management Plan
Version No < 1 >
Date dd/mm/yy
19
TABLE OF CONTENTS
1 INTRODUCTION
1.1
Purpose of Project Management Plan
2 EXECUTIVE SUMMARY OF PROJECT CHARTER
2.1
Assumptions/Constraints
3 SCOPE MANAGEMENT
3.1
Work Breakdown Structure
3.2
Deployment Plan
3.3
Change Control Management
4 SCHEDULE/TIME MANAGEMENT
4.1
Milestones
4.2
Project Schedule
4.2.1 Dependencies
5 COST/BUDGET MANAGEMENT
6 QUALITY MANAGEMENT
7 HUMAN RESOURCE MANAGEMENT
8 COMMUNICATIONS MANAGEMENT
8.1
Communication Matrix
9 RISK MANAGEMENT
9.1
Risk Log
10ISSUE MANAGEMENT
10.1
Issue Log
11PROCUREMENT MANAGEMENT
12COMPLIANCE RELATED PLANNING
Appendix A: Project Management Plan Approval
Appendix B: REFERENCES
Appendix C: KEY TERMS
Appendix D: SUMMARY OF SPENDING
20
Appendix D
< Project Name >
Project Requirement Specification
Version No < 1 >
Date dd/mm/yy
21
Appendix D
Table of Contents
1. EXECUTIVE SUMMARY
1.1 Project Overview
1.2 Purpose and Scope of this Specification
2. PRODUCT/SERVICE DESCRIPTION
2.1 Product Context
2.2 User Characteristics
2.3 Assumptions
2.4 Constraints
2.5 Dependencies
3. REQUIREMENTS
3.1 Functional Requirements
3.2 User Interface Requirements
3.3 Usability
3.4 Performance
3.4.1 Capacity
3.4.2 Availability
3.4.3 Latency
3.5 Manageability/Maintainability
3.5.1 Monitoring
3.5.2 Maintenance
3.5.3 Operations
3.6 System Interface/Integration
3.6.1 Network and Hardware Interfaces
3.6.2 Systems Interfaces
3.7 Security
3.7.1 Protection
3.7.2 Authorization and Authentication
3.8 Data Management
3.9 Standards Compliance
3.10
Portability
4. USER SCENARIOS/USE CASES
5. DELETED OR DEFERRED REQUIREMENTS
6. REQUIREMENTS CONFIRMATION/STAKEHOLDER SIGN-OFF
APPENDIX
Appendix A. Definitions, Acronyms, and Abbreviations
Appendix B. References
Appendix C. RequirementsTraceability Matrix
Appendix D. Organizing the Requirements
22
Appendix E
Project Design Description (PDD)
Cover Page
Table of Contents
1
INTRODUCTION
1.1. Functional Requirements
1.2. Non-Functional Requirements
1.3. Design Overview
1.4. Requirements Traceability Matrix
2
SYSTEM ARCHITECTURAL DESIGN
2.1. System use-cases
2.2. Interaction Diagrams
2.3. Class Diagrams
2.4. System Architecture
2.5. Database Design
3 DETAILED DESCRIPTIONS OF COMPONENTS
3.1. Component-n
4 USER INTERFACE DESIGN
4.1.
Description of the User Interface
4.2.
Screen Images
4.3.
Objects and Actions
5. ADDITIONAL MATERIALS
23
Appendix F
Project Test Documentation (PTD)
Cover Page
Table of Contents
1 INTRODUCTION
1.1. System Overview
1.2. Test Approach
2 TEST PLAN
2.1. Features to be Tested
2.2. Features not to be Tested
2.3. Testing Tools and Environment
2.4. System Testing
2.4.1. Unit Testing
2.4.2. Integration and Regression Testing
2.4.3. Performance and stress testing
2.4.4. User acceptance testing
2.4.5. Test cases
3 TEST CASES
3.1 Case-n
3.2 Purpose
3.3 Inputs
3.4 Expected Outputs & Pass/Fail criteria
3.4 Test Procedure
4 ADDITIONAL MATERIAL (including appendix A)
APPENDIX A. TEST LOGS
A.n Log for test n
A.n.1 Test Results
A.n.2 Incident/Bug Report
24
Appendix G
Submission Instructions:
x
The graduation project report must be submitted in A4 size. Number of copies to be submitted: Two
(One copy for your Department, One for your Project Guide).
x
Each group member must print and keep one copy of signed and sealed project report. (As project report
may be requested by interviewers during your early career job interviews)
x
The certificate page as depicted in the following pages must consist of names and University ID numbers
of all group members.
Paper, Typing, Format Instructions:
x
x
Paper (A4 size) must be used for the preparation of the project report. Typing must be done on one side
of the paper with character font in size 12 of Times New Roman.
The layout must provide a margin of 4 cm on the left, 3 cm on the top and bottom and 2 cm on the right.
i.e. Left margin space 4 cm
top and bottom margin space 3 cm
Right margin space 2 cm
x
x
x
Fresh paragraph must commence after five spaces. Double-spacing or One and half line spacing shall
be provided through the report.
The page numbers must be indicated at bottom-middle of each page.
Should not underline the heading/subheadings and must not put colons (:) in headings or subheadings.
Binding Instructions:
x
The report must be properly bound, using Rexene of black color. The bound front cover must indicate
in suitable embossed letter the following:
Top:
(Title of Project)
(Full Name and University ID)
Bottom:
Department of CS/IT/CE/IS
College of Computer and Information Sciences
Majmaah University
(Year/Semester of Submission)
25
Instructions format for first few significant pages:
x
Two blank papers (first and last) must be provided that is one at the beginning and one at the end.
Third Page
x
The third page must contain the following
Title
Project report submitted in partial fulfillment of the requirement for the award of the Degree of Bachelor of
Science
By
(Name of the All Group Member(s))
(All University ID Number(s))
(Email(s))
Bottom
Department of CS/IT/CE/IS
College of Computer and Information Sciences
Majmaah University
Al Majmaah, Saudi Arabia
Fourth Page
x
26
The fourth page must contain a certificate signed by the guide(s) in the following format.
Certificate
ǥǥǥǥ
Name1
UID1
Name2
UID2
Name3
UID3
Name4
UID4
in partial fulfillment for the award of the Degree of Bachelor of Science in (CS/IT/CE/IS) to the Majmaah
University, AlMajmaah, Saudi Arabia is a record of authentic work carried out under my guidance and
supervision.
The results embodied in this project report have not been submitted to any other University or Institute
for the award of any Degree or Diploma.
(Guide Name)
(Designation)
Head of the Department
Fifth Page
(Required only if project activity is carried out in external organization)
The fifth page may include the External Certificate given by Organization or Company where the group has
done the project. College certificate must precede this certificate.
Sixth Page
The sixth page may include the Acknowledgements (If any)
In this sections the author(s) can acknowledge his/her gratitude or convey thanks to one or more persons.
27
Seventh Page
x
x
x
The seventh page must contain an abstract of the Project report.
Group Members are expected to write the brief summary of the problem statement. The reader of this
abstract must grasp a quick idea about the objectives of project that students are going to perform.
The candidate may also emphasize his/her ideas/contributions here.
Eight and Ninth Page
x
In this page, a table of contents, list of tables, list of figures, and photographs and notation must be
provided.
Important Note about Page Numbering standards:
All the above pages ǤǤǡǡǡǡǥ
The document pages ǤǤͳǡʹǡ͵ǥǥ
Arrangement of Units/Chapters depending upon the project
The following is suggested format for arranging the project report content into various units or chapters:
1. EXECUTIVE SUMMARY
1.1 Project Overview
1.2 Purpose and Scope of this Specification
2. PRODUCT/SERVICE DESCRIPTION
2.1 Product Context
2.2 User Characteristics
2.3 Assumptions
2.4 Constraints
2.5 Dependencies
3. REQUIREMENTS
3.1 Functional Requirements
3.2 User Interface Requirements
4. SYSTEM ARCHITECTURAL DESIGN
4.1. System use-cases
4.2. Interaction Diagrams
4.3. Class Diagrams
4.4. System Architecture
4.5. Database Design
5. DETAILED DESCRIPTIONS OF COMPONENTS
5.1. Component-n
28
6.USER INTERFACE DESIGN
6.1 Description of the User Interface
6.2 Screen Images
6.3 Objects and Actions
7. TEST PLAN
7.1 Features to be Tested
7.2 Features not to be Tested
7.3 Testing Tools and Environment
7.4 System Testing
7.4.1 Unit Testing
7.4.2 Integration and Regression Testing
7.4.3 Performance and stress testing
7.4.4 User acceptance testing
8. TEST CASES
8.1 Case-n
8.2 Purpose
8.3 Inputs
8.4 Expected Outputs & Pass/Fail criteria
8.5 Test Procedure
9. Conclusions
10. Further Enhancements/Recommendations
11. References/Bibliography
12. Appendices (if any).
Instruction for Arrangement of Paragraph in a Chapter:
x
x
x
29
Each paragraph in a chapter must be properly numbered for example, 2.1, 2.2 etc., where first digit
represents the Chapter Number and second digit the paragraph number. There is no need to indicate
the number for the first paragraph in a chapter.
Sub-paragraphs, if any indicated as 1.1.1, 1.1.2 etc. i.e. first digit representing the chapter, the second
representing the paragraph and third representing the sub-paragraph.
ǯrline the headings or subheadings or side heading. Instead use the bold letters.
Instructions for Photographs/Figures and Tables
x
x
x
The figures, photographs and tables occurring in a chapter may be serially numbered as Fig. 1.1, 1.2 etc.,
where the first digit represents the chapter, the second digit represents Figure number.
The photographs may be represented as Photo 1.1, 1.2 etc., the first digit representing chapter and the
second digit represents Photograph number.
The tables may be represented as Table 1.1, 1.2 etc., the first digit representing chapter and the second
digit represents table number.
Instructions for Graphs:
x
(No hand drawn graphs) The graph must clearly indicate the points, which are used for drawing the
curve or curves and also must be generated using MATLAB or MS-OFFICE or any other professional
graphing tool etc.
Instructions for Bibliography or References:
x
The following format may be used for writing the Bibliography/References.
Author Name, Title of the book or paper, Publisher name, year.
Eg:
Sergois, Aggelos, Konstantinos Koutroumbas , and Dionisis Cavouras. Introduction to Pattern Recognition: A
Matlab Approach. Elsevier: Academic Press AP, 2012.
(An article in a journal)
Booth, Wayne C. “Kenneth Burke’s Way of Knowing.” Critical Inquiry 1 (1974): 1-22. Winks, Robin W.
“The Sinister Oriental Thriller: Fiction and the Asian Scene.” Journal of Popular Culture 19.2 (1985):
49-61.
x
30
The bibliography list must be made strictly in alphabetical order of the name of the authors.
Sample format of certificate page (Fourth Page)
Certificate
This is to certify that the project report entitled (YOUR PROJECT TITLE) being submitted by
(Group Member Name 1)
(UID 1)
Group Member Name 2)
(UID 2)
(Group Member Name 3)
(UID 3)
(Group Member Name 3)
(UID 4)
in partial fulfillment for the award of the Degree of Bachelor of Science in (CS/IT/CE/IS) to the College of
Computer Sciences, Majmaah University is a record of authentic work carried out under my guidance and
supervision. The results embodied in this project report have not been submitted to any other University or
Institute for the award of any Degree or Diploma.
(Supervisor)
Designation
Head of the Department
32
Appendix H
Final Year Project Start Form
Fill in the information below as detailed as you can when submitting your project idea.
Proposed Team
Student
ID
Name
Email
Credit
Hrs *
Area of interest (Tick one or more)
Development Track
1. Web Development
2. Multimedia
3. Mobile
Applications
4. Network
Applications
5. Others:
Research Track
1. Software Engineering
2. Information Security
3. Digital Forensics
4. Innovative Tool Development
5. Others:
Abstract of the Proposed Projects
_____________________________________________________________________________________________________________________
_____________________________________________________________________________________________________________________
_____________________________________________________________________________________________________________________
_____________________________________________________________________________________________________________________
_____________________________________________________________________________________________________________________
_____________________________________________________________________________________________________________________
________________________________________________________________________________________________________________
33
(For Office use only)
(To be filled by the Project Coordinator)
Project Accepted
Project Rejected
Supervisor Name:
Reason(s):
GP Coordinator, CS/IT/CE/IS Department
34
Proposal for FINAL YEAR PROJECT IN CS/IT/CE/IS – By Faculty Members
Title of the Project
Abstract of the project
Keywords
PROJECT DESCRIPTION
ǯ
SYSTEM REQUIREMENT
SOFTWARE REQUIREMENTS
Operating system
:
Language
:
Browsers
:
Packages
:
HARDWARE REQUIREMENTS
Processor
RAM
35
:
: —GB (minimum)
Secondary Memory
: –MB/GB (minimum)
Display
:
Milestones and Timelines
Number Milestone
Name
Milestone
Description
Timeline
Week no.
from the
start
of
the
project
36
1
Requirements
Specification
2
Technology
familiarization
3
Database
creation
4
High-level and
Detailed Design
5
Implementation
of the front-end
of the system
6
Integrating the
front-end with
the database
7
Integration
Testing
8
Final Review
Remarks
Appendix I
GP Regular Supervision Record Form
Students and supervisors should use this form to help structure and provide a record of their meetings.
ǯ
the project and the required tasks.
SECTION 1 to be completed by the STUDENT prior to supervision meeting
37
a)
Name:
b)
ǯǣ
c)
Date/time of supervision:
d)
Date of last supervision:
e)
Work submitted to supervisor since last supervision meeting (with date work submitted and
returned to you)
f)
Work undertaken since last supervision meeting:
g)
Issues you would like to discuss in the supervision meeting:
SECTION 2 to be completed at the supervision meeting
a)
Topics covered in supervision meeting (please refer to Section 1(g) above):
b)
Work student should undertake between now and next formal meeting (with dates:
SECTION 3
Date/Time of next meeting:
This form contains a good summary of our meeting
Signatures :
Student
Date
Supervisor
Date
A copy of this form should be kept by the supervisor , the student, and in tǯ
Office
38
Appendix J
Monthly Progress Report
Department of _____
College of Computer and Information Systems (CCIS)
Project ID:
Project Name:
Name of the Supervisor:
Date:
Period covered: From _____/____/20__ to _____/____/20__
Names of Team members:
1.
List and describe your tasks during last month
2.
List and describe your pending tasks from last month along with their
reasons
3.
Task Plan for the next month
4.
Any other comments
Signatures:
39
Signature of the Supervisor:
Team MembeU¶V
Name & ID
Please
write
Designation
Signature
Date
_____/____/20__
_____/____/20__
_____/____/20__
_____/____/20__
anything below. To be filled by the GP Coordinator
*3&RRUGLQDWRU¶V&RPPHQWV
40
GRQ¶W
Appendix K
Evaluation Rubrics: Graduation Project-I & II
Content
Literature
review
Developing(2)
Competent(3)
Exceptional(4)
The student is not
able to understand
issues
and
problems, not able
to find modern
tools, simulators
that are used in the
literature review
for similar target
project
The student is able
to understand issues
and problems, also
able to identify
similar
projects,
modern
tools,
simulators,
advanced
techniques that are
used
in
the
literature review for
similar
target
project
The student is able
to
interpret and
discuss a solution
,know approaches of
self-learning during
literature
review
and analysis
Able to Identify
similar projects
in the literature,
Develops
a
strategy. comes
up
with
a
reasonable
solution
Suggests
new
approaches
and
improves on what has
been done before
Identify
the
current critical
issues
confronting the
discipline from
literature review
Articulate and relate
the
computing
issues with problem
physical variables.
Express the problem
mathematically
Analyze
the
problem
and
divide it into
components
Define/identify a
problem
constraints
Select and justify
a solution to a
technical
problem.
Identify the current
critical issues and
develop the frame
work that improves
on what has been
done before ,also find
the ethical issues that
are related to the
target project
Define/identify
a
problem constraints ,
Identify
missing
knowledge in seeking
problem
solution,
then self-learning the
missing knowledge
Literature
Analysis
The student is not
able to interpret
and discuss any
solution given in
the literature
Problem
Formulation
Not
able
to
Articulate
and
relate
the
computing issues
with
problem
physical variables.
Project Design
41
Unsatisfactory(1)
Not
able
to Know the Design Know and apply Describes
the
understand
the principal.
Use System Design & rationale for design
design principal
Design & Modeling Modeling tool,
decisions taken
tools in the project.
Coding, Testing Do not know the Know the Coding
&
Coding principal, principal, use latest
Implementation latest
tool tool, language
,language ,
How Testing is
done for
the
Project , also do
not know the
Importance of the
Project in Society
Team Work
42
Design Test cases
for Testing of the
Project
Know
the
Importance
of
the Project in
Society
Evaluate the result
according to the list of
requirements
that
was created in the
definition , know the
Importance of the
Project &
Future Work
System Design &
Modeling, Fulfill
the
basis
for
implementation
and unit test
Researches
and
gathers information.
Fulfill duties of team
roles
Shares in work of
team
Attends the team
meetings
and
contributes in the
discussions
Fulfill duties of
team roles
Shares in work of
team
Attends the team
meetings,
Researches and
gathers
information.
Attends the team
meetings
and
contributes in the
discussions
Communication Do
not
Skills
communicate and
present effectively,
Oral as well as
written
communication
skills are poor
Communicate and
present effectively,
Report is Good
written,
respond to some of
the question
Communicate
and
present
effectively, Listen
and respond to
most
of
the
question
Oral as well as
written
communication skill
is good, Report is
written
in
a
professional
way,
respond
to
all
question
