Whether purchasing and configuring a system or building a system from the ground up, too many projects deliver systems that fail to cater for the complexity of the real world, allow too much or too little data entry freedom and/or break down over time.
Why is this? It’s often because of a mistaken belief that users and developers between them can design a system without the involvement of a business analyst.
Our speaker, Graham Witt, will describe some projects that have failed in this manner and describe what went wrong, why, and how such problems can be avoided.
This breakfast briefing will provide you with an insight into the following topics:
- checking for ambiguity in user requirements
- understanding relevant real world objects and their lifecycles
- moving from specific to generic concepts
- dealing with exceptions
- understanding the business rules behind the user interface
- designing for update as well as insertion
Attendees will learn:
- The relevance of these issues and how they impact Agile Projects, Data Warehouse and Big Data projects; and
- What analysis needs to be done if the resulting system is going to work as required for more than a few months.
Register now!
