APPENDIX – 1

105
 Project Dissertation Semester V and
Project Implementation Semester VI
Chapter 1 to 4 should be submitted in Semester V in spiral binding. These chapter have also to
be included in Semester VI report. Semester VI report has to be hard bound with golden embossing.
Students will be evaluated based on the dissertation in semester V and dissertation and viva
voce in Semester VI.

I. OBJECTIVES
 Describe the Systems Development Life Cycle (SDLC).
 Evaluate systems requirements.
 Complete a problem definition.
 Evaluate a problem definition.
 Determine how to collect information to determine requirements.
 Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time
feasibility and Operational feasibility for the project.
 Work on data collection methods for fact finding.
 Construct and evaluate data flow diagrams.
 Construct and evaluate data dictionaries.
 Evaluate methods of process description to include structured English, decision tables and
decision trees.
 Evaluate alternative tools for the analysis process.
 Create and evaluate such alternative graphical tools as systems flow charts and state
transition diagrams.
 Decide the S/W requirement specifications and H/W requirement specifications.
 Plan the systems design phase of the SDLC.
 Distinguish between logical and physical design requirements.
 Design and evaluate system outputs.

106
 Design and evaluate systems inputs.
 Design and evaluate validity checks for input data.
 Design and evaluate user interfaces for input.
 Design and evaluate file structures to include the use of indexes.
 Estimate storage requirements.
 Explain the various file update processes based on the standard file organizations.
 Decide various data structures.
 Construct and evaluate entity-relationship (ER) diagrams for RDBMS related projects.
 Perform normalization for the unnormalized tables for RDBMS related projects
 Decide the various processing systems to include distributed, client/server, online and others.
 Perform project cost estimates using various techniques.
 Schedule projects using both GANTT and PERT charts.
 Perform coding for the project.
 Documentation requirements and prepare and evaluate systems documentation.
 Perform various systems testing techniques/strategies to include the phases of testing.
 Systems implementation and its key problems.
 Generate various reports.
 Be able to prepare and evaluate a final report.
 Brief the maintenance procedures and the role of configuration management in operations.
 To decide the future scope and further enhancement of the system.
 Plan for several appendices to be placed in support with the project report documentation.
 organized and documented programs in a reasonable time.
 Work effectively as an individual or as a team member to produce correct, efficient, well-
Recognize problems that are amenable to computer solutions, and knowledge of the
tool necessary for solving such problems.
 Develop of the ability to assess the implications of work performed.
 Get good exposure and command in one or more application areas and on the software
 Develop quality software using the software engineering principles
 Develop of the ability to communicate effectively.

107
II. Type of the Project
The majority of the students are expected to work on a real-life project preferably in some industry/
Research and Development Laboratories/Educational Institution/Software Company. Students are
encouraged to work in the areas listed. However, it is not mandatory for a student to work on a
real-life project. The student can formulate a project problem with the help of her/his Guide and
submit the project proposal of the same. Approval of the project proposal is mandatory. If
approved, the student can commence working on it, and complete it. Use the latest versions of the
software packages for the development of the project.

108
III. SOFTWARE AND BROAD AREAS OF APPLICATION

FRONT END / GUI Tools .Net Technologies, Java

DBMS/BACK END Oracle, SQL Plus, MY SQL, SQL Server,
LANGUAGES C, C++, Java, VC++, C#, R, Python
SCRIPTING LANGUAGES PHP,JSP, SHELL Scripts (Unix)
.NET Platform F#, C#. Net, Visual C#. Net, ASP.Net
MIDDLE WARE (COMPONENT) COM/DCOM, Active-X, EJB
TECHNOLOGIES
UNIX INTERNALS Device Drivers, RPC, Threads, Socket programming
NETWORK/WIRELESS -
TECHNOLOGIES
REALTIME OPERATING SYSTEM/ LINUX, Raspberry Pi, Arduino, 8051
EMBEDDED SKILLS

APPLICATION AREAS Financial / Insurance / Manufacturing / Multimedia /

Computer Graphics / Instructional Design/ Database
Management System/ Internet / Intranet / Computer
Networking-Communication Software development/ E-
Commerce/ ERP/ MRP/ TCP-IP programming /
Routing protocols programming/ Socket programming.

IV. Introduction
The project report should be documented with scientific approach to the solution of the
problem that the students have sought to address. The project report should be prepared in
order to solve the problem in a methodical and professional manner, making due references
to appropriate techniques, technologies and professional standards. The student should start
the documentation process from the first phase of software development so that one can easily
identify the issues to be focused upon in the ultimate project report. The student should also
include the details from the project diary, in which they will record the progress of their
project throughout the course. The project report should contain enough details to enable
examiners to evaluate the work. The important points should be highlighted in the body of
the report, with details often referred to appendices.

109
1.1 PROJECT REPORT:
Title Page
Original Copy of the Approved Format of the Project Proposal
Certificate of Authenticated work
Role and Responsibility Form
Abstract
Acknowledgement
Table of Contents
Table of Figures
CHAPTER 1: INTRODUCTION
1.1 Background
1.2 Objectives
1.3 Purpose, Scope, and Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Achievements
1.5 Organization of Report
CHAPTER 2: SURVEY OF TECHNOLOGIES
CHAPTER 3: REQUIREMENTS AND ANALYSIS
3.1 Problem Definition
3.2 Requirements Specification
3.3 Planning and Scheduling
3.4 Software and Hardware Requirements
3.5 Preliminary Product Description
3.6 Conceptual Models

110
CHAPTER 4: SYSTEM DESIGN
4.1 Basic Modules
4.2 Data Design
4.2.1 Schema Design
4.2.2 Data Integrity and Constraints
4.3 Procedural Design
4.3.1 Logic Diagrams
4.3.2 Data Structures
4.3.3 Algorithms Design
4.4 User interface design
4.5 Security Issues
4.6 Test Cases Design
The documentation should use tools like star UML, Visio for windows, Rational Rose for design
as part of Software Project Management Practical Course. The documentation should be spiral
bound for semester V and the entire documentation should be hard bound during semester VI.
CHAPTER 5: IMPLEMENTATION AND TESTING
5.1 Implementation Approaches
5.2 Coding Details and Code Efficiency
5.2.1 Code Efficiency
5.3 Testing Approach
5.3.1 Unit Testing
5.3.2 Integrated Testing
5.3.3 Beta Testing
5.4 Modifications and Improvements
5.5 Test Cases
CHAPTER 6: RESULTS AND DISCUSSION
6.1 Test Reports
6.2 User Documentation

111
CHAPTER 7: CONCLUSIONS
7.1 Conclusion
7.1.1 Significance of the System
7.2 Limitations of the System
7.3 Future Scope of the Project
REFERENCES
GLOSSARY
APPENDIX A
APPENDIX B
V. EXPLANATION OF
CONTENTS Title Page
Sample format of Title page is given in Appendix 1 of this block. Students should follow the
given format.
Original Copy of the Approved Format of the Project Proposal
Sample format of Project Proposal is given in Appendix 2 of this block. Students
should follow the given format.
Certificate of Authenticated work
Sample format of Certificate of Authenticated work is given in Appendix 3 of this
block. Students should follow the given format.
Role and Responsibility Form
Sample format for Role and Responsibility Form is given in Appendix 4 of this
block. Students should follow the given format.
Abstract
This should be one/two short paragraphs (100-150 words total), summarising the project work.
It is important that this is not just a re-statement of the original project outline. A suggested flow
is background, project aims and main achievements. From the abstract, a reader should be able
to ascertain if the project is of interest to them and, it should present results of which they may
wish to know more details.

112
 Acknowledgements
This should express student’s gratitude to those who have helped in the preparation of project.

Table of Contents: The table of contents gives the readers a view of the detailed structure of the
report. The students would need to provide section and subsection headings with associated
pages. The formatting details of these sections and subsections are given below.
Table of Figures: List of all Figures, Tables, Graphs, Charts etc. along with their page numbers
in a table of figures.

Chapter 1: Introduction
The introduction has several parts as given below:
Background: A description of the background and context of the project and its relation to work
already done in the area. Summaries existing work in the area concerned with the project work.

Objectives: Concise statement of the aims and objectives of the project. Define exactly what is
going to be done in the project; the objectives should be about 30 /40 words.
Purpose, Scope and Applicability: The description of Purpose, Scope, and Applicability are
given below:

• Purpose: Description of the topic of the project that answers questions on why this project is
being done. How the project could improve the system its significance and theoretical
framework.
• Scope: A brief overview of the methodology, assumptions and limitations. The students should
answer the question: What are the main issues being covered in the project? What are the main
functions of the project?
• Applicability: The student should explain the direct and indirect applications of their work. Briefly
discuss how this project will serve the computer world and people.
Achievements: Explain what knowledge the student achieved after the completion of the work.
What contributions has the project made to the chosen area? Goals achieved - describes the

113
Degree to which the findings support the original objectives laid out by the project. The goals
may be partially or fully achieved, or exceeded.
Organization of Report: Summarizing the remaining chapters of the project report, in effect, giving
the reader an overview of what is to come in the project report.

Chapter 2: Survey of Technologies

In this chapter Survey of Technologies should demonstrate the student’s awareness and
understanding of Available Technologies related to the topic of the project. The student should give
the detail of all the related technologies that are necessary to complete the project. This should
describe the technologies available in the chosen area and present a comparative study of all those
Available Technologies. Explain why the student selected the one technology for the completion
of the objectives of the project.

Chapter 3: Requirements and Analysis

Problem Definition: Define the problem on which the students are working in the project.
Provide details of the overall problem and then divide the problem in to sub-problems. Define each
sub-problem clearly. Requirements Specification: In this phase the student should define the
requirements of the system, independent of how these requirements will be accomplished. The
Requirements Specification describes the things in the system and the actions that can be done on
these things. Identify the operation and problems of the existing system.Planning and Scheduling:
Planning and scheduling is a complicated part of software development. Planning, for our
purposes, can be thought of as determining all the small tasks that must be carried out in order
to accomplish the goal. Planning also takes into account, rules, and known as constraints, which,
control when certain tasks can or cannot happen. Scheduling can be thought of as determining
whether adequate resources are available to carry out the plan. The student should show the Gantt
chart and Program Evaluation Review Technique (PERT).

Software and Hardware Requirements: Define the details of all the software and hardware
needed for the development and implementation of the project.
• Hardware Requirement: In this section, the equipment, graphics card, numeric co-processor,
mouse, disk capacity, RAM capacity etc. necessary to run the software must be noted.

114
• Logic Diagrams: Define the systematical flow of procedure that improves its comprehension and
helps the programmer during implementation. e.g., Control Flow Chart, Process Diagrams etc.
• Data Structures: Create and define the data structure used in procedures.
• Algorithms Design: With proper explanations of input data, output data, logic of processes,
design and explain the working of algorithms.

User Interface Design: Define user, task, environment analysis and how to map those requirements
in order to develop a “User Interface”. Describe the external and internal components and the
architecture of user interface. Show some rough pictorial views of the user interface and its
components.

Security Issues: Discuss Real-time considerations and Security issues related to the project and
explain how the student intends avoiding those security problems. What are the security policy
plans and architecture?

Test Cases Design: Define test cases, which will provide easy detection of errors and mistakes with
in a minimum period of time and with the least effort. Explain the different conditions in which the
students wish to ensure the correct working of the project.

Chapter 5: Implementation and Testing

Implementation Approaches: Define the plan of implementation, and the standards the students
have used in the implementation.
Coding Details and Code Efficiency: Students not need include full source code, instead, include
only the important codes (algorithms, applets code, forms code etc). The program code should
contain comments needed for explaining the work a piece of code does. Comments may be needed
to explain why it does it, or, why it does a particular way.
The student can explain the function of the code with a shot of the output screen of that program
code.

115
• Code Efficiency: The student should explain how the code is efficient and how the students
have handled code optimization.

Testing Approach: Testing should be according to the scheme presented in the system design
chapter and should follow some suitable model – e.g., category partition, state machine-based.
Both functional testing and user-acceptance testing are appropriate. Explain the approach of testing.
• Unit Testing: Unit testing deals with testing a unit or module as a whole. This would test the
interaction of many functions but, do confine the test within one module.
• Integrated Testing: Brings all the modules together into a special testing environment, then checks
for errors, bugs and interoperability. It deals with tests for the entire application. Application limits
and features are tested here.
Modifications and Improvements: Once the students finish the testing they are bound to be faced
with bugs, errors and they will need to modify your source code to improve the system. Define
what modification are implemented in the system and how it improved the system.

Chapter 6: Results and Discussion

Test Reports: Explain the test results and reports based on the test cases, which should show that
the project is capable of facing any problematic situation and that it works fine in different
conditions. Take the different sample inputs and show the outputs.
User Documentation: Define the working of the software; explain its different functions,
components with screen shots. The user document should provide all the details of the product in
such a way that any user reading the manual, is able to understand the working and functionality
of the document.
Chapter 7: Conclusions
Conclusion: The conclusions can be summarized in a fairly short chapter (2 or 3 pages). This
chapter brings together many of the points that would have made in the other chapters. Limitations
of the System: Explain the limitations encountered during the testing of the project that the students
were not able to modify. List the criticisms accepted during the demonstrations of the
project.

116
Future Scope of the Project describes two things: firstly, new areas of investigation prompted by
developments in this project, and secondly, parts of the current work that was not completed due
to time constraints and/or problems encountered.

REFERENCES

It is very important that the students acknowledge the work of others that they have used or adapted
in their own work, or that provides the essential background or context to the project. The use
of references is the standard way to do this. Please follow the given standard for the references for
books, journals, and online material. The citation is mandatory in both the reports. E.g: Linhares,
A., & Brum, P. (2007). Understanding our understanding of strategic scenarios: What role do
chunks play? Cognitive Science, 31(6), 989-1007. https://doi.org/doi:10.1080/03640210701703725

Lipson, Charles (2011). Cite right : A quick guide to citation styles; MLA, APA, Chicago, the
sciences, professions, and more (2nd ed.). Chicago [u.a.]: University of Chicago Press. p. 187.
ISBN 9780226484648.

Elaine Ritchie, J Knite. (2001). Artificial Intelligence, Chapter 2 ,p.p 23 - 44. Tata McGrawHill.

GLOSSARY
If you the students any acronyms, abbreviations, symbols, or uncommon terms in the project report
then their meaning should be explained where they first occur. If they go on to use any of them
extensively then it is helpful to list them in this section and define the meaning.

APPENDICES
These may be provided to include further details of results, mathematical derivations, certain
illustrative parts of the program code (e.g., class interfaces), user documentation etc.In particular,
if there are technical details of the work done that might be useful to others who wish to build on
this work, but that are not sufficiently important to the project as a whole to justify being
discussed in the main body of the project, then they should be included as appendices.

117
VI. SUMMARY

Project development usually involves an engineering approach to the design and development
of a software system that fulfils a practical need. Projects also often form an important focus for
discussion at interviews with future employers as they provide a detailed example of what the
students are capable of achieving. In this course the students can choose your project topic from
the lists given in Unit 4: Category-wise Problem Definition.

VII. FURTHER READINGS

1. Modern Systems Analysis and Design; Jeffrey A. Hoffer, Joey F. George, Joseph,S. Valacich;
Pearson Education; Third Edition; 2002.
2. ISO/IEC 12207: Software Life Cycle Process
(http://www.software.org/quagmire/descriptions/iso-
iec12207.asp).
3. IEEE 1063: Software User Documentation (http://ieeexplore.ieee.org).
4. ISO/IEC: 18019: Guidelines for the Design and Preparation of User Documentation for
Application Software.
5. http://www.sce.carleton.ca/squall.
6. http://en.tldp.org/HOWTO/Software-Release-Practice-HOWTO/documentation.html.
7. http://www.sei.cmu.edu/cmm/

118
 FORMAT FOR THE APPROVAL PROJECT PROPOSAL
(Note: All entries of the pro forma of approval should be filled up with appropriate
and complete information. Incomplete pro forma of approval in any respect will be
summarily rejected.)
PNR No.: …………………… Enrolment no: …………....

1. Name of the Student……………………………………………………………….

2. Title of the Project…………………………………………………………………

3. Name of the Guide………………………………………………………………...
4. Teaching experience of the guide…………………………………………………..
…………………………………………………………………………………………
…………………………………………………………………………………………
………………………………………………………………………............................

5. Is this your first submission? Yes NO

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

Signature of the Head of Department

Date: …………………

119
 (All the text in the report should be in times new roman)

TITLE OF THE PROJECT

(NOT EXCEEDING 2 LINES, 24 BOLD,
ALL CAPS)
A Project Report (12 Bold)
Submitted in partial fulfillment of the
Requirements for the award of the Degree of (size-12)
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)(14 BOLD,
CAPS)

By(12 Bold)

Name of The Student (size-15, title case)

Seat Number (size-15)

Under the esteemed guidance of (13 bold) Mr./Mrs. Name

of The Guide (15 bold, title case) Designation (14
Bold, title case)

COLLEGE LOGO

DEPARTMENT OF COMPUTER AND INFORMATIVE SCIENCE (12

BOLD, CAPS)
COLLEGE NAME (14 BOLD, CAPS) (Affiliated to
Sabarmati University) (12, Title case, bold, italic) CITY, PIN
CODE(12 bold, CAPS)
GUJARAT (12 bold, CAPS) YEAR
(12 bold)

120
 COLLEGE NAME (14 BOLD, CAPS) (Affiliated to
Sabarmati University) (13, bold, italic) CITY-
GUJARAT-PINCODE(13 bold, CAPS)

DEPARTMENT OF COMPUTER AND INFORMATIVE SCIENCE (14

BOLD, CAPS)

College Logo

CERTIFICATE (14 BOLD, CAPS, underlined,centered)

This is to certify that the project entitled, "Title of The Project ", is bonafide work of NAME OF
THE STUDENT bearing Seat.No: (NUMBER) submitted in partial fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from Sabarmati University. (12, times new roman, justified)

Internal Guide (12 bold) Coordinator

(Don‟t write names of lecturers or HOD)

External Examiner

Date: College Seal

121
COMPANY CERTIFICATE (if applicable)

122
 (Project Abstract page format)
Abstract (20bold, caps, centered)

Content (12, justified)

Note: Entire document should be with 1.5

line spacing and all paragraphs should start with 1 tab space.

123
 ACKNOWLEDGEMENT
(20, BOLD, ALL CAPS, CENTERED)

The acknowledgement should be in times new roman, 12 font with 1.5 line
spacing, justified.

124
 (Declaration page format)

DECLARATION (20 bold, centered, all caps)

Content (12, justified)

I hereby declare that the project entitled, “Title of the Project” done at place where the
project is done, has not been in any case duplicated to submit to any other university for the award
of any degree. To the best of my knowledge other than me, no one has submitted to any other
university.
The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted
as final semester project as part of our curriculum.

Name and Signature of the Student

125
 TABLE OF CONTENTS (20bold, caps, centered)

Should be generated automatically using word processing

software.
Chapter 1: Introduction 01(no bold)
1.1 Background 02(no bold)
1.2 Objectives ….
1.3 Purpose and Scope ….
1.2.1 Purpose ….
1.2.2 Scope
………………………………
…………………………………
Chapter 2: System Analysis
2.1 Existing System
2.2 Proposed System
2.3 Requirement Analysis
2.4 Hardware Requirements
2.5 Software Requirements
2.6 Justification of selection of Technology
Chapter 3: System Design
3.1 Module Division
3.2 Data Dictionary
3.3 ER Diagrams
3.4 DFD/UML Diagrams
Chapter 4: Implementation and Testing
4.1 Code (Place Core segments)
4.2 Testing Approach
4.2.1 Unit Testing (Test cases and Test Results)
4.2.2 Integration System (Test cases and Test Results)

Chapter 5: Results and Discussions (Output Screens)

Chapter 6: Conclusion and Future Work
Chapter 7: References

126
 List of Tables (20 bold, centered, Title Case)

Should be generated automatically using word processing

software.

127
 List of Figures (20 bold, centered, Title Case)

Should be generated automatically using word processing

software.

128
 (Project Introduction page format)
Chapter 1

Introduction (20 Bold, centered)

Content or text (12, justified)

Note: Introduction has to cover brief description of the project with minimum 4 pages.

129
 Chapter 2

System Analysis (20 bold, Centered)

Subheadings are as shown below with following format (16 bold, CAPS)
2.1 Existing System (16 Bold)
2.1.1 (14 bold, title case)
2.1.1.1 (12 bold, title case)

2.2 Proposed System

2.3 Requirement Analysis
2.4 Hardware Requirements
2.5 Software Requirements
2.6 Justification of Platform – (how h/w & s/w satisfying theproject)
Table 2.1: Caption

130
 Chapter 3

System Design (20 bold, centered)

Subheadings are as shown below with following format (16 bold, CAPS)
Specify figures as Fig 11.1 – caption
3.1 Module Division
3.2 Data Dictionary
3.3 E-R Diagrams
3.4 Data Flow Diagrams / UML

Note: write brief description at the bottom of all diagrams

Sample Figure

Fig. 3.1: Caption

131
 Chapter 4

Implementation and Testing (20 bold, centered)

4.1 Code (Place Core segments)
Content includes description about coding phase in your project (Font-12)
(* don’t include complete code ----- just description)
4.2 Testing Approach
Subheadings are as shown below with following format (16 bold, CAPS)
4.2.1 Unit Testing
4.2.2 Integration Testing
Note:

 Explain about above testing methods

 Explain how the above techniques are applied in your project
Provide Test plans, test cases, etc. relevant to your project

132
 Chapter 5

Results and Discussions (20 bold, centered)

Note: Place Screen Shots and write the functionality of each screen at the bottom

133
 Chapter 6

Conclusion and Future Work (20 bold, centered)

The conclusions can be summarized in a fairly short chapter around 300 words. Also include
limitations of your system and future scope (12, justified)

134
 Chapter 7

References (20 bold, centered)

Content (12, LEFT)

[1] Title of the book, Author

[2] Full URL of online references

[3]

* NOTE ABOUT PROJECT VIVA VOCE:

Student may be asked to write code for problem during VIVA to demonstrate his coding
capabilities and he/she may be asked to write any segment of coding used in the in the project. The
project can be done in group of at most four students. However, the length and depth of the project
should be justified for the projects done in group. A big project can be modularized and different
modules can be assigned as separate project to different students.

Marks Distribution: Semester V:

50 Marks Documentation: 50
marks Semester VI: 150 Marks
Documentation: 50 Marks:
Implementation and Viva Voce: 100 Marks

The plagiarism should be maintained as per the UGC guidelines.

135