IGNOU BCSP-64 Project Guideline

1.    CALENDAR FOR THE PROJECT

GUIDELINES FOR PROJECT FORMULATION

The project work constitutes a major component in most of the professional programmes and it is to be carried out with due care and should be executed with seriousness by the candidates.

TYPE OF PROJECT

As majority of the students are expected to work out a real life project in some industry/research and development laboratories/educational institutions/software companies, it is suggested that the project is to be chosen which should have some direct relevance in day-to-day activities of the candidates in his/her institution. Students are encouraged to work in the areas listed at the end. 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 Guide.

PROJECT PROPOSAL (SYNOPSIS)

The project proposal should be prepared in consultation with your guide. The project proposal should clearly state the project objectives and the environment of the proposed project to be undertaken. The project work should compulsorily include the software development. The project proposal should contain complete details in the following form:

1. Title of the Project
2. Introduction and Objectives of the Project
3. Project Category (RDBMS/OOPS/Networking/Multimedia/Artificial Intelligence/Expert Systems etc.)
4. Analysis (DFDs at least up to second level , ER Diagrams/ Class Diagrams/ Database Design etc. as per the project requirements).
5. A complete structure which includes:

– Number of modules and their description to provide an estimation of the student’s effort on the project.

– Data Structures as per the project requirements for all the modules.

– Process Logic of each module.

– Testing process to be used.

– Reports generation ( Mention tentative content of report)

6. Tools / Platform, Hardware and Software Requirement specifications
7. Are you doing this project for any Industry/Client? Mention Yes/No. If Yes, Mention the Name and Address of the Industry or Client
8. Future scope and further enhancement of the project.

Note: You are advised to see Auto and Video Program available on IGNOUSOCIS youtube channel. The list of web links of which is give on page number 17.

PROJECT PROPOSAL SUBMISSION AND APPROVAL

After finalising the topic and the selection of the guide, students should send the Project Proposal Proforma given on page no. 6 along with the synopsis and bio-data of the guide to The Regional Director of the Regional Centre concerned. Incomplete project proposals in any respect will be summarily rejected.

COMMUNICATION OF APPROVAL

Communication regarding the Approval / Non-approval of the project will be sent to you within four weeks after the receipt of the project proposal by the Regional Centre concerned.

RESUBMISSION OF THE PROJECT PROPOSAL IN CASE OF NON-APPROVAL

In case of non-approval, the suggestions for reformulating the project will be communicated to you. The revised project synopsis along with a new Performa, should be re-submitted along with a copy of the earlier synopsis and non-approval project proposal Performa in the next slot. For example, if the student submitted the synopsis during the 1st April to 30th June slot and is not approved due to some reasons, s/he is eligible to resubmit the revised project synopsis only during the next slot i.e., 1st October to 31st December. These guidelines are applicable for earlier batch students also whose project work is pending.

ELIGIBILITY OF PROJECT GUIDE

1. A person having Ph.D./M.Tech. in Computer Science.

OR

2. A person having B.E/B.Tech (Computer Science), MCA, M.Sc (Computer Science) with minimum 2 years experience in Industry / Teaching.

PROJECT REPORT FORMULATION

ITEMS TO BE INCLUDED IN THE PROJECT REPORT

The following items should be included in the Project Report:

1. The project report must contain the following:

• Introduction

• Objectives

• Tools/Environment Used

• Analysis Document (This should include SRS in proper structure based on Software Engineering concepts, E-R diagrams/Class diagrams/any related diagrams (if the former are not applicable), Data flow diagrams/other similar diagrams (if the former is not applicable), Data dictionary)

• Design Document (Modularization details, Data integrity & constraints including database design, Procedural design, User interface design)

• Program code (Complete code (well indented)/Detailed specification instead of code*, Comments & Description. The program code should always be developed in such a way that it includes complete error handling, passing of parameters as required, placement of procedure/function statements as needed.)

• Testing (Test case designs are to be included separately for Unit testing, Integration testing, System testing; Reports of the outcome of Unit testing, Integration testing, System testing are to be included separately. Also, details of debugging and code improvement are to be included.)

• Input and Output Screens

• Implementation of Security for the Software developed (In case, you have set up a User Name and Password for your software, you should ensure the security of User Name and Password during transmission to server)

• Limitations of the Project

• Future Application of the Project

• Bibliography

*Students who have done their project for any organization are permitted to attach detailed
algorithm/specification instead of code, in case, the organization doesn’t permit them to attach the code.
Student needs to attach letter in the project report from the Project Manager of the project in the
organization that they are not permitting student to attach the code. In the absence of such letter, the
student needs to attach the code compulsorily.

The project report should be hard bound; should consist of a Contents page; all pages of report should be numbered; content should be well organized in a meaningful manner; printouts of text & screen layouts should be original and should not be xeroxed)

2. Original copy of the Approved Project Proposal Proforma, Synopsis and Guide‟s Bio-data.
3. Certificate of Originality (Format given on page no. 13).
4. The Project Report may be about 50 to 80 double spaced A-4 size typed pages (excluding program code). However,10% variation on either side is permissible.

SUBMISSION OF PROJECT REPORT

Only one copy of the project report is to be submitted to the following address by registered insured post: Regional Director, Concerned Regional Centre by the date mentioned in the Calendar for the project (refer to page-3).

TYPE OF 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 at the end (Refer page no.15). 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. If approved, the student can commence working on it and complete it.

PROJECT EVALUATION

The Project Report is evaluated for 150 marks and the Viva-Voce is for 50 marks. To be declared successful, the student should secure at least 40% marks separately in both project report evaluation (i.e.60/150) and viva-voce (i.e.20/50). Students will be duly intimated about the schedule of viva-voce by a letter from the respective Regional Centre. An unsuccessful student can either submit the same project after following comments on the assessment sheet or s/he can do a different project. Always, ensure that the BCSP-064 project guidelines are followed.

Unfair cases of copied versions of the project synopsis and project reports will be sent to Unfair Means Committee of IGNOU for action.

RESUBMISSION OF THE BCA PROJECT IN CASE OF FAILED STUDENTS

If the student is unsuccessful in the project, s/he should „re-do‟ the whole cycle, right from the submission of the project synopsis. Students are advised to select a new topic for the project and should prepare and submit the project synopsis to the Regional Centre concerned as per the project guidelines. There are no separate slots for the submission of the project synopsis / project reports for the failed students. Respective submissions of the project synopsis and the project reports should be done strictly as per the “calendar for the BCA project” given in the project guidelines. Along with the resubmission of the project report, the student is required to remit the pro-rata fee (subject to change as per university rule – contact your concerned Regional Centre for necessary update). The fee should be remitted to the Regional Centre at the time of resubmission of the project report by the way of Demand Draft favouring IGNOU and payable at the city where your Regional Centre is located.

ENQUIRIES

Enquiries regarding the Project Report and Viva-Voce should be addressed to the Regional Director,
Concerned Regional Centre. In all correspondence, please quote your Enrolment No.

IMPORTANT POINTS WHILE PREPARING THE PROJECT REPORT

1. The Project Report should be submitted in A-4 size typed in double space. The Project Report should be hard bound.
2. Ensure that it contains the following:

• Project Proposal Proforma. All the items should be filled. The signatures of both student and Guide should be present.

• Project Synopsis. Both Guide and student should sign on the Project Synopsis. Guide‟s Bio data. The Biodata should consist of signature of the Guide. Certificate of Originality (Format given on Page no.13)

• All signatures should be accompanied by the date of signature.
• It should include all items mentioned in Section IV.

3. If any project report is received in the absence of the items listed above, it will be rejected and returned to students for compliance. Also, violation of Project Guidelines may lead to rejection of the Project .
4. Only One hard bound original copy of the project report is to be submitted to „The Regional Director, Concerned Regional Centre‟ by registered insured post. One copy of the same Project Report is to be retained with the student and the student is supposed to carry his copy while appearing for viva voce. Spiral binding of Project Report is not permitted.

5. Xerox copy of the project report is not acceptable.
6. Not more than one student is permitted to work on a Project.
7. If the title of the Project differs from the title mentioned in the Project Proposal, the Project Report will be rejected and will be returned back to the student.
8. Kindly mention on the top of the envelope “BCA PROJECT REPORT (BCSP-064)”. This will facilitate sorting out project reports at the Regional Centre.
9. The envelope containing the remuneration form for the Project Guide duly signed by the Guide and the student, should be sent to “Regional Director, Concerned Regional Centre.”
10. In case, students require any letter from the University for doing a project in any organization, they may request the Regional Director of the concerned Regional centre for the issuance of the same in the format indicated under Project Trainee in this document. (Refer to Page number : 15).

LIST OF BROAD AREAS OF APPLICATION AND RELATED TOOLS