服务器作为移动应用程序用例图中的参与者 [英] Server as an actor in use case diagram for mobile application

问题描述

我开发了一个与服务器通信的安卓应用程序.通过该应用程序，用户在服务器正在运行的系统上进行身份验证，并在服务器能够向我的应用程序发送信息之后.

I have developed an android application that communicates with a server. Through the application the user authenticates on the system that the server is running and after the server is able to send information to my application.

我正在为我的应用程序制作用例图 (UML)，但我不确定是否应该将服务器表示为参与者(外部)或从图中省略它...我是 UML 新手所以目前这些定义让我有点困惑......

I'm making a use case diagram (UML) for my application but I'm not sure if I should represent the server as an actor (external) or omit it from the diagram... I'm new in UML so the definitions are a little confusing to me at the moment...

谁能帮我解决这个问题?

Can anyone help me with this?

(对不起，如果这不是提出这类问题的合适地方).

(Sorry if this is not the right place to put those kind of questions).

推荐答案

首先，图是给谁看的?你想和它交流什么?

First off, who is the diagram for? And what are you trying to communicate with it?

UC 诊断通常用于描述用户(参与者)及其想要实现的目标(用例).他们不关注如何促进用户的目标.

UC diags are typically used to dscribe Users (Actors) and what they want to achieve (Use Cases). They don't focus on how the user's goals are facilitated.

您的问题主要集中在技术上；唯一可辨别的用例是用户"Actor 的身份验证".这似乎不是特别有见地.按照这种思路，下一个问题将是:为什么需要对用户进行身份验证?即一旦成功通过身份验证，他/她可以做什么?这些东西是否在您的系统范围内?相关地，身份验证通常带有一组伴随的 UC:首先注册(例如设置名称、密码、可记住的数据)、重置/检索丢失的密码等.

Your question focuses primarily on the technology; the only discernable Use Case is "Authenticate" for the "User" Actor. That doesn't seem particularly insightful. Developing this line of thinking, the next question would be: why does the User need to be authenticated? i.e. what can he/she do once successfully authenticated? And are those things in scope for your system? Relatedly, authentication commonly comes with a set of companion UCs: registering in the first place (e.g. setting name, pwd, memorable data), resetting / retrieving lost pwd, etc.

以上所有内容都假设您确实在努力传达用户是谁以及他们需要做什么.这可能不是你的目的；也许您想传达解决方案设计(用户访问应用程序、应用程序向服务器发送消息等).如果是这样，那么使用序列图和/或组件图可能会更好.

The above all assumes you're really trying to communicate who the users are and what they need to do. It may be that's not your purpose; maybe you want to communicate the solution design (User accesses application, app sends message to server, etc.). If so then you're probably better served with sequence diagram(s) and/or component diagrams.

请注意，两者并不相互排斥:解决方案设计自然源于用户需求.所以可能两者都适用.一切都取决于你想交流什么.

Note the two aren't mutually exclusive: solution design naturally flows from user needs. So it may be both are applicable. All depends on what you want to communicate.

第

这篇关于服务器作为移动应用程序用例图中的参与者的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！