粉丝439获赞1.2万

在待机状态按遥控器不防键一次,本机将响 dook love me 提示,提示本机进入步防模式,五秒后响一声外进入警戒状态。在不防警戒状态,触碰或者敲击, 本机立即开始响警报声,两秒二到十二秒内仍检测到触碰,则立即响三十秒持续警报声。当本机警报时,直接按遥控的撤房键,警报声将停止并退出布房模式。按闪电键,铃声有六曲可选, 循环提示不妨模式不可用 遥控配对,先装上电池, 然后长按遥控的铃声键,可进入寻码模式。在 by 的一声后,按新遥控的撤房键或者不防键 慧翔 by by 两声,你就可以使用新增加的遥控了。


hi, my name is chloe and i'll be teaching you everything you need to know about uml use case diagrams we'll start with a high level overview then we'll talk about systems actors use cases and relationships and finally we'll build an entire use case diagram together and go over examples to explain these concepts in depth have you ever had an idea that makes perfect sense in your head, but when you try to explain it to someone else they're completely lost maybe your idea is for a new app and every time you talk about it people don't really understand how they'd interact with the app or what it would do this type of scenario is where a use case diagram is very helpful here's a simple description of a use case diagram first it shows a system or application then it shows the people organizations or other systems that interact with it and finally it shows a basic flow of what the system or application does it's a very high level and typically won't show a lot of detail but it's a great way to communicate complex ideas in a fairly basic way before we really get into the tutorial let's talk about how you're going to make a use case diagram you can draw them out with pen and paper but a diagramming application is going to be much easier today i'll be using lucid chart and you can too for free actually just click the link to access lucid charts website, enter your email address and you'll have a free lucic chart account in just a few seconds it's easy to use and you can follow along with me as we build a use case diagram okay, so we're gonna break down use case diagrams into four different elements systems actors use cases and relationships let's start with systems a system is whatever you're developing it could be a website a software component a business process an app or any number of other things represent a system with a rectangle and you put the name of the system at the top, we're going to build a use case diagram for a very simple banking application we'll call our system banking app this rectangle helps to find the scope of this system anything within this rectangle happens within the banking app anything outside of this rectangle doesn't happen in the banking app the next element is an actor which is depicted by this stick figure an actor is going to be someone or something that uses our system to achieve a goal that could be a person an organization another system or an external device so who or what is going to be using our banking app? the most obvious actor is a customer we are going to have customers that download and use our banking app another actor that we want in our diagram is the bank the bank is going to provide information that feeds into our banking app like transactions and account balances here are a couple things to keep in mind when dealing with actors first, it's important to note that these actors are external objects they always need to be placed outside of our system second actors need to be thought of as types or categories for our banking app an actor isn't going to be a specific individual or a specific organization we won't label our actors as john and chase bank we want to keep things categorical so right now we're saying that both customers and banks are going to use our app and this brings up the topic of primary and secondary actors a primary actor initiates the use of the system while a secondary actor is more reactionary so in our example, which actor is primary and which actor is secondary the primary actor is customer the customer is going to initiate the use of our system they're going to pull out their phone open up our banking app and do something with it bank on the other hand is a secondary actor the bank is only going to act once the customer does something if the customer goes on the app to see how much money is in their account only then does the bank engage with our system to provide the balance primary actors should be to the left of the system and secondary actors should be to the right this just visually reinforces the fact that customer engages with the banking app and then the bank reacts the next element is a use case and this is where you really start to describe what our system does a use case is depicted with this oval shape and it represents an action that accomplishes some sort of task within the system they're going to be placed within the rectangle because there are actions that occur within the banking app so what is our banking app going to do we're going to keep things very simple our banking app is going to allow a customer to log in check their account balance transfer funds between accounts and make payments towards bills so, if this is what our banking app does we're going to have use cases that describe each of those actions we'll have a use case called login another called check balance, another called transfer funds and finally make payment you can see that each of these use cases starts with a verb and reinforces an action that takes place we also want them to be sufficiently descriptive if this use case just had transfer that would be too big finally it's good practice to put your use cases in a logical order when possible that's why we put login at the top that's the first thing that will happen when a customer uses our banking app the final element in use case diagrams are relationships an actor by definition is using our system to achieve a goal, so each actor has to interact with at least one of the use cases within our system in our example, a customer is going to log into our banking app so we draw a solid line between the actor and the use case to show this relationship this type of relationship is called an association and it just signifies a basic communication or interaction a customer is going to interact with the rest of these use cases as well they're going to check balance transfer funds and make payment so we'll draw solid lines out to each of those as well secondary actors will also have relationships remember each actor has to interact with at least one use case so which use cases will the bank interact with when a customer wants to check their balance on the app, the bank is going to provide the cracked amount let's draw a line between bank and check balance similarly when a customer wants to transfer funds or make a payment the bank is going to follow through with those transactions we don't need to draw a lion to log in because that process happens within the banking app there's no need for the bank to actually get involved with the login process there are three other types of relationships in addition to association there's include extend and generalization let's build out this diagram with additional use cases in in order to explain these types of relationships when a customer types in their login information, our banking app is going to verify the password before completing the login process, but if the password is incorrect the banking app is going to display an error message, so let's create two new use cases for verify password and display log in error when a customer wants to transfer funds or make a payment our banking app is going to make sure there's enough money to complete those transactions, so we'll also create another use case called verify sufficient funds and finally when a customer wants to make a payment our banking app is going to give them the option of paying from either their checking account or their savings account so we'll create two more use cases called pay from checking and pay from savings let's circle back to this verify password use case and talk about relationships again how does verify password relate to the rest of the diagram neither of our actors are directly initiating this action it's just immediately going to happen within our banking app every time there's an attempt to log in this is an include relationship an include relationship shows dependency between a base use case and an included use case every time the base use case is executed the included use case is executed as well another way to think of it is that the base use case requires an included use case in order to be complete when you have an include relationship, you draw a dash line with an arrow that points towards the included use case so in our example login is the base use case and verify password is the included use case every time a customer logs in our banking app will automatically verify password this login use case won't be complete unless verified password is complete so we draw a dash line with the arrow pointing towards the included use case and we write include in double chevrons the next type of relationship is the extend relationship an extend relationship has a base use case and an extend use case when the base use case is executed the extend use case will happen sometimes, but not every time the extend use case will only happen if certain criteria are met another way to think of it is that you have the option to extend the behavior of the base use case when you have an extend in relationship you draw a dash line with an arrow that points towards the base use case in our example login is a base use case and display login error is an extended use case our banking app won't display a login area message every time a customer logs in this will only happen once in a while when a customer accidentally enters an incorrect password since this is an extend relationship we draw a dash line with an arrow that points to the base use case and write extend between double chevrons hopefully this thoroughly explains the difference between include and extend relationships, but just in case here's a very basic example to help differentiate between the two if you sneeze, you will close your eyes that's an included relationship because it's going to happen every time additionally if you sneeze, you might say excuse me that's an extended relationship because it's supplements the sneeze, but isn't completely necessary in the sneezing process just remember that include happens every time extend happens just sometimes and don't forget that the arrows point in opposite directions one quick thing to note is that multiple based use cases can point to the same included or extended use case for example both transfer funds and make payment are going to point to verify sufficient funds as an included use case, we want our banking app to make this check every time either of these base use cases occur you don't need to duplicate the verify sufficient funds use case the simpler your diagram the better the last type of relationship will discuss is generalization also known as inheritance when you make a payment from our banking app you can do so from either your checking account or your savings account in this scenario make a payment is a general use case and pay from savings and pay from checking are specialized use cases you could also use the terms parent and children each child shares the common behaviors of the parent, but each child adds something more on its own to show that this is a generalization we draw this type of arrow from the children up to the parent you can have generalizations on use cases like we have here you can also have generalizations with actors in certain scenarios you might want to distinguish between a new customer and a returning customer you can make them both children to a general customer actor which would allow you to have certain behaviors or qualities unique to each of these children one last shape that we'll quickly talk about is a use case with extension points you can see an example here the name of the use case is above the line and then there are extension points below the line extension points are just a detailed version of extend relationships this use case shows that a customer can set up their profile in our banking app and then these extension points show us that when a customer is setting up their profile, they'll have the option to navigate to a couple different screens if a customer is confused they can go to profile help and if they want details regarding their private information they can go to privacy info those extension points branch off to extended use cases go to profile help and show privacy info we can even add a note to show what sort of conditions would lead to these extension points now we have a complete use case diagram with various elements that help explain what our banking app does this is a very basic example but remember that even complex systems should be restricted to a simplistic visualization of functionality behavior and relationships if you'd like to take a closer look at this example click on the card in the upper right hand corner you'll find this exact banking app example plus several other examples and resources thanks for watching this tutorial on uml use case diagrams please subscribe to our channel to see more helpful tutorials leave a comment below if you have any thoughts or questions and lastly click here to try lucid chart for free and start making your own uml diagrams。

啊,因为我今天上火了,你看我嘴角这里,嗯,长泡了啊,所以我带一个口罩,以以避免影响我美丽的容颜呐, 那我今天突然很想给大家讲解一下我的专业知识啊,虽然我是搞品质的,但是 ie 方面的一些见解的话,很想给每位朋友来分享一下。 我敢说埃及其他手法很多人只知道是什么,但是不知道怎么运用,甚至你连他的含义都不知道。我给你举一个简单的比方, 双手法。什么叫双手法?你在操作 cnc 机台的时候,你的 sop 要求你必须要双手拿证据,双手放在证据里面,然后再 加工产品,这叫不叫双手法?你开一台通床的时候,必须要双手同时按一下启动键,这叫不叫双手法。 其实很多人认为这就是双手法,因为他用到了双手在操作,其实不是所谓的双手法是什么呢?我举一个简单的例子,一群平管中心的科长在吃饭, 然后会发现大家因为工作太累了,都很饿,所以菜一上来就被吃完了, 甚至你都没有喝到汤,然后甚至你没有看到上的菜是什么,就已经吃完了。 然后因为你怎么操作呢?你每一次拿起筷子夹菜吃,拿起筷子夹菜吃, 你是单手操作啊,如果你是这样操作,一手拿筷子,一手拿勺子啊,夹菜喝汤,夹菜喝汤,夹菜喝汤, 然后你同时用上了另外一只手,你会发现你的效率提升了一倍。你本来只是能吃到 几口菜的,结果你同时还喝到了几口汤,但是你的操作时间并没有变化, 你用上了另外一只手,让你吃到喝到的东西多了一倍,所以说 i 一来对于 i 一的双手法来说,就是用上另外一只手,让你 的效率提升一倍,这才是真正的双手法。好举这一个简单的例子 告诉大家, i 一不是单单 i 一七大手法几个字那么简单,真正要运用的话,必须要首先懂得他的真正含义, 你有什么疑问留言给我,我一定给你做一个详细的解答。
