The document discusses the process of defining requirements for a new system. It involves understanding the current system, identifying improvements, and defining requirements for the new system. The final deliverable is a system proposal that compiles detailed requirements, use cases, process models, and data models. Requirements determination transforms high-level business needs into precise requirements for what the system must do. Requirements include business, user, functional, system, and nonfunctional needs. The process involves elicitation techniques like interviews to work with stakeholders and determine requirements.

1. Requirement
Definition

5. Process of analysis
• Understand the existing situation (the as-is system).
• Identify improvements.
• Define requirements for the new system (the to-be
system).

6. Requirements Determination
• The final deliverable of the analysis phase is the system
proposal, which compiles the detailed requirements
definition statement, use cases, process models, and
data model together with a revised feasibility analysis
and work plan
• Requirements determination is performed to transform the
system request’s highlevel statement of business requirements
into a more detailed, precise list of what the new system must
do to provide the needed value to the business.

7. Requirement
• A requirement is simply a statement of what the system must do or what
characteristics it needs to have.
• describe what the business needs (business requirements);
• what the users need to do (user requirements);
• what the software should do ( functional requirements);
• characteristics the system should have (nonfunctional requirements); and
• How the system should be built (system requirements).

8. Business requirements
• “Increase market share”;
• “Shorten order processing time”;
• “Reduce customer
• service costs”;
• “Lower inventory spoilage”;
• “Improve responsiveness to customer service requests”; and
• “Provide account access to mobile customers.”

9. User requirements
• user requirements describe tasks that the users perform as an integral part
of the
• business’ operations, such as:
• “Schedule a client appointment”;
• “Place a new customer order”;
• “Re-order inventory”;
• “Determine available credit”; and
• “Look up account balances.

10. Functional requirement
• A functional requirement relates directly to a process the system has to
perform as a part of supporting a user task and/or information it needs to
provide as the user is performing a task.
• “the product capabilities, or
• things that a product must do for its users.
• define how the system will support the user in completing a task.
• user requirement is “Schedule a client appointment.”
• The functional requirements associated with that task include: “Determine
client availability,” “Find available openings matching client availability,”
“Select desired appointment,” “Record appointment,” and “Confirm
appointment.”

12. System requirements.
• Describing how the system will be implemented.
• System requirements focus on describing how to create the software
product that will be produced from the
project.

13. Nonfunctional requirements
• “the quality attributes,
• design, and implementation constraints, and
• external interfaces which a product must have
• behavioral properties that the system must have, such as performance and
usability.
• The ability to access the system through a mobile device

15. Process of Determining Requirements
• Elicitation techniques that can be used to acquire information, including
• interviews,
• questionnaires,
• observation,
• joint application development (JAD), and
• document analysis.
• businesspeople and analysts working together to determine requirements.
• who have an interest in the new system (often called stakeholders)

20. Requiremen
ts definition
• Requirements definition—
is a straightforward text
report that simply lists the
functional and
nonfunctional
requirements in an outline
format
• Requirements definition
for Holiday Travel
Vehicles, a fictitious
recreational vehicle
dealership.

22. Strategies - Requirement Analysis
• Problem Analysis
• Root Cause Analysis
• Duration Analysis
• Activity-Based Costing
• Informal Benchmarking
• Outcome Analysis
• Technology Analysis
• Activity Elimination

23. Problem analysis
• Problem analysis means asking the users and managers to identify problems with the as-is system
and to describe how to solve them in the to-be system.
• Most users have a very good idea of the changes they would like to see, and most will be quite
vocal about suggesting them. Most

25. Music
Download

26. System
Proposal

28. • https://fajarbaskoro.blogspot.com/2023/03/panduan-standarisasi-
dokumen.html