Task 1: Requirement specification
Task1a: Stakeholders, functional and non-functional requirements for the coursework specification:
Introduction
There are about three stakeholders for the system given in the coursework specification identified by the writer; below is the list of them all, together with their functional requirements. The writer has also identified about four non-functional requirements.
a) Bank customer (User)
The functional requirements of bank customer are:
1. User Login
2. View balance
3. Withdraw cash
4. Perform deposit
b) Bank operator
The functional requirements for a bank operator are:
1. System startup
2. System shutdown
c) Bank network system
The functional requirement for bank network system is
1. Bank session_operation
Non-functional requirements for the system are:
1. Reliability
2. Availability
3. Security and
4. Performance
Task1b: Requirement specification template:
1 Introduction
This is a SRS for automated teller machine in advanced requirement requirements engineering and software architecture module. The template deviates from IEEE standard 830 - 1998.
1.1 Purpose
This software requirement specification (SRS) document is written as part of coursework exercise and is intended for the coursework module leader at De Montfort University. Other interested parties for this document can be software developers of the ATM system.
1.2 Scope
ATM is a safety-critical and real-time system and is part of a large banking network. The ATM is
Maria will be brought in to the requirements solicitation to provide information and resources of the physical requirements while agreeing upon acceptable and favorable terms for the system as a whole. Yvonne will be brought in as an overall eye of the system. Her point of view will be more thorough about the system than the end users. Her sight is of an overall understanding whereas the end users only see their portion. Other key stakeholders will be advised of the information and updated to the progress as the information becomes available. The other key stakeholders will include the other executives of Riordan Manufacturing.
The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.
The previous two parts of this three-part assignment, the systems analysis and application architecture and process design aspect of the credentialing software project at TPI Health Systems (TPI) was explored. This last paper will explore the implementation stage of the systems development life cycle (SDLC) as it related to the credentialing project at TPI.
After all the information is obtained, analysts will review, analyze and structure the information obtained so they can develop an overall understanding of the new system’s requirements. To define the new system requirements; drawing diagrams, workflow diagrams and activity diagrams will be used to express and model the new system’s processing requirements. Last, the IT team selects and recommends an alternative to Riordan Manufacturing. The recommendation recaps the results of the analysis phase activities, and together the team makes firm decisions about an alternative.
Each model was worked close by the others to guarantee streamlined correlations with be made among themselves, revealing and cross-referencing issues found while making comparable and similar models. Once these models were made, necessities and utilize cases moved toward becoming clearer and could be utilized to manufacture the Software Requirements Specification to later convey to the customer to improve the items prerequisites and stream of control to guarantee we were not missing any expected
Team Mates as you know that we have chosen the Requirements in System Development Life Cycle, so have came across the following stages in the Requirements in my research which will be posted below specifically under their requirements.
Requirement elicitation and analysis was done in series of steps. Firstly, we carefully read and analyzed the product description to identify project context. After this stakeholders of the system and the roles of these stakeholders were identified. Raw requirement for the system were identified on the basis of the
Design – The requirements needed for functioning, support, and training are designed in this step. Emphasis is given to the functioning of the system and is produced as a high level guide. All the technical details for developing the system are created in a final system design.
1.the methods used to identify stakeholders and their needs, wants and demands. Were items 3, 4, and 6 in the Concept generation table Fig 2
An automated teller machine or automatic teller machine (ATM), also known as an automated banking machine (ABM) in Canada, and a Cashpoint (which is a trademark of Lloyds TSB), cash machine or sometimes a hole in the wall in British English, is a computerised telecommunications device that provides the clients of a financial institution with access to financial transactions in a public space without the need for a cashier, human clerk or bank teller. ATMs are known by various other names including ATM machine, automated banking machine, and various regional variants derived from trademarks on ATM systems held by particular banks.
This ATM system requires that there be an active network link to the Bank and that the ATM has available cash to dispense.
One of the important goals of Requirement Analysis is to develop a high quality requirement specification document.
The proposed system must ensure accurate and predictable delivery. This is possible only if ATM is a Connection-Oriented system.
Along with the ATM Card and the Pin there is also need for a validation process to ensure the authenticity of the user ad the security measures to contact the bank and also withhold the card. The system must also return the card to the user. The withdrawal process has its own set of requirements, there has to be a validation in place that allows the users to only withdraw certain bill and only those bills. For the deposit requirements it only goes without saying that the user is only allowed to deposit the same bills that they are allowed to withdraw as well there is a limitation to how much the user can deposit at any given time. The system should also allow the user to transfer money between different accounts, as well as the bank types does not have to be the same. The system should give the uses the option to print a receipt which should contain nature of transaction, balances, date, time, location and a photograph. It should also give the user various notices in the form of prompts. The system should also update the database of the bank and account of the user
The account holder can easily access their money through ATMs, transfer and check their account online. Although, banks put limits on the number of transactions and transfers per month.