BCA IV Summer Training Project

8/3/2019 BCA IV Summer Training Project

http://slidepdf.com/reader/full/bca-iv-summer-training-project 1/21

SUMMER TRAINING PROJECT

BCA - 353



Objective

To apply theoretical concepts, tools &techniques of Software Engineering on a realinformation system.

It is planned to link and extend the work done

in the summer training with the project workthat is to be done during the semester.



Un iversity Scheme for SummerTrai n ing & Project

Summer Trai n ing (BCA 353)

Credits : 2Duration : Eight Weeks

Marks : 100

M in or Project (BCA-355)

Credits : 4Evaluation Scheme:

(a) External : 60 Marks

(b) Internal : 40 Marks



Scope of Summer Trai n ing & Project

A team of two stude n ts shall work o n on e topican d submit a joi n t report.

The SRS worked out during the summer trainingare to be converted into an application usingfront & back-end tools during the Vth semesteras a software project independently by eachstudent.



Schedule of Submissio n sTo be Completed by

Date

Activity Marks

Allotted

Remarks

16th June 2011 Briefing about the Summer Training - -21th June 2011 Finalisation of Topic22st June 2011 Commencement of Summer Training at

the Institute12th July 2011 Completion & Submission of activities

Under Chapter-1

10 As per Appendix-

A.26th July 2011 Completion & Submission of activities

Under Chapter-215 As per Appendix-

A.11th August2011

Completion & Submission of activitiesUnder Chapter-3

25 As per Appendix-A.

26th August 2011 Submission of Final Report (One hard

copy & CD) to the respective guides

10 As per Appendix-

A & B.29-31st August2011

Presentation & Viva before theCommittee

40

Total Marks 100



SUMM ARY OF LIST OF ENCLOSURES

Chapter-1: I n troductio n

1.1 Descriptio n of Or gan isatio n :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 reference tothe information system under study.



Chapter 1 (co n td..)1.2Data Collectio n :

1.2.1Inputs1.2.2Outputs1.2.3Storage and processing requirements1.2.4Entities in the system & their connectivity/linkages1.2.5Flow of data between the entities1.2.6Description of method/source of collection of datafor each set of data

1.2.6.1 Questionnaire1.2.6.2 Interview1.2.6.3 Document analysis1.2.6.4 Internet.



Chapter 1 (co n td..)

1.3. Project Pla nn ing :1.3.1 Plan of distribution of work amongst theteam members as follows:1.3.2 Name of task/activity,1.3.3 Precedence/order (date-wise) in whichthese are performed

1.3.4 The name of the team member who hasperformed that task/activity.1.3.5 Gantt & other charts using MS Project



Chapter 2System A n alysis

2.1 Descriptio n of In formatio n System:2.1.1 Description of the functioning of information system under study innarrative 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 relatio n ships used forcon verti ng in put i n to output

2.2.1 Decision tree/Decision table or both .



As an example, a block diagram for BillingInformation System of a Departmental Store is

shown in the figure below:

Customer Purchase

Order Process

Purchase Order

Item Details

Stock List

Verify Stock

Availability

Verified

Details

Bill

Process

Purchase Order

with Details

Price List

Customer Invoice

Price of Items

Customer Purchase

Order Process

Purchase Order

Item Details

Stock List

Verify Stock

Availability

Verified

Details

Bill

Process

Purchase Order

with Details

Price List

Customer Invoice

Price of Items



T he 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

NameData Elements

PurchaseOrder

Date, Item Code, Item Name, Quantity. Any other Labels to 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 Requireme n t Specificatio n (SRS)

3.1 Physical Specificatio n s:

3 .1.1 DFDThe 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.OUTPUT NAME: INVOICE LINKED TO BILL PROCESS

Field Name Field Type Field Size (No of Characters)

Description

Date MMDDYYYY 10 Date of Invoice

Item Code Alphanumeric 10 Unique code of each item

Item Name Alphabetic 20 Name of item

Quantity Numeric 10 Quantity of each item

Price Numeric 4.2 Price of each item up totwo decimal places

Total Amount Numeric 5.2 Quantity x Price of eachItem up to two decimal

placesGross Amount Numeric 6.2 Total amount of all the

itemsDiscount Numeric 4.2 Discount to be given on

Gross Amount as per policy.

Tax Numeric 3 .2 Tax to be levied as per policy on (Gross Amount ± Discount)

Net Amount Payable Numeric 6.2 Net Amount payable

(Gross ± Discount + Tax)



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 (co n td..)

3.4 Validatio n Specificatio n s:3.4.1 Description of the validation rules to be included forinput/output, wherever required.



3.5 Database Specificatio n s

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 eachitem

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

Documents

BCA IV Summer Training Project