Some of you may be working on systems with many complex relationships between the parts. These complex systems may be described as a system of systems, or may be described as a product line, or perhaps both at once.
In these cases, you will often find that the requirements of a large, overall system are shared among a number of related projects, each of which implements some well-defined part of the overall system.
Author: Geri Schneider Winters
This paper provides an in-depth introduction to the new BPMN standard, illustrating how it is used to model business processes and web services. The paper also provides greater detail on how BPMN fits within BPM, BPEL’s, BPMS’s, UML and other new industry standards and initiatives described above.
Geri Schneider Winters writes about whether or not you could write alternatives to alternatives in use cases.
There is no actual standard for the formatting of a use case specification, just guidelines and best practices. Therefore, if using alternatives to alternatives in use cases makes the use case more clear - use it, by any means.
"Business Analysis is about thinking what your solution should do, while Design is about how to make it happen using the technology available. Don't ever combine the two - you save nothing." This paper by Brian Cooney, principal instructor at IRM, describes the need for clear separation between the two phases and the benefits this provides for a successful project outcome.
Author: Brian Cooney
Given a specific project with a reasonably defined charter and clear business goals you, the business analyst, set out to elicit and document the detailed business requirements. So when do you stop? How do you know when you are done gathering the requirements?
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: