WNWS45
WNWS45
Objective
2. As per the syllabi of BCA (Paper No BCA-355 of 4 credits), students of Semester V are
to design and develop an application software in continuation with the summer training carried
out during BCA Semester IV on a real information system and to submit a written report. In this
case evaluation has two components, viz.
Paper No : BCA -355 (IT MINOR PROJECT)
Credits :4
Max Mark’s : 100
(a) Internal : 40 Marks
(b) External : 60 Marks
Time Duration : 12 Weeks (17th August-16th November ’2010)
Scope of Project
3. The SRS worked out during the summer training are to be converted into an application
using front & back-end tools during the Vth semester as a software project independently by
each student.
Methodology
5. Methodology and activities that are to be performed to conduct the summer training
project are given in details in Appendix-A.
Format & Final Report
6. The Guidelines for the format to be used for compilation of the project report are given in
Appendix-B. All students are to adhere to these guidelines.
Schedule of Submissions
Formation of Teams
8. As stated summer training project is to be conducted by a team of TWO students. Team
composition and names of guides is given in Appendix-C.
(Prof S Chaturvedi)
Director
Description of System: Give brief description of the organisation and the proposed information
system whose analytical study has been during semester IV summer training period.
System Requirement Submission Report (As per IEEE Format): The SRS worked out during
the summer training IVth semester has to be formally explained as per IEEE standard notation
for implementing the user requirement of the proposed system as per analysis done during two
months training period.
Physical Design: Explain relationship between various components (processes, input, output &
entities) of the system. Draw DFD’s or other relative diagrams. (As per the implemented system
design)
Database Design: Depending on the tool/package used, give contents of each file including
Field Name, Type, and Size & Description. Generate ER diagram and Tabular Data Dictionary
of the all supported data files & objects.(As per implemented database schema)
Interface Design:
(a) Output Design: Screen & Print layouts, i.e., the format and contents (fields) to be
included – along with the file to which it is linked.
(b) Input (Form or Screen) Design: For keying-in data. Give fields, format, codes to be
used, validation (error detection) requirements & the file to which it is linked.
Purpose: To carry out the activities of writing actual programmes, their debugging, testing and
validation. Following activities are to be carried out:
Describe what has been achieved vis-à-vis objectives & scope of the project. Is the application
developed by you ready for use or some bugs remain? Describe limitations and scope for future
development/improvement.
Appendix-B
(Refer Para 8)
Format
Title Page
Certificate
Acknowledgement
4. In the “Acknowledgement” page, the writer recognises his indebtedness for guidance and
assistance by the guide and other members of the faculty. Courtesy demands that he/she also
recognises specific contributions by other persons or institutions such as libraries and research
foundations. Acknowledgements should be expressed simply, tastefully, and tactfully duly
signed above the name.
Table of Contents
6. The guidelines for the Body of the Project Report (methodology) are detailed in
Appendix-A. Following aspects must be adhered to:
(a) Page Size: Good quality white A4 size executive bond paper should be used for
typing and duplication.
(b) Chapter/Para Numbering: The chapters are to be numbered as Chapter-1,
Chapter-2 etc. The heading/title of the chapter is to appear below the chapter number in
uppercase. Paragraphs are to be numbered as 1,2,3 etc in every chapter separately. Sub-
paras are to be numbered as 1.1, 1.2, 1.3----, 2.1, 2.2, 2.3-----etc. Sub-sub paras are to be
numbered as 1.11, 1.12, 1.13, 2.11, 2.12, 2.13 etc.
(d) Page Numbers: All text pages starting from Body of the Project Report as well
as program source code listings should be numbered at the bottom center of the pages.
(i) Font Size: 12, Times New Roman, Double Spacing, Single Side Writing.
(ii) Paragraphs Heading Font Size: 12, Times New Roman, Underlined
(iii) Page/Title Font Size: 14
(f) Table and Figure Number: Table and figure numbers are to be written at the
bottom of the table/ figure as given below:
(g) Binding & Color Code of the Report: Each team is to submit a joint written
project report in following format along with a project CD.
(i) Hard Bound Report
(ii) Background of the cover page – Dark Brown
(iii) Letters in Silver White
Appendices
7. The appendices are to be attached at the end of the report and to be numbered as
Appendix-A, Appendix-B etc right justified at the top of the page. Below the word Appendix
write in parenthesis “Refer Para No__”. The para number is to be the number in the body of text
where the reference of appendix is given. An appendix may have annexure (s). If there are
annexure, these are to be attached immediately after the said appendix. The annexures are to be
numbered as Annexure-I, Annexure-II etc.
Annexure-I
To
We, 1. (Name & Roll No) & 2. (Name & Roll No) certify that the Minor Project Report
organisation or of the Institute). The matter embodied in this project work has not been
submitted earlier for the award of any degree or diploma to the best of my knowledge and
belief.
Date:
Countersigned
Director
Annexure-III
TABLE OF CONTENTS
S No Topic Page No
1 Certificate -
2 Acknowledgements -
3 List of Tables/Figures/Symbols -
4 Chapter-1: Introduction
5 Chapter-2: System Analysis
6 Chapter-3: System Design
8 Appendices
LIST OF TABLES
LIST OF FIGURES
LIST OF SYMBOLS