use-case

问题 I'm making a new app the would need multiple social registration beside the regular email/password signup, however there is a particular case that might cause problems with data integrity ... Example: A user signs up with facebook but no email was returned. I create in the db a user with email and password set to null, and a social profile entry with his id, token and provider name. then the user next time signs up with email and password, so i create a new record in users table for him. And

问题 I have a follow up question from CRUD in a use-case diagram? If i am required to break down complex use case such as " Manage User " (Let's assume this is complex), would it be alright to extend them into different cases? Or should i use include? 回答1: This is fine. <<extend>> means that the extending UC is optional. As a side note: avoid <<extend>> and <<include>> since they are a sign of functional decomposition. And that's not what you are supposed to do with use case synthesis. CRUD

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 3 years ago . I want to ask you about my class diagram. I'm making a class diagram for simple web portal for my weekend university studies. Is it made correctly? What would you change if I you were mine? Use cases you can find here Class diagram from use case diagram. Should I create each

问题 I am writing a Product requirements specification. In this document I must describe the ways that the user can interact with the system in a very high level. Several of these operations are "Create-Read-Update-Delete" on some objects. The question is, when writing use cases for these operations, what is the right way to do so? Can I write only one Use Case called "Manage Object x" and then have these operations as included Use Cases? Or do I have to create one use case per operation, per

问题 Let's say I have the following actor : User Let's say I have the following Use Cases : Register Log On Complete Demographics Survey Choose Modules I'm confused as to how to properly model the Log On use case. Currently I have a diagram that has a relationship between the User and Log On. Should the Log On use case be included (includes relationship) with each use case (with the exception of Register) since the user needs to be logged in to complete those functions? 回答1: If the user is

问题 From my experiance, JavaScript does this: manipulating the DOM or other host objects adding event handlers doing Ajax Since I started digging into prototypal inheritance, I would like to know how it is actually used in practice. What are the use cases? Is anyone here actively using inheritance patterns? What for? (I understand that there are lots of answers to my question - I just would like to hear some of them to get the feel of using inheritance in JavaScript) 回答1: My experience working

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 2 years ago . I am new to writing use cases.I heard that Use cases are non-technical expressions . I have the following task for which i have to write Use case. ( I reduced the requirement for your understanding ) Registered Customer of ABC company logged in to the system with credentials

问题 I'm developing an application that takes advantages of restaurants' dataset. Each week my system will run a CRON job in order to synchronize the restaurants that are available on a public API to my database. However, how do I draw the sequence diagram for this CRON job? Who is the actor? 回答1: The actor would be some scheduler (or you can use the Cron object if you like). The target would be your Synchronizer object doing all that fancy web scanning. You can use a loop fragment to show the

问题 Question 1: What is the correct way to build a Use Case (or more than one) with 2 ways to do the same action? For example: I have a 3 screens in an iOS app: 1. A map view, which can be "long pressed" and has a camera button. 2. A camera view, which is shown if the user taps the camera button in the map view. 3. A place/pin editing view, which is shown if the user "long presses" the map view, or after the user chooses a photo in the camera view. This editing view has a save button to actually

问题 The concept of a coroutine sounds very interesting, but I don't know, if it makes sense in a real productive environment? What are use-cases for coroutines, that can be solved more elegant, simpler or more efficient as with other methods? 回答1: True coroutines require support from your tooling - they need to be implemented by the compiler and supported by the underlying framework. One real world example of Coroutines is found with the "yield return" keyword provided in C# 2.0, which allows you