Getting It Right
•Download as PPT, PDF•
9 likes•1,255 views
Why and how to separate business rules, and business requirements
![Agenda ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (17)
Similar to Getting It Right
Similar to Getting It Right (20)
More from Scott Sehlhorst
More from Scott Sehlhorst (8)
Recently uploaded
Recently uploaded (20)
Getting It Right
- 1. Getting it Right Rules and Requirements in Software James Taylor Scott Sehlhorst
- 3. Challenges in Specifying Systems Elicitation of requirements, processes, rules is error prone
- 4. Challenges in Specifying Systems Elicitation of requirements, processes, rules is error prone Implementation of complex software takes too long
- 5. Challenges in Specifying Systems Elicitation of requirements, processes, rules is error prone Implementation of complex software takes too long Changing existing applications takes too long
- 6. Challenges in Specifying Systems Elicitation of requirements, processes, rules is error prone Maintenance costs are excessive Implementation of complex software takes too long Changing existing applications takes too long
- 7. The Challenges / Goals
- 8. The Challenges / Goals
- 9. The Challenges / Goals
- 13. Different Models for Different Needs
- 15. What are Business Rules?
- 26. Rules and Requirements Overview
- 27. Rules and Requirements Overview
- 28. Rules and Requirements Overview
- 29. Rules and Requirements Overview
- 30. Traceability (Rules <-> Requirements)
- 31. Traceability (Rules <-> Requirements)
- 32. Traceability (Rules <-> Requirements)
- 33. Traceability (Rules <-> Requirements)
- 44. Review of Use Cases & Rules
- 46. Thanks James Taylor – [email_address] Scott Sehlhorst – [email_address]
Editor's Notes
- Anyone developing software will agree that getting it right—building software that is destined for success—is critical. It is no fun to build the wrong software or to build software that fails—fails to do what is needed, fails to delight its users, fails to meet its users’ needs. Managing requirements, and the process of defining requirements can materially contribute to building the right software. But business rules are not requirements, and they must be found, developed and managed differently. What you will learn: The differences between rules and requirements. How they can and should be developed together. What techniques work for capturing and managing them. What to watch for.