Final Year IGNOU-BCA Projects
Reporting Guidelines
:Presenter:
Sunil Ji Garg
GM, UPTEC
YOU can ASK QUESTIONS during the Presentation Also.
AGENDA OF THIS TALK
• How to Document & Report Your
Project
• How to write the requirement analysis.
• How to make ER-DIAs and DFDs
• Building all steps of System
Development Life Cycle.
• Tips for VIVA-VOCE
TITLE OF PROJECT
Keep it simple and understandable.
For e.g. “Online Computer Hardware Store is
preferred over “Preparing a program for
buying and selling hardware using the client
server architecture on internet”.
Include the Key-Aspect:
For e.g. “Meta-tag based search system for an
information catalogue” is preferable over “File
search module”.
Include the platform name when relevant.
E.g. “Making a windows like GUI on an UNIX
terminal.
INTRODUCTION
Expand Your Title into these lines.
Explain the problem your project attends to
(For e.g. manual to computerised system
transaction)
Try relating to a real life situation.
Do not make it a pc. Of literary work with
flowery language.
Do not write a short note on IT scenario, stick
to project domain.
Do not copy the marketing literature of the
company where you did the project.
Explain scope of your work also.
Sample Introduction
Creating A Online Shop for Medicine Distribution
Online shopping is a procedure in which the introducing
companies gives information of their products on their
website. In the field of medicine distribution this could
be particularly useful since there is a wide range of
products, that are delivered to medicine stores as per
their day to day requirements.
By introducing this system it would be possible for a
drug-store to order medicines directly to the distributor
on the distributor’s website. He would also be able to
make payments and track the status of his deliveries.
By using this facility he would be able to get away with
intermediaries involved in distribution system.
PROJECT OBJECTIVES:
Remember that all solutions in life aim at
performing the three E’s
ECOMOMICAL
ERROR-FREE
EFFICIENT.
 Explain How your project attends to these.
Try relating to a real life situation.
Be specific about how these things are done
by quoting examples..
You can also detail your scope of work in
project objectives.
Do not write long article here. Use Bulleted
points.
Sample Objectives
• To create a system that makes it easier for a
drug-store to order a large set of medicines
at distributor’s website.
• To allow creation of purchase-orders online
with automatic quantity, price totaling along
with application of tax etc.
• To track the status of order and medicine
deliveries.
TOOLS/ENVIRONMENT
Segregate your tools/environment into
following headings:
• O/S PLATFORM
• DBMS TOOLS/ENV.
• PROGRAMMING TOOLS/ENV.
• DATA PREPARATION TOOLS
• SUPPORT UTILITIES AND
APPLICATIONS
SAMPLE TOOLS/ENVIRONMENT
•
•
•
•
•
Operating System: WINDOWS XP Professional
Programming Language: ASP, JAVASCRIPT
Database: SQL SERVER 7.0
Page Dev. Tool: FRONTPAGE/OFFICE XP
IIS 4.0 Webserver on Win/XP professional used
to publish pages
• Photoshop 7.0 and Gif-Animator used to create
web images.
• MSDN ref. Library
Steps of System Dev. Life Cycle
•
•
•
•
•
•
Investigation and Requirement Collection
Requirement & Risk Analysis
Architectural Design
Development and Debugging
Implementation and Testing
Maintenance and support
Project Management Model
Linear / Prototyping / Incremental / Spiral
/ Component Based
Be Prepared to answer a query related to
your project model with required justification.
For e.g it is better to use prototyping model
for a entirely new development where
requirements are not initially clear. Spiral
Model is good for development projects for a
specific customer.
Requirement Collection & Study
• Write how you went about collecting
various data from end users.
• Write about existing methodologies and
how you thought that your project
would be of help there.
• Write about the key requirements
explained by the user/studied by you.
• Write about any unique needs.
Sample Requirement Study
Online Tendering System
For this in a meeting with tender dept of
<customer> following specific requirements
were given.
• Earnest money deposit system could be by
credit card/draft with a status followup.
• Tender procedure was standard but tender
could be opened online by the participants
with authorisation codes.
REQUIREMENT ANALYSIS
Diagram and Description both is expected.
Write descriptive analysis with your
proposal to attend to the problem domain.
Discuss some other options if possible.
Human Computer Interface also needs to be
depicted.
Remember in a DFD depicts flow of data, not
the instructions to do a job.
For manual to computerised system
conversion you may draw DFD for both
manual and proposed computerised system
separately.
Upto 2nd/3rd Level DFD is usually desired.
Use E-R Diagrams for Database Intensive
projects.
Common DFD Mistake:
CORRECT
Request Form
Emp
Pay
Salary
Salary
Emp
WRONG
Salary Database
Take Request
Emp
Pay Sal.
Salary
Salary Database
Emp
Sample DFD (Examination System)
USER
EXAMINATION DEPT
Login
Admin
Application
Hall Ticket
Report
User Data
A
Login Check
Login Verif.
B
USER
Hall Ticket
Status
Hall Ticket
C
A – User Interaction Process
Course Data
B – Course Selection Process
C – Hall Ticket Generation Proc.
DFD refinement
• DFD Level is increased by refining processes
by partitioning it more
User Name &
Course Data
Ticket Creation
Status to User
Data
Hall Allotment
Logic
Ticket
Hall Data
Ticket Creation
Logic
E-R Diagram Concept
• Show Entities, Relationships,
Relationship Cardinality (1-1,1-N,N-N)
and modality (Optional/must). Depict
Entity attributes also.
Code
Counsellor
Course
Name
Evaluates
St.No.
Assignment
Here Counsellor Vs./Assignment cardinality is 1-Many.
It could be many to many for a study center
perspective. Modality for counsellor is 1 (Must) and
assignment is 0 (optional).
Architectural Design
• Data Centred, Data Flow, Layered
• Also depict this design with the help of diagram.
• Cover the design details up to your modules and
interaction between modules.
• Cover Module Description with parameters and
relationships between modules.
• Over all process logic shall also be explained
with relation to its implementation in design.
Module Description
This is generally an explanation of
circles in your last level of refinement
of DFD.
Basic functionality of each shall be
provided.
Program subroutine description may
also be required
Shall try to cover query and reporting
modules also.
Data Description
• Data Description:
– Column name, Type and description shall
be provided.
– Shall also include reasoning for type, size
and division for specific cases (For e.g.
FirstName, LastName).
– For Applications not using DBMS, input
and output parameters shall be explained
with boundary conditions. (For e.g. Text or
Binary Data)
Program Structure & Coding
• Program Structure:
– Advisable to provide a flow chart with
decision paths.
– Should map with basic requirements.
• Coding:
– Attach Full Listing.
– Verify correct variable and routine
names.
– Verify sufficient commenting of
modules and classes.
Output Reports
• Necessarily provide a list of all outputs
attached.
• Attach All Sample Reports with sample
data
• Give some samples with specific queries.
• Attach sample of display forms also.
• Ensure that Reports map to the
requirements model.
Testing Strategy Used
• Explain how would test each module with
by giving USE cases.
• Explain module level testing with boundary
values also.
• Explain how you tested after Integrating
modules.
• Give list of test cases for customer
evaluation that map to his requirement.
• Some Testing routines could be a part of
program code, highlight them.
Limitations and Constraints
• Limitations:
– Data-size related.
– No. of users related.
– No. of files related.
– File Formats.
• Constraints:
– Hardware Constraints like RAM, Processor
speed, line speed.
– Software constraints like plug-ins, dlls,
interaction with other applications
Future Applications
• Talk about project extensions possible.
• Talk about application of similar idea in some
other area. Stick to problem domain.
• Talk about possible changes in
technological/user options.
• Sample for Hospital Management:
–
–
–
–
–
Can be extended to keep patient’s bedside record.
Bed status checking on net.
Online Hospital drug store.
Patients record keeping for subsequent analysis.
Annual Health tests Management.
Bibilography & Conventions
• Give Details of reference books used.
• You can also refer websites.
• Prepare a list of acronyms and details
used in your project report.
• Reference to any other source like
electronic media, news media, CDs can
also be provided.
•
•
•
•
•
•
•
•
•
•
•
•
Sample
Project
List
Hospital Management System (VB/Oracle, ASP/Access)
Pathology Report generation (C++, VB, ASP, Java)
Encryption/Decryption for Email (VB, C++, VC++, Java)
Student/Teacher Collaboration (ASP, Java servlets)
Personal Income Tax Planner (ASP, Jscript, Java, VB, C++)
Trader sales register (VB/Oracle, ASP/Access, SQL-Server)
Airlines Boarding Pass System (VB/Oracle, ASP, C++)
Pre-Paid Taxi Management System (C++, VB, ASP, Jscript)
Menu-Recipe Management system (C++, VB, ASP)
Editor for a Unix Text Terminal (C++)
Departmental Document Management System (PERL, C++)
Automatic Stock Trigger Warning System (VB/Oracle, ASP
Access etc.)
Preparing for Viva-Voce
• Generate your own question set, around 50-100
and work them out.
• Revise your DFD and practice its explanation.
• Testing Points are a favorite question, prepare it
thoroughly.
• DBMS/RDBMS difference shall be clearly
understood.
• The project model should be clearly justifiable.
• Object Oriented Concept should be well prepared
with key points and examples.
• Be sure of every single word of your projectreport and read it thoroughly before you go for
Viva-Voce.
THANK-YOU
OPEN FOR MORE QUESTIONS
Find a copy of this presentation on
http://www.uptecnet.com/pe/ignou.htm