Author: Jiangnan Baiyi, source: Yun.
Business modeling is an optional chapter before the entire four-step process of RUP is started:
1. the development team is very idiotic about the business of the target organization and cannot carry out system use case requirements.
2. Seek business process reengineering and automation.
The two possible reasons are different in different layers, but the goal is to draw the line of view between the client and the development team. For small teams, you can only model a small part of the business that is least clear and most important to the software systems to be developed.
Most of the concepts and processes of case modeling are used in business modeling. The ibm dw Chinese site has a good tutorial titled understanding the problems to be solved: Business Modeling Technology Introduction (you need to register a DW account for free). It's almost the same after reading it, business modeling has exceeded the scope of software. The detailed description of RUP and the UML business modeling may not be absolutely correct. Therefore, you do not have to go into the details in the RUP document.
To put it simply, the most practical component of business modeling is the business vocabulary, business case model, and business analysis model.
Business and system use cases are siblings, but the latter's main character is the software system to be developed and its functions. The former's main character turns to the entire target organization, and its core business and supporting and management business, and usually more than one system in the Organization.
The analysis model shows how to implement business use cases within the Organization. In order to take care of the reader's level, use a more intuitive and easy-to-understand swimming track activity diagram instead of analyzing the sequence diagram commonly used in the model for expression. I usually add an activity diagram directly under the use case instead of creating a usecase realize.
The two shards generally have four elements:
Bussiness use case, Business Use Case.
Bussiness actor is a customer, partner, and system outside the target organization.
Bussiness worker: employees and systems in the target organization.
Bussiness entity, a business entity, is suitable for information systems that are very sensitive to data objects.
You can easily switch from a business analysis model to a system case model. In business use cases, the activities to be attended by the development system are the use cases, and the bussieness actor or worker before and after the activities are the actor.
References:
- Ibm dw Chinese site tutorial "understanding the issues to be solved: Business Modeling Technology Introduction" (you need to register a DW account for free)
PS. sin. It's not time to write csdn's travel to Beijing.