System Analysis and Design ( Requirement Determination )

1. What is Requirements Determination?

• It refers to converting high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models.

1. What is a requirement?

-  a statement of what the system must do or a characteristic it must have and will later evolve into a technical description of how the system will be implemented. . It describes a system feature, capability, or constraint. Generally requirements focus on what a system should do, rather than how it should do it. It must capture and describe user information requirements in a form that is precise and easily understand by users.

2. Fill-in the table below as many details as you can:

Functional Requirements	Description	Examples
Process-Oriented	- refers to the calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish.	● Every order shall be allocated a unique identifier (ORDER_ID) which the user shall be able to copy to the account’s permanent storage area.
Information-Oriented	- is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.	● The user shall be able to search either all of the initial set of databases or select a subset from it. ● The system shall provide appropriate viewers for the user to read documents in the document store.

2. Fill-in the table below as many details as you can:

Non-functional Requirements	Description	Examples
Operational	is the ability to keep an equipment, a system or a whole industrial installation in a safe and reliable functioning condition, according to pre-defined operational requirements.	• The system should be able to fit in a pocket or purse • The system should be able to integrate with the existing inventory system.
Performance	-  is the rate of work accomplished by a computer system. Depending on the context, high computer performance may involve one or more of the following:	• Any interaction between the user and the system should not exceed 2 seconds. • The system should receive updated inventory information every 15 minutes.
Security	- is the degree of resistance to, or protection from, harm. It applies to any vulnerable and/or valuable asset, such as a person, dwelling, community, item, nation, or organization.	• Only direct managers can see personnel records of staff • Customers can see their order history only during business hours.
Cultural and Political	-is the ability to function in other geographic/cultural areas.	• The system should be able to distinguish between United States and European currency • The system shall comply with insurance industry standards.

4. What is Use Case?

- is a series of related interactions between a user (or more generally, an “actor”) and a system that enables the user to achieve a goal. To phrase this definition in another way, a use case describes the system's behavior as it responds to a series of related requests from an actor.

-  is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term "system" refers to something being developed or operated, such as a mail-order product sales and service. Use case diagrams are employed in UML (Unified Modeling Language), a standard notation for the modeling of real-world objects and systems.

1. What is use case diagram?

• is a representation of a user's interaction with the system that shows the relationship between the user and the different use cases in which the user is involved. A use case diagram can identify the different types of users of a system and the different use cases and will often be accompanied by other types of diagrams as well. Just like the figure below.

5. Fill-in the table below as many details as you can:

Step	Activities	Typical Asked Questions
Identify the use cases	System Startup System shutdown Session<<include>> Invalid PIN <<extend>> Transaction Withdrawal Deposit Transfer Inquiry	How does ATM banking work? What are the ATM banking system steps?
2. Identify the major steps within each use case	System is started when the switch is turned “on”. System is shut down when the switch is the turned “off.” System reads a customer’s ATM card Individual types of transaction will be tested below Withdraw System asks customer  to choose an account to withdraw from Deposit System asks customer to choose an account to deposit to Transfer System asks customer to choose an account to transfer from Inquiry System asks customer to choose an account to inquire about Invalid PIN Customer is asked to reenter PIN	What steps does an ATM operator do in ATM bank?
3. Identify elements within steps.	Operator Panel Operator Panel Card Reader Customer console, consisting of a display and keyboard Choose withdrawal transaction Network connection to the bank Cash dispenser Envelope acceptor Receipt Printer	What are the components of an ATM Bank?
4. Confirm the use case	A real ATM typically has a timeout mechanism that begins beeping and ultimately ejects the card and ends the session if the user fails to respond within a certain amount of time. While a customer who leaves before this happens might inadvertently leave a card behind, at least the customer would not be "logged in" with his/her PIN. (Thus, the security risk is comparable to that resulting from a lost card, with the customer's account still PIN protected.)	What changes would be needed to the system requirements, design, and code to improve security this way?