Hello Logout
 

Projects

Design and development of Speed Cash System [ SCS ]

 

Title of the project

 

Design and development of Speed Cash System [ SCS ]

 

Abstract of the project

 

The Speed Cash System is used to transfer money from one place to another within a day. This is basically used to speed up the money transfer. The necessary information for the money transfer from the source bank to the destination bank is sent in the form of file on daily basis. This file contains the information like remitter details, beneficiary details and DD (Demand Draft) details, etc.

 

Basically the remitter is a person who sends the money and the beneficiary is the person who receives the money. If the remitter has already an account with the bank, the deduction at the back end should happen instead of cash dealings. Once the file is received, it is processed and the data is put into the database. Then it is again processed and DD is printed. The printed DD will be handed over to the concerned person.

 

Various reports are generated by this system.

 

Keywords

 

Generic Technlogy keywords

 

Databases, Networks and Middleware

 

Specific Technology keywords

 

MS-SQL server / Oracle, Visual Basic .NET, Any tool to dump the data from file into tables.

 

Project type keywords

 

Analysis, Design, Implementation, Testing, User Interface

 

Functional components of the project

 

Following is a list of functionalities of the system. More functionalities as deemed appropriate can be added list. And, in places where the description of functionality is not adequate, appropriate assumptions can be made.

 

User Login

 

First to enter this system the users has to login to this system. Basically there are  2 types of users in this system.

 

1.      Admin users – The admin users can create / maintain the user information.

 

2.      Normal users – The normal user is similar to admin user, but can’t create / maintain the user information. But they can change their own password if needed.

 

  • First a login screen should be displayed to get the user details. The user has to enter the user-id and the password. The password has to be masked with character ‘*’.
  • The user details should be verified against the details in the user tables and if he / she is valid user, they should be entered into the system. Once entered, based on the user type access to the different modules to be enabled / disabled.

 

  • If user enters wrong password for continuously 5 times, the account should be locked. The information about the login and logout details should be stored in a separate table.

 

User Details

 

This module contains 2 parts. User maintenance and password change.

 

  • User maintenance is used to create a new user, modify the details of existing user or remove the existing user.  Only the admin type user will have access to this part. Normal user won’t have access to this. While storing into database the password should be encrypted and stored. The user can choose his / her own logic to encrypt the password.

 

  • User password is used to change their own password. Both admin and normal user will have access to this.

 

File Processing

 

The file received from source bank is processed as follows.

 

  • The remitter, beneficiary and DD records are coming in the same file.

 

  • These 3 types of records have different record formats.

 

  • These 3 types of records are identified using the first 2 characters of the record. If it is ‘00’ it is remitter record. If it is ‘01’ it is beneficiary record. If it is ‘02’ it is DD related record.

 

  • The records are validated for various conditions. For e.g., validation on remitter information, beneficiary information, etc.

 

  • If the record is invalid it has be put into separate table.

 

  • Valid records are kept separately for further processing – DD printing.

DD Stock Maintenance

 

This module is used to maintain the DD related information like DD numbers, etc. We should be able to add, modify and delete the DD related information. Only Admin users have the access to this module.

  • To add the DD information the following information are captured. For e.g., DD serial No, DD starting no, DD ending No, etc.

 

DD Printing

 

This module is used to print the DDs in the predefined structure format. There are 3 parts – Normal DD printing, Duplicate DD printing and DD cancellation.

 

  • The Normal DD printing is to print DDs for the valid records received in the file. The DD is printed using the information received in the current file. The DD number is generated automatically for each DD.

 

  • The duplicate DD printing option is used to print DDs in case any original DD is not printed properly or any damage is happened to that. For this the old DD number is received as input and new DD number is generated and DD is printed. The old DD is marked as cancelled.

 

  • To cancel any DD, the DD number is taken as input and the same should be marked as cancelled.

 

Reports

 

This module is used to print various online reports.

 

  • User details report – This contains various information about the users available.

 

  • User login details report – This reports takes the user ID and from / to date as input and generates the report containing the login date, login time and logout time, etc.

 

  • DD details report – This gives the details of DD stock related details.

 

  • DD printed report – This gives the report about the DDs printed between a given date range.

 

  • Valid Remitter report – This gives the details about the report on various valid remitter for a given date range.

 

  • Valid Beneficiary report – This gives the details about the report on various valid beneficiary for a given date range.

 

  • Invalid Remitter report – This gives the details about the report on various invalid remitter for a given date range.

 

  • Invalid Beneficiary report – This gives the details about the report on various invalid beneficiary for a given date range.

 

 

Help

 

This module contains the following 2 things – Help and About.

 

  • The Help menu should display the detail information about the system. It is like a typical help system available in any windows application.

 

  • The About menu should give information about this software like developed by,  version and contact details.

 

Steps to start-off the project

 

The following steps will be helpful to start off the project.

 

  1. Study and be comfortable with technologies such as

 

  1. Visual Basic.NET / Active Server Pages .NET and HTML
  2. SQL server / Oracle

 

            Some links to these technologies are given in the ‘Guidelines and References’ 

            section of this document

 

  1. The system should be user friendly as much as possible. Display messages wherever required.

 

  1. Give the help facility in detail and easy to understand.

 

Requirements

 

Hardware requirements

 

Number

Description

Alternatives (If available)

1

PC with min 10 GB hard-disk and 512 MB RAM.

Not-Applicable

 

 

Software requirements

 

Number

Description

Alternatives (If available)

1

Windows 98/XP/2000

--

2

MS-SQL server / Oracle

--

3

Visual Basic .NET

--

4

Any tool to dump the data from file into database.

 

 

 

Manpower requirements

 

2 students can complete this in 5-6 months if they work fulltime on it.

 

Milestones and Timelines

 

Number

Milestone Name

Milestone Description

 

 

Timeline

 

Week no. 

from the start

of the project

Remarks

1

Requirements Specification

Complete specification of the system (with appropriate assumptions). A document detailing the same should be written and a presentation on that be made.

2

Attempt should be made to add some more relevant functionalities other than those that are listed in this document.

2

Technology familiarization

Understanding of the technology needed to implement the project.

6

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.

3

Database creation

A database design should be done and the same should be created with the necessary tables.

7

It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.

It would be better to have some sample data to use during development stage.

4

High-level and Detailed  Design

[ In other words, HLD and LLD]

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.

10

The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).

5

Implementation of the system

[ Coding ]

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options described above.

This phase contains code to communicate with the database also.

14

During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

6

Unit Testing

The system should be thoroughly tested by running for all the scenarios.

16

Another 1 week should be there to handle any issues found during testing of the system.

7

Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).

18

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

8

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

20

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

 

 

 

Guidelines and References

 

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp(ASP tutorial)

 

http://www.functionx.com/sqlserver/(SQL-server tutorial)



Tags :
2
Your rating: None Average: 2 (1 vote)