Summer Training

Summer Training Project Guidelines Objective:

All the students enrolled for BCA Programme, have to undergo compulsory summer training/ Project of minimum 06weeks in an organization in the IT field. The aim of the project is to give the students an integrated experience in solving a real-life problem by applying knowledge and skills gained on completion of theory papers and in-house practical papers during BCA course. It provides an occasion for students to realize the importance of resource and time management, ownership of task towards deliverables, innovation and efficiency in the task management. It also provides a good opportunity for students to build, enhance and sustain high levels of professional conduct and performance and evolves a problem solver frame of mind in students at early stage. It also prepares students for taking up responsible assignments in the corporate establishment.

General Guidelines:

1. The project should be original, of real-life value, and not copied from existing material from any source. Astudent should ensure that he understands what is expected by preparing a requirement document of his understanding and get it reviewed by the guide.

2. Design document should also be reviewed and code should also be peer reviewed.

3. A user manual has to be prepared and reviewed.

4. Testing has to be thorough and at various levels, followed by an acceptance test based on the requirement document and user manual.

5. Students should follow the steps as discussed in Software Development Life Cycle while writing dissertation and use Software Engineering Methodologies for development of deliverables, mere programming will not be sufficient. Students must note that interviewers for job are often more interested in the problem solved, alternatives that could have been tried and the benefits derived from the developed application, rather than just implementation details.

6. One Project will be submitted only by one student. However, if the nature of the project is very big & large enough to be divided in different independent big modules having an estimated required effort of minimum 06weeks to be developed by one person, can be taken up and designed in such a way that every student will be responsible for one module and will submit only that specific module as it were a complete software project.

7. 7. Every student has to get his / her synopsis approved from the guide.

8. The synopsis must be brief i.e., not more that 4-6 pages. It must address details like (however, students may follow the SRS format of IEEE for writing Synopsis).

a. Name / title of the project b. Statement about the problem c. Why the Particular topic is chosen? It must address Present State of the Art.

d. Objective and scope of the project e. Analysis, Design, Development & Testing Methodology f. H/W & S/W to be used g. Testing Technologies to be used h. What contribution / value addition would the project make i. Limitations / constraints of the project j. Conclusion, Future Scope for Modification k. References and Bibliography.

9. After approval of the Synopsis, Students will need to give Two Presentations / Demonstration, as per the schedule fixed by their respective Institutions or University. First Presentation will ideally be given after Design phase is over. Second should be given when System Testing is over. First Presentation (Summer Training) should be given in the first month. Second Presentation (Projects) is in second month. Final Project reports should be given latest by the end of the third month of the semester.

10. Summer Training report has to be submitted by 31st October of every academic year.

11. The student will submit his/her project report/thesis in the prescribed format, as given hereunder, after the second presentation. The project report/thesis should include:

a. ONE hard copy (Maroon color with golden print) of the project report / thesis.

b. Soft copy of project on CD including all resource code/ compiled binary code and the manuscript in MS-Word document format.

12. Note the following guidelines with respect to Preparation of the Documentation. Please note that documentation is meant for other people, and hence it must be self-explanatory, in all respect.

12.1 The sequence of the Pages in the Project Report will be as follows:

1. One Transparency Sheet

2. Title Page (Strictly as per the sample supplied)

3. Institute’s Certificate

4. Company’s Certificate

5. Candidate Declaration of originality of work

6. Acknowledgement.

7. Abstract

8. List of Figures (Strictly as per the sample supplied)

9. List of Tables (Strictly as per the sample supplied)

10. List of Abbreviations (Strictly as per the sample supplied)

11. Contents (Strictly as per the sample supplied) and then body of the dissertation according to the content.

12.2 The pages coming under the preview of the CONTENTS will only be numbered in the BOTTOM of the Page Centrally Aligned.

12.3 ONE Hardbound Copies (One Original and Two Xerox) will be submitted with the Institute out of which one will be given back to the candidate. All the students are required to follow the same binding format in maroon color with back quote mentioning title of the project, name of the student and year.

12.4 At the end of the Project Report Two White blank sheets must be attached.

12.5 At the beginning of each chapter one blank page (Strictly as per the sample supplied) must be attached. These pages will neither be numbered nor counted in total numbering of pages. They will only indicate the beginning of a New Chapter with its learning objectives.

12.6 Font size of the documentation will be 12 Times New Roman and the pages will be one and half line spaced. The page margin will be as under: - Top – 1 inch, Bottom – 1 inch, Left – 1.5 inch, Right – 1 inch.

12.7 Kindly note that all-methodological details and theoretical aspects must be written in students’ own words. Copying from books or other students will not be accepted, in any case.

All students are informed not to write definition of various concepts in index, mention the topics w. r.

t. to your project (i.e., how various concepts have been implemented in the project) * No detailed theories required TEMPLATE FOR CHAPTER SCHEME C O N T E N T S (font size -18) CHAPTER 1: PROBLEM FORMULATION Page No.

1.1 Introduction about the Company 1.2 Introduction about the Problem 1.3 Present State of the Art 1.4 Need of Computerization 1.5 Proposed Software / Project 1.6 Importance of the work CHAPTER 2: SYSTEM ANALYSIS Page No.

2.1 Feasibility Study 2.1.1 Technical Feasibility 2.1.2 Economic Feasibility 2.1.3 Operational Feasibility 2.1.4 Other Feasibility Dimensions 2.2 Analysis Methodology 2.3 Choice of the Platforms 2.3.1 S/W used 2.3.1 H/W used CHAPTER 3: SYSTEM DESIGN# Page No.

3.1 Design Methodology 3.2 Database Design 3.2.1 ERD 3.2.2 DFD 3.3 Input Design 3.4 Output Design 3.5 Code Design and Development CHAPTER 4: TESTING AND IMPLEMENTATION## Page No.

4.1 Testing Methodology 4.1.1 Unit Testing 4.1.2 Module Testing 4.1.3 Integration Testing 4.1.4 System Testing 4.1.5 White Box / Black Box Testing 4.1.6 Acceptance Testing 4.2 Test Data & Test Cases 4.3 Test Reports and Debugging 4.4 Implementation Manual 4.5 Implementation 4.6 Users’ Training 4.6 Post Implementation Maintenance CHAPTER 5: CONCLUSION AND REFERENCES Page No.

5.1 Conclusion 5.2 System Specifications 5.2.1 H/W Requirement 5.2.2 S/W Requirement 5.3 Limitations of the System 5.4 Future Scope for Modification 5.5