ACCOUNT MANAGEMENT SYSTEM PROJECT REPORT

ACCOUNT MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

BANK ACCOUNT MANAGEMENT SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

ACCOUNT MANAGEMENT SYSTEM PROJECT SOURCE CODE

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

OBJECTIVES OF THE PROJECT

The objective is to create application software which cans mange all about the customers currently working in bank in order relative them from their manual accounting system. 

The various reasons which led to the conversion of the manual system of the bank to the computerized system are as follows:-

Ø  Entry of information in various registers was a very hectic job for the customer.

Ø  The entry of information causing error in entering details of customer.

Ø  Even the redundancy of the record was also found through they had taken certain precautions like entering the information with the pencil, leaving the space for making the entry in future, if not possibly confirmed about the details.

Ø  The error prone details causing the making in the other related registers, which might some problem while producing reports.

Ø  Even a lot of times begin spent on the entering of details after crosschecking details from various registers.

Ø  Then the security of these registers being a major problem. Even a single page should not be teased. The n it should not get into the hand of some unauthorized person.

Ø  And last but not least, because it is vary calculation oriented and computerized system can be used for given current result always.

The proposed Bank Account system will make current manual system easy to monitor, efficient and almost error free.

HARDWARE & SOFTWARE REQUIREMENT - ACCOUNT MANAGEMENT SYSTEM PROJECT

(A) HARDWARE REQUIREMENT-

An Intel based central processing unit capable of running any sort of windows operating system such as Pentium based workstation.

·         Minimum 64 MB RAM (128 MB Desirable) at server.

·         Minimum 60 MB of free disk space for files.

·         A CD Rom drive

·         Minimum 48 MB of RAM at workstation.

·         VGA 15” color monitor for workstation.

(B)              SOFTWARE REQUIREMENT-

                                      The software requirements are as follows.

·         Windows 98 or Above

·         C editor

·         Microsoft word

INTRODUCTION

Bank account system involves maintaining of account related information. This requires grater accuracy, speed that is why the proposed system is the computerization of the existing system. The computerization system does the job monitoring the record in easy and effective manner as stated below:

Ø  Efficiently handles customer, account related data.

Ø  Monitor transaction and makes related information.

Ø  Keeps records of customer account detail and other information.

Ø  Generates reports.

Account system involved maintaining data related different customer and his transaction. This required greater accuracy, speed that is why the proposed system is the computerization of the existing system. The computerized system does the job of the monitoring the information easy and effective manner.

DISCRIPTION OF EXISTING SYSTEM - ACCOUNT MANAGEMENT SYSTEM PROJECT

In the ongoing process, the records are maintained manually and the paper work is more.

Entering Record-

Entry of each record is done manually each time the record is done

Manually .each time the record is maintained on paper and it maximizes the maintenance of additional files.

Searching the record-

Due to absence of unique identification of person the searching of record takes much time. And in the wastage of time increase.

Deleting the Record-

In the current system there is no concept of deleting record.

Modification of Records-

If any modification is required it is done directly on the documents being preserved in correspondence to account information.

Sorting of Records-

All the record of Account is maintained on papers. And if in any case we want to see any particular record we have to search a lot of pages.

PROBLEMS

1. As the work is carried out manually so the requirement of the maintenance of record.
2. The system is handled manually so it requires a lot of time to maintain the records.
3. The current system is not reliable as manually recording often leads to mistakes and no accurate result are found.
4. No feasibility
5. As huge data is to be maintaining, so it’s not easy to maintain the huge data without any error, which in turn makes the less efficient.

 

DISCRIPTION OF PURPOSED SYSTEM 

To avoid the limitation of current system it’s necessary to design and develop a new system which have the following benefit and the existing system.

(a)Everything is automated which reduce the risk factor.

(b)Flexibility in generating of information.

(c)Quick retrieved and maintenance of data.

(d)Highly accurate.

(e)User satisfaction.

FEASIBILITY STUDY - ACCOUNT MANAGEMENT SYSTEM PROJECT

Feasibility study is a report directed management. It evaluates the impact of the proposed changes in the area(s) in question. The report is a formal document for management, brief enough and sufficiently, non technical to be understandable, yet detailed enough to provide the basis for system design.

Technical feasibility

Technical feasibility centers around the existing system (hardware, software, etc) into what it can sort the proposed addition.

Present system Vs. Candidate System

CRITERIA	PRESENT SYSTEM	CANDIDATE SYSTEM
System accuracy	75%	90%
Growth potential	Average	Good
Response time	Average	Good
User friendly	No	Yes

Economical Feasibility

              Economical analysis in the most frequently used method for evaluation the effectiveness of a candidate system. This procedure is to determine the benefits and saving that are expected from a candidate system and compare it with cost.

Present system Vs. Candidate System

CRITERIA	PRESENT SYSTEM	CANDIDATE SYSTEM
System Performance	Only one task can be performed at a time	One computer system perform more then one task
User training	15 days or more	In a minimum time
System Operation	Fair	Very Good

Operational Feasibility

Employees of  any organization are inherently resistant to changes because they believe that it will be very difficult to adapt in the new system. Computers have been to facilitate changes. it is well known that computerization has something to do with transfers, retraining and changes in  employee job status.

Present system Vs. Candidate System

CRITERIA	PRESENT SYSTEM	CANDIDATE SYSTEM
Operation time	The present system takes more time for displaying procedures	It takes less time in comparison to present system.
Reliability	It is less reliable	It is more reliable.
Accuracy	75%	95%
Retrieval	It takes few minutes	It takes few seconds

Feasibility Study

A study was undertaken to compare the existing manual system with the new proposed system to be developed.

Economic Feasibility

                 The Bank Account System will considerably reduce the manpower and to time necessary to manage the process and generate the report for the following imperative action to be taken place on the basis of the reports. The proposed system will require only the Person to manage the Contacts. The new system will generate the reports automatically optimizing the efforts and time required.

                 Thus proposed system is economically feasible because it is being developed with out having to incur the heavy development costs and it will considerably reduce time and effort required managing the present system.

 Technical Feasibility

                 The proposed system, which is to be developed, will be installed at Personal Computer. Since we have to also install the computer systems with the configuration given below:-

System Configuration

§  One PC with any version above Windows98

§  Turbo C editor

§  Switches to connect the computer’s Together

                 So we have necessary Hardware and Software supporting the implementation of the proposed system. There is however a need of the one technical person to effectively manage the resource in the computer. Since there are no technical constraints the project is technically feasible.

Behavioral Feasibility

                 Since the new system is going to solve the difficulties that come in the manual system of the procurement, reports in handwritten. So proposed system is completely feasible is terms of the behavior.

Project Plan - ACCOUNT MANAGEMENT SYSTEM PROJECT

                 The Objective of the software project planning is to provide a framework that enables an owner to make reasonable estimate of the resources, cost and schedule. The project leader is responsible for designing the system precisely according the requirement specified by the customer. He is also responsible for maintenance of the system for certain period of time. Since cost of maintenance is much higher than cost of developing system. Thus to reduce developing and maintenance cost, to provide the system in predefine time proper planning of system is necessary.

For this project, we used the Waterfall Model. The methodology has the following phases:

·         Initial Investigation

            The most crucial phase of managing system projects is planning to launch a system investigation, we need a master plan detailing the steps to be taken, the people to be questioned, and outcome expected. The initial investigation has the objective of determining whether the user’s request has potential merits the major steps are defining user requirements, studying the present system and defining the performance expected by the candidate system to meet user requirements. The first step in the system development life cycle is the identification of need. There may be a user request to change, improve or enhance an existing system. The initial investigation is one way of handling these needs. The objective is to determine whether the request is valid and feasible before a recommendation is reached to do nothing, improve or modify the existing system, are to build a new one.

                      Thus for an effective maintenance, paper follow-up and handling of the data resulting from different information in records, it felt necessary to develop a  Bank account System so that monitoring and maintenance of record data could be done.

INFORMATION GATHERING

A key parts of the system analysis is gathering information about the present system. The developer must know that information to gather, where to find it, how to collect it, and what to make of it.

            The proper use of tools for gathering information is the key to successful analysis. The tools are

Ø  The Traditional Interview

Ø  Questionnaires

Ø  On-site Observation         

The major objective of on-site observation is to get as close as possible to the real system. In the interest to get more potential information we personally approached the senior officials of the concerned department.

Required data are collected as forms.  

·         Analysis phase

                

                 It includes the study of the problem and creation of the System Requirement Specification (SRS) Document. The most crucial phase of the managing system projects is analysis. It requires the people to be questioned, study of manual system if it exits, and on the site observations. Analysis is necessary to understand the problem, the software system is to solve

                 The analysis model is concise, precise abstraction of what the desired system must do, not how it will done. Thus, main emphasis in analysis phase is on identifying what is needed from system. The objective is to determine whether the request is valid and feasible before a recommendation is reach to do nothing , improve or modify the existing system, or to building a new one. Thus Bank Account System is automation of the existing manual system.

                 An SRS establishes the basis for agreement between the client and the developer on what the software will do. An SRS provides references for validation of the final product. A high quality SRS is prerequisite to high quality software, which reduces overall development cost of system.

Design Phase - ACCOUNT MANAGEMENT SYSTEM PROJECT

It begins when the analysis phase and thus requirements documents, for the software to be developed has been prepared. The objective of the design process is to be to produce a model or representation of the system, which is used to build the system. The design of the system is essentially a blueprint or plan for solution for system.


Design process for software system has two levels:

1.      System Design

2.      Object Design

The System Design is the high-level strategy for solving the problem and building a solution. System design includes decisions about the organization of the system into subsystem, the allocation of the subsystem to hardware and software component and major conceptual and policy decisions that for the detailed design.

The Object Design phase determines the full definitions of the classes and the association used in the implementations as well as interfaces and algorithms of the methods used to implement operations.

·         Implementation   of the project required the design of the system developed in the design phase of the project to be coded and implemented. The modules defines in the design phase are coded in ‘C’ language.  Integration phase requires the integration of the various modules developed in the project implementation phases. In implementation, it is important to follow good software engineering practice so that tracing to the design is straightforward and so that the implemented system remains flexible and extensible, thus it reduce cost of maintenance and enhancement of the system.

·         Testing Phase includes the conformation of the acceptance criteria set down in the system requirements specification document. The development of the software system involved a series of activities where opportunities for injection of human fallibilities are enormous. Error may begin occur at every stage of the system development where the objectives may be erroneously or imperfectly specified as well as later design and development stage. Software testing is critical element of software quality assurance and represents the review of specification, design and coding. Testing can’t show the absences of defects, it can only show that software defects are present.

Packaging and Deployment phase    comes after completion of the software. Application packaging is the act of creating a package that can install our application onto user’s computer. A package consists of the files that contain compressed project files and any other necessary files the user needs to install and run the application. These files may include setup programs secondary files, or other needed files. The additional files vary based on the type of packaging. One can create two kind of packaging – standard package or internet packages. If we plan to distribute on disk, floppy or via a network share, we should create a standard package for our application. If we plan to distribute via an internet or internet site, we should create an Internet package

USER MANUAL - ACCOUNT MANAGEMENT SYSTEM PROJECT

There is no use of mouse to handle the software .The keyboard is meant for providing any sort of inputs. There is only vertical menu with key access.

    Vertical menu includes the following under their respective headings.

1.    ADD ACCOUNT: the personal directory file.

2.    DELETE ACCOUNT: Delete Customer Account details.

3.    MODIFY ACCOUNT: This modifies the details of Account holder.

4.    DISPLAY ACCOUNT INFORMATION: This displays the customer Debit & Credit Account

5.    SEARCH: find the customer information.

6.    EXIT: close Bank account system.

SCOPE OF FUTURE ENHANCEMENT - ACCOUNT MANAGEMENT SYSTEM PROJECT

The application certainly has same striking advantage over manual system. There will be no paper work as possible and the information will be updated as it changes.

ü  It is automation of Telephone directory system.

ü  With this system one can generate the report of the address.

ü  It secures the database of Telephone directory system from the unauthorized person.

ü  The operator does not require any previous training because of its user friendliness the operator is free from any technicality of the backend processing, that is how database is maintained.

ü  If the process of the working changes in future then the alteration in the system will be done easily and will not cause in the mismanaging of data.

ü  Furthermore with its implementation very large amount of data will be secure and editing and addition or deletion of data is done very easily.

ü  In future according to the user’s requirement it can be updated so that to reach the user specification.

CONCLUSION - ACCOUNT MANAGEMENT SYSTEM PROJECT

The application certainly has some striking feature over manual system. User queries have become quite accurate and efficient. Lot of paper work has been eliminated. Future modification and enhancements have become quite easier now in comparison to the previous manual system.

Last but one of the most important advantages of the banking system is that, through this system the whole procedure will take too less time in comparison of the manual system.

No doubt BAS will be helpful for institutes in all procedure, which will be monitoring through Account. At the first step BAS will only be installed in the bank .The main advantage of BAS is that, it will become a powerful tool in establishment of better system in comparison of the existing system. It helps to protect the system from the corruption. After installation of BAS in the bank, there is a greater possibility of stabilization a clear and fair system, which will be accurate, update and fast.

There is no doubt that there always remains some scope of improvement. The important thing is that the system developed should be flexible to accommodate any future enhancements. This system can be used to provide some enhancement without rewriting of existing code.