1
Document Issued: FALL 2018
Version: 2.0
Prepared By: FYP Committee
DEPARTMENT OF COMPUTER SCIENCE
UNDERGRADUATE
FINAL YEAR PROJECT
HANDBOOK
Guidelines, Procedures and Regulations
COMSATS UNIVERSITY ISLAMABAD
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Final year project guide for computer science, Assignments of Network Analysis
Final year project guide for computer science student
Typology: Assignments
2019/2020
1 / 79
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Final year project guide for computer science and more Assignments Network Analysis in PDF only on Docsity!
1
Document Issued: FALL 2018 Version: 2. Prepared By: FYP Committee
DEPARTMENT OF COMPUTER SCIENCE
UNDERGRADUATE
FINAL YEAR PROJECT
HANDBOOK
Guidelines, Procedures and Regulations
COMSATS UNIVERSITY ISLAMABAD
CUI/PC/Notices/FA18/001 Date: 30 Aug 2018
Schedule for FYP Milestone, Deliverables and Evaluation
Final Year Project-I (6th Semester)
Sr. # Activity Deadline 1 Collection of Project ideas from faculty. Friday- 3 rd^ week of semester 2 Display of proposed FYP ideas to the students Monday- 6 th^ week of semester 3 Project scope document online submission by students Friday- 11 th^ week of semester 4 Display (result) of accepted projects Monday- 17 th^ week of semester
Final Year Project-I ( 7 th^ Semester)
Sr. # Activity Deadline 1 Scope and SRS seminar Friday- 1 st^ week of semester 2 EVALUATION 1: Defence of Scope and SRS Monday- 3 rd^ week of semester 3 Evaluation result will be shared with student on/before Friday- 4 th^ week of semester 4 SDS document & 30% Implementation seminar Friday- 4 th^ week of semester 5 EVALUATION 2: SDS document & 30% Implementation First Monday Sessional-Right after second 6 Evaluation result will be shared with student on/before Friday-One week after evaluation 2
Final Year Project-II ( 8 th^ Semester)
Sr. # Activity Deadline 1 EVALUATION 3: 60% Implementation Monday- 2 nd^ week of semester 2 Evaluation result will be shared with student on/before Friday- 3 rd^ week of semester 3 Implementation seminar Friday- 4 th^ week of semester 4 EVALUATION 4: System Testing & Debugging^ 100% Implementation with^ Monday-One week before 2
nd sessional 5 Evaluation result will be shared with student on/before Friday-Next week of evaluations 6 Submission of Project Report (2 copies in spiral binding) NEXT DAY OF EVALUATION 4 7 External Examiner Nomination to Exam Department AFTER OPEN HOUSE PROJECT DISPLAY 8 Project Evaluation by External Examiner To be announced by Exam Dept. 9 BOOK BINDING submission along with Project Executable Code in DVD 04 Days after External Evaluation 10 Result Submission to the Exam Department To be announced by Exam Dept.
1. INTRODUCTION
The Final Year Project (FYP) is a mandatory prerequisite for award of degree in BS (CS) and BS (SE) programs. At the department of Computer Science, CUI Islamabad campus, it is spread over the final three semesters as follows: 6 th^ Semester : Submission of FYP Scope document, 7 th^ Semester : Presentation and submission of Software Requirement Specification (SRS) and Software Design Document (SDD), 8 th^ Semester : Implementation.
1.1. Objectives
FYPs are considered as unitary of the core components for computer science and software engineering discipline students at the undergraduate levels. These projects play a key role in forming the students‟ mind-set towards performing real life projects. In summation, the FYP aims to encourage the student to integrate and use almost all core modules/forms they have examined during their undergraduate journey. The objectives of FYP include: To identify and formulate a computer-based system according to agreed requirements. To use and implement latest tools and technologies to meet the requirement of the software industry. To apply software engineering theory and practices in the modelling and design of computer-based systems. To select and utilize the knowledge, techniques and skills of their respective discipline to produce a mandatory system. To work effectively in a team environment. To apply the professional, ethical, legal, and social issues and responsibilities. To present effectively to a range of audiences.
1.2 Assigning Students to Supervisors and Projects
- Faculty of Department of Computer Science, with designation of lecturer and above is eligible for supervision of FYP. Rest of the faculty can co-supervise.
- Each faculty member eligible for supervision, must supervise or co-supervise at least one project and Maximum THREE FYPs every semester.
2. GUIDELINES
The student who is eligible for FYP is encouraged to conform to the guidelines provided by FYP committee. In case of any complain/request, student should submit their issues in the prescribed Performa (See Appendix C) to their respective coordinators: FYP Coordinator-1, FYP Coordinator-II. If a student has any issue with their supervisor, evaluator or the respective FYP Coordinator, he or she can submit their complaint within three days of the incidence to the FYP Moderator. The FYP Convener will be the final authority to resolve the issue. For any updates and notifications regarding FYP, it is mandatory for every FYP student to join their respective FYP-FB groups. Link will be given to respective CRs. If a student fails to follow the SOPs/Guideline and show non-compliance on the deliverables assigned by FYP committee, he / she can be penalised according to SECTION 2.5. Research based projects must be based on substantial coding/implementation, GUI and must be in the form of a product. 2.1. Guidelines for Student 2.1.1. Registration Guidelines Registration: o Each student doing FYP must register on CU Online during registration week in 7 th^ and 8th^ semester according to their Scheme of Studies. Formation and number of students in an FYP Group: There can be minimum 2 and maximum 3 members in an FYP group, depending on the scope of the project. 2.1.2. Evaluation Folder: Each FYP will have an evaluation folder that include: i- Meeting log with Supervisor (See Appendix D). ii- Evaluator's comments/recommendations/suggestions at each milestone. iii- Supervisor remarks on the evaluators' comments /recommendations/suggestions. iv- All documentation related to FYP (e.g. Scope, SRS, and SDD etc.).
2.2.2 Role of FYP Coordinator Prepare and share (with students and faculty) FYP semester schedule with the approval of convener, before start of the semester. Organize and manage students FYP evaluation activities. Coordinate with convener, evaluator, supervisor and students. Process all cases regarding FYP Funding. Resolve any query related to all stakeholders. Coordinate with Account, audit, exam, transport and security offices. Submit Final FYP result to Exam department.
2.2.3 Role of Moderator FYP Moderator will be responsible/contact person for following activities Monitoring of FYP process. Contact person for conflict of interest among stakeholders. Recruitment Drives. Recruitment Seminars. Inter & Intra departmental activities. FYP Industrial Collaboration & Participation in National Level Events.
2.3. Role of Supervisor
The role of supervisor includes: (may not be limited to this only) Discussing the project plan and suggesting changes if necessary. Ensure regular and effective meetings with students. Advising on the appropriate materials and methods/design/technology to use. Offering advice on sources of information for respective project. Advising on issues related to FYP report write up. Reading drafts of each chapter of FYP report. Ensure that their groups are following required standard SRS, SDD, and Presentation etc. Grade their FYP students after every milestone as per defined rubrics.
2.4. Role of Evaluation Committee
Each FYP group will be evaluated by a team of faculty members (referred as evaluators). They are collectively responsible for both: Critique and evaluate different stages of FYP (milestone) according to predefined rubrics (See Appendix B) along with the convener. Submit evaluations as per evaluation plan/ rubrics to Final Year Projects Office through prescribed method. SOPs for Evaluation Committee The evaluation team assigned at the 1st^ milestone (i.e. Scope Document Evaluation) will evaluate project throughout the year. The evaluator should make the presentation venue before time to avert any unnecessary delay. Evaluators will be assigned evaluation slots as per timetable. It is the evaluator's responsibility to ensure; o The smooth conduct of all evaluations according to announced FYP schedule.
o If any evaluator is not available during the evaluation, he or she inform the respective
coordinator and must provide their substitute.
o Any issue regarding substitute arrangement, should be reported to the convener with
CC to coordinators. Ensure completion of evaluation of milestone within allocated time (30 minutes). There will be 05 minutes for Q/A between evaluators and students at the end of the demonstration. After evaluation of project, there will be 05 minutes (if required) for discussion between evaluators and supervisor(s). Evaluators are required to complete the evaluation result sheets within the evaluation week and submit it to respective the FYP Coordinator. Evaluators should not discuss evaluation matters with students after the evaluation slot. Evaluators are requested to follow announced schedule and time for smooth conduct of evaluation process.
NON-COMPLIANCE For non-compliance from a student on the tasks assigned by FYP committee; o For First Time: 30% Marks will be deducted from the current mile stone. o Regular Non-Compliance: 10% Marks deduction to a degradation grade on recommendation of coordinator, to be decided by convener FYP committee. Probation: If 02 probations are assigned by the evaluation team then the student(s) will present their FYP in next semester.
2.6. FORMATTING AND LAYOUT
Students will be provided template files for FYP document and presentation of each milestone through their respective FYP Facebook groups. FYP Template Files are appended. (See Appendix A).
3. Road Map for BS
6. Project Evaluation - III Student will present his/her project implementation (100%) in front of FYP committee with complete project report.If project is plagiarised / behind the time line / not according to the scope, students will getpermanent I.P and they will appear in next semester.If approved, submit 2 copies after incorporating changes 2. Supervisor Selection and Project Registration Student can only register for project if he/shesuccessfully completed the core courses Project is worth 6 credit hours and ideallycompleted in two semesters Student should select supervisor according to thehis/her working of interest 1. Courses Completion Student can register for Final Year Project after completing the perquisite courses as prescribed in the scheme of studies. 3. Project Scope and SRS Submission and Defence Submission of scope document will be in 6 Screening team will decide if the project idea is i) acceptedth^ semester. Pre- ii) changes iv) Not accepted accepted with minor changes iii) accepted with major After acceptance, student will present his/her project scope with SRS in front of FYP committee. If approved, resubmit scope document after incorporating any changes suggested by FYP committee. Students will notevaluation committee be allowed without to appear inevidence of atfront least of the four meetings with their supervisor before every milestone.
- Project Evaluation – I and SDS Submission Student will present his/her project implementation (30%) with SDS in front of FYP committee.SDS can be accepted with minor / major revision after incorporating any changes committee. suggested by FYP If project is plagiarised / behind the time line / not according to the scope, students will get conditional I.P.
- Project Evaluation - II Student will present his/her project implementation (60%) in front of FYP committee. If project is plagiarised / behind the time line / notaccording to the scope, students will get conditional I.P.
- External Defence Student will present his/her work in front ofnominated external examiner. Submit final approved report along with CD(containing complete project data) after incorporating changes suggested by external to the FYP secretaries.
Collection of 02 Spiral Bindings from students Verification & Submission of Spiral Bindings to exam department Resolving queries of Exam related to External Evaluator & Spiral Binding Contact External Evaluator for availability (Date & Time) External Evaluation Schedule External Availability Students Availability Resolving student terminal exam clashes Preparation of External Evaluation Sheets Conduct External evaluations Compilation of combined result (FYP-I &II) Compilation of complete Result Sheets (Committee + Supervisor + External marks) Verification of complete result Making Back up of complete result for record Collection of FYP Report Book Binding + DVD from students Verification of collected Book Bindings Submission of Result Sheets & Book Binding to Exam Department Resolving queries of Exam & Students Compilation and submission of ICEF form
APPENDIX A
(DOCUMENTATION TEMPLATES)
SCOPE DOCUMENT REVSION HISTORY
Supervisor Signature
Date:
No. Comment Action
Table of Contents
- Introduction
- 1.1. Objectives…………………………………………………………………....
- 1.2. Assigning Students to Supervisors and Projects
- Guidelines
- 2.1. Guidelines for Students
- 2.2. Role of Convener, Coordinator and Moderator .............................................
- 2.3. Role of Supervisor
- 2.4. Role of Evaluation Team
- 2.5. Penalties
- 2.6. Formatting and Layout……………………………………………………...
- Road map for FYP……………………………………………………...……
- Milestone and Activities
- 4.1. 06 th Semester Students
- 4.2. 07 th Semester Students
- 4.3. 08 th Semester Students
- Appendix A- Documentation Templates
- Appendix B- Evaluation Rubrics
- Appendix C- FYP Forms
- Appendix D- Meeting & Evaluation Log
- Introduction
- Problem Statement.................................................................................................................
- Problem Solution for Proposed System
- Related System Analysis/Literature Review
- Advantages/Benefits of Proposed System
- Scope........................................................................................................................................
- Modules
- 7.1 Module 1: Module Name
- 7.2 Module 2: Module Name
- System Limitations/Constraints
- Software Process Methodology
- Tools and Technologies..........................................................................................................
- Project Stakeholders and Roles
- Team Members Individual Tasks/Work Division
- Data Gathering Approach
- Concepts
- Gantt chart
- Mockups
- Conclusion
- References
- Plaragism Report
Introduction
Specify the purpose of this project proposal document along with description detailed background of the system. (Usually in 10-12 sentences).
Problem Statement
What problem does your software solve? Why you are developing this system? Does the same system already exists? If yes , how will a re-implementation aid your learning? What skills do you expect to learn from this project? (Usually in 14-16 sentences)
Problem Solution for Proposed System
Briefly explain how your system solves the problems mentioned in the problem statement. (Usually in 14-16 sentences)
Related System Analysis/Literature Review
Write about the existing/similar systems related to your proposed project. At least three existing systems should be discussed. Don‟t use more than 4 sentences for explaining a single system/application. Briefly explain the related system analysis which help to specify the contribution of the proposed project. ( Note : Research based projects may provide literature review instead of related system analysis.)
Table 1 Related System Analysis with proposed project solution Application Name Weakness Proposed Project Solution The name of related application(s).
Weaknesses may include limited features, low quality functionality and processes.
The way the proposed project mitigates the weaknesses.
Advantages/Benefits of Proposed System
Write down the advantages and benefits of the system you are developing. In other words, you have to mention here advantage of your proposed solution to the existing problem. (Usually in 5-7 advantages)
Scope
Write down the scope of your project in a paragraph. Briefly define the main functionalities of the proposed project. Scope defines the boundaries and range of the proposed solution, that what would be the part of your project and what will be not. Write down in logical flow with consistency. (Usually in 14-18sentences)
Modules
Write down the modules of the proposed project. Don‟t forget to mention special/new features. Briefly explain your one module in 6 to 8 sentences. (Note: Usually 5-6 Modules for 2 student‟s projects and 8-9 modules for 3 student‟s project)
Explanation of a Module: Module is a section of a program that performs a task. Programs consist of modules, each of which contains one or more routines. The term routine is synonymous with procedure, function, and subroutine.
Example:
Enterprise resource planning (ERP) software - is comprised of several large modules (for example, finance, supply chain and payroll, etc.), which may be implemented with little or no customization.
(Briefly explain each module with respect to major functionality in user context)
Module 1: Module Name
Module 2: Module Name
System Limitations/Constraints
Write down the limitations and constraints of the proposed project. (Usually 2-4 constraints)
Software Process Methodology
Write down your software methodology/ software process that will be used for project development. .Also mention why you have chosen this methodology. (Usually 3-5 sentences)
- You can use Object Oriented Methodology, or Procedural methodology.
- Choice of methodology will affect choice of tools and technologies
- Choice of methodology will affect nature of design (SDS)
- Choice should be made depending on your expertise and your needs e.g. most simulation and device level software can only be programmed in procedural languages.