In this topic i will share about the fundamental concept of Requirement in agile software development, deep dive into detail processes of how to manage the requirements from the beginning and the last we will try a lot of tools accordingly
- Principal Software Architect at Telkom Indonesia
- Engineering Lead of Digital Product Engineering Chapter Digital Business & Technology
- Solutions Architect at Online Single Submission System (oss.go.id)
- Head of Engineer at PeduliLindungi
- Software Architect Lead at Telkom Indonesia
- Professional Mentor at Purwadhika Digital Technology School
- Cloud Computing Instructor at Google Bangkit
- Software Engineer
- Professional Lecture
- Researcher
- Speaker
- Author
Rony Setyawan, S.T., M.Kom., CCP., CSAP.
“As a rule, software systems do not work well until they have been used
and have failed repeatedly in real applications.”
by Douglas Crockford
Section One
Introduction of Requirements
Software requirements for a system are the description of what the system should do, the service or
services that it provides and the constraints on its operation
Software Requirement
- (1) A condition or capability needed by a user to solve a problem or achieve an objective.
- (2) A condition or capability that must be met or possessed by a system or system component to satisfy a
contract, standard, specification, or other formally imposed document.
- (3) A documented representation of a condition or capability as in 1 or 2.
Requirements
Software Crisis
Never Completed System Missed Deadlines Exceeded Budget
Difficult to modify It works but difficult to use Doesn’t t do all that required of it
Loss of trust from users
Section One
Introduction of Requirements
Requirement Process Actors
Section Two
Requirement Processes
USERS
PROJECT LEADER
CUSTOMERS
REQUIREMENT
ANALYST
MARKET ANALYST
DEVELOPMENT
TEAM
TEST TEAM
REGULATORS
STAKEHOLDERS
MAINTENANCE
TEAM
PROJECT SPONSOR