Presented as guest lecturer for SUNY Albany's 636 - Systems Analysis in the Information Environment. The lecture is actuallly an interactive requirements gathering process where I engage the students in creating a product. They act as various stakeholders and I guide them using the slide presentation as a basis for dicussion.

1. Definitions:
• Requirements - That which is required.
• Analysis - a method of studying the nature of
something or of determining it's essential
features.

2. Correlation
• Analysis is used to gather requirements
• Functional requirements
• Non-functional requirements

3. Let's make something
• Robot
• Video game
• Bouncing shoes
•??

4. Functional
• Things the product must do.
• Arise from the fundamental reason for the
product.

5. Non-functional
• Properties or qualities the product must have
• Often relate to product success
• Sometimes enhance the product

6. Stakeholders
• Customer
• Financiers
• Users / field experts
• Developers
• ... Anyone who has an interest in the product

7. Stakeholders
• Management
• Inspectors
• Marketing
• Legal
• Opposition
• Professional standards groups
• Government
• Special interest groups
• ...

8. Constraints
• Limitations of the product
• Financial
• Time
• Physical
• Risk

9. Project Triangle
Qu
st
Co
ali
Time ty

10. How to gather
requirements
• Use your stakeholders
• Trawling
• Apprenticing
• Observing
• Interviewing

11. Tools for analysis
• Written documentation
• UML
• Use Cases
• Diagrams

12. Use Case

13. Books
- Mastering the Requirements Process
Robertson and Robertson
- UML Distilled
Fowler

14. Startup weekend
• http://techvalley.startupweekend.org
• March 2 - 4, 2012