PROJECT

The Basics
TYBSc IT
 What is it?
• A software project is to be done part of
the T.Y. BSc IT curriculum.
• Project is of 200 marks
o 100 marks for documentation
o 100 marks for actual project
 50% credit is for project quality and innovative
technology and automation used
 50% is based on presentation, Viva.
 Content
• The deliverables at the end are
o The code
o The document
o Power point presentation
 Where should it be done?
• A software project can be coded at :
o At the project site where the project was
allocated
o At home
o At the college
 How many in a group?
• Every student can take up an individual
project
• Maximum 2 in a team is permissible
 Nature of Project
• The software project must be a
LIVE PROJECT
• The project need not be done through a
software company.
• It can be an independent idea, but should be
approved by a company that it will be
accepted and implemented.
• Company should certify that student has
successfully completed the project
 Nature of Project
• Type of applications that can be explored are:
o Banking
o Financial Institutions
o Coaching institutes
o Hotel management
o Document management
o Custodial services
o Store management
o Inventory management
o Workshop management
o Order tracking systems
o School administration
o Library management
o Retail management
o Super market
o Credit / Debit card management
 Nature of Project
o University Management
o Clinical/ Hospital management
o Share accounting
o Scheduling
o Reception Desk management
o Knowledge management
o Telephone related services
o Automobile shop floor management
o Automobile stock/marketing management
o Chemicals management
o Medical store management…..
The list goes on and on….
 Software recommended
• The student is free to choose a software as per the
nature of the project.
• As a foresight it is recommended that atleast a basic
backend of MS Access and front end of Visual Basic/
VB.net/C#/ JSP/ ASP should be implemented.
• Projects based on systems where database and
front end is not applicable, should be preferably
coded in Java platform eg: Chat server, MMS
messaging
• Technologies of the higher order welcome but at
your own risk to be ready for the self learning
experience.
 Documentation- Number of copies
• The documentation must be hard bound with
black cover and title must be golden
embossed.
• 1 copy is submitted to the college
• 1 copy will be signed by the external examiner
will the student's copy for reference.
• For a team of 2, one individual copy each and
1 joint common copy for the college will do.
 Outline of Documentation
• Title page that must be printed in gold
embossing on the top black cover of the
project.
• College certificate page
• Company Certificate Page
• Acknowledgements
• Synopsis
• Table of contents
 Outline of Documentation
• Chapter 1
o Organizational profile
o Existing backgroundsystem
o Problem definition
o Solution strategy
o Proposed system
o Objectives
o Beneficiaries
 Outline of Documentation
• Chapter 2- Feasibility study &
Requirement specifications
o Software/Hardware feasibility
o Time schedule feasibility
o Economic/ Other factors feasibility
o SDLC methodology used
o Gantt Chart
 Outline of Documentation
• Chapter 3- Design
o Entity Relationship Diagram
o Context Level diagram
o Level 0 to n DFD
o System flow
o Structure chart
 Symbols used in ERD
• Entity Relationship diagram
ERD
Notations for DFD
Context Level to levels of DFD
DFD
Numbering DFDs
0-Level DFD/ Context Level
Diagram
Level 1 DFD
Complete DFD
 Outline of Documentation
• Chapter 4 –Coding
o Menu Tree (if any)
o Event Listing
o Table listing
o Program Listing –with purpose of every program along with specs
o Snapshots of Interfaces.
 Splash form (Login form) – in color
 Menu form (MDI) – in color
 Forms/ Interface screens – in color
 The coding can be listed for every screen
 If coding is too long/complicated then it may be included in a CD and
sample code may be provided with certain important forms
 Reports Listing
o The navigation can be explained.
 Documentation
• Chapter 5- Testing and implementation
o Test cases used can be listed with the
output generated
o The debugging summary may be mentioned
o Flaws in design/ code rectified and
implemented may be summarized
o Shortcomings/ limitations may be listed
 Documentation
• Chapter 6- Conclusions
o Summary of project and learning experience
o Enhancements possible if any
o Other areas of application for the product
o Futuristic approach
 Contents of PPT
• Synopsis
• Organizational profile
• Existing background/system
• Problem definition
• Solution strategy
• Proposed system
 Contents of PPT
• Entity Relationship diagram
• Context Level diagram
• Level 0 to n DFD
• System flow
• Structure chart
 Contents of PPT
• If code not permitted by the company then
• Snapshots of Interfaces.
o Splash form (Login form)
o Menu form (MDI)
o Forms/ Interface screens
o Reports
 Contents of PPT
• Conclusions
• Followed by live demo….
 Best of Luck

Thank You