I am completing the analysis of a system am am wondering if anyone can comment on the structure and acceptability of my use case diagram.
In particular, I am interested if I have used the use case diagram in an appropriate way.
Any comments would be appreciated.
Use Case Diagram
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for that comment, I am using this as an analysis tool of a current system rather than using it to represent a solution.
Part of the system represents a manual process i.e. requesting information, getting forms etc where as the final bit reflects the actual computerised section of the current system.
I take it that your view has not changed?
This looks more like a flowchart :)
Assuming that these are all indeed system use cases - form information, form etc are all automated - there are several use cases that would need more actors e.g.
Return completed form to service. This is something Volunteer cannot complete alone. Local service has to be involved. until local service accepts the returned form, the action "return" is incomplete.
Another way to phrase it - when Volunteer "returns" the form - who "accepts" it?
Likewise when you say fwd to HR, the Local service task does not end with fwding alone. HR has to accept and acknowledge. Only upon receiving the ack can local service claim that fwding is done. So HR gets involved in this action.
Business Accounts
Answer for Membership
by: lyonstPosted on 2008-07-01 at 06:15:00ID: 21907447
Hi, Muggle08. From what I can see above I don't see any problems with the User Case Diagram. Perhaps just a few too many Use Cases..
Some comments:
Not sure if Enquire about Volunteering is a Use Case? Does this instigate any process or is it a manual process outside the system.
You could possibley combine the last 2 use cases into a single Use Case?
Also actions like Check and Forward could be combined into a Process Use Case - Such as Process Registration Form and use Post Conditions or Alternate Flows to Describe Accept/Reject actions..
Let eme know if this helps or if you have any further questions..
T.