User: 3291191 (qingrun)
========================================================== ============
Message group: tech-savvy (157)
========================================================== ============
Message Type: Chat History
========================================================== ============
--------------------------------------------------
Message object: ********* (fengwu qingqiu)
--------------------------------------------------
15:58:59 fengwu qingqiu
Hello :) Let's get started .. I am not very clear about the relationship between P40 and p41 cases in your book. first, you must call usecase2 every time you call usecase1. but I checked the UML reference manual. it is possible. the base may or may not be well formmcm without the specified sion
15:59:57 qingrun
Oh.
16:00:14 qingrun
Can you post the full text. In this section, I should not make such errors.
16:00:31 qingrun
There is an error in the book, that is, the direction of extend is reversed. I didn't notice it at the time.
16:02:12 fengwu qingqiu
The second problem is the <extend> relationship. In Figure 1.8, usecase2 is an extended use case of usecase1. but is the arrow reversed .. the description in the UML Reference Manual is a dashed arrow is drawn from the extension use case symbol to the base Use Case symbol with a stick arrowhead on the base.
16:02:43 qingrun
Yes, this is the error I mentioned just now.
16:02:48 fengwu qingqiu
Sorry... I asked the second question in white... why am I playing?
16:02:55 qingrun
Include should be correct.
16:02:57 qingrun
It's okay.
16:03:44 fengwu qingqiu
First, please wait a moment. I will give you a description about the inclusion.
16:04:19 qingrun
Okay. Haha
16:08:10 fengwu qingqiu
The includsion explicitly modifies the effect of the base. The base may or may not be well formed withou the SiON,
An instantiation of the base executes the extension Sion.
------
Contains the effect of modifying the base use case displayed by the use case. The base use case can or does not contain the use case, but the base Use Case instance executes the use case. (The Chinese version of the UML reference manual translates the mechanic's book .)
16:11:09 qingrun
Yes. This passage is the same as what I mean.
16:11:56 qingrun
The base use case can include or does not include the included use case. However, during execution, the hard-running instance must execute the included use case. There is no difference. Haha
16:12:22 qingrun
This translation is relatively easy. It is a print, not a free translation. Haha
16:14:51 fengwu qingqiu
Can I understand it intuitively. for example, I have a use case called user management. there are two use cases: User addition and user deletion. the user manages the use cases <include> added by the user and deleted by the user.
16:17:02 qingrun
This is not the case.
Because not every time a user is managed and executed, it will be added and deleted. if you separate the two, this is the result. Therefore, you cannot use include or extend.
If you add a use case in user management to obtain the user list, it is an include, because whether it is to delete or add, you must first obtain the user list for operation.
16:20:58 fengwu qingqiu
Haha .. so what does the base may or may not be well formed without the sion do? I'm a little dizzy .. when will it be included?
16:26:49 fengwu qingqiu
The reason why I asked this question is that I still have a book on hand .. it makes the relationship between member management and member information updates <include> .. member Management <include> member information update ..
16:27:08 qingrun
I think he means: In this base case, you may have implemented or not implemented this included case. That's all. There is a possibility that, in user management
The added user must include the basic information and detailed information of the user. It is possible that the basic use case user management only includes the addition of basic information, and the addition of detailed information is implemented through this included use case.
16:27:34 qingrun
This relationship has been explained for nearly three years. No problem.
16:27:47 qingrun
What book are you talking about? Let me see.
16:27:58 qingrun
I think it may be that the book was wrong.
16:29:00 fengwu qingqiu
Haha... tools commonly used by system analysts... soft test tutorials. Edited by CSAI ..
16:29:20 qingrun
Haha. I understand. He wrote the error. I can guarantee this.
16:29:34 qingrun
I know those soft exams. One of my friends participated in the compilation.
16:29:46 fengwu qingqiu
OK... That's fine. I'll bother you with the next question.
16:30:04 qingrun
What's the problem? Please.
16:30:10 fengwu qingqiu
Alas. It's boring. Get a certificate. At least you have a certain goal in your life.
16:30:30 qingrun
Take an exam. It also has advantages.
16:32:37 fengwu qingqiu
According to your experience, when will the system architecture be designed? When else? I plan to use J2EE at the very beginning. Or a small system. I thought it could be done with MVC at the very beginning. Then I began to analyze the requirements.
16:34:29 qingrun
In fact, this is not an immediate task. In general, the architecture design starts after the initial requirement is obtained and ends after the analysis model starts. During model development, there is another adjustment, or modification.
16:36:40 fengwu qingqiu
Oh... I think we need to develop our R & D capabilities. For example, some companies are familiar with J2EE. Maybe the architecture of any system is J2EE.
16:37:10 qingrun
Haha. Of course there will be a habit problem. This is beyond the technical influence. Haha
16:38:06 fengwu qingqiu
^_^... I am very sorry to talk to you today. Today is Thanksgiving. Happy holidays. I will try to disturb you if you have any questions... haha
16:38:51 qingrun
Sorry, if you have any valuable questions, please feel free to disturb me. Don't ask me purely conceptual questions. Haha
16:42:25 fengwu qingqiu
To be honest, I am working on application software in a hardware company... to add value to hardware... I used to carry a project by myself. haha .. softwares do not pay much attention to these issues... sometimes we can only blindly touch the image .. small projects are also integrated. recently I want to lead a large project .. no .. it is also for the convenience of future maintenance colleagues.
16:43:18 qingrun
Oh, yes. A larger project requires a higher degree of standardization. This is inevitable. We can also see from the manufacturing industry.
16:44:56 fengwu qingqiu
The most painful thing is that there is no need to investigate the object .... because it is not for a specific person or organization. therefore, you can only refer to other products. then let go of your creativity. have you ever experienced this?
16:46:27 qingrun
Haha. Yes. However, there were very few projects that grew bigger and bigger.
16:50:40 fengwu qingqiu
How do you analyze your needs .. think about it first .. will you deliberately give up some good ideas due to technical restrictions .. for example, I plan to use J2EE at the beginning. however, some ideas cannot be implemented. then I deliberately avoided this. I mean my creativity is bound by the inherent software technology.
16:54:31 qingrun
Haha. This is a technical approach. No. To make software, you must be pragmatic, rather than simply selling technology. People in China still don't understand what software is, so they always come up with a variety of jokes.