Final Year IGNOU-BCA Projects Reporting Guidelines: Sunil Ji Garg
Final Year IGNOU-BCA Projects Reporting Guidelines: Sunil Ji Garg
:Presenter:
Sunil Ji Garg
GM, UPTEC
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 drugstore to order medicines directly to the distributor on the distributors 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 Es
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 distributors 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
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.
C
A User Interaction Process
Course Data
DFD refinement
DFD Level is increased by refining processes by partitioning it more
User Name & Course Data Ticket Creation Status to User Data
Evaluates
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:
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.
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.
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 project-report and read it thoroughly before you go for VivaVoce.
THANK-YOU
OPEN FOR MORE QUESTIONS Find a copy of this presentation on http://www.uptecnet.com/pe/ignou.htm