A Complete Database Project on ATM Management System

A Complete Database Project on ATM Management System

This is a complete project on ATM management system so let you guys download this free.

This project made by the team including members Ghulam Mujtaba Khan(Admin), Muhammad Muhazzab Hussain (Admin: usefulwap.com), Muhammad Waqas, Ghulam Abbas. So all the credit goes to these four member. Not: This project is offered free and only for educational purpose. Anyone is not allowed to sell or buy. So Please use it for educational purpose.

So Starts:

First of we will look on the ATM database development life cycle.

So, the development life cycle is a necessary thing and first step to know that how is it work and how many steps needed and what the things are needed and what the information we must gather before starting on this project. So first of all the thing to survey and get the info from people and gather information that actually what the people need.

The Database System Development

Lifecycle

As a database system is a fundamental component of the larger organization-wide information system, the database system development lifecycle is inherently associated with the lifecycle of the information system. The stages of the database system development lifecycle are shown in the following finger.

� Database planning

� System definition

� Requirements collection and analysis

� Database design

� DBMS selection (optional)

� Application design

� Prototyping (optional)

� Implementation

� Data conversion and loading

� Testing

Operational maintenance

�                Database Planning

The management activities that allow the stages of the database system development lifecycle to be realized as efficiently and effectively as possible.

Database planning must be integrated with the overall IS strategy of the organization.

There are three main issues involved in formulating an IS strategy,  which are:

�       Identification of enterprise plans and goals with subsequent determination of information system needs;

�       Evaluation of current information systems to determine existing strengths and weaknesses;

Appraisal of IT opportunities that might yield competitive advantage. Database planning should also include the development of standards that govern how data will be collected, how the format should be specified, what necessary documentation will be needed, and how design and implementation should proceed. Standards can be very time consuming to develop and maintain, requiring resources to set them up initially, and to continue maintaining them. However, a well-designed set of standards provides a basis for training staff and measuring quality control, and can ensure that work conforms to a pattern, irrespective of staff skills and experience. For example, specific rules may govern how data items can be named in the data dictionary, which in turn may prevent both redundancy and inconsistency. Any legal or enterprise requirements concerning the data should be documented, such as the stipulation that some types of data must be treated confidentially.

�                System Definition

The system definition describes the scope and boundaries of the database application and the major user views.

Before attempting to design a database system, it is essential that we first identify the boundaries of the system that we are investigating and how it interfaces with other parts of the organization�s information system. It is important that we include within our system boundaries not only the current users and application areas, but also future users and applications. We present a diagram that represents the scope and boundaries of the ATMNO database system in following Figure. Included within the scope and boundary of the database system are the major user views that are to be supported by the database.

�                Requirements Collection and Analysis

The process of collecting and analyzing information about the part of the organization that is to be supported by the database system  and using this information to identify the requirements for the new system.

Requirements collection and analysis is a preliminary stage to database design. The amount of data gathered depends on the nature of the problem and the policies of the enterprise. Too much study too soon leads to paralysis by analysis. Too little thought can result in an unnecessary waste of both time and money due to working on the wrong solution to the wrong problem.

Another important activity associated with this stage is deciding how to deal with the situation where there is more than one user view for the database system. There are three main approaches to 

managing the requirements of a database system with multiple user views, namely:

�     The centralized approach

�     The view integration approach

�    A combination of both approaches

      

ATM Management Platform

Conceptual Database Design

1)       Build Conceptual Data Model

1.1)           Entity Types:

1.   Administrator

2.   User

3.   ATM Card

4.   Account

5.   Branch

6.  Security

1.2)         Relationship Type: For Conceptual Model

Initial Level:

Next Level:

Complete Diagram:

1.1)          

ATM Management Platform

link download