A previous IRM article Event Based Analysis and Modelling described how business functionality in a requirements package can be broken down into a table with column headings – Event, Trigger, Initiator, Use Case name, etc. Each business function is a separate event and has a unique number. A typical business function might contain several unique events each of which we want to end up as a component of a larger software application. So how do we go from a table containing…
Continue ReadingEvent-Based Analysis & Modelling
29/04/2011 |
By IRM Training
Many business analysts mix structured techniques with UML and use events as the entry point to their analysis activity. An event can be any activity, action or business process where the system under investigation needs to respond. In this approach to business analysis, once the scope of the system has been identified, the first deliverable is a table (a list) of events. Event-based analysis aligns very well with UML and object-oriented development as both are based on how a system…
Continue Reading