Embedded Files
- The connection between Operation Requests and Machine is Share Phenomena.
- The Workpieses are entirely contained in the Machine.
- There are no Phenomena involving the Workpieses that do not also involve the Machine.
- The Operation Requests are a one-dimensional active dynamic domain:
- Operation Requests occur in some time ordering without external stimulus.
- Operation Requests accounts for only some aspects of the users domain.
- Operation Requests are seen simply as a time-ordered sequence of operations, structured only with respect to the individual Workpiese.
- The Workpieses form an inner dynamic domain:
- The Workpieses can change, but only in response to externally controlled events.
- A Workpiese is independent to another Workpiese:
- An operation is an operation just on one Workpiese.
Business Process Modeling with URN:
- User Requirements Notation (URN) combines goals and scenarios in order to help capture and reason about user requirements prior to detailed design.
- URN is generally suitable for describing most types of reactive and distributed systems, with a particular focus on Telecommunications Systems and Services.
- The applications range from goal modeling and requirements description to high-level design.
- URN has concepts for the specification of behavior, structure, goals, and non-functional requirements, which are all relevant for business process modeling.
- Goal-Ooriented Requirement Language: Captures business or system goals, al-ternative means of achieving goals, and the rationale for goals and alternatives.
- Non-Functional Requirements
- Use Case Map:
- A Use Case Map model depicts scenarios as causal flows of responsibilities that can be superimposed on underlying structures of components.
- The Use Case Map responsibilities are scenario activities representing something to be per-formed (operation, action, task, function, etc.).
- Responsibilities can potentially be allocated to components, which are generic enough to represent software entities (e.g., objects, processes, databases, or servers) as well as non-software entities (e.g., actors or hardware resources).
- Scenarios are initiated at Start points, represented as Filled Circles, and terminate at End points, shown as Bars.
- Paths show the Causal Relationships between Start and End points.
- Generic Components are shown as Rectangles, and they are responsible for the various activities (called Responsibilities and indicated by X’s on a Path) allocated to them.
- Labels for guarding conditions are shown between Square Brackets.
- Diamonds are used to represent Stubs, which are containers for sub-maps called Plugins.
- Stubs have named Input and Output segments that are bound to Start and End points in a Plugin, hence ensuring the continuation of a scenario from a parent map to a submap, and to the parent map again.
- Business Process Modeling (BPM) is a structured method for describing and analyzing opportunities of improving the business objectives of stakeholders, including providers and customers.
- BPM usually involves identifying the roles of users involved in the process, and the definition of activities (often described as workflows or services) that contribute to the satis-faction of well-defined business goals.
- BPM approaches need to address the well-known “W5 questions”:
- Why do this activity?
- What should this activity be precisely?
- Who is involved in this activity?
- Where and when should this activity be performed?
- A business process model should enable ways of (formally) analyzing the processes and goal satisfaction.
- Business process models should be understandable to various stakeholders, including customers.
Process-Aware Information Systems:
- Person-to-Application Processes: Workflow Management
- Person-to-Person Processes: Computer-Supported Collaborative Work
- Enterprise Application Integration and Business-to-Business Integration Processes
- Process Modeling Using UML
- Process Modeling Using Event-Driven Process Chains
- Process Modeling Using Petri Nets
- Patterns of Process Modeling
- Process Design and Redesign
- Process Mining
- Transactional Business Processes
- Standards for Workflow Definition and Execution
- The Business Process Execution Language for Web Services
- Workflow Management in Staffware
- The FLOWer Case-Handling Approach: Beyond Workflow Management
Page updated
Google Sites
Report abuse