Walkman 16:55:54
Ok. Thank you.
I still have a question: How to draw "system boundary" in Rose, in PowerDesigner, it is very painful, but in rose, it can't find it. Qingrun 16:59:00. The system boundary is logo through the USE Case and Actor, and the research object within the system is not used as an example. Qingrun 16:59:15 Therefore, there is no need to set this boundary. The line passers-by 16:58:34 The system boundary is used to divide the participants within the system, the boundary of the participant with the outside.
Qingrun 17:01:13 Your definition is also very vague, what is internal participants? Use case, or actor? Qingrun 17:01:36 The internal system is not defined by the Actor, you'd better take a look at the definition of the actor. Qingrun 17:02:17 A system use case, for another system, maybe an actor. Walkman 17:02:11 I said the system, it is the processing system I want to develop, some of the internal users, is an internal actor, and there is actor outside, isn't it right?
I have written this on my book. At the same time, this also involves the issue of large systems and small systems, that is to distinguish between your research objects and objects associated with research objects.
Oh, it is not necessarily right, this needs to be judged, my statement, at least I think it is correct. Qingrun 17:05:27 Do you refer to the book? Pay attention to the definition of these things in the book. Don't make a mistake. Walkman 17:03:34 Haha, it is a bit of a little. Qingrun 17:05:42 I think it is wrong to understand. Qingrun 17:06:19 You may be confused between the large system of the two systems, and the definition between the subsystems within the large system. Of course, it does not rule out the reason why the book is wrong. I have seen a lot of books. Walkman 17:12:57 You are right, I understand the wrong Yunrun 17:15:29. Ha ha. How to understand, talk about it. I can verify that I understand it correctly. Walkman 17:15:00 I want to know now, how to put a few use cases "circle", make a "system boundary", PowerDesigner, just draw a rectangular box first, as "system boundary", put "use case" "Put it, the boundary is actor. Qingrun 17:17:28 huh, I suggest a subcontract. There is a corresponding instructions in my book. Qingrun 17:17:39 also has an example. Walkman 17:16:08 is. I still see your book last night. It is a subcontract. Qingrun 17:18:25 This is a way of dividing the internal module relationship between the system. Of course, you can also take each module into a small subsystem, which has become the relationship between large systems and small systems. Walkman 17:17:19 oh. understood.
It's just that it is not intuitive, is it? Can you see which use cases from the package? Qingrun 17:19:51 From the package, of course, can you see which packages in the package, and the exemption outside the package. Walkman 17:18:19. understood.
Want to know if you compare Rose or PowerDesigner? Qingrun 17:20:42 Do database design, generally still adopting PD. Do system design, it is not possible to use PD. Walkman 17:19:26 Can you use PD? These can be done in the PD, Yue Yun 17: 21: 50pd is to do a database design. This is my current thinking. Moreover, it is also a public understanding. Walkman 17:20:19 Well. Also.
