SUMMER TRAINING PROJECT

BCA - 353

Objective
To apply theoretical concepts, tools & techniques of Software Engineering on a real information system.

It is planned to link and extend the work done in the summer training with the project work that is to be done during the semester.

University Scheme for Summer Training & Project

Summer Training (BCA 353) Credits : 2 Duration : Eight Weeks Marks : 100 Minor Project (BCA-355) Credits : 4 Evaluation Scheme: (a) (b) External : 60 Marks Internal : 40 Marks

Scope of Summer Training & Project

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 independently by each student.

Schedule of Submissions
To be Completed by Date Activity Marks Allotted Remarks

Briefing about the Summer Training Finalisation of Topic Commencement of Summer Training at the Institute 12th July 2011 Completion & Submission of activities Under Chapter-1 26th July 2011 Completion & Submission of activities Under Chapter-2 11th August Completion & Submission of activities 2011 Under Chapter-3 26th August 2011 Submission of Final Report (One hard copy & CD) to the respective guides 29-31st August Presentation & Viva before the 2011 Committee Total Marks

16th June 2011 21th June 2011 22st June 2011

10 15 25 10 40 100

As per AppendixA. As per AppendixA. As per AppendixA. As per AppendixA & B.

SUMMARY OF LIST OF ENCLOSURES

Chapter-1: Introduction 1.1 Description of Organisation:
1.1.1 General description 1.1.2 Organisational objectives, 1.1.3 Key Result Areas (KRAs), 1.1.4 Organisational structure, 1.1.5 Functions/activities of organization in the information system under study.

reference

to

Chapter 1 (contd..)
1.2Data Collection:
1.2.1Inputs 1.2.2Outputs 1.2.3Storage and processing requirements 1.2.4Entities in the system & their connectivity/linkages 1.2.5Flow of data between the entities 1.2.6Description of method/source of collection of data for each set of data 1.2.6.1 Questionnaire 1.2.6.2 Interview 1.2.6.3 Document analysis 1.2.6.4 Internet.

Chapter 1 (contd..)
1.3. Project Planning:
1.3.1 Plan of distribution of work amongst the team members as follows: 1.3.2 Name of task/activity, 1.3.3 Precedence/order (date-wise) in which these are performed 1.3.4 The name of the team member who has performed that task/activity. 1.3.5 Gantt & other charts using MS Project

Chapter 2
System Analysis

2.1 Description of Information System:

2.1.1 Description of the functioning of information system under study in narrative form in details. Functional Block Diagram . 2.1.2 List of Processes included in the information system under study. 2.1.3 List of Input & Output for each process identified 2.1.4 List of data elements connected with each process identified 2.1.5 Catalogue of data elements is to be presented in tabular form

2.2 Procedures/rules/mathematical relationships used for converting input into output

2.2.1 Decision tree/Decision table or both .

As an example, a block diagram for Billing Information System of a Departmental Store is shown in the figure below:
Purchase Order Purchase Purchase Order Customer Order Item Details with Details Process Bill Process Invoice

Customer

Verify Stock Availability

Verified Details Stock List

Price of Items Price List

The analysis is to focus on the following activities (giving proper references of source of data): Identify the Processes Identify the Input to & Output of each process: Identify the data elements/fields that are included in Input and Output:

Input/Output Data Elements Name Purchase Date, Item Code, Item Name, Quantity. Any other Labels to Order be included. Invoice Date, Item Code, Item Name, Quantity, Price of each item, Total amount charged for each item, Gross Amount, Discount, Tax, Net Amount Payable. Any other Labels to be included, e.g., name of organisation, terms & conditions etc.

Identify the procedures/rules/mathematical relationships used for converting input into output:

Chapter-3: Systems Requirement Specification (SRS)

3.1 Physical Specifications: 3.1.1 DFD The various symbols to be used in DFD is as follows

3.1.2 ERD

3.2 Output Specifications:

3.2.1 Detailed characteristics of contents (fields) to be included in each Output screen or document.

3.2 Output Specifications

3.2.2 List of data elements (comprising Field Name, Field Type, Field Size & description) for each Output presented in the tabular form.
Field Name Date Item Code Item Name Quantity Price Total Amount OUTPUT NAME: INVOICE LINKED TO BILL PROCESS Field Type Field Size (No of Description Characters) MMDDYYYY 10 Date of Invoice Alphanumeric Alphabetic Numeric Numeric Numeric 10 20 10 4.2 5.2 Unique code of each item Name of item Quantity of each item Price of each item up to two decimal places Quantity x Price of each Item up to two decimal places Total amount of all the items Discount to be given on Gross Amount as per policy. Tax to be levied as per policy on (Gross Amount Discount) Net Amount payable (Gross Discount + Tax)

Gross Amount Discount

Numeric Numeric

6.2 4.2

Tax

Numeric

3.2

Net Amount Payable

Numeric

6.2

3.3 Input Specifications

3.3.1 Detailed characteristics of contents (fields) to be included in each Input screen or document.

3.3.2 List of data elements (comprising Field Name, Field Type, Field Size & description) for each Input presented in the tabular form
INPUT NAME: PURCHASE ORDER LINKED TO PURCHASE ORDER PROCESS

Field Name

Field Type

Field Size (No of Characters)

Description

Date

MMDDYYYY

10

Date of Purchase Order

Item Code

Alphanumeric

10

Unique code of each item

Item Name

Alphabetic

20

Name of item

Quantity

Numeric

10

Quantity of each item

Chapter 3 (contd..)
3.4 Validation Specifications:
3.4.1 Description of the validation rules to be included for input/output, wherever required.

3.5 Database Specifications

3.5.1 Detailed characteristic of fields of each file/table included in the database are to be tabulated with Field Name, Type, and Size & Description
FILE NAME: STOCK LIST LINKED TO PURCHASE ORDER PROCESS

Field Name

Field Code

Field Type

Size (No of Characters)

Description

Item Code

Item_Code

Alphanumeric

10

Unique code of each item

Item Name

Item_Code

Alphabetic

20

Name of item

Quantity

Qty

Numeric

10

Quantity in stock

3.6 Processing Logic: 3.6.1 Programme Flow Chart