use-case

问题 I'm making a use case diagram for a new system. I'm wondering when a system should be included as an actor in use case diagram? Thanks. 回答1: As stated in another answer, an actor is a system or role interacting with the system under development. You should include a system as an actor in a use case if it is outside the system you are developing, and if it directly interacts with the system you are developing. This is important because you need to define the boundary of your system, which

问题 I am very new to the concept of use case diagrams and I am a little confused, I have a use case diagram "Monthly Report Archiving" and I want to ask if the use of << include >> of a case must pass login? and Is the use case that I made correct? so in my case right now it's about "Monthly Report Archiving". The flow is: public relations receives a proposal from the community, then the proposal data will be stored by the community relations into the system to be later seen by Division X and

问题 I'm creating a plug-in which adds various functions on top of a core application. The plug-in gives administrators the ability to upload a CSV file and performs the following functions depending on the information entered in the file (by performing operations on the database of the core application): Creating users Can be administrators or normal users Creating projects Can be parent projects or sub-projects of a parent project Sub-projects get copied from a given parent project (so the

问题 I'm creating a plug-in which adds various functions on top of a core application. The plug-in gives administrators the ability to upload a CSV file and performs the following functions depending on the information entered in the file (by performing operations on the database of the core application): Creating users Can be administrators or normal users Creating projects Can be parent projects or sub-projects of a parent project Sub-projects get copied from a given parent project (so the

问题 I found a strange keyword in NSObject.h - (oneway void)release; I searched the web, and learned it relates to asynchronous message passing, which looks similar with Erlang's message passing. It seems this can make many interesting things. What are some good use-cases of this keyword? 回答1: oneway is used with the distributed objects API, which allows use of objective-c objects between different threads or applications. It tells the system that it should not block the calling thread until the

问题 hello, my first question is how I can place cases to better readability? I want to make this diagram fit on a A4-sized paper. But I am aware that this diagram may be badly made, so I ask you to advice, maybe I should share on the smaller part? 回答1: You need to to connect a use case only to its primary actor. So eventually you have to create a common role where the UC is used by this common actor role. Then your specific actors inherit from this common one. Like in @Amir's example

问题 I'm not sure if i got the right concept. I was told by people that Boundary = View Entity = Model Control = Controller however based on my knowledge of MVC. (fat model, thin controller) Isn't the Boundary = Controller, Control = Model (the busienss logic) and Entity = Model (The orm classes or similar entity classes which does only crud ). I may be wrong, please guide me! 回答1: Actually your first definition is simply correct. The meaning of words is sometimes confusing. The following link

问题 I'm not sure if i got the right concept. I was told by people that Boundary = View Entity = Model Control = Controller however based on my knowledge of MVC. (fat model, thin controller) Isn't the Boundary = Controller, Control = Model (the busienss logic) and Entity = Model (The orm classes or similar entity classes which does only crud ). I may be wrong, please guide me! 回答1: Actually your first definition is simply correct. The meaning of words is sometimes confusing. The following link

问题 I have a use case that the actor will contact with, that use case includes two other use cases. The actor can contact with them as well. So my question can I connect the actors to those two use cases? This the first image where the actor is just connected to the main use case, this is the second image where the actor is connected to both the main use cases, and its included two use cases is the second correct? 回答1: If the included use case (UC) can be run only as inclusion/extension to some

问题 I have a use case that the actor will contact with, that use case includes two other use cases. The actor can contact with them as well. So my question can I connect the actors to those two use cases? This the first image where the actor is just connected to the main use case, this is the second image where the actor is connected to both the main use cases, and its included two use cases is the second correct? 回答1: If the included use case (UC) can be run only as inclusion/extension to some