ACKNOWLEDGEMENT
ACKNOWLEDGEMENT
We wish to express our heart-felt thanks to everyone who helped us to complete this project. We would like to thanks Mr ASHWANI KUMAR for providing us the opportunity to undertake our MCA Project.
Everyone knows that efficient work is nothing but mutual coordination between two or more people. For us it was very difficult to make a real time project without the help of people surrounding us.
We are extremely thankful to CMC LIMITED, NOIDA for providing us the project in their organization between the environments of project work.
We would like to express gratitude towards Mrs. (Project Coordinator) and Mrs. Neetu
ma’am(Trainer) for their logistic help. With the help of scientific people it is very easy to
complete our project under these people in the organization.
We would like to thank our parents for their moral support. Last but not least, thanks to the almighty that was always with us.
Table Of Contents
1. Organization Profile………..7-12 pages.
2. Abstract ……….13-14 pages.
3. Modules……….15-18 pages.
3.1
Administration Module
3.2
In-house fabrication Module
3.3 External small fabrication Module
3.4
External large fabrication Module
4. System Analysis ……….19-32 pages.
4.1 Existing System………..19-20 pages.
4.2 Problem Domain……….21-22 pages.
4.3 Proposed System……….22 page.
4.4 Snapshot to MS Visual Studio .NET…..23-25 pages.
4.5 System Requirement……….. 25-26 pages.
4.5 Feasibility Study……….27-32 pages.
5.
System Design………33-76 pages.
5.1 System Design………... 33-38 page.
6.
Testing ………..97-105 pages.
6.1 Introduction……….
6.2 Test Strategy………....
7.
System Implementation, Security Measure & Maintenance.106-108 pages.
8.
Future Scope………109-110 page.
9.
Conclusion………111 page.
10.
Bibliography………112 page.
11.
Appendix……….113page
12.
Glossary………..116-118 pages.
C
OMPANY
P
R
@
F
!
LE
CMC Limited is a leading IT solutions company and a subsidiary of Tata Consultancy Services
Limited (TCS Ltd ), one of the world's leading information technology consulting, services and business process outsourcing organizations. We are a part of the Tata group, India's best-known business
With 18 offices, 150 service locations, 520 non-resident locations and over 3,000 employees worldwide, we provide a wide spectrum of unique information technology solutions and services to a clientele of premier organizations in the government and private sectors.
CMC Americas, our subsidiary, services clients in the US, while our branch offices in the UK and Dubai market our products and services in Europe, Africa and the Middle East.
As a part of the TATA group, we will align ourselves with the TCS vision: To be among the Global Top 10 by 2010.
CMC was incorporated on December 26, 1975, as the ‘Computer Maintenance Corporation Private Limited’. The Government of India held 100 per cent of the equity share capital. On August 19, 1977, it was converted into a public limited company.
In 1978, when IBM wound up its operations in India, CMC took over the maintenance of IBM installations at over 800 locations around India and, subsequently, maintenance of computers supplied by other foreign manufacturers as well.
In 1980, we perceived the need for total IT system solutions in India, and acquired a ‘solutions’ orientation. We aligned our focus with the government’s thrust on IT development activities. To reflect our diversified business activities, we renamed ourselves ‘CMC Limited’, and obtained a fresh certificate of incorporation dated August 27, 1984.
Following a spurt in the global demand for IT services in the early 1990s, particularly in the United States, we decided to expand our operations and market our product and service offerings in these markets. Towards this end, in 1991, we acquired Baton Rouge International Inc, USA (it was subsequently renamed CMC Americas, Inc, in 2003), one of the first cross-border acquisitions by an Indian IT firm.
In 1992, the Indian government divested 16.69 per cent of CMC’s equity to the General Insurance Corporation of India and its subsidiaries who, in turn, sold part of their stake to the public in 1996. In 1993, CMC’s shares were listed on the Hyderabad Stock Exchange and the Bombay Stock Exchange (BSE).
To service and develop our clientele in the UK and Europe, we opened a branch office in London, in 2000. The next year, the government divested 51 per cent of CMC’s equity to TATA Sons Ltd, through a strategic sale, and CMC became a part of the TATA group.
Corporate profile
CMC Limited is a leading IT solutions company and a subsidiary of TATA Consultancy Services Limited (TCS Ltd), one of the world’s leading information technology consulting, services and business process outsourcing organizations. We are a part of the TATA group, India’s best-known business conglomerate.
With 18 offices, 150 service locations, 520 non-resident locations and over 3,000 employees worldwide, we provide a wide spectrum of unique information technology solutions and services to a clientele of premier organizations in the government and private sectors.
CMC Americas, our subsidiary, services clients in the US, while our branch offices in the UK and Dubai market our products and services in Europe, Africa and the Middle East.
Service Offering
Data warehousing Education and training Event management
Infrastructure development IT-enabled services
Networking
WE OFFER
Large and complex project management capabilities End-to-end solutions capability
Extensive domain expertise and technological competencies Sizable resource pool with diverse skill sets
Strong customer relationships Strong service delivery chain
Large and complex project management capabilities End-to-end solutions capability
Extensive domain expertise and technological competencies Sizable resource pool with diverse skill sets
About Project
ABSTRACT
About Project
E-banking is one of the most challenging tasks in computer science for many reasons. First, the number of end-users of this complex system is extremely high as e-payment concerns the whole world. Second, financial transactions must be as secure as possible to limit frauds while providing a fast service to users. Finally, the banking infrastructure involves many different technologies in electronics (smartcards, payment terminal) and IT (server, networks...).
We can also identify many problems that limit some new developments and evolutions in the e-banking domain. The industrial community in this area – banks, smartcards manufacturers... – is not very accessible. Each manufacturer of an e-banking component has a partial knowledge on the global chain. As a result it does not facilitate the global evolution of the e-banking chain.
The E-Banking is an application that has been developed for a well-established Bank.
In the world of this competitive environment and Technological development, the bank has been totally computerized in the last 3 Years, and to increase its customer base has started planning, for a concept called as e-banking; with this concept the bank wants to move very nearer to the customers and increase its basic operational strategies. Through E-Banking the Bank wants to introduce the core concept of IT based Enabled Services (ITES).
Using the constructs of MS-SQLServer2005 and all the user interfaces has been designed using the
ASP.Net technologies. The database connectivity is planned using the “SQL Connection” methodology.
The standards of security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports,
Which are produced as per the applicable strategies and standards that are put? Forwarded by the administrative staff.
MODULES
3.MODULES:
This project is having three modules:
• Bank Master Module
• Transaction Module
3.2. MODULE DESCRIPTION
Bank Master Module:
This module mainly deals with creation of new Account i.e. Adding new Account Holders. Other activities such as viewing, Modifying, Deleting Account holder Details.
Transaction Module:
This module deals with different types of transactions such as Deposit, Withdraw and Interest calculation related to customer as well as Bank.
Reports Module:
This module deals with generation of reports for customer and Bank such as Daily reports, weakly reports and report for a particular period of time.
The customer is privileged to use most of the system only as a viewing phase; the only online transactions the customer can do are cheque book requisition and fund transfer among his personal accounts.
The project has been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of MS-SQLServer2000 and all the user interfaces has been designed using the ASP.Net technologies. The database connectivity is planned using the “SQL Connection” methodology. The standards of
Security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports.
Provide administration to control and monitor various transactions. The administration should include the following Add new branch details to the database. The details should include branch name and password etc to logon the system Modify the existing details of an office Add the specification of various
components for displaying it to the customer Provide pre-defined queries
Project organization:
Project organization contains following activities which are related to “E-BANKING”:
It providing electronic connection between bank and customer in order to prepare, manage and control financial transactions.
People use Internet bank to keep eye on their money matters, view Account balance and check receiving payments from other parties. It providing faster, easier and more reliable
Services to customers of e-banking.
The online banking system is designed for financial institutions to deal with their basic banking services. The system allows customers to open accounts, view account balances and statement details, transfer funds between accounts and change personal information and passwords. Any customer is able to scan interest details, dong with frequently requested information for checking, savings, and certificate of deposit accounts quickly and easily without interacting with bank clerks. In addition Multiple users can access it at the same time, rather than personally standing in h e s for ATM or banking clerks.
The online banking system provides access 24 hours a day to customers' accounts information. Therefore customers can enjoy the convenience of financial controls of their accounts through Internet. In addition, the customers can move funds between bank accounts in a cost-free way According to standard of software industry; the system described above belongs to dynamic Web application.
Manual Process
→
Customer→
Inquires for an existing service Physically visits the bank or some specific information↓
Leaves
←
Associated and integrates the←
the in charge clerk information as needed checks the specificationand answer query
→
Customer→
Raises a request for Physically visits the bank checkbook by filling in thePrescribed format
↓
Customer makes a
←
The cheque book is send←
The in charge clerk accepts counter sign and for manage initials the request and prepares receives the cheque cheque book with respect tobook given specification
PROBLEM DOMAIN
Problem domain:
• In existing manual system, it is difficult to maintain a large scale order transactions.
• In existing manual system huge expenditure and lot of time is spend in
communicating the information across the external bank branches & the centralized system.
• Manually the information may not be as secure as in automated system.
3.2 PROPOSED SYSTEM
In proposed system we are concentrating the problems what ever a client faced with existing manual system. By introducing Automation system for Banking Information system. The client is provides fast services to the customer. The transaction service, report generation service and every service is available at no delay.
This project is an attempt to make the task of administrator as well as customers easier. The administrator has the right to know everything. He has the right to know the account details of the users and bank reports. The development of the new system contains the following activities which try to automate the entire process keeping in view of the database integration approach.
1. The administrators have grates accessibility in collecting the consistent Information that is very much necessary for the system to exist and Coordinate.
2. The system at any point of time can give the customers information related To their
Accounts and accounts status
The balance enquiry
the fund transfer standards
The cheque book request
3. The system can provide information related to the different types of accounts that are existing within the bank.
4. The system can provide the bank administration with information on the Number of customers who are existing in the system.
5. The system at any point of time can provide the information related to the executed transactions by the customer.
There are following Features which are related to provide the E-Banking services for the customers.
• The main goal of every company is to maximize profits for its owners and banks are not any exception. Automated e-banking services offer a perfect opportunity for maximizing profits.
• The main benefit from the bank customers’ point of view is significant saving of time by the automation of banking services processing and introduction of an easy maintenance tools for managing customer’s money. The main advantages of e-banking for corporate customers are as follows :
Reduced costs in accessing and using the banking services.
Increased comfort and timesaving — transactions can be made 24 hours a day, without requiring the physical interaction with the bank.
Quick and continuous access to information. Corporations will have easier access to information as, they can check on multiple accounts at the click of a button.
Better cash management. E-banking facilities speed up cash cycle and increases efficiency of business processes as large variety of cash management instruments is available on Internet sites.
Project justification:
Need for computerization:
Project justifies the need of computerization which is used to act as the interface which provides following activities:
Reduced costs.
This is in terms of the cost of availing and using the various banking products and services.
Convenience.
All the banking transactions can be performed from the comfort of the home or office or from the place a customer wants to.
Speed.
The response of the medium is very fast; therefore customers can actually wait till the last minute before concluding a fund transfer.
Funds management.
Customers can download their history
Of different accounts and do a “what-if” analysis on their own PC before affecting any transaction on the web. This will lead to better funds management.
Security.
It provides the security & secure data accessing
3.3 SNAPSHOT TO MS VISUAL STUDIO .NET
IT Platform – The Technological Aspect.
3.3.1 INTRODUCTION
Visual Studio.net is the tool for rapidly building enterprise scale ASP.NET web applications and high performance desktop applications. Visual studio.net includes component based development tools, such as Visual C#, Visual J#, Visual Basic.net and visual C++ .net, as well as number of additional technologies to simplify team- based design, development, and deployment your solutions.
Visual studio supports the Microsoft.Net framework, which provides the common language runtime and unified programming classes;ASP.NET uses this component to create ASP.NET web applications and XML web services.
The .NET framework is an integral windows component that supports building and running the
next generation of applications and XML web services. The .NET framework is designed to fulfill the following objectives:
• To provide a consistent object-oriented programming environment whether object is stored and executed locally, but internet distributed, or executed remotely.
• To provide a code execution environment that minimizes software deployment and versioning conflicts.
3.3.2 THE .NET FRAMEWORK
The .NET framework is a Multilanguage environment for building, deploying, and running XML web services and web applications. It consists of 2 parts:
3.3.3 COMMON LANGUAGE RUNTIME (CLR)
The common language runtime is the foundation of the .NET framework. Runtime is an agent that manages code at execution time, providing core services such as memory management, thread management and remoting while also enforcing strict type safety and other forms of code accuracy that promote security and robustness. In fact the concept of code management is a fundamental principle of runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is called unmanaged code. The Class library, the other main component of the .NET framework is a comprehensive object oriented collection of reusable types that you can use to develop applications ranging from traditional command line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET such as web forms and XML web services.
The .NET framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code thereby creating a software environment that can exploit both managed and unmanaged features. The .NET framework not only provides several runtime hosts but also supports the development of third party runtime hosts.
3.3.4 ASP.NET
ASP.NET builds on the programming classes of the .NET framework, providing a web application model with a set of controls and infrastructure that make it simple to build asp web applications.ASP.NET includes a set of controls that encapsulate common HTML user interface elements such as text boxes and drop down menus. These controls run on the web server however and push their user interface as HTML to the browser. On the server the controls expose an object oriented programming model that brings the richness of object oriented programming to the web developer.ASP.NET also provides infrastructure services such as session state management and process recycling that further reduce the amount of code a developer must write and increase application
reliability. In addition ASP.NET uses these same components to enable developers to deliver software as a service. Using XML web services features we can write our own business logic and use the ASP.NET infrastructure to deliver that service via SOAP.
3.3.5 SQL Server 2005
•
SQL SERVER 2005 is a Microsoft Product that is Software used to provide service that deals with the database.•
SQL is a query language that is used to interact with the database.•
It can be accessed by most programming languages.•
Information stored in a SQL Server 2005 database hosted on a web server can be accessed from anywhere in the world with a computer.•
This makes it a good way to store information that needs the ability to change over time, but also needs to be accessed over the net. Some examples that can utilize SQL Server 2005 are a web message board or a customer's shipping status.•
SQL Server has some differences from Oracle 9i such as the unique key can have at most one null value here. It uses various stored procedures as a compiled object.•
SQL Server 2005 Express is the free version of the Microsoft SQL Server 2005 database.•
It replaces MSDE (Microsoft SQL Server 2000 Desktop Engine), which was based onMicrosoft SQL Server 2000.
•
Organizations that have developed MSDE applications will find it easy to move to SQL Server 2005 Express.•
It is easy to move your MSDE applications to SQL Server 2005 Express.•
SQL Server 2005 Express has a number of important advantages over MSDE, such as visual configuration tools, XML data support, and simplified deployment of applications. These changes have resulted in a number of important differences between SQL Server 2005 Express and MSDE.Some of these advantages are:
•
Increased Maximum Database Size•
New Data Types•
SQL Service Broker•
Reporting ServicesSYSTEM
3.4 SYSTEM REQUIREMENT
3.4.1 SOFTWARE
For t he develop this project. The various Software resources are used.
• Front End :Visual studio.Net
• Back End :MS SQL Server 2005
• Web Server :IIS (Internet Information Services)
• Technology: .NET Framework (ASP.NET with C#)
• Code-Behind Language: C#, JavaScript, HTML
3.4.2 HARDWARE
CPU : INTEL PENTIUM III
CLOCK SPEED : 2.8 GHz MAIN MEMORY : 256 MB SECONDRY MEMORY: 4 GB CACHE MEMORY : 1MB MONITOR : SVGA FLOPPY DRIVE : 1.44MB
PRINTER : LASER JET
3.4.3 OPERATING SYSTEM
• Windows XP Professional
• Windows XP 2005 server
3.5 FEASIBILITY STUDY
“At present, as pointed out earlier, most of the work is done manually. And there is no denying the fact that computers would quicken the work if a solution is developed prudently. So, the first question that whether computerization is necessary is not so important. The main concern was then regarding the selection of software / hardware / mode of work-in / interface etc. “
The total number of databases that were identified to build system is 17. The major parts of the databases are categorized as administration components and customer of based components. The administration components are useful is managing the actual master date that may be necessary the maintain the consistency of the system. These databases purely used for the internal organizational needs and necessities.
The uses of customer components are designed to handle to transactional states that arises upon the system whereas customer makes a visit onto the portal for the same of a product purchase. The customer’s components are scheduled accept parametrical information from the uses as per the system necessity.
GUI’S
In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browses interface. The GUI’S at the top level have been categorized
i. Administration users interface ii. Account Holder interface
The Administration users interface concentrate on the consistent in that is practically part of organizational actuaries and which needs proper
authentication for date collation. These interfaces to the visitors with all the transactional states lute date in date deletion and date updation only with the Date search capabilities.
The Account holder interface helps the ordinary website visitors is transacting through the required services that provided upon the site. The customer
interfaces also help the ordinary users in managing their own information.
The different parts of the present model were checked with three criteria in mind and
overall it has been considered as a workable and balanced solution and would not be obsolete in very near future. The balance was sought between technology and the real environment
3.5.1 ECONOMIC FEASIBILITY
The organization is fully capable of arranging all the basic software according to the requirement. No extra software or hardware needs to be acquired because they already have the system and other relevant software. Major benefits expected from this system are
• Increased speed of work with many of the mundane task being automatically done leaving more time for other things.
• Less time consuming or in other words say that there is no time consuming to see the appropriate reports as compare it with the manual system.
• More accurate. Certainly, computers are less prone to error than the human being.
• More flexible.
As the benefits expected far outweigh the cost to be incurred, the new system is very much economically feasible.
The benefits of this project include four types:
COST SAVING BENEFITS
This project reduces the administrative and operational cost. Because of the reduction in the use of paper, the cost also reduces.
IMPRPVE SERVICE - LEVEL BENEFITS
Proposed system improves the system’s performance because the current system is based on manual processing while the proposed system is based on computer processing.
IMPROVE INFORMATION BENEFITS
TIME SAVING BENEFITS
It saves lots of time and provides the same result in a far lesser period of time.
3.5.2 Technical Feasibility
Meaning: Can the work for the project be done with current equipment existing software technology and available personnel? If new technology is needed, what is the likelihood that it can be developed?
Reply: In this project the work cannot be done by the current system because currently all the records, filling, transactions, entries, are done by manuals. It is really time consuming and margin of error is more. Yes, the current available personnel can develop this system but special training should be given to those personnel to improve their skills. Yes new technology or software, which is currently working in the market, is to be needed to develop this system.
It can be developed easily with this software and for a long term it is working effectively and margin of error is less.
• Hardware: Hardware selected has been examined against the processing capacity, and the
memory requirement for current as well as near future workload.
FEASIBILITY STUDY
Many feasibility studies are disillusioning for both users and analysts. The most successful system projects are not necessarily the biggest or most visible in a business but rather those than truly meet user expectations.
Before the development of the Project titled “E-BANKING” the need to study the feasibility of the successful execution of the project was felt and thus the following factors are considered for a feasibility study.
Need Analysis:
In need analysis the following factors are considered.
Current Issues
The current issues involve the following factors.
1- Provide facility to do registration for account management
2- Provide facility to transfer account within one workshop and from one workshop to another bank.
3- Provide facility to request for the checkbook, cards, cash book. 4- Provide facility for employee for sorting the request.
5- Provide facility to client for recruitment in organization. 6- Provide facility for the last transactions.
7- Provide facility for client to see the mail and send mail.
Feasibility Considerations:
The analyst must consider the following feasibility step by step-Economic feasibility, Behavior Feasibility, Operational Feasibility, Social Feasibility, Management feasibility, Legal Feasibility, Time feasibility.
Economic Feasibility:
Economic analysis’s most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost/benefit analysis; the procedure is to determine the benefits and savings that are expected from a proposed system and compare them with costs. If benefits outweigh costs, a decision is taken to design and implement the system otherwise; further justification or alternative in the proposed system will have to be made if it is to have a change of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle.
Operational Feasibility:
The project is easy to operate and it has a user-friendly interface. The working staff of the company can be trained easily. It is easy for the staff to adapt and use according to the proposed system. A ready willingness is shown by the staff and the customer to use the proposed system. Hence the system is operationally feasible.
FEASIBILITY STUDY
DOCUMENTATION
Feasibility Study Documentation
Introduction: - This Project aims the creation of a secure “E-BANKING” System which is
accessible to all the customer of bank.
Implementation environment: -ASP.NET,SQL SERVER,HTML. Constraints: - The designed software is Web based application. Management Summary and References:
Important Findings: - This software will be very useful especially for bank & financial
Managements Interface.
Comments: - This project is completed. Recommendations:-
At least four persons should work on the entire project. Latest technologies should be preferred.
Impact: - The impact of the software will be immense and effective for the Administration as
well as the client due to the flexibility in maintaining data.
System Description:
SQL Server is required
Feasibility of allocated elements: - The software can be installed at Server and can be made
available at different nodes.
Evaluation of Technical Risk:
Since the technical team is efficient and the project though little bit complex there is maximum probability of execution of this project within stipulated time.
4.1 SYSTEM DESIGN
In Analysis of the System, we have seen what a system should do. In System Design phase the emphasis will be on how to do what a system should do.
There are two main approaches to design: 1. Data Centered Approach. 2. Process Centered Approach
The present project is designed based on Data Centered Approach as the modern school of thinking on this subject is that if data is organized effectively the processes can always be designed in such a way that the data is made available to them.
The principle of Object Oriented Design (OOD) is adapted where designing is defined as a collection of data and its associated characteristics (processes) as objects. These objects are inline with real life objects.
Logical Design:
Data Structured approach is being adapted since data can be associated with physical structures which can see and feel and it is therefore logical to start with data rather than processes which are invisible--. They are there, but processes cannot be touched or felt.
Logical Design deals with aspects of design which can be implemented on any operating environment i.e. one need not know on which machine or operating system or database the system is going to be working.
In physical design, the output of logical design is implemented using the features of a particular environment.
The following are the contents of the data stores:
Physical Objects:
Login Form Registration Form Request Form
The characteristics of each group mentioned above are listed one by one.
DESIGN OF
PROCEDURE
Software design is both a process and a model. The design process is a sequence of steps that’s enable the designer to all aspects of the software to be built. Basic design principles enable the software engineer to navigate the design process. There are some principles of software design, -The design process should not suffer from “tunnel vision”.
-The design should be traceable to the analysis. -The design should not reinvent the wheel
-The design should “minimize the intellectual distance” between the software and the problem as it exists in the real world.
-The design should exhibit uniformity and integration. -The design should be structured to accommodate change.
-The design should be structured to degrade gently, even when aberrant data, events, or operating conditions are encountered.
-Design is not coding, coding is not design.
-The design should be assessed for quality as it is being created, not after the fact. -The design should be reviewed to minimize conceptual (semantic).
Independence is measured using two qualitative criteria: Cohesion and Coupling. Cohesion is a measure of the relative functional strength of a module. Coupling is a measure of the relative interdependence among modules.
COHESION
A Cohesion module performs a single task within a software procedure, requiring little interaction with procedures being performed in order parts of a program .Cohesion is the measure of functional relatedness of elements within single module. When dividing a system into modules; it must be ensured that the activities within the module are tightly bound to one another. Cohesion can be viewed as opposite of coupling. In Functional Cohesion, all activities in the module are functionally related or they perform a similar function whereas in Sequential Cohesion, modules are divided into a series of activities such as that the output of one module becomes the input to the next module and the chain continue.
Coupling is a measure of interconnection among modules in software structure. Coupling depends on the interface complexity between modules, the point at which entry or reference is made to a module, and what data pass across the interface. The main criteria for deciding the modules from technical angle are to reduce the interdependencies between different modules i.e. to reduce the degree of coupling between modules. If there is lot of dependence across modules, then the degree of coupling is high while if the dependencies between modules are far and few, the degree of coupling is low.
The overall objective is to keep the degree of coupling as low as possible. This is achieved by eliminating unnecessary relationships
-By reducing the number of necessary relationships. -By increasing the flexibility of necessary relationships. In Trainee Management System Normal Coupling is used.
In Normal Coupling, data is passed across modules through parameters. Data can be passed across modules in one of the three ways.
-Data Coupling -Stamp Coupling -Control Coupling
Data Coupling:
In Data Coupling data is passed across modules through parameters.
These parameters are basically elementary form of data. In the project Data Coupling is used.
In, Trainee Management System, the Functional Cohesion is coupled with functional cohesion in order to achieve best form of cohesion.
A defined process is followed for the module activities that include Addition of new Member (either Guide or Trainee), Projects, and Modules
This process is as below:
At start up the Welcome Page will open that will send user to Home Page.
In Home Page all the basic link will be available like login for customer/corporate,static information of organization,Recruitment,Request form, e.t.c
if the user has Inet Id he/she can enter in her/his account by the customer login page.
INet User can do online transaction, request for cheque book, cards , e.t.c
If visitor wants to do registration for Inet Id ,Registration Form Will be available on the Home page.
In Corporate Login part Only Employee of the Bank who has the Corporate Id can login Employee with corporate Id has authority to deny the request, sorting of request of
visitor and customer,send approval of request and vacancies of bank to the inet user by mail.
Inet User can change their address; see the last transaction, balance of their account. Inet user has their own mailbox in which they can see their mails regarding to their
request, bank jobs and schemes and advertisement of bank.
Corporate User has the facility to delete the record of any customer and can also see the report.
DATA FLOW
DIAGRAM
4.2 DATA FLOW DIAGRAM
The data flow diagrams depict the flow of the information within the system. The system and its user act as sink with all the information following into them. Client act the source as all the request are generated by him. The record is held in the storage spaces
depict by partially open rectangle. Arrows within the DFD show the flow of the information form one processing point to another.
DFD is quit important as its records in a pictorial form all the information flow within the system. With the help of DFD we can identify the current information structure of the system. The structure of the system can thus be analyzed and it helps in
making improvement within the current system. We can group a few processing sites together or reduce expenditure; we redirect the flow of the information to make the system
more efficient.
The DFD is intended to represent information flow but it is not a flowchart and is
not intended to indicate decision-making, flow of control, loops and other procedural aspects of the system. DFD is a useful graphical tool and is applied at the earlier stages of requirements analysis. It may be further refined at preliminary design stage and is used as mechanism for creating a top level structural design for software.
Data Flow Diagram
1:
Level Zero DFD
E-Banking
System
User (id and
password
holder)
Data AdministratorServer Database
Retrieve Server Application Input Id/ Password2: Level One DFD
Authenticatio
n Welcome Page Services
User Login
Input ID
/Password Request
3: Level Two DFD
DATABASE
Change Password
Provide Security Details Authorized User Check A/C Status
Fund Transfer Cheques-book Request entry
Login Accounts Change Password Security Transfer Cheques-Book Request
5.3. E-R DIAGRAMS
The ER data model allows us to describe the data involved in the real world enterprise in terms of objects and is widely used to develop an initial design. It provides useful concepts that allow us to move from an informal description of what users want from their database to a more detailed, precise description that can be implemented in a DBMS.
The ER model describes the relation ship between various entities based on some relation ship. Each entity will have a set of attributes, which describe the entity. The entities are related based on an attribute, which is showed by a rhombus describing the relationship.
The one represented here are URL diagrams, which are now considered as the standard form of representation. These are the enhancements made to the ER diagrams that are widely used.
CUSTOMER
Customer
Use r Pass wor d 1:n has m HasAccount
Cust_id A/c type min_bal
1:nPerfo rms 1:nThroug h
Transaction
a/c no Tr_id Tr_type Amount max_ba lMANAGEMENT
Passwor d Management User_id 1:nDes ign Customer User_ id Userna me Passwor d A/c noTable Description
1) Table Name: bank_master
Column Name DataType Constraints
Bank_id int primary key
Bank_name varchar(12)
Bank_add varchar(20)
2) Table Name: branch_master
Column Name DataType Constraints
Branch_id int primary key
Branch_name varchar(12)
Branch_add varchar(20)
3) Table Name: bank_branch
Column Name DataType Constraints
Bank_id int foreign key
Branch_id int foreign
4) Table Name: customer_details
Column Name DataType Constraints
Cust_id int primary key,identity
Cust_name varchar(12)
Cust_add varchar(12)
Cust_phone varchar(10)
5) Table Name: user_login
Column Name DataType Constraints
Cust_id int foreign key
Password varchar(10)
FAQ varchar(50)
Transpass varchar(20)
Countno int
First_time_login datetime
6) Table Name: customer_acc_details
Column Name DataType Constraints
Cust_acc_no number(18,0) primary key, identity
Cust_id int foreign key
Acc_branch_id int foreign key
cust_acc_type_id int foreign key
acc_opening_date datetime acc_opening_bal int current_bal nvarchar(20) acc_nominee_name varchar(20) nominee_relation_with_cust varchar(20) nominee_add varchar(20)
8) Table Name: transaction_type
Column Name DataType Constraints
Trans_type_id int primary key, identity
Trans_type_name varchar(20)
9) Table Name: cust_trans
Column Name DataType Constraints
Trans_id int primary key, identity
Cust_acc_no int foreign key
Trans_type_id int
5.4 DATA MODELING
Implementation independent models are usually called logically models. Data modeling is a very popular logical modeling technique. Data modeling has evolves into a logical system analysis technique can component process models (Data Flow Diagram ). Numerous data modeling technique exist but most popular is the Entity Relationship Diagram.
4.3.1 Entity Relationship Diagram
Any Entity relationship diagram illustrate “Data at rest”. This contrast some what with data flow diagram, which for most part illustrate data in motion. Entity relationship Diagram does no depict flow or processing. They should not be read like data flow diagram or flow chart. E-R Diagrams do not imply how that is implemented, created, modified, used or deleted.
The application of E-R Model has including the following steps:
• First, the entities of the system have been identified and taken tables have been constructed to represent each identity.
• Second, the relationship between the entities has been identified and then current tables have been extended and new tables have been created to represent these relationship.
• Third, the attributes of each entity have been identified and then the tables have been extended to include these attributes.
SECURITY AND
CONTROL
Testing
Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also.
Psychology of Testing
The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. Hence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesn’t work. Testing is the process of executing a program with the intent of finding errors.
Testing Objectives
The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say,
Testing is a process of executing a program with the intent of
finding an error.
A successful test is one that uncovers an as yet undiscovered error.
A good test case is one that has a high probability of finding
error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable
standards.
Levels of Testing
In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are as shown below
Client needs nneeds Acceptance Testing Requirement s System Testing Design Integration Testing Code Unit Testing
System
Testing
The philosophy behind
testing is to find errors. Test
cases are devised with this in mind. A strategy employed for system testing is code testing.
Code Testing
:This strategy examines the logic of the program. To follow this method we developed some test data that resulted in executing every instruction in the program and module i.e. every path is tested. Systems are not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing performed or for that matter is performed on all systems.
Unit Testing
Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. All modules must be successful in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many modules like Login, BankAdmin, Transactions , New User e.t.c.
Giving different sets of inputs has tested each module. When developing the module as well as finishing the development so that each module works without any error. The inputs are validated when accepting from the user. In this application developer tests the programs up as system. Software units in a system are the modules and routines that are assembled and integrated to form a specific function. Unit testing is first done on modules, independent of one another to locate errors. This enables to detect errors. Through this errors resulting from interaction between modules initially avoided.
Link Testing
Link testing does not test software but rather the integration of each module in system. The primary concern is the compatibility of each module. The Programmer tests where modules are designed with different parameters, length, type etc.
Integration Testing
After the unit testing we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.
In this project integrating all the modules forms the main system. When Integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with
which the two services run perfectly before Integration.
System Testing
Here the entire software system is tested. The reference document for this process is the requirements document, and the goal as to see if software meets its requirements. Here entire ‘E-Banking’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.
Acceptance Testing
Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on external behavior of the system; the internal logic of program is not emphasized.
In this project ‘Banking Management Of Database System’ I have collected some data and tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. The testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.
Black Box Testing
This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules.
Criteria Satisfied by Test Cases
1) Test cases that reduced by a count that is greater than one, the number of additional test cases that much be designed to achieve reasonable testing.
2) Test cases that tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.
In the Implementation Phase, the project reaches fruition. After the development phase of the SDLC is complete, the system is implemented. Any hardware that has been purchased will be delivered and installed. Software, which was designed in phase 3, and programmed in phase 4 of the SLDC, will be installed on any PCs that require it. Any person that will be using the program will also be trained this phase of the SLDC.
The System development life cycle during the implementation phase, both the hardware and the software is tested. Although the programmer will find and fix many problems, almost invariability, the user will uncover problems that the developer has been unable to stimulate. This leads on to the sixth and final stage.
6.1.1 SITE PREPARATION
For this we need web server, Internet connection, web hosting (launching the web-application on web server), and domain name registration, sql server 2005 database.
DATABASE IMPLEMENTATION
A crucial phase in SLDC is the successful implementation of the system; implementation simply means bringing the new system into operation.
Due to our well-written documentation and user training methods developed by the experts will aid the user staff so that they can use the system efficiently and effectively.
Firstly install the software and start using. As the software has been implemented for performing all the tasks related to Client Information System and as a result it will reduce the
If there is one issue which has always pestered the computer software fraternity then that is that of security. No matter what one does there always has been someone looking for ways to break that security wall that has been built for the software. This issue has now become even more critical with the world getting highly networked. We at Knowledge Torrent have always been very much appreciative of this problem and have done tried continuously to do the required to prevent any kind of untoward incident from happening. We not only think about out side attack but also the natural catastrophes like earth quack and internal hacking. We have thus categorized the security issue in three sections:
• Internal Hacking
• External hacking
• Natural catastrophe
For the external hacking purpose we have sophisticated firewalls which prevent any breach of security. Also we are shortly going for SSL. This issue has cropped up so as to facilitate online transaction. Since our B2B exchange is in place so we have to go for payment gateways and this does make the SSL a very important issue.
As far as to prevent natural catastrophe, which can destroy our servers, we have multiple servers which are continuously updated and are different geographical places. With these security measures we hope to counter any security beaches. Still as I said security on net is a tricky issue so we keep our self-updated on this front and make necessary change as and when required.
• The capability to develop network-based integrated control and synchronization of various data acquisition systems have evolved with Internet technologies.
• The focus of the programmer on the security of material was to assist Member States in the establishment of systems necessary to prevent nuclear material and other radioactive sources from being diverted to unauthorized purposes.
6.3 MAINTENANCE:
Software maintenance is the last phase in the software Engineering process that eliminates errors in the working system during its work span and to tune the system to any variations in its working environment. The system requires maintenance as there may be changes and requirements in the organizational needs, government policies, hardware and software environment etc. often small system deficiencies are found as a system is brought into operation and changes are made to remove them. System requirements may be revised as a result of system usage or changing operational needs. Perhaps oversight that occurred during the development process needs to be corrected. Often the maintenance need arises to capture additional data for storage in a database or in transaction files or perhaps it may be necessary to add error detection features to prevent system users from in adversely taking an unwanted action.
Maintenance of the system after it is installed is concerned with an additional factor in hardware. Once the system is delivered and installed there is a brief warranty period during which time the vendor is responsible for maintenance. This is a typically a 90 day period after that time the purchaser has the option of acquiring maintenance from various sources. Maintenance source excepting vendor is also available from companies specializing in providing the service, called third party maintenance companies.
When the system is installed, it is generally used for long period. The average
life of system is 4-6 years, with the eldest applications often is used for over 10 years. The need for debugging and correcting errors or failure on an emergency basic is comparatively low: less than 20% of the task of correction. System and organization are in constant state of flux;
Following table summarized the broad classes of maintenance found in development of information systems
CATEGORY ACTIVITY
Corrective Emergency fixes, routine debugging.
Adaptive Accommodation of changes to data and to hardware and software, changes in the external environment.
Perfective User enhancement, improved documentation recording of computational efficiency, user recommendations for new capabilities.
Preventive Routine service of transactions & inquiry prevent breakdowns, future maintainability reliability enhancement, recovering design information to improve the overall quality.
6.3.1 MAINTAINABLE DESIGN
The points to reduce the needs for maintenance are:
More accurately defining the user’s requirements during the system development.
Assembling better system documentation.
Using more effective methods for designing process logic and communicating it to project team members.
Making better use of existing tools and techniques.
FUTURE SCOPE OF THE PROJECT:
The major part of the project is designed and developed by using ASP.NET. But in future .NET Framework and Active Server Pages will be incorporated to enhance the performance of the project. It will be evaluated and maintained by our own server and package. Login Id validation and implementation is also a future application, which will be incorporated.
Optimization though is the age-old concept but is a principal motive to be achieved, for this each and every module is tested in isolation to check its workability and participation in the project.
At now this project provides the following functionality:
• Banking System related information
• All transactions of payment & automate data flow for Bank Management and Customers Account Management are error free, through in the E-Banking System.
In the future this project can be enhanced to include the following:
• Online balance inquiry
• Article search facility on the web application about the Bank System.
• Online amount transfer from one account to another.
Conclusion:
The primary purpose of this project is to replace the existing manual processing with error free, high speed, and low cost and should improve the system capability.
This is a well defined job of our team that has taken seven weeks to analyze the situation in which this project will work and the application of the Microsoft .NET that will use this project. It was a good experience for us to work in a team group that has a very friendly environment and learning atmosphere.
Working on the project was good experience. I understand the importance of Planning and designing as a part of software development. But it’s very difficult to complete the program for single person. Developing the project has helped us some experience on real-time development Procedures. Well, it’s my pleasure to make project for the title of “E-BANKING”. .
BIBLIOGRAPHY
:In this project, I concern many book and study material. These are references:
BOOKS CONSULTED:
• ASP.NET 3.5 with C#
By: Chris ullman,John Kauffman,chris Hart, Dave Sussman ,Daniel Maharry Publication: WROX.
• ASP.NET Website Programming, C Sharp Edition
By: Marco Bellinaso , Kevin Hoffman Publication: WROX.
• Building ASP.NET and ADO.NET
Publication: Microsoft Press
• ASP.Net 3.5 Black Book
Publication: Dreamtech
• SQL SERVER 2005 Black Book.
SITES REFERRED: • spiderdotnet.com • wrox.com • dynamicsdrive.com • google.co.in
Appendix:
[1] Time Progress Chart
35 30 D 25 A Y 20 S 15 10 5 0 MODULES
Module data conversion to the back end access
Module for information Generation for project undertaken Module for paper form design
Module for report designing
Module for interface Information system to cricket record package Lag time in module completion
[2] SYMBOL USED Symbol used for DFD
are:-Source of data
Data Flow
Logical Data Flow
Process that transform data flow
Output as Document that is in printout through printer
Any Data from data base
Predefined Process
Alternate Process
Component Used
Tabled view in the table in database
GLOSSARY
Analysis Breaking a problem into successively
Manageable Parts for individual study.
Attribute A data item that characterizes an object.
DBMSThe software that determines how data must be structured to produce the user’s view
and maintain and update the system.
Data Flow Movement of data in a system from a point of origin to specific destinations-indicated by a line and arrow.
Data security Protection of data from loss, disclosure,modification or
destruction.
Design Process of developing the technical and operational specification of a candidate system for implements.
Feasibility Study A procedure that identifies, describes and evaluate candidate system and select the best system for Implementation.
Flow chart A graphic picture of the logical steps and sequence involved in a procedure or a program.
Form A physical carrier of data of information.
Gantt chart A static system model used for scheduling portrays output performance against time.
Implementation In system development- a phase that focuses on user training,site preparation and file conversion for installing a candidate system.
Maintenace Restoring to its original condition.
Normalization A process of replacing a given file with its logical Equivalent the object is to derive simple files with no redundant elements.
