Bakre

Project Guide
For session 2010-2014 on ward
BSSE, BSCS, BSIT and MCS

Degree programs
Department of Computer and Software Technology

University of Swat
Department of Computer and Software Technology, University of Swat
Table of Contents
1. Introduction 3
2. Administration and Registration 3
3. When to Start 5
4. The First Step: Finding a Topic and Advisor------------------------------------------------5
5. Project proposal 5
6. The Thesis Document and Finishing Up-----------------------------------------------------5
6 .0 Specific guidelines for the parts of the project repot-----------------------5
6.1. Writing an Abstract 6
6.2. Page Format 6
6.3. Type-----------------------------------------------------------------------------------------7
6.4. Sections and Subsections 7
6.5. References 8
6.6. Title Page and Copyright 8
6.7. Approval from Supervisor 8
6.8. Internal Presentations and examiner assignment----------------------------8
6.9. External and Final Presentation 9
6.10. Hard Binding 9
7. Contents of the CD Attached 10
8. Student/Supervisor Weekly Meetings 10
9. Appendices-(A to I) 11
2
Thesis Guide Composed By: Fida Hussain Chairman Department of Computer and Software Technology
1. Introduction
The final project requirement gives students an opportunity to develop and demonstrate their
ability to carry out document a reasonably comprehensive project requiring considerable
initiative, creative thought, and a good deal of individual responsibility. The thesis may be a
design project, an analytical paper, or experimental work of a technical nature.
MCS, BSCS, BSSE and BSIT projects normally involve one or more of the following:
 Development of software that might:

i. Test a new algorithm developed for scheduling and management problems;
ii. be used for application of software engineering tools (testing and quality assurance,
for example);
iii. enhance and improve networking, client/server, and e-commerce techniques;
iv. simulate a real system (e.g. Artificial Intelligence);
v. aid in a diagnostic procedure;
vi. analyze a theory or theorem which is an abstraction or idealization of an actual
process or system;
vii. Apply some of the standard methods (of communication theory or control theory, for
example) to aid in understanding of a process or system;
 Studies of real world business organization problems and suggest solutions;
 Improvements and enhancements in an Operating System by developing new device
drivers and utilities etc;
 Demonstrate application of Software Engineering techniques.
The project will generally be completed in one semester in the time equivalent to two regular
subjects (6 Cr. Hours). Ordinarily the project is an individual effort; however, group projects are
possible if the work of the individuals can be evaluated separately. Separate thesis documents
must be submitted by each student. The project normally begins during the senior year and
completed during the final semester. The student selects a project title which represents the work
to be done. It is responsibility of the students to ensure both the deadlines and procedures
described below are met and that all necessary documents are completed and in full compliance
with the departmental and university requirements the department will refuse to accept any
thesis/ project that fails to meet these standards.
2. Administration and Registration
The CS project is administered by the head of DC&ST. Questions about final project policies
and procedures should be addressed to him. All the students must be registered in the university
while working on their projects. They must be enrolled during the semester they until they
defend the project even though their final year has been completed.. Students who fail to
complete their projects on time must therefore register for at least one additional unit of project
during the subsequent semester.
3
4
3. When to Start
Start to think about your project as early as possible. Be on the alert for interesting problems that
come to your attention in class, personal contacts, or through the technical literature. The best
time to start defining a project is during the senior year (3 rd Semester for MCS and 7th semester
for 4 years bachelor degree).
4. The First Step: Finding a Topic and Supervisor
It's not as difficult to find a project topic and an advisor as many students think. Any faculty
member may supervise a CS project. If you wish to be supervised by a faculty member outside
the CUSIT, you may request permission. Find a project which is of direct and intense interest to
you and which will give you a maximum opportunity not only to learn about the subject being
investigated, but also about proper methods of technical investigation. You should avoid projects
so remote from your current training that acquiring the necessary background will cause
excessive delay. As soon as you have reached a meeting of minds with an advisor, start work on
a project proposal to get your topic defined, formalized and approved.
5. The Project Proposal
It is very important that the work on the Project Proposal be started as soon as an advisor has
agreed to work with you on a problem. Do NOT wait until the week before the proposal deadline
to start. The proposal must be submitted duly signed by the student and the supervisor before
undertaking the major work on the project. Each student must present and explain his/her project
proposal to the faculty members. The proposal must be substantiated (Appendix G) including
references and must be accompanied by a Thesis Proposal Cover Sheet (Appendix D) along with
supervisor approval sheet (Appendix F). The overall project life cycle is depicted in the
following figure.
6. The Project Document and Finishing Up
The thesis write-up is considered a major part of the final project .Specific bibliographic citations
should be included whenever reference is made to documents or other communications. It must
be well written, clearly organized, and contain no stylistic or grammatical errors. Advisors are
encouraged to require early drafts, to provide criticism of the writing as well as the technical
content, to require re-writes, and to insist that the final document conform to the accepted
standards of technical writing. The final grade should be based in part on the writing quality of
the thesis.
6.0 Specific guidelines for the parts of the project repot
Keep the format as simple as possible. Complexity breeds confusion. The mode of presentation
should be consistent throughout the documentation.
Keeping these two points in mind can both simplify the task of organizing the documentation
and minimize the possibility of it being rejected by the departmental format checkers.
The project report has three main parts or division
5
 Preliminary pages
 The text
 The appendix
Some sections with the preliminary pages and the appendix are optional, but the order of items
with the project report , regardless of what parts may be left out is as follows:
Preliminary pages
 Title page (unnumbered)

 Project approval pages (unnumbered)
 Abstract (the first of the number preliminary pages)
 Dedication
 Acknowledgment
 Table of contents.
 List of tables
 List of figures, illustrations, symbols, abbreviations, (optional)
The text
The text should be according to the table of contents provided in the project guide
6.1 Writing an Abstract
You must include an abstract, and it should contain your thesis title, your name, your Project
Supervisor, the degree and the date (see the sample in Appendix A). Those students who found it
difficult to get their thesis title short enough should have no difficulty writing an abstract. Start
by writing out a full title, with all the adjectives and phrases you cut from the title. Describe your
methods or procedures in a couple of sentences, and your conclusions or results in another
sentence or two. It should be no longer than 150 words. It may be helpful to refer back to your
Project Proposal.
6.2. Page Format
While no specific format is required, it is important to structure your paper clearly and logically.
However, there must be at least one-inch margins on the top and bottom, with all text, charts,
photographs, and code INSIDE the margins. The side margins must both be one and one quarter
inch. This includes appendices of code (try using a copier to reduce material to make it fit). Lack
of control over your formatter is NOT an excuse for failure to adhere to these rules. For pages of
code, remember that there are good quality photocopiers available that will reduce your code so
that it fits within the margins.
Page size: A4
Page numbering: Bottom right - part of the footnote
Title page not numbered. All other pages before the page of
chapter one numbered in lower roman numerals (i, ii, iii, …). All
6
other pages starting from first page of chapter one to last page of
the report numbered using Arabic numerals.
Foot-note: Each page shall have a footnote giving the title of the project /
thesis only. In case of long titles shorter versions should be
used. There shall be a line over the footnote.
Chapter Startup: Each chapter shall be numbered as Chapter 1, Chapter 2, etc. The
name of the chapter shall be written immediately below. Both shall
be centered horizontally as well as vertically. The actual chapter
content shall start from the next page.
Text: Only one side of the paper shall be used. The other side shall be
blank. When a report is opened the right side would contain text,
figures, or tables and the left side would be blank.
Tables and Figures: Each table / figure shall be numbered. For example "Table 1.2:
Population distribution in Asia" or "Figure 3.2: Temperature
distribution". The table number or figure number shall be placed as
normal text centered at the bottom of the table or figure or
sideways with table / figure title coming on the opening side of the
paper and note on the binding side.
Line Spacing: 1.5 pts
Paragraph: Single spaced. Line entered paragraph. DONOT put indents at the
beginning of the paragraph. Left aligned or justified.
6.3 Type
Normal and plane text:

Font Type: Times-New roman
Font Size: 12
Headings:
Chapter Heading: Font Arial Bold Size 16 Title Case normal
Heading 1: Font Arial Bold Size 14 Title Case normal
Heading 2: Font Arial Bold Size 12 Title Case normal
Heading 3: Font Arial Bold Size 12 Title Case italic
7
6.4 Sections and Subsections
In case of sections and subsections follow this format:

Section 1
1.1
1.1.1
a
b
c
i
ii
iii
The subsequent reference to a any section shall be made using the section and its number.
For example section 2.1.3 means chapter 2 section 1 subsection 3.
6.5 References
References are to be placed in square brackets and interlaced in the text. For example "A number
of profiles of Asian researchers can be found in the literature [2]. A project report / thesis can not
be accepted without proper references.
The references shall be quoted in the following format:
The articles from journals, books, and magazines are written as:
[1] Jennifer Eyre, "The Digital Signal Processor: Derby", IEEE Spectrum,
June 2001, pp 62-68.
[2] Nabila Zar, "Wasey Omar", In Person: Profiles of Researchers in Africa,
Asia, and the Americas, International Development Research Center,
Ottawa, 1995, pp 67-73.
[3] The books are written as:
[1] Wayne C Booth, Gregory G. Colomb, Joseph M. Williams, The Craft of
Research, The University Chicago Press, Chicago, 1995.
[2]
The Internet links shall be complete URLs to the final article.
[1] http://www.parc.xerox.com/csl/projects/aop/workshops.shtml
6.6 Title Page and Copyright
Make your title page look EXACTLY like the sample provided in Appendix D of this guide. The
author must, as a condition of the degree, grant nonexclusive permission to the university to
reproduce and distribute publicly copies of the thesis. A statement to this effect must appear on
the title page. (See the sample title page in Appendix C.) You must submit correct title pages. If
CUSIT holds the copyright, grant it to CUSIT and omit the permissions sentence.
You automatically have the copyright unless you received money from CUSIT for doing the
research or writing it up, or if the work used equipment or facilities provided to the Institute
under conditions that impose copyright restrictions. Use the date on which you hope to submit
the document.
8
6.7 Approval from Supervisor
When your project supervisor becomes satisfied from both your software and documentation.
Then initially submit one copies of your thesis with your project supervisor. The title page (see
samples in Appendix C ) must bear your and your project supervisor original signatures. The
Departmental committee signature will be provided later. The copies must be submitted in
temporary binders consisting of two pieces of cardboard and binder clips. Do not hole-punch or
bind your thesis in any other way. On the front cover of each binder, place a label containing
your name, project title, supervisor, degree and date
6.8 Internal Presentations and examiner assignment.
After evaluation of the thesis report by the departmental committee, the student will have to
present the project to the faculty members. There on the Head of Dept will assign the internal
examiner for making the software and documentation up to mark and internal evaluation. The
internal examiner will report that all the changes suggested by the project committee and internal
examiner is successfully accommodated in the software and documentation. The thesis report
will not be forwarded to examination for assigning the external examiner until approved by the
internal examiner.
6.9 External and Final Presentation
The external examiner will be assigned to the student’s final project by the
examination department. As the examination reports to the department about the date
and time, the student will be contacted through his/her available contact number.
Make sure on time arrival to the venue and arrangement which are necessary for
demonstrating the final project in front of external examiner.
After the final presentation the student will accommodate all the changes suggested by
the external examiner, otherwise the external examiner reserve the right to hold on the
Grade/Marks until the changes are accommodated.
6.10 Hard Binding
After final oral presentation you have to submit four (4) copies of your thesis in hard binding to
the department of computer science, failing which result will not be declared. It must also
contain all corrections recommended by internal and external examiners and also
recommendations, suggestions forwarded during the oral presentation. These four copies will be
distributed as follows:
Library One Copy
Examination Section One Copy
Department One Copy
Students Own One Copy
7. Contents of the CD Attached
9
All reports / theses must accompany a CD whose contents shall have the following:
Top level directories:
Doc All documents related to the project

Instructions how to access the CD to the point to running the project
All reports already submitted
The final project report in thesis form
Installation instructions
Trouble shooting instructions in case of
problems User manual
Research material including URLs
Papers consulted / referred to
Slides of the presentations
Src All source files that will be needed to compile the project.
Further subdirectories can be used.
This must include sample data files as well.
Project The running project including sample data files as well as sample output. This should
be in a form that if copied to a machine runs without errors. This may an exe file of an entire
project, an installer depending on the project or simply a running project.
You can have sub directories with appropriate names.
8. Student/Supervisor Weekly Meetings.
Every student will have required meeting to his/her supervisor at least for two hours weekly the
guide lines for those meeting are provided as under. At the end of every weekly meeting the
student will write up what they have discussed in today meeting and what are the things to do for
the next coming week meeting on weekly progress report (Appendix-H) signed by the
supervisor. At the time of internal presentation the student will have provide the weekly progress
reports to the head department of computer science.
Week-01 Initial Requirement Analysis, Project Scope & Features Discussion
Week-02 Detailed Requirement Analysis, Initial Planning and Time Scheduling
Week-03 Project Management Plan & Task Assignments
Week-04 Software Risk Management Plan & Detailed Requirement Specification
Document.
Week-05 Software Design Specification & Methodology and Complete Data Base Designing.
Week-06 Discussion about the site/SW Visual Design, Layouts and themes
Week-07 Submission of progress report and discussion for improvement.
Week-08 Software implementation report-1
Week-11 Reviews and Tests Procedures Application.
Week-12 Discussion about the final presentation and s/w demo to the faculty or internal
Presentation
10
Appendices
Appendix A. Proposal approval page
Appendix B. Proposal table of contents
Appendix C Weekly project progress
Appendix D. Title Page
Appendix E Final approval page.
Appendix F. Abstract
Appendix G. Declaration
Appendix H Project table of contents
Appendix I. Dissertation Submission and Copyright
11
Appendix-A
Proposed Project Title
This project proposal is submitted to the Department of Computer and Software

Technology, University of Swat as on
November 26, 2014
Author
[Student Name & Signature]
Supervisor
[Supervisor Name & Signature]
12
Appendix-B
Project Proposal Format
1. Introduction
2. Existing system
3. Problem areas
4. Proposed Solution
5. Key Stakeholders
6. Infrastructure
a. Equipments/ resources.
b. Computer hardware
c. Communication and networks
7. Software components/ sub system
a. General description of the Software components
b. Detail description of each major Software component
c. Interface to other systems (if applicable)
d. Database considerations
e. Use of existing software components (if applicable)
f. Feasibility of SW components to be developed
8. Schedule
a. Major activity list
b. Milestones
c. Dependencies
d. WBS(work breakdown structure)
9. Developmental tools and utilities
10. Developmental environment
11. Development methodology
12. Reviews
13. Special considerations
a. Reliability
b. Timing
c. Data integrity
d. Backup and recovery
14. Risk management
15. testing methodologies
16. References
17. Annexure (if any)
13
Appendix-C
Weekly Project Progress Report
Project title:
Student Name: Reg#:
Supervisor Name:
Date of meeting:------------------------- week#:----------
Discussion topic: ------------------------------------------------------------------------------
Description:
Supervisor Signature
14
Appendix–D
Your Final Project Title
Session 2010-14
Submitted by
[Student Name]
[Program and batch No]
Supervised by
[Supervisor Name]
Department of Computer and Software

Technology University of Swat
15
Appendix-E

University of Swat
Final Approval
This is certified that we have studied this project report, titled [your project title],
submitted by [your name] University Registration Number 0000-44-fgg-4004. We
conclude that this project report is of sufficient standard to warrant its acceptance
by the University of Swat for the award of the degree of Bachelor of Science in
computer science (BSCS).
Final Project Evaluation Committee

External Examiner
Name: Designation
Institute:
Internal Examiner
Name: Designation
Institute:
Supervisor
Name: Designation
Institute:
16
Appendix -F
Your Project Title

By
Student’s Name
Submitted to
University of Swat
May 16, 2014
ABSTRACT
The stratigraphic model editor provides a convenient and efficient tool for geophysicists
manipulating the complex models used in ray tracing and other forward modeling techniques.
The editor allows the user to build a model of the earth on a Symbolic Lisp Machine screen using
the mouse. The earth models manipulated by the program represent a two-dimensional slice of
the earth, typically extending three or four miles down and having 10 to 50 layers. The layers
need not be flat, but can contain features such as reefs and salt domes. These models are
important in exploration geophysics. The editor generates data files representing this model that
can be used as input to a ray-tracing program. The description of the file format is written in a
high-level declarative language, so that the editor can be easily modified to support other
formats.
17
Appendix-G
Declaration
I hereby declare that this software neither as a whole nor as a part thereof has been copied from
any source. Further, I declare that I have developed this software and the accompanied reports
entirely on the basis of my personal efforts, made under the sincere guidance of my supervisor.
No portion of this work presented in this report has been submitted in support of an application
for another degree or qualification of this or any other university or institution learning. If any
part of this system is proved to be copied or found to be a report of some other, I will stand by
the consequences.
Student Name & Signature

email@address.com
18
Appendix-H
PROPOSED TABLE OF CONTENTS
1 INTRODUCTION
1.1 Objectives
1.2 Background
1.3 Project Structure
1.4 System Salient Features
2 SOFTWARE PROJET PLAN
2.1 Introduction
2.2 Project Overview
2.3 Project Deliverables
2.4 Software Project Management Plan
2.5 Reference Materials
2.6 Definition, Acronyms, or Abbreviations
2.1 Project Organization
1.1 Gantt-Chart
1.2 Work Products
1.3 Organizational Structure
1.3.1 Organizational Boundaries & Interfaces
1.4 Project Responsibilities (WBS)
2.2 Managerial Process
2.1 Management Objectives and Priorities
2.3 Assumptions, Dependencies and Constrains
2.4 Risk Management
2.5 Monitoring and Controlling Mechanics
2.6 Staff Plan
2.7 Technical Process
7.1 Methods, Tools and Techniques
7.1.1 Hardware Environment
7.1.2 Operating System
7.1.3 S/W Tools & Techniques
7.1.4 S/W Documentation
7.1.5 Project Support Functions
2.8 Work Packages, Schedule and Budget
8.1 Work Packages
8.1.1 Work Products
8.1.2 Resource Requirements
8.2 Budget & Resource Allocation
8.3 Schedule
CHAPTER 3: RISK MANAGEMENT PLAN
Introduction
Purpose
Roles and Responsibilities
19
Risk Documentation
Risk List
Risk Data Items
Closing Risk
Activities
Schedules for Risk Management Activities
Risk Management Budget
Risk Management Tools
Introduction
Usability
Strength
CHAPTER 4: REQUIREMENT ANALYSIS & SPECIFICATION
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Overview
2. General Description
2.1 Product Perspectives
2.2 Product Functions
2.3 User Characteristics
2.4 General Constraints
2.4.1 The Product
2.4.2 Hardware Constraints
2.4.3 Guide Lines
3 Specification Requirements
3.1 Functional Requirements
 Functional Requirements of Administrator
 Functional Requirements of User/Member
3.2 Nonfunctional Requirements
 Design Constraints
 Performance Requirements
 Business Process
 Audit Trails
 Traceability
 Consistency
 Reliability
 Error Tolerance
 Simplicity
 Documentation
 Coding Standards
 Testing With Code Reviews
 Other Requirements
4 Required Deliverables
4.1 Requirement Specification Document
4.2 Installation Software
4.3 User Training
20
4.4 User Guide/Manual
 General Descriptions
 Development Environment
 Decomposition Descriptions
 Use Cases Scenarios
 Real Use Cases
 Use Case Diagrams
 Activity diagram
CHAPTER 5: SOFTWARE DESIGN
Design process activities
 Architectural design
 Abstract specification
 Interface design
 Component design
 Data structure design
 Algorithm design
 UI design The design which is based on requirements Specification and can be tr
Supported by Possible Model
.
 System Model
 Object Model
 Sequence Model
 Collaboration diagram
 State transition Model
 Structural Model
 Data flow Model
CHAPTER 6: DATABASE DESIGN
Conceptual design
 Business Rules
 Data Dictionary
(Tables with all fields along with field data type and Description)
 ERD (ER-win, MS-Visio)
Logical design
 Tool (SQL) based design
Physical design
 Space and size consideration
CHAPTER 7: TOOLS AND TECHNOLOGIES
CHAPTER 8: TESTING
SOFTWARE TEST PLAN
Product Visualization
Time Limit
Team for Testing
Decomposition Module
Description of Plan
21
TESTING
1. Introduction
1.1 Product Name
1.2 Test Cases Developed by
1.3 Document Generated by
1.4 Date
1.5 Test Report Reference Number
3. Test Cases
4. Test case execution
5. test case Report
CHAPTER 9: APPLICATION DEPLOYMENT AND USER
GUIDE LINES
9.1 Application deployment strategy
9.1.1 Deployment diagram
9.2 Maintenance considerations
9.3 User Guide
APPENDIX
References
22
Appendix-J
Dissertation
Submission and Copyright
The dissertation submitted to the Department of Computer and Software Technology

University of Swat as a partial fulfillment of the requirements for the award of the degree of
Bachelor of Science in Computer Science (BSCS).
The author hereby grants to University of Swat a permission to reproduce and distribute publicly
paper and electronic copies of this thesis and to grant others the right to do so.
Copyright 2014©Studentname. All rights reserved
Author
[Student Name]
Batch, Program
September 17, 2014
23

Bakre

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bakre

Uploaded by

Copyright:

Available Formats

Project Guide

For session 2010-2014 on ward

BSSE, BSCS, BSIT and MCS

Department of Computer and Software Technology

 Development of software that might:

2. Administration and Registration

4. The First Step: Finding a Topic and Supervisor

5. The Project Proposal

6. The Project Document and Finishing Up

6.0 Specific guidelines for the parts of the project repot

 Title page (unnumbered)

6.1 Writing an Abstract

6.2. Page Format

Line Spacing: 1.5 pts

Normal and plane text:

6.4 Sections and Subsections

In case of sections and subsections follow this format:

6.6 Title Page and Copyright

6.7 Approval from Supervisor

6.8 Internal Presentations and examiner assignment.

6.9 External and Final Presentation

6.10 Hard Binding

7. Contents of the CD Attached

Doc All documents related to the project

8. Student/Supervisor Weekly Meetings.

Appendix A. Proposal approval page

Appendix B. Proposal table of contents

Appendix C Weekly project progress

Appendix D. Title Page

Appendix E Final approval page.

Appendix H Project table of contents

Appendix I. Dissertation Submission and Copyright

Proposed Project Title

This project proposal is submitted to the Department of Computer and Software

November 26, 2014

Project Proposal Format

Weekly Project Progress Report

Student Name: Reg#:

Discussion topic: ------------------------------------------------------------------------------

Your Final Project Title

Department of Computer and Software

Department of Computer and Software Technology

Final Project Evaluation Committee

Your Project Title

May 16, 2014

Student Name & Signature

PROPOSED TABLE OF CONTENTS

The dissertation submitted to the Department of Computer and Software Technology

Copyright 2014©Studentname. All rights reserved

You might also like