bank management system | My Assignment Tutor

[Document title] [Document subtitle] [Date] [Company name] [Company address] Contents Rationale: 1 Requirement analysis: 2 System elements and Functionality of the system: 4 Database Design: 6 Overview: The ‘bank management system’ project is a computerized telecommunications device that offers customers of a financial institution access to financial transactions in a public environment and does not require a staff member or a bank taller. Bancing system? needs genuineness and validity if a system has these simple logics, which means we why 1st person? can build up and validate a new system that allows users and users to make any kind of virtual transaction in minimal amounts of time anywhere reframe. The customer accounts for the identification of any individual are among the most authentic codes. It always appears and credit, withdraw, transfers money, connects aadhar and a branch to the same bank, and changes the account location. Day-to-day banking in the economic world is most useful and necessary to grow the nation as well as the economic strength. Thousands of banks transact millions per day, and thousands of people use banking systems every day very vague statement. As we why 1st person? know, if more users are needed by more banks and more employees, it also means that we bring more money into the bank, it’s more risky and not very safe.(Wu et al., 1999) Rationale: This paper offers a cutting-edge approach to developing an efficient and safe web banking system. First, the latest developments and advances in the growth of Web systems and the operating needs of e-banking environment are presented. In addition, the web banking prototype is provided by the use of working flow and diagrams and its approach to implementation based on web programming technologies such as server active pages and web services, using its concept based analysis and design based on a waterfall model please elaborate on this model. As the number of users of the resulting systems has dramatically increased as the number of web interfaces in companies and supporting applications is growing. This trend has been accompanied by the growth in user focused design models which make user needs a priority in system design and also make user satisfaction a major measure of efficiency, performance and quality. In addition, more and more of our company please reframe and do not use 1st personx and customers are connected together through Web interfaces. The use of the web is furthermore experimented and implemented in many organisations to capture and make use of ideas in knowledge management, particularly through collaborative tools. The objective and meaning of the analysis are set in this paper. For nearly twenty years web information systems (WBIS) have been developed and used by business organisations. The objective of this project is to create an online database design that enables banks to efficiently coordinate employee, customer and other relevant information. An significant component of any framework is a database design. Traditionally, application design comprises two steps: we create a conceptual business process model and create a physical model that is implemented as a set of tables to map that model to the data basis. Therefore an overall system performance is certainly impacted by a database design. Most of the banking transactions take place online at this technologically advanced time. This is therefore a topic that needs to be examined progressively as the project deals with the design of banking databases. The project report consists of details about the conceptual and physical design of the database, generated tables and queries for different views. Project report also contains recommendations for improving the database and issues and lessons learned(Walker, 1992). Practitioners and researchers have made progress on our knowledge of how to grow WBIS. This study recognises the progress of WBIS growth and aims to boost practicers and researchers’ awareness. Business organisations are constantly adjusting to changes in the marketplace which involve the use of ICT to process and increase information quality in this evolving environment(Wu et al., 1999). In these years, which years? web technology is undergoing significant changes, both as regards types of systems based on web technology, development work, required approaches and skills, etc. We have to reconsider the construction work organisation. In this context, the essence of web creation needs to be deepened and known. In recent years, web technology has evolved considerably as a basis for the creation of complex information systems. The technology is still fairly straightforward with a range of unresolved issues, but its advantages and potential are such that much of the information system design today is focused to a certain degree on web technology reframe. WBIS needs to be developed to balance the organisation objectives and the criteria of the methodology to create information systems (ISDM). In a constantly evolving organisation, ISDM is a highly systematic and ordered approach which is difficult to use. Additional pressure from the Web developer to meet evolving organisational requirements will influence the use of WBIS methodology effectively and efficiently. Because of the organisation’s intense time emphasis, WBIS methodologies could not be adopted by the web developer as laid down. Organizations increase their web-based expenditure and use. There is an immense increase in the complexity of a web-based application and a new medium to serve all aspects of organisational function. At the same time, the activities being funded by IT are becoming more demanding and the stakeholders are facing increasing demands for better quality goods and services, better product and service complexity, higher flexibility, shorter lead times etc. Research is also done by large groups, with individuals from diverse backgrounds and perspectives, to meet these demands. The new processes and services can also be used by government organisations to generate online sales, to improve global business efficiency and dynamics, to develop applications that can be controlled from the outset, which will eliminate isolated systems and lead to systems where we can share information(Walker, 1992). Please add more references in this part Requirement analysis: Please provide relevant sub-headings Defining of the system overall functionality – missing The following tasks are our system of research and designing WBISs: E-R analysis, scenario analysis, architecture design and specification of attributes (Figure 1). First, an E-R analysis is used to analyse the problem domain under which a WBIS can work. Scenario analysis then decides how future customers communicate with the WBIS to achieve their business objectives. The architecture of the WBIS is developed based on the results of these analyses. The attributes of the WBIS web resources are then specified for maintenance. The WBIS is designed on a design basis. Finally, the WBIS is checked and brought into the workplace using the scenarios. It is held and updated throughout its entire existence after the introduction. After the E-R analysis, scenario analysis is performed to determine who the users are, what web services they need, how the resources can be visited and used and how WBISs are responding to users in order to achieve their objectives. Scenario analysis is an accepted method in the area of information technology. The research and design of WBISs – a kind of software framework – are based upon this technology. The study of the scenario is carried out as follows: first, the objectives of the users are established(Momani, 2010). Software requirements: The software is a number of processes that allow the machine to perform the various tasks using the coded information or a program that is fed into the computer hardware. The software is like a wire current that cannot be seen, but can be felt. 1. Operating System:- NT/2000 Windows / XP Hardware requirements: Hardware is a collection of physical components that executes the proper predefined instructions. In other words, electronic and mechanical computer components may be said to constitute hardware. This kit is built on a powerful Visual Basic programming language. The user interface is strong. The backend is ACCESS, used for database retention. Almost all common microcomputers are available. To run this package, the following are the minimum hardware specifications: – Computer staff: – Minimum includes a 128 MB RAM P-III processor(Momani, 2010). Scenarios and architectural designs are complementary and carried out in near cross-checks. Scenario analysis facilitates navigation paths and web tools needed to achieve users’ objectives. These paths and tools form the cornerstone of architectural design. Only after designing the architecture can the scenarios be validated. The study and design transforms entities and relationships in the diagrams of E-R into Web tools and architectural navigation links. System elements and Functionality of the system: A meta-level connection creates a semantic relationship between two web services. Meta-level connections are classified according to their semanthemas. Thus a navigation link with the same type-name can be established in an RMDMW diagram as a meta-level link.The usual connections are defined by the anchors of references in HTML files (i.e. tags). Since these links themselves form part of the Web resources material, maintainers must check every resource and, if necessary, repair errors. This makes maintaining the credibility of Web resources ties in WBISs rather difficult. The architecture we give in our study. Our work is at an initial level, so without too much technical information we want to clarify our idea here this is not a blog post. Please use an academic tone to write the paper. The first three sections are the study of requirements, the methodology of design and the architecture of four levels. The next step is the development of the Web Application following the requirement analysis that enables process analysis to be considered. Our idea is to describe a creative approach that incorporates the IDM design methodology in a timely manner, with a process description that identifies the touch points between the methodology and the process definition. Our response to the problem of relationship management is the meta-level connection mechanism. This mechanism allows users to build a connection between two remote Web sources without having to access or change the resources content. The mechanism allows users to Two HTTP methods, Connect and UNLINK are used and the information is transmitted via the LINK HTTP header fields. The Relation method creates a meta-level connection between two tools. A meta-level connection can be removed by the UNLINK process. Since the protocol uses HTTP only, users can use firewalls with sufficient protection to work with the web resources of remote sites. In addition, in handling Web-resource connections, the meta-level framework has two more advantages over HTML links(Wanli et al., 2011). (1) Meta-level links may connect non-HTML Web resources. (2) connections to meta-level can be accessed more quickly. This is because clients need only receive headers for meta-level links from servers. Clients are required to get HTML links from servers, to interpret and extract the links, and to get the bodies of web resources. WebArchitect includes graphic clients and notification agents and works with enhanced WBIS-enhanced HTTP servers. Two methods for meta-level connections can be used on the servers Connect and UNLINK. A distributed WBIS can be managed by WebArchitect, which includes more than one server on different hosts. The macro and the micro view customers are two customer groups. Macro customers present a description of a WBIS architecture. Microcustomers have a comprehensive insight into a part of the architecture and the Web resources management functions. Micro customers view the rectangle region of the Macro customer in great detail. WBISs architecture as tree graphs is visualised by WebArchitect. We use tree diagrams since hierarchy is an important structure for all functional WBIS architectures. However, loops are also part of the architecture. We use a ‘back link’ technique, which first creates tree structures and then retracts links to nodes generated after they are identified. In collaborative and batch mode WebArchitect visualises the web structure. In the interactive mode the tree structure spreads from the user-specified web resource. In batch mode, the tree structure is generated from a starting Web source set to the defined depth by the users(Wanli et al., 2011). A basic MVC architecture with a centralised database storage is intended for the website directory. Where required, the user interfaces must be built with the HTML5 and CSS3 styles. We can build the middleware with the SQL queries by using PHP scripts. The source code for each machine programme, including the file name, executed function, author and development day(Johnson, 1983). Data dictionary, including a description of any tables structure or database interacting with the system. The filename, creation date, field name, field type, field size, field length, relationships to other databases and main fields name must be included. If the app interacts with other systems. Any two types of standardised design or prototypes used for the design of any device can be used as an option. Remember the design of prototypes where system evaluations are made using a pre-created application and review is carried out to see if the new system can be applied or if modifications and enhancements are required according to the organization’s requirements. Properly document it all. This evaluation is undertaken in collaboration with the project stakeholders. Please note that it is also necessary to engage the user in this part of this phase, that we make the full display usable and comfortable and give us ideas for a design with friendly features and also useful for subsequent projects. Functionalities: The proposed system is very computer-based, in order to secure highly accurate user account data that even decreases harm to the machine and human errors, and it is highly efficient to give both consumers and banks the best possible service, as customer access is less user-friendly than a regular banking system. The validity of the data will be checked when entered. Suitable massages are given if necessary, so that the user isn’t in an instant maize. The screen for data entry is designed to allow all manipulations of the data to be carried out and also provides record display facilities. A valid user ID and device login password must be available to the customer. (The information of the user can be hardcoded to begin at the back end. We can also start with zero on the initial balance.)The current balance is shown in that specific account after a legitimate user logs in.Customers can carry out transactions such as deposit and cancellation of their accounts.The accounts of Saving Bank Account, the Credit Bank Account, and the Everyday Bank accounts are all open.Transfer to other accounts of funds.Customer deposit of money.For future references, we must keep track of all transactions as this is to be shown to the consumer.The machine must also have a different user class who is a system administrator. 7.Any banking list client may be viewed, added, edit or deleted by the administrator.All of the above tasks can work with the backend database using SQL queries with middleware PHP and front end HTML, HTML5, and CSS.After depositing or exchanging money, the user logs out and then logs in back, and the new balance should not be lost in older transactions. Figure-DRD of the system Database Design: Diagram ER is referred to as Diagram for Entity-Relation. It is used for analysis of the database structure. It displays relationships and their attributes. An ER model is a communications instrument. The following description is given in ER bank diagram: Bank has client. Bank have client. Banks are known by their name, code, headquarters address. Banks have branches. Branches. A branch no., branch name, address is defined. One or more accounts are available to the customer. Accounts are ac no., acc type, balance are listed. Loans may be used by the customer. Loan id, loan type and sum are the defining elements of loans. The bank branch is associated with account and credits. Database: type customer = record customer _ id : string; customer _ name : string; customer _ street : string; customer _ city : integer; branch(branch-name, branch-city, assets) customer(customer-name, customer-street, customer-city) account(account-number, branch-name, balance) Attributes and their characteristics are: Bank entity: Bank name, code and address are the attributes of a bank entity. Code is the Bank Entity’s primary key. Customer Entity: Customernumber attributes, names, phone numbers and addresses are Customer id. Customer id is the Customer Entity Primary Key. Branch Entity: Branch Entity Attributes are Name and Address. Branch Entity attributes. Branch id is the branch entity’s primary key. Account Entity: Account Entity Attributes are Account number, Account Type, etc. Account number for the account entity is the primary, branch-name, amount) depositor(customer-name, account-number) borrower(customer-name, loan-number) Bank has branches=>1: one bank can have several branches, but one branch cannot belong to several banks, so the bank-sector relationship can be one-to-much. Accounts => one branch may have a lot of accounts, but one account can’t belong to many industries, so that the branch-to-account relationship is one to many. Give branch credit => 1: N A industry may have many loans, but a loan cannot be part of many industries, so the branch/loan relationship is one to many. Customer loan => M: N Loan (Assume loan can be jointly held by many Customers). One customer can have several loans, and one loan can also be paid by one or several customers, which means there are several or many relationships between the loan and the customer. SQL is a syntax for the execution of queries. However, the syntax to update, insert and delete records also contains the SQL language. Ø The Data Manipulation Language (DML) of the SQL is generated by these query and updating commands: – v SELECT — Selects database v UPDATE data — changes database v Remove — deletes data from the database v INSERT INTO — adds fresh data into a database table Table Build — creates a new table for the database Altering (changing) a database table DROP TABLE – removes the table of the database INDEX Build – generates an index (search key) DROP INDEX – Removing an index SQL 2000 MS SERVER References An interactive web-based management system may improve diabetes care by doctors the name of the authors should be here. (2003). Evidence-Based Healthcare, 7(3), 119–121. citation missing Johnson, E. M. (1983). Planning and Organising A Bank Sales Management System: A Case Study. International Journal of Bank Marketing, 1(2), 41–52. please use more recent reference Koch, T. W., & Steven Scott Macdonald. (2010). Bank management. South-Western Cengage Learning. Citation missing Momani, A. M. (2010). Web-Based Evaluation System for Learning Management Systems. SSRN Electronic Journal. Shelyuk, А. (2013). Research of components of the system of bank deposit management. Journal of Governance and Regulation, 2(1), 65–70. citation missing Walker, J. (1992). Reporting systems for bank management : building a bank management information system. Toppan. please use more recent reference Wanli, F., Jun, Z., & Hong, Z. (2011). Cadre Information Management System Design and Implementation of People’s Bank. Procedia Engineering, 15, 3989–3992. Wu, C.-L., Wu, P., & Shiau, A.-L. (1999). A Computerized Management System for Cell Bank. Analytical Biochemistry, 275(2), 260–262. please use more recent reference


Leave a Reply

Your email address will not be published. Required fields are marked *