The ModelIntegra Method
However, it is surprisingly hard to write and to maintain readable, clearly structured use-case specifications for large systems. To do this, requirements analysts need guidance on how to use different textual and graphical description techniques in a consistent and methodical way.
The ModelIntegra Method provides a consistent, field-proven methodological framework for requirements analysts based on state-of-the-art description techniques.
Advantages and Features
- Clearly defined, field-proven method provides guidance for requirements analysts. Description techniques and their relations are defined by means of a UML profile.
- UML use case diagrams provide a high-level overview over the system functionality. Classification of use cases as primary, secondary and system level use cases assures a uniform abstraction level.
- Standardized textual information for use cases like description, frequency, trigger, pre- and postconditions is specified in a uniform and integrated way.
- UML activity diagrams are used as a means for precisely specifying use case behavior. Special stereotypes allow the specification of normal and variant interaction sequences based on activity diagrams. Textual action descriptions provide detailed information about intended behavior.
- Business-related data is specified by means of UML class diagrams. Business objects can be used as input and output parameters of use cases.
- Support for component-based specification and development of large information systems. Support for incremental and iterative development by partitioning specifications into work sections.
- Possibility to reference requirements, business process functions, test cases and service interfaces in order to achieve universal traceability.