Bank account management system in java, Study Guides, Projects, Research of Java Programming

Download Bank account management system in java and more Study Guides, Projects, Research Java Programming in PDF only on Docsity!

CONTENTS

1. Synopsis
2. System Analysis  CFD  DFD
3. Fundamental requirement  I/O Requirement  Process Requirement  Storage Requirement  Control Requirement
4. System Design  I/O Design  Process Design  Database Design
5. Coding and Testing
6. Implementation Issue
7. User manual
8. Future Enhancement
9. Conclusion
10. Bibliography

OBJECTIVES OF THE PROJECT

Objective 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

(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

DISCRIPTION OF EXISTING SYSTEM

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.

FEASIBILITY STUDY

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.

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 Windows  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.

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

CONTEXT FLOW DIAGRAM

BANK

ACCOUNT

SYSTEM

CUSTOMER CUSTOMER

CUSTOMER

CUSTOMER INFORMATION

FILE

Order Account Process Response Transaction information