Software Engineering SEN (22413) MSBTE Micro Project

 Software Engineering (22413) MSBTE Micro Project

Software Engineering SEN (22413) MSBTE Micro Project

program Name and Code: Software Engineering SEN (22413)

Course Name and Code: CS 4 I

Academic Year : 

Semester: Fourth

Annexure-I

A MICRO PROJECT ON "Bank Management System"

1.0   Aims/Benefits of the Micro Project

Aim:- This software is capable of managing various transactions such as new account entries, deposits, withdrawals, money transactions for different processes, loan entries, and bill management using cash or cheques. Consequently, these features of the software will enhance system efficiency by saving transaction time.

2.0   Course outcome addressed.

1. Select the relevant software process model for the given problem. 2. Prepare SRS for the given problem. 3. Prepare test cases for the given module. 4. Estimate the size & Cost of the software product using the given method. 5. Study & apply software quality assurance (SQA) activity for given software.

3.0 Proposed methodology

1. Focused on the selection of an appropriate topic for the micro-project.

2. Select the topic i.e. To Prepare a report on Bank Management System.

3. Brief study on our topic.

4. Gather all information based on the topic of the micro project.

5. Analysis and study of our topic in detail.

6. Following all the above methodologies we successfully completed our microproject.

4.0 Action Plan

Sr. No.	Detail of activity	Plan start date	Plan finish date	Name of responsible team members
1	Searching the topic for micro-project
2	Search information from the Software Engineering SEN (22413) book and from the internet.
3	Discuss with the project guide.
4	arrange all information in MS Word
5	Prepare a report on it using MS Word
6	print micro project

5.0 Resources used

Sr. no.	Name of resource material	Specifications	Quantity
1	Computer System	16 GB RAM, Windows 11 OS	1
2	Internet	Youtube / Wikipedia
3	textbook/manual	Software Engineering SEN (22413)	1

annexure-II
Micro-Project Report

A MICRO PROJECT ON "Bank Management System"

Brief Introduction/Rationale

Software Engineering serves as the basis for adhering to professional processes that involve principles, techniques, and practices in software development. This course offers a structure for software professionals to construct software products that are guaranteed to be of high quality. It empowers students to combine their expertise in a specific domain with their programming abilities to produce top-notch software products.

1. Project Scope:

• The scope of this project is limited to the operational activities of the banking system's units, which encompass account opening, fund deposits, fund withdrawals, and transfers. 
• This application can be utilized by any bank to enhance customer service. 
• Customers can conveniently access all their accounts across different branches of the same bank with just one click. 
• Additionally, the bank can use this application to share upcoming plans with customers. Managers can also access all accounts within the bank using this application. 
• Furthermore, there is potential for global communication among all banks worldwide if this application is extended.

2. OVERALL DESCRIPTION

• Product Perspective

The client will have access to a client interface, which allows them to interact with the banking system. This interface will be web-based and serve as the webpage of the banking application. Initially, a page will be displayed, prompting the user to indicate if they are an ordinary or corporate customer. Afterward, the page will redirect to a login page where the user can input their login details. If the login information is valid, the user will be directed to a home page that displays their entire transaction list, allowing them to perform various banking activities. All of these activities fall within the client interface. The administrator, on the other hand, will have an administrative interface that utilizes a graphical user interface (GUI) to view the entire system. They will also have their own login page, enabling them to access their respective actions.

This administrative interface offers various environments in which he can manage the database and create backups for the stored information. Additionally, he can register users by assigning them usernames, and passwords, and creating accounts in the database. Moreover, he can access and handle checkbook requests to provide them to clients.

• Product Features

1. Login Process This module allows valid customers to access the functionalities provided by the bank.
2. Balance Enquiry This module maintains the balance details of a particular account.
3. Update Profile This module allows the customer to update the profile of their account.
4. Funds Transfer This module allows customers to transfer funds from one account to another within the same bank.
5. Change of Password This module allows customers to change their password.
6. Mini Statements This module allows customers to view their transaction details

•  User Classes & Characteristics

Customers: Normal users must have either a fixed or savings account and maintain a minimum balance of Rs. 500. They are able to transfer funds to another account within the same bank and can access their monthly or annual statements. Industrialists, entrepreneurs, organizations, and academicians: These users are required to have all three types of accounts and maintain a minimum balance of Rs. 20,000. They can view the statements of their respective organizations or industries.

• Design & Implementation Constraint

• This system works only on a single server.
• This is designed in ASP.Net.
• The language used is C#.
• Limited to HTTP/HTTPS protocols.

• User Documentation

A registered user can have the following facilities:

• Accounts and accounts status.
• The balance inquiry.
• The fund transfer standards.
• Cheque Book Request.
• Password Changing.

• Assumption & Dependencies

The details of customers such as username, password, account type, and their corresponding authority details should be manually entered by the administrator before using this system.

• Every user should be comfortable of working with a computer and net browsing.
• He should be aware of the banking system.
• He must have basic knowledge of English too.

• Operating Environment

3. EXTERNAL INTERFACE REQUIREMENT

• User Interface

There are four different ways for a user to interact with the system:

• Viewers:

Numerous individuals who are unidentified or lack authentication visit the official website of the Bank through the Internet. They gather information and discover the various schemes offered on the bank's web page. These viewers or visitors eventually become customers of the bank.

• New User:

Who visited the Bank webpage or heard about the bank and is preparing to open an account in the bank? They register the bank application form, submit it, and open an account at the nearest bank.

• Existing User:

The existing user is the most common type of user in the online banking system. Each user has their own account and registered or authorized login access. The existing user can log in online to their account and perform operations such as depositing, withdrawing, transferring, making balance queries, and conducting transactions. Doing all these banking operations online is helpful for the user as it saves time and is an efficient process.

• Administrator:

The admin is the master user of the system because they play the main role in the system. The admin grants and maintains the database of existing users and also grants permissions to users. The admin has authority over all other users.

• Hardware Interface

• Software Interface

• Communication Interface

The APNA Bank website, www.apnabank.com, provides banking facilities that can be accessed anytime and anywhere through the Internet. Additionally, it offers a Mobile Banking service that operates through SMS.

• The client on the Internet will be using HTTP/HTTPS protocol.
• Client on Intranet will be using TCP/IP protocol
• A Web Browser such as IE 6.0 or equivalent

4. Other Non-functional Requirement

• Performance Requirement

The system can handle a large number of customer requests for the desired service. Access is only granted to valid bank users who need services such as balance inquiry, profile updates, fund transfers, mini statements, stop payment requests, and cheque book requests. It is available 24/7 throughout the entire week.

• Safety Requirement

By integrating a secure database and proven DB2 UDB into the system, we can ensure reliable performance and data integrity. It is essential to have a power backup for the server system due to the product's 24x7 availability and the need to provide uninterrupted information. Additionally, it is crucial to back up the data daily, even if a user's operation is unsuccessful or a power failure occurs during the operation.

• Security Requirement

Sensitive data is safeguarded against unauthorized access through the use of suitable technology and the implementation of strict user-access criteria. The facility provides unique user numbers and passwords in such a manner that prevents unauthorized users from logging in. Operational rights for individual users and terminals can be defined, ensuring that each user is granted access only to specific terminals and options.

Online Banking utilizes the SSL (Secure Socket Layer) protocol to transfer data securely. SSL is an encryption method that establishes a protected environment for transmitting information between the customer's web browser and the Bank. To encrypt the SSL session, Online Banking employs a 128-bit digital certificate provided by VeriSign. SSL is widely accepted as the standard for encrypted communication and guarantees the security of the customer's interactions with the Bank on the Internet.

• Software Quality Attributes

1. Usability

The system has two types of users - members and administrators. Members are expected to have basic knowledge of computers and Internet browsing, while administrators have more in-depth knowledge of the system and can fix any issues that may occur due to disk crashes, power failures, or other emergencies. To ensure smooth usage of the system, it is essential to provide a proper user interface, user manual, online help, and a guide for using and maintaining the system. These resources should be comprehensive enough to educate users on how to use the system effectively and avoid any difficulties.

   2. Reliability

The safety-critical system prioritizes dropping to the next lower floor and opening its doors if it deviates from normal operation mode. This emergency behavior must only occur for valid reasons. The system must be highly reliable to ensure the integrity of data and prevent any potential harm caused by incorrect or incomplete data.

   3. Availability

When operating under normal conditions, a user's request for service shall be handled within 1 second. The user will receive immediate feedback on the system's activities through a clicked link page. Even during peak system load, individual users at the server in the security office, at the links, or inside the banking system will not experience any service response delays longer than 1 second. The system is always available for the user, being used 24 hours a day, 7 days a week, and 365 days a year.

5. System Design

• Process Description(Data Flow Diagram

A data flow diagram (DFD) is a visual depiction of how data moves within an information system, illustrating its procedural elements. Frequently, DFDs serve as an initial phase in generating an overview of the system that can be further developed.

COMMON DFD OF BANK SYSTEM

ZERO LEVEL DFD

1ST LEVEL DFD

Test Cases

Test Case Name	Test Case Description	Step name	Step Description n	Test Data	Expected Result
TC_ATM_01_Ban k Money withdrawal verify card insertion with invalid cards	This test case to validate card insertion functionality with invalid card	Step 1	Insert invalid card of Other bank card in the insertion point of ATM	Invalid card like other hank card	ATM should not accept the card and display a message "please insert valid ATM card". invalid bank card in the insertion point of ATM Invalid card like other bank card
TC ATM 02 Bank	This test case	Step	Insert invalid card of expired ATM card in the insertion point of ATM in wrong angle	Valid	ATM should not accept the
Money withdrawal	to validate	2		Atm	card and display a message
verify card	card insertion			card	"Sorry unable to process"
insertion with valid	functionality
Card	with invalid
	card

TC ATM 0_3Bank Money withdrawal_ verify pin number entry with invalid pin number	This test case is verify the functionality of pin number functionality with invalid pin number	Stepl	Insert valid card in the insertion point of ATM	Valid ATM Card	ATM should display the language page with the following objects ENGLISH, TELUGU,HINDI
Money withdrawal_	This test case is to verify the functionality of pin numbers functionality with invalid pin numbers upto 3 times	Step1			ATMshoulddisplay
verify pin number entry with invalid pin number up to 3 times		Step 2			languagepage. ATM should display the pin number page in
					corresponding language
					selected.
_ATM_Bank_ Money withdrawal	This test is to verify	Step 1	Insert valid card Valid	Valid atm	ATMshoulddisplaylanguagepage.
verify account type	functionality		ATM in the	card
selection with	of an object		insertion
correct			card
account type			point of
with correct			ATM
TC ATM 09 Bank	This test is to	Step	Enter the	Valid	ATM should display The
Money withdrawal	verify the	1	valid Valid	pin	account type selection
verify account type	functionality		pin ATM	number	page
selection with	of the		should
wrong account type	account		display the
	selection		account
	type with		type
	wrong		selection
	account type		page.

6.0 Skilled Developed/Learning Outcome of this Micro-Project

• Select a Suitable software process model for software development.
• Prepare software requirement specifications.
• Use Software modeling to create data designs.
• Estimate size and cost of software product.
• Apply project management & quality assurance principles in s/w development

7.0 Application of this Micro-Project

1. Online banking with key banks is fast, secure, convenient, and free.

2. Quick, simple, authenticated access to accounts via the web application.

3. Simply scalable to grow with changing system requirements.

4. Global enterprise-wide access to information.

5. Improved data security, restricting unauthorized access.

6. Minimize Storage Space.

Go to Link