B.Sc.I.T.

Black Book Sem 6 Template Reference

• 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
The dissertation and viva voce in Semester VI.
• The documentation should use tools like star UML, Visuo for windows, Rational Rose for design
• The documentation should be spiral bound for semester V and
The entire documentation should be hard bound during semester VI
• Title Should be in the middle for each page heading
For e,g CHAPTER 1: INTRODUCTION
• 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

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 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:
o Semester V: 50 Marks
▪ Documentation: 50 marks
o Semester VI: 150 Marks
▪ Documentation: 50 Marks:
▪ Implementation and Viva Voce: 100 Marks
• The plagiarism should be maintained as per the UGC guidelines.
 Objectives
1. Describe the Systems Development Life Cycle (SDLC).
2. Evaluate systems requirements.
3. Complete a problem definition.
4. Determine how to collect information to determine requirements.
5. Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time feasibility,
and Operational feasibility for the project.
6. Work on data collection methods for fact-finding.
7. Construct and evaluate data flow diagrams.
8. Construct and evaluate data dictionaries.
9. Evaluate methods of process description to include structured English, decision tables, and decision
trees.
10. Evaluate alternative tools for the analysis process.
11. Create and evaluate such alternative graphical tools as systems flow charts and state transition
diagrams.
12. Decide the S/W requirement specifications and H/W requirement specifications.
13. Plan the systems design phase of the SDLC.
14. Distinguish between logical and physical design requirements.
15. Design and evaluate system outputs.
16. Design and evaluate systems inputs.
17. Design and evaluate validity checks for input data.
18. Design and evaluate user interfaces for input.
19. Design and evaluate file structures to include the use of indexes.
20. Estimate storage requirements.
21. Explain the various file update processes based on the standard file organizations.
22. Decide various data structures.
23. Construct and evaluate entity-relationship (ER) diagrams for RDBMS related projects.
24. Perform normalization for the unnormalized tables for RDBMS related projects.
25. Perform project cost estimates using various techniques.
26. Schedule projects using both GANTT and PERT charts.
27. Perform coding for the project.
28. Documentation requirements and prepare and evaluate systems documentation.
29. Perform various systems testing techniques/strategies to include the phases of testing.
30. Systems implementation and its key problems.
31. Generate various reports.
32. Be able to prepare and evaluate a final report.
33. Brief the maintenance procedures and the role of configuration management in operations.
34. To decide the future scope and further enhancement of the system.
35. Plan for several appendices to be placed in support with the project report documentation.
36. Work effectively as an individual or as a team member to produce correct, efficient, well-organized,
and documented programs in a reasonable time.
37. Recognize problems that are amenable to computer solutions and knowledge of the tools necessary for
solving such problems.
38. Develop the ability to assess the implications of work performed.
39. Get good exposure and command in one or more application areas and on the software.
40. Develop quality software using the software engineering principles.
41. Develop the ability to communicate effectively.
Project Report
1. Title Page
(Appendix 1)
2. Original Copy of the Approved Proforma of the Project Proposal
(Appendix 2)
3. Certificate of Authenticated work
(Appendix 3)
4. Abstract
(Appendix 4)
Background, Project Aims and Main Achievements
(one/two short paragraphs (100-150 words total))
5. Acknowledgement
(Appendix 5)
Express student’s gratitude to those who have helped in the project preparation
6. Declaration
(Appendix 6)
7. Table of Contents
Should be generated automatically using word processing software
8. List of Tables
9. List of Figures
Include all Figures, Graphs, Charts whatever applicable along with Pg Nos.
CHAPTER 1: INTRODUCTION (Min 4 Pages)
1.1 Background
Summarize existing work in the area
1.2 Objectives (30 /40 words)
1.3.1 Purpose
why this project is being done, How the project could improve the system its significance and
theoretical framework
1.3.2 Scope
Methodology, Assumptions, Limitations, Main Issues and Main Functions
1.3.3 Applicability
Direct and indirect applications of the work
How this project will serve the computer world and people
1.4Achievements
What knowledge the student achieved after the completion of the work Contributions the
project has made to the chosen area
Goals achieved
(Goals may be partially, fully achieved or exceeded.)
1.5 Organisation of Report
Overview of what is to come in the project report.

CHAPTER 2 : SURVEY OF TECHNOLOGIES

Students awareness and understanding of Available Technologies related to the topic of the project
Detail of all the related technologies that are necessary to complete the project. Technologies
available in the chosen area and its comparative study
Table 2.1 : Comparative Study

Why the student selected the technology for the completion of the objectives of the project
CHAPTER 3: REQUIREMENTS AND SYSTEM ANALYSIS
3.1 Problem Definition
3.2 Feasibility Study
Economic
Technical
Behavioral
3.3 Existing System (16 Bold)
3.4 Proposed System
3.5 Requirements Analysis and Specification
3.6 Hardware Requirements
Equipment, Graphics card, numeric co-processor, mouse, disk capacity, Ram Capacity etc
3.7 Software Requirements
Operating system, the compiler, testing tools, linker, and the libraries etc.
necessary to compile, link and install the software must be listed
3.8 Work Breakdown Structure (WBS)
3.9 Planning and Scheduling
Constraints
Resources
Gantt Chart and Program Evaluation Review Technique (PERT)
3.10 Justification of Platform – (how h/w & s/w satisfying the project)
3.11 Preliminary Product Description
(Initial, High-level overview of software product/system)
Requirements, Objectives, Functions and Operations of the new system
3.12 Conceptual Models (System Flowcharts, Object Oriented diagrams, Waterfall, Spiral)
CHAPTER 4 : SYSTEM DESIGN
Screen Layouts
Business Rules
Process Diagrams
Pseudo Code
4.1 Module Division
4.1.1 Basic Modules
Briefly describe all modules and functionality
4.1.2 Data Design
4.1.2.1 Schema Design
4.1.2.2 Data Integrity and Constraints
4.1.3 Procedural Design
4.1.1 Logic Diagrams
Control Flow Chart, Process Diagrams
4.1.2 Data Structures
4.1.3 Algorithms Design
Input Data, Output Data, Logic of processes, Design and working of algorithms
4.1.7 User interface design
User, task, environment analysis and mapping requirements to develop UI
Internal, external component and architecture
Rough Pictorial Views of UI and its components
4.1.8 Security Issues
Issues and to avoid security problems
Security Policy plans and architecture
4.1.9 Test Cases Design
Conditions to ensure correct working
4.2 Data Dictionary (Schema Design, Data Integrity and Constraints)
4.3 E-R Diagrams
4.4 UML Diagrams (Any software can be used like star UML, Visio or Rational Rose)
(Data Flow, Class, Usecase, Sequence, Activity, Component, Deployment)
CHAPTER 5: IMPLEMENTATION AND TESTING
5.1 Implementation Approaches
Implementation Plan and Standards
5.2 Coding Details and Code Efficiency
Include Code with comments to explain the work of code but not full source code but,
Only important codes where comments should explain why it does and in specified way it does.
It can be associated with output of program to explain the code
a. Algorithms
b. Applets Code
c. Forms Code
5.2.1 Code Efficiency
Explain how the codes are efficient and optimizations have been handled
5.3 Testing Approach
It should follow scheme mentioned in system design chapter and follow model like
Category Partition or State machine based.
5.3.1 Unit Testing
Testing a unit or module as a whole
Interactions of many functions but confine the test within one module
5.3.2 Integrated Testing
All module together into special testing environment that checks for
Errors, Bugs and Interoperability
It includes test for entire application, limits of application and features
5.3.3 Beta Testing
5.4 Modifications and Improvements
After finishing testing to resolve the bugs and errors source code is modified to improve the system
Define what modifications are done and how they are implemented to improve the system
5.5 Test Cases

CHAPTER 6: RESULTS AND DISCUSSION

6.1 Test Reports
Test Results and Reports that will show project is capable of facing any problematic situation
And it works in different conditions
6.2 User Documentation
Define the Working,Functions,Components with screenshots of the software
CHAPTER 7: CONCLUSIONS
7.1 Conclusion (2 or 3 pages)
7.1.1 Significance of the System
7.2 Limitations of the System
During testing limitations and criticism that were not able to modify and accepted
7.3 Future Scope of the Project
New Areas of investigation
Current Work part that was not completed due to time constraints and / or problems encountered
References
Acknowledge the work of others used or adapted in your own project
Which provided background or context to the project
Citiation is mandatory
Citations typically include details such as the author(s), title of the work, publication date,
publisher (for books), journal name (for articles), page numbers

Glossary
If any acronyms, abbreviations, symbols, or uncommon terms in the project report is used 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.
 Appendix 1
(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 INFORMATION TECHNOLOGY(12 BOLD, CAPS)

COLLEGE NAME (14 BOLD, CAPS)
(Affiliated to University of Mumbai) (12, Title case, bold, italic)
CITY, PIN CODE(12 bold, CAPS)
MAHARASHTRA (12 bold, CAPS)
YEAR (12 bold)
 Appendix 2
PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

(Note: All entries of the proforma of approval should be filled up with appropriate and
complete information. Incomplete proforma of approval in any respect will be summarily
rejected.)

PNR No.: …………………… Seat 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 Coordinator

Date: …………………
 Appendix 3
COLLEGE NAME (14 BOLD, CAPS)
(Affiliated to University of Mumbai) (13, bold, italic)
CITY-MAHARASHTRA-PINCODE(13 bold, CAPS)

DEPARTMENT OF INFORMATION TECHNOLOGY (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 University of Mumbai. (12, times new roman, justified)

Internal Guide (12 bold) Coordinator

External Examiner

Date: College Seal

COMPANY CERTIFICATE (if applicable)
 Appendix 4
(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.
 Appendix 5
ACKNOWLEDGEMENT
(20, BOLD, ALL CAPS, CENTERED)

The acknowledgement should be in times new roman, 12 font with 1.5 line spacing,
justified.
 Appendix 6
(Declaration page format)
DECLARATION (20 bold, centered, allcaps)

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

 TABLE OF CONTENTS (20bold, caps, centered)

Should be generated automatically using word processing software.

For e,g

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
1.3.3 Applicability

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
3.5 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
 List of Tables (20 bold, centered, Title Case)

Should be generated automatically using word processing software.

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

Should be generated automatically using word processing software.

 (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.
 Chapter 2:
Survey Of Technoologies
 Chapter 3

System Analysis (20 bold, Centered)

Subheadings are as shown below with following format (16 bold, CAPS)

3.1 Existing System (16 Bold)

3.1.1 (14 bold, title case)
3.1.1.1 (12 bold, title case)
3.2 Proposed System
3.3 Requirement Analysis
3.4 Hardware Requirements
3.5 Software Requirements
3.6 Justification of Platform – (how h/w & s/w satisfying the project)

Table 3.1: Caption

 Chapter 4

System Design (20 bold, centered)

Subheadings are as shown below with following format (16 bold, CAPS)
Specify figures as Fig 11.1 – caption
4.1 Module Division
4.2 Data Dictionary
4.3 E-R Diagrams
4.4 Data Flow Diagrams
4.5 UML Diagrams

Note: write brief description at the bottom of all diagrams

Sample Figure

Fig. 4.1: Caption

 Chapter 5
Implementation and Testing (20 bold, centered)
5.1 Code (Place Core segments)
Content includes description about coding phase in your project (Font-12)
(* don’t include complete code-----just description)
5.2 Testing Approach
Subheadings are as shown below with following format (16 bold, CAPS)
5.2.1 Unit Testing
5.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
 Chapter 5
Results and Discussions (20 bold, centered)
Note: Place Screen Shots and write the functionality of each screen at the bottom
 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)
 Chapter 7
References (20 bold, centered)
Content (12, LEFT)
[1] Title of the book, Author
[2] Full URL of online references
[3] ------------