Software requirement specification for banking

Improve Article. Save Article. Like Article. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert.

Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Software Engineering. You can change your ad preferences anytime. Next SlideShares. You are reading a preview. Create your free account to continue reading. Sign Up. Upcoming SlideShare. Online Banking Project. Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Download Now Download Download to read offline.

Srs for banking system Jun. Jaydev Kishnani Follow. Computer Engineer. What to Upload to SlideShare. A few thoughts on work life-balance. Is vc still a thing final.

The GaryVee Content Model. Mammalian Brain Chemistry Explains Everything. Related Books Free with a 30 day trial from Scribd.

Related Audiobooks Free with a 30 day trial from Scribd. Elizabeth Howell. Srs for banking system 1. Introduction 1. Literature survey 2. Requirements 3. Data Dictionary Design and Implementation State diagram Activity Diagram Testing And Results Conclusion Bibliography INDEX 2.

A bank has several automated teller machines ATMs , which are geographically distributed and connected via a wide area network to a central server.

By using the ATM machine, a customer can withdraw cash from either checking or savings account, query the balance of an account, or transfer funds from one account to another. A transaction is initiated when a customer inserts an ATM card into the card reader. Encoded on the magnetic strip on the back of the ATM card is the card number, the start date, and the expiration date. Assuming the card is recognized, the system validates the ATM card to determine that the expiration date has not passed, that the user- entered PIN personal identification number matches the PIN maintained by the system, and that the card is not lost or stolen.

The customer is allowed three attempts to enter the correct PIN; the card is confiscated if the third attempt fails. Cards that have been reported lost or stolen are also confiscated. If the PIN is validated satisfactorily, the customer is prompted for a withdrawal, query, or transfer transaction. Before a transfer transaction can be approved, the system determines that the customer has at least two accounts and that there are sufficient funds in the account to be debited.

For approved query and transfer requests, a receipt is printed and card ejected. A customer may cancel a transaction at any time; the transaction is terminated and the card is ejected. Customer records, account records, and debit card records are all maintained at the server. We can see long queues of customers in a bank every now and then. This queue is the final result of the slow processing speed of the Bank.

So, a highly interactive and user-friendly solution should be developed. It is immaterial with which branch of the Bank the customer deals with. For the smooth working of the bank, the bank needs to be designed in such a way that, all the operations that were previously performed with difficulties are performed easily in this system. For the customers an internet solution is the most appropriate one as almost all customers have access to it.

A well interfaced GUI would be used for connecting to the main database server for updating and retrieving the data of the customers. It would also deal with the Employees of the Bank, their registration, removal, manager allotment, etc. They may relate to emergent system properties such as reliability, response time and store occupancy.

They may specify system performance, security, availability, and other emergent properties. Here we will see the two examples for requirements, at Atomic and uniquely identified requirements levels.

So let us continue with example of system build for education domain. This is a bad requirement because it is not atomic because it talks about two different entities undergraduates and post-graduates courses. So obviously it is not a good requirement but bad requirement, so correspondence good requirement would be to separate it out into two requirements. So one talks about the enrolment to undergraduate courses while the other talks about the enrolment to the post-graduate courses.

Similarly the next requirement quality is to check for uniquely identified, here we have two separate requirement but they both have same ID 1. So, if we are referring our requirement with reference to ID , but it is not clear which exact requirement we are referring to document or other part of the system as both have same ID 1. Also, each and every requirement should be complete. Here the other relevant information is not clear, so the other relevant information should be spelt out in good requirement to make the requirement complete.

The problem in this requirement is that from the first requirement it seems that the courses are divided into two categories under graduate courses and post graduate courses and student can opt either of two but not both.

But when you read other requirement it conflicts with the first requirement and it tells that some courses will open to both post-graduate and under-graduate. Which means that every course will be marked either being as under-graduate course or post-graduate course.

Each and every requirement should be traceable because there are already different levels of requirement, we already saw that at the top we had business requirements, and then we have an architectural and design requirements followed by system integration requirements. Now when we convert business requirement into architectural and design requirements or we convert architectural and design requirements to system integration requirements there has to be traceability.

Which means that we should be able to take each and every business requirements and map it to the corresponding one or more software architectural and design requirement. So converting it to a good requirement it says same thing but it is mapped with the requirement id 4.

So mapping should be there for each and every requirement. Same way we have high level and low level mapping requirement, the mapping is also there between system and integration requirement to the code that implements that requirement and also there is a mapping between the system and integration requirement to the test case which test that particular requirement.

Then each and every requirement must be prioritized, so the team has guideline so which requirement that able to implement first and which can be done later on. Here you can see the bad priority has register student, maintain user information and each and every requirement has given priority Everything cannot be at same priority, so requirement can be prioritized.

So the example of good requirement over here is the register student and enroll courses is given the highest priority 1, while maintain user information comes below at priority 2 and then we have view report card at priority Now there are two problems with this requirement first is that each page meaning that there can be many pages, which going to blow up the testing efforts.

The other problem is that it say the page is going to load in acceptable time frame, now what is acceptable time frame?