Q: It is easy to make some designers to produce some misunderstandings when Usecase, such as the insensitiveness between the use of examples, the flow of data streams, there are other weaknesses, how to avoid these problems? A: The use case is a good way to help determine the boundary of the system. Reasonable use does not have a big problem. And at different stages of the process, the care of the use case is different, and the use case itself is able to track. The whole process tracks. The Software Process used is influential to how to use better usage. It is part of Software Process, such as from the perspective of the system, will help. It is a double-sided blade, it is well-skated, just fine. Q: The designer is too early to enter the USE CASE, and the premature decomposition of Use Case so that the internal structure of this system is not closed, how to avoid this problem? A: A good process will have a great help. For example, RUP defines the products you can get in each stage. Of course, in actual work, you need to grasp this degree. That is, it is not possible to enter the detail phase prematurely, causing transition design; there is no detail, working entirely under the thick line, causing no design. It is possible to cut a process for your company and your own team. A stable team is needed to practice, especially a stable process coach. The team fluctuates too much, unfavorable and processes, then the use of use-case, class diagram ....) is not very good. Stable team, suitable / clear process, reasonable role allocation should help Q: Organization model, data model, business process model, function model (USE case), we have been walking when applying application design This method A: Organization model, data model, business process model, function model (USE case) is a specific technology, not Process. Process defines the products that can be obtained at each stage, such as what particle size is obtained during the demand phase- Case, in the analysis phase, your use-case must be the TRACE of the demand phase, at this stage you want USE-CASE to refine what is metric, you need it to help describe USE-CASE. Every stage of product is different, but from the entire processs, they are continuous, can be manageable. Similarly, you introduce data models at that stage, what is the particle size, need to be defined, this process is the software process Crop, can also be said to be our software company's own process transformation. And this process can also be described by UML, and the original process is guided.
