在线作业门户系统用例图 [英] Online Job Portal System Use Case Diagrams
问题描述
我想为在线职位门户系统提供正确的用例图。这是我的尝试：
I want to have a correct use case diagram for an online job portal system. Here is my attemp:
我有些疑问：
-
我看不出在哪里制作登录用例巫婆是该系统的重要用例。
I can't see where making "Login" use case witch is an important use case for this system.
该用例图未显示简单访问者和已注册访问者之间的区别。前者可以查看职位空缺，也可以查看建议，而不必承担开户的义务。后者可以查看职位空缺，查看建议，上传简历（登录后），申请工作（登录后）...在我的图表中是否有两个角色简单访客和注册访客是正确的？还是有一种无需增加第二个参与者就能区分这两个参与者的方法？
This use case diagram is not showing the difference between a simple visitor and a registered one. The former could view vacancies, view advice without the obligation for having an account. The latter could view vacancies, view advice, upload CV (after be logged), apply for a job (after be logged) ... Is having two actors "Simple visitor" and "Registred Visitor" in my diagram will be correct? Or is there a way to differentiate these two actors without the need to add a second?
Edit1：
考虑到您的评论，这是我的修改版本：
Taking into account your remarks, here is my modified version:
Edit2：
我对用例图感到不满意。这是我的新版本。用例添加的用例是：
I feel unsatisfied with my use case diagram. Here is my new version. use Cases added are:
- 主持人：通知求职者/雇主，拒绝职位空缺/申请，管理付款。
- JobSeeker：查看简历，下载简历，查看申请状态，查看雇主详细信息，搜索雇主。
- 雇主：查看简历，搜索简历，下载简历，编辑职位，删除职位，查看工作查找者详细信息，搜索工作查找者。
对于开发部分，我想将工作分为三个模块：一个用于主持人，一个给JobSeeker，一个给雇主。
And for the development part, I want to partition the work into three modules: one for the moderator, one for the JobSeeker and one for the Employer.
是否有备注？
推荐答案
-
我认为，登录名应属于帐户管理，如此处。您还可以在其中添加密码恢复作为登录的包含。
I think, Login should belong to Account management, as it is here. You can also add there password restoring as "include" of login.
关于新老用户，这并不容易。因为，这种差异也适用于雇主。新雇主只能看到没有私人信息（简称为缩短的简历）和职位空缺的简历，并且无法获得申请和发布职位空缺。我认为，您应该在右边有四个角色-已注册/未注册的搜索者/雇主。未注册的参与者将是已注册参与者的概括。这由更一般的实体上带有空心三角形的箭头表示。因此，如果您已经为未注册的人（父母）显示了与某个用例的联系，则无需为已注册的人（孩子）再次显示该用例-他从其父母那里继承了所有东西。
About new and old users it is not so easy. Because, this difference is applicable on Employer, too. new employer can only see CV without private info (let's call them Shortened CV) and vacancies and can't get applications and publish vacancies. I think, you should have four actors on the right side - registered/unregistered Seeker/Employer. Unregistered actors will be Generalization of the registered ones. This is shown by arrow with empty triangle on the more general entity. So, if you already have shown a connection to some use case for an unregistered guy(parent), you don't need to show it again for the registered one(child) - he inherits all from its "parent".
- 关于将状态从未注册更改为已注册，您可以画一个状态机图来解释它-状态图是第二常见的图在UML中可以直接用在用例图中。但是，如果是为了真正的工作，则不需要-它太明显了。
您可以将如果将属于相同主题的用例组划分为子系统，该图将更具可读性。您还可以对不同的子系统及其用例使用不同的颜色组-客户和老师只是喜欢彩色图片：-）
You can combine the groups of use cases belonging to same themes into subsystems, the diagram would be more readable. Also you can use different colours groups for different subsystems and their use cases - clients and teachers simply LOVE coloured pictures :-)
如果可能的话，请直接使用
If it is possible, use straight lines or curves for connections - it will be more readable.
而且您在这里没有任何付款系统！是超出范围了，还是您忘记了？
And you haven't any payment system here! Is it out of scope, or you have forgotten?
这篇关于在线作业门户系统用例图的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
