1. Elicitation and Requirements
By Craig Estano

2. My background University of Oregon: Computer Science graduate
Delivering large complex enterprise level systems
Waterfall methodology experience
Blue Cross Blue Shield
Kaiser-Permanente
Agile methodology experience Since 2004
Idaho Department of Health and Welfare
eBay
Fidelity Investment
Western Governors University
Red Bell Real Estate

3. Requirements? What are requirements? How do you get them?
How do you know the requirements are pertinent?
How do you know the requirements are complete?
How do we know we are being Agile?

4. What are requirements? Business Requirements Functional Requirements
Scope of work
Functional Requirements
Features
User Stories
Task
What is the Difference?
What
How
Non-Functional Requirements
ISO 25010
Extensibility
Interoperability
Maintainability
Monitoring
Security
Availability and Stability
Performance
Scalability
Usability
Licensing

5. Software Development Life Cycle
Planning
Defining
Designing
Building
Testing
Deploying
Maintaining

6. Business Requirements
When should this occur?
During Planning and Defining
What are the deliverables?
Business Strategic Plan
Problem & Solution Defined
Scope of Work
Strategic Plan, What are we trying to solve for?, Who are the users?, & How will it solve the problem?

7. Functional Requirements
When should this occur?
Waterfall
Planning thru Designing
Agile
Continuously
What are the deliverables?
Use Cases
Features
User Stories
Mockups
Tasks

8. Non-Functional Requirements
When should this occur?
What are the deliverables?
During Planning
Availability and Stability
Disaster Recovery
Monitoring
Security
Performance Requirements
Scalability
Thru Designing
Accessibility
Compliance
Extensibility
Interoperability
Usability
Thru Testing
Backup
Maintainability
Testability
Performance Testing
Compliance issues are probably imbedded in your business rules - maybe 2 or 3 stories
In the example of Fidelity requiring 1k tps. You can just write a couple stories that the system should be fast. Every CRUD – Performance, Thruput and Load. Log time stamps for every transaction.
In the eBay example. If you need to know and possible block an actor. 1 story will not prevent attacks. IP address, how many time has the user login failed, what is the GPS location on the mobile device

9. Non-Functional Matrix (ISO 25010)
Rank
Non-functional requirements
Comment or example
Ownership 5
Accessibility
Usability by people with disabilities
Team, Drew 1
Availability and stability
SLA or mission capable rate
Backup
Backup can be complicate when data is in multiple locates
Drew
Compliance
Dan Jackson, Rob Harris Drew
Disaster Recovery
set of policies and procedures to enable the recovery or continuation of vital technology infrastructure
Drew (DB) Kevin (Hardware) 3
Extensibility
adding features, and carry-forward of customizations at next major version upgrade
Team 2
Licensing
Legal issues or Patent-infringement-avoidance
Craig Estano
Interoperability
Works across known and unknown browsers and devices
Diego
Ranking
1 = Extremely important Mission critical
3 = Slightly important Consider and plan for these
5 = Not important Discard from planning
Lookup ISO Create a matrix. Rank their importance. Assign Ownership

10. How do you get Requirements?
Stakeholders perspective
Executives perspective
BA perspective
PAUSE

11. BA Core Concept Model (BACCM)
Prepare for Elicitation
Conduct Elicitation
Confirm Elicitation Results
Communicate Business Analysis Information
Manage Stakeholder Collaboration
All seriousness aside. How do we really get requirements

12. Elicitation Techniques
Brainstorming / Focus groups / Workshops
Mind Mapping
Surveys and Questionnaires
Observation / Interviews
Process Analysis and Modelling

13. Characteristics of Requirements
Atomic
Complete
Consistent
Concise
Feasible
Unambiguous
Testable
Prioritized
Understandable

14. Elicitation Results Verify Requirements Resolve conflicts
Documentation
Presentations
Approved Requirements

15. Questions?
Craig Estano
Red Bell Real Estate