You are on page 1of 6

Education and Research Department

Project Specification for C Programming


July 2005

Document No.
ER/CORP/CRS/LA07/00 6

Authorized By
Dr. M. P. Ravindra

Ver. Revision Signature / Date


Ver. 1.0 July 2005

COMPANY CONFIDENTIAL

Infosys

Document Revision History

Document Revision History


Ver. Revision 1.0

Date JUL-2005

Author(s) Sujith S. Mathew

Reviewer(s) Deepak R. Shenoy

Description Review for FP Restructure 2005

ER/CORP/CRS/LA07/006

Version No. 1.0

Page ii

Infosys

Table of Contents

Contents
Education and Research Department..............................................................................1 Project Specification for C Programming.......................................................................1 1 OVERVIEW....................................................................................................................1 2 BUSINESS REQUIREMENTS.....................................................................................1 3 Project Specification for C Programming module........................................................1 3.1 Operations...............................................................................................................3 4 OPERATING ENVIRONMENT REQUIREMENTS..................................................3 4.1 Hardware.................................................................................................................3 4.2 Software...................................................................................................................3 4.3 Network....................................................................................................................3 4.4 Communication.......................................................................................................3 5 PERFORMANCE REQUIREMENTS..........................................................................3

ER/CORP/CRS/LA07/006

Version No. 1.0

Page iii

Infosys

Project Specification for C Programming

1 OVERVIEW
The OSDB project will be carried out during the following modules of the OS (Open System) stream: 1. C Programming 2. C++ Programming 3. Oracle 4. VB 5. POST The banking application to be developed as a part of OSDB project will be carried out in different modules of the OS (Open System) stream. The document gives an explanation of the project and the details of the features that need to be implemented as part of every module. The project will focus only on two functionalities, Login and Staff Transactions, for the first four modules of the OS stream. The remaining functionalities will be completed as part of the POST project.

2 BUSINESS REQUIREMENTS
The project has four main functionalities: 1. Login 2. Transactions carried out by the Bank Manger 3. Transactions carried out by a Staff member 4. Transactions carried out by a Customer 5. Logout The requirements for the project are available in the attached document.
Project Specification

The following section describes the details of the project that have to be completed in C Programming module of the OS stream.

3 Project Specification for C Programming module


The C project will involve the implementation of the Login and the Staff modules. The Login module will accept the Login ID and Passwords of a Staff member. The IDs and respective passwords have to be stored in a file and verified when the staff enters the same.

ER/CORP/CRS/LA07/006

Version No. 1.0

Page 1

Infosys

Project Specification for C Programming

The screen should have the option where the user can choose his/her identity as a Manger, a Staff member or a Customer of the Bank. The Staff module will have the following functionalities: 1. Add a Customer A staff member should be able to add a customer to the list of customers in the bank 2. Add an Account A staff member should be able to add an account for an existing customer 3. Deposit A staff member should be able to update an account with an amount that is deposited to the account 4. Withdrawal A staff member should be able to update an account with an amount that is withdrawn from the account 5. Balance Enquiry A staff member should be allowed to see the balance of any account that is registered with the bank 6. Logoff A staff member should be allowed to logoff from the system after all the transactions are complete. The solution should be menu driven, giving a staff member the option to select from one of the above actions. After the completion of a transaction the staff member should be shown the menu again till the staff logs off. The data relevant to the above functionalities will be stored in flat files. The formats of the files are as given below. 1. Customer File (cust.dat) a. Customer ID b. Customer Name c. Address d. Phone number - 5 characters - 20 characters - 30 characters - 10 digits

2. Account File (account.dat) a. Customer ID - 5 characters b. Account Number - 10 characters c. Account Type - 2 characters i. SB - savings back account ii. CA - current account iii. RD - Recurring Deposit iv. FD - Fixed Deposit d. Balance - 12 digits (2 digits after decimal)

ER/CORP/CRS/LA07/006

Version No. 1.0

Page 2

Infosys

Project Specification for C Programming

3. Deposit/Withdrawal File (DW.dat) a. Account Number - 10 characters b. Date - Date format (yyyy-mm-dd) c. Amount - 12 digits (2 digits after decimal) d. Transaction Type - 6 characters i. Cash ii. Cheque iii. DD - Demand Draft iv. MT - Money Transfer v. INT - Interest

3.1 Operations
a. To open an account the customer details should be available in cust.dat b. The minimum balance that should be maintained in an account is Rs.1000/c. The details in the files should be in a sorted order. i. Based on Customer number for customer file or account file ii. Based on Account Number for the Deposit/Withdrawal file

4 OPERATING ENVIRONMENT REQUIREMENTS


4.1 Hardware
The developer will use a Intel based PC and will connect remotely to a UNIX server

4.2 Software
The project will be executed in the UNIX environment Telnet will be used to connect to the remote UNIX server UNIX based C Compiler should be used for compiling the source code

4.3 Network
The developers system and the UNIX server must be on a LAN

4.4 Communication
Telnet will be used to communicate between the developers system and the UNIX server

5 PERFORMANCE REQUIREMENTS
NA

ER/CORP/CRS/LA07/006

Version No. 1.0

Page 3

You might also like