Institute Of Innovation In Technology And Management Conduct of Summer Training: BCA Semester IV Objectives of Summer Training To expose the

e the students to the current environment. To establish the link between theory and practical. To apply concepts, tools and techniques of Software engineering on a real information system. To understand the functioning of any software organization. To know latest trends in the market.

University scheme for Summer Training & project As per the syllabi of BCA (Paper No BCA-353 of two credits), students of Semester IV are to carryout Summer Training for the duration of Eight Weeks and to submit a written report within Two Weeks of the commencement of Vth semester. Summer Training report shall be of 100 marks and shall wholly be evaluated by an internal committee comprising HOD, Summer Training Coordinator and respective guides. Scope of Summer Training & project

It is to be completed during the Summer vacation. Students are to use a real information system that exists it could be a system either from within IITM or an external organization. It is partly the responsibility of the students to find a relevant topic & organization for his/her project and decide it in consultation with the guide allocated to him/her. A team of two students shall work on one topic and submit a joint report. 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 interpedently by each student. Students are advised to retain one copy of their Summer Training report. The details regarding the project shall be communicated separately on the commencement of Vth semester.

Guidelines for students

It is compulsory for each and every student to undergo Summer Training. Summer Training takes place at the end of Semester IV. Students will be divided into groups and each group will be assigned a faculty in charge for support & guidance. Each student is required to keep continuous interactions with Faculty Incharge regarding the Project proceedings. Report once in a week to your Faculty Incharge personally. The Project Report after the last date of submission will not be accepted. Project Report will consist of 1 hard copy and CD

Methodology Methodology and activities that are to be performed to conduct the Summer Training Project are given in details in Appendix-A. Format & Final Report 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. Date 4th July 11
11th July 11 20th July11 10th Aug11 16th Aug11 18-25th Aug11 Formation of teams As stated Summer Training Project is to be conducted by a team of 2 students. Team composition and names of guides is given in Appendix- C. 1. All students of BCA-IV Sem 2. All IT faculty members Dr. Vikas Mehra (Director)

Activity Marks Commencement of Summer Training Completion & submission of activities under Chapter-1 Completion & submission of activities under Chapter-2 Completion & submission of activities under Chapter-3 Submission of final report to the respective guides Presentation and viva

Remarks

as per Appendix-A as per Appendix-B as per Appendix-C

METHODOLOGY FOR THE PROJECT WORK Chapter-1: Introduction This chapter should include the following aspects: This chapter should include the following aspects

Appendix-A

Description of organization: give brief description of the organization that you have selected for the study of information system and collection of data. Briefly describe organizational objectives, key result areas, organizational structure, and its functions/activities in reference to the information system under study. If the reference is outside the institute describe its nature of business, products etc. Data collection: for developing information system data is required in respect of input, output, storage and processing requirements. Data is also required in respect of entities involved in the system & their connectivity and flow of data between the entities. The data can be collected either through questionnaire, interview or any other technique. Describe method/ source of collection of data for each set of data Note: In the Training environment your guide will invariably act as the user of system and define the requirements of data. Project Planning: Give the plan of distribution of work amongst the team members giving name of task/activity, precedence/order (date-wise) in which these are performed and the name of the team member who has performed that task/activity. Present the above data in Gantt & other charts using MS Project based.

Chapter-2: System Analysis

Appendix-B

Description of Information System: Describe the functioning of information system under study in narrative form in details. Draw a functional Block Diagram to show generic input, output and connectivity/flows between various entities of the system. It must also include external/outside entities that interact with the organization to identify external source/sink of data/information. As an example, a block diagram for Billing Information System of a Departmental Store is shown in the figure below: Purchase Order Process Bill Process

Customer

Customer

Stock list

Price list

The analysis is to focus on the following activities (giving proper references of source of data): a) Identify the processes: this activity involves identifying processes included in the information system under study. Meaningful names are to be assigned to each process. In the above example, two processes are purchase order and bill. b) Identify the input to and output of each process: for each process identified in step (a), indentify input and output. Give meaningful names to each input and output. Conceptually, each process shall have at least one input and one output. Fro example, in the above example the input to purchase order process is purchase orders of customers and the output of bill process is invoice. c) Identify the data elements/ fields that are included in input and output: for each input & output identified in step (b), identify data elements connected with each. Catalogue of data elements is to be presented in tabular form. An example is given below: Input/ output name Purchase order Invoice Data elements Data, item code, item name, etc. Date, item code, item name, quantity, price, discount, name of company, terms and conditions etc.

d) Identify the procedures/rules/ mathematical relationships used for converting input into output: this is to facilitate the programmer to write a correct programme as per the policy of the organization. It is to be noted, the data which is included in the output and is not supplied by the input, is to be provided processing the input. As analysis of each output and input on these lines will facilitate in 4

identifying procedures/ rules/ mathematical relations required to be incorporated with the information system under study. For example in the above case, following aspects need to be described clearly: i. Formula for calculating for total amount charged for each item, gross amount and net amount ii. Tax policy, and iii. Discount policy. Note: as far as possible real procedures & policies in vogue are to be used. However, students may assume certain procedures but they must be clearly explained and included in project.

Chapter 3- Systems Requirements Specification (SRS)

Appendix-C

Based on the analysis and data presented in chapter-2, system requirement specifications are to be specified in this chapter focusing on the following activities (give proper references of source of data): Physical Specifications: explain relationship between various components (processes, input, output &entities) of the system using DFDs and ER diagram. Output Specications: it requires specification of detailed characteristics of contents (Fields) to be include in each Output Screen and Print layouts. Compile a list of data elements (comprising field name, field type , field sixe & description) for each output and present it I the tabular form. An example for Invoice in the above case is given below: OUTPUT NAME: INVOICE LINKED TO BILL PROCESS Field name Field type Field size Description Date Mm-dd-yyyy 10 Date of invoice Item code Alphanumeric 10 Unique code of each item Quantity Numeric 10 Quantity of each item Price Numeric 4,2 Price of each item up to 2 decimal places Amount Numeric 5,2 Amount of each item up to 2 decimal places Input specifications: it requires specification of detailed characteristics of contents (fields) to be included in each Input Screen. Compile a list of data elements (comprising field name, field type, field sixe & description) for each input and present it in the tabular form. An example for purchase order in the above case is given below INPUT NAME: PURCHASE OREDER LINKED TO PURCHASE ORDER POCESS Field name Field type Field size Description Date mm-dd-yyyy 10 Date of purchase order Item code Alphanumeric 10 Unique code of each item Quantity Numeric 10 Quantity of each item Validation Specifications: Describe the validation rules to be included for input/ output wherever required.

Database Specifications: a database may have one or more files/ tables. Specifications of each file/ table included in the database are to be tabulated with field name, type and size and description. In the case of billing information system above file specifications of stock list is given below:

FILE NAME: STOCK LIST LINKED TO PURCHASE ORDER PROCESS Field name Field type Field size Description Item code Alphanumeric 10 Unique code of each item Quantity Numeric 10 Quantity of each item Processing logic: Explain processing logic to convert input into output using programme flow chart.

FORMAT OF THE PROJECT REPORT FORMAT 1) The format for compilation of final report is given below: a. Title page b. Certificate c. Acknowledgements d. Table of contents e. List of tables f. List of figures g. List of symbols h. Body of the project report i. Appendices Title page 2) The format of the title page is attached as Annexure I. Certificate 3) The format of the certificate is attached as Annexure-II. A certificate by the student, guide and duly authenticated by the director is to be attached. Acknowledgement 4) I the acknowledgement page, the writer recognize his indebtness for guidance and assistance by the guide and other members of the faculty. Courtesy demands that he/ she also recognize specific contributions by other persons or institutions such as libraries and research foundations. Acknowledgement should be expressed simple, tastefully and tactfully duly signed above the name. Table of contents 5) The format of table of contents and list of tables/ figures/ symbols is attached as Annexure-III. Body Of The Project Report: Guidelines For Project Report Writing 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/ pare 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 not to be numbered. Subparas are to be numbered as (a), (b) (c) . sub paras are to be numbered as (i), (ii)..etc. c. Page specifications: i. Left margin ii. Right margin iii. Top margin iv. Bottom margin

: 1 inch : 1 inch : 1 inch : 1 inch

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 centre of the pages. e. Normal body text: i. Font size : 12, times new roman, double spacing, single side writing ii. Paragraphs heading font size: 12, times new roman, underlines 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: i. Table no-1 : file design for employee record ii. Figure no-1: data flow diagram g. Binding and Color Code of the Report: each student is to submit a written project report in spiral binding along with a CD. 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.

Annexure-I

Title of the Project Report (Font size=18)

Submitted in partial fulfillment of the requirements For the award of the degree of Bachelor of Computer Applications To Guru Gobind Singh Indraprastha University, Delhi

Guide: (Guide name)

Submitted By: Name Enrollment no. Course

Institute of Innovation in Technology and Management New Delhi-110058 Batch (2009-12)

10

Annexure-II Certificate
I, name & enrollment no. certify that the Summer Training project report entitled ___________________ done by me is an authentic work carried out by me at _____________________(name of the organization). The matter embodied in this project report has not been submitted earlier for the ward of any degree or diploma to the best of my knowledge and belief.

Name Signature of the student

Date:

Certified that the project report entitled __________________ done by the above student is completed under my guidance.

Signature of the Guide Date: Name of the Guide: Designation:

Countersigned Director

11

Annexure III FORMAT FOR TABLE OF CONTENTS TABLE OF CONTENTS S.NO 1. 2. 3. 4. 5. 6. 7. Topic Certificate Acknowledgement List of tables/ figures/ symbols Chapter-1: Introduction Chapter-2 : System Analysis Chapter-3 : System Design Appendices Page No.

FORMAT FOR LIST OF TABLES/ FIGURES/ SYMBOLS LIST OF TABLES TABLE NO. 1. 2. Title File design for Employee record File design for Personal details LIST OF FIGURES FIGURE NO. 1. 2. Title Data Flow Diagram Input Screen for Data Entry LIST OF SYMBOLS S. NO. 1. 2. SYMBOL S Kbps Nomenclature & Meaning Sigma Kilo bits per second Page No. Page No.

12