In the tomorrow unit, I asked me to tell the system concept from the perspective of business data. I really don't know what way to express and explain. So I have learned the following discussion, I feel similar to what I encountered. Article link: http://www.shecn.com/best/g1/g107.htm China UML Forum
Original (KKNIGHT) Help discussed: I always feel that Rose is defect on painting business flowchart -------------------- -------------------------------------------------- ------------
I can't find which function of Rose can be very good. Business Use Case View, USE Case View, Class Diagram is not suitable. It seems that Activity Daigram is appropriate, but it is not possible to layered, and the courseware is relatively simple. I think that in the business model, ROSE should introduce data flow maps to describe the overall business flow diagram. I hope everyone will discuss it. ==== Activity Daigram is actually very similar to the data flow map. In the UML, there is an unclear thing for a graphic, and you can use documents and other diagrams that this expansion is not available. - <0b> BOSS_CH 2001/03/07 11:50 (20 clicks) ==== Original (John_Zhu at 2001/03/07 13:14 Paste) Reply: Help discuss: I always feel Rose's business process There is a defect on the figure ------------------------------------------------------------------------------------------------------------------------------------ ----------------------------------
Business flow charts can be drawn by Activity Daigram, but first Rose is an object-oriented modeling tool, to give up a part of the traditional implementation when modeling, using rose to use ROSE. In the establishment of UML, it is controversial during the establishment of Activity Daigram, mainly because the use is not good, will sacrifice Rose's objectivity. There is also his truth in Rose, but the data flow map can be used as a tool for discovery objects. Not necessarily in Rose, of course, if you must be painted in Rose, it is also possible, use Activity Daigram to add Business Entity, but it is a bit unmelted ==== Original (KKNIGHT passed at 2001/03/07 14:02) Reply: Help discuss: I always feel that rose has a defect on the business flow chart --------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------
I think the data flow map is a good place to be able to understand, communicate, and even participate in the production. In fact, customers, especially business customers, they have their own business flow charts, such as bills and operational flow charts, which are very met with data flow maps. I think it is still good to add data flow map in the early stage of commercial modeling or demand analysis. I don't emphasize that it is different from it because it is indeed different from OO. But you can use other tools to draw data flow maps, even with PowerPoint, Visio, but my feelings are ROSE, you don't advocate this thing, emphasize the use of OO methods in business modeling phases to describe the real world. I want to analyze this thing is to let people understand, so it is necessary to introduce some representations close to the reality. Personal view, I hope everyone will correct. ====== Original (Gooses paste at 2001/03/07 15:00) Reply: Help discuss: I always feel that Rose is defective on the flowchart of the business process ------------ -------------------------------------------------- ------------------
Business Processing Sequence Diagram Actor >> Form Object >> Control Object >> Data Object Which database is controlled by Control Object to determine which database.
Business Query Sequence Diagram is similar, but the process has a certain difference.
The Actor is generally classified by the role.
==== Original (Lcgong) Activity Diagram, USE Case Model, Collaboration Diagram is flexible to use. -------------------------------------------------- ------------------------------
Activity Diagram, Uses Case Model, Collaboration / Sequence Diagram is the different views of Business Modeling. It is a different cross section of the system architecture. There is also a logic between the profiles. Therefore, for the user as long as the appropriate order, the level is explained, the customer can understand, because the symbol of the UML itself is not complicated. ==== Original (LIAOFAN) The system modeling is based on the system modeling, the business process is the form of expression ------------------- -------------------------------------------------- ---------
UML emphasizes the object-oriented modeling, emphasizing the reuse of analysis results. The most important thing is to establish a stable model framework based on the problem facing the system, and one of the criteria for checking the framework is whether the business process can achieve smoothly and whether the business process can adapt to changes. So it does not emphasize business flow chart in UML, and Activity Daigram is just an auxiliary means. Too much attention to business processes, easy to get into the trap of process analysis, affect the inherent rationality of the model. === Not completely, the business process within Rose is not defined, implied in the relationship between USE Case and Usecase - <0B> John_Zhu 2001/03/08 14:37 (19 clicks) ==== Original text (OMC2000 paste at 2001/03/08 09:04) Reply: Help discuss: I always feel that Rose is defective on painting business flowchart ------------------- -------------------------------------------------- ----------- You can use activity diagram. === Original (Asiaalien) Reply: Help discuss: I always think Rose is in painting business flow chart defective------------------------------------------------ --------------------------------
Can take a look at Playcase! I think you must be software such as MIS system to domestic users, otherwise Rose is very good. === Original (Rode paste at 2001/03/09 08:56) Tube ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------
Essress UML - 1 Software Requirements Business Process USE-Case Application System Architecture Diagram: Sequence Diagram and Interaction Diagram belongs to the analysis model for the business domain, based on the basic concept of the business domain, not abstract Out of object concept; there is a sequencediagram and intection diagram when designing, at this time, the concept is based on the concept, which is a detailed design, and it is developed from an outstanding design; Data Model: Index mode of database mode.
Note: UML is just a modeling language, so it can replace the E-R diagram, business flow chart (business flow chart will spatially flattened, and use-case is a space model), data dictionary. ==== Original (John_Zhu at 2001/03/09 09:32) Business Flow Chart, ER map is also a means of system modeling ------------------------------------------------------------------------------------------ -------------------------------------------------- ----------------
The difference between UML and traditional structured modeling methods is not only on ideas, and there is also a way, I personally think not to use UML to harden the traditional structured modeling method. ==== Original (Rode paste at 2001/03/09 10:37) Tube See you: --------------------------------------------------------------------------------------------------------- -------------------------------------------------- -
Tube 2: Our purpose is the model of the system, that is, from different angles and perspectives to look at the concept of the entire business field, UML constructs models in the business field, indeed, he built a UML world Live business model, but how to build this model
Before, you must first understand the business domian; however, the data graph is indeed from the perspective of function or active.
The perspective of the body describes the BD, which is a whole understanding (see what you use), so the skeleton of the system is coming out. Then
We can use UML to describe this skeleton while adding blood and meat, and Business Domain Model has appeared. Private consideration: The flowchart is indispensable.
