1

enter image description here[![ ][2]][2]

Here's the flow of my project-

1. User logs into the system providing Username and password, which is authenticated by the Server with help of the Database

2. After authentication, User ie. Farmer will be able to Start water sprinkler's Motor or
Star Pesticide sprinkler motor or
Start camera to monitor his farm or
Schedule the Water pump/Pesticide motor for future time.

3. Now Server, Water Motor, Pesticide sprinkler, Camera nor Micro controller are Humans, so Is the diagram correct to represent them as Actors? Or what is the right way to represent them? What corrections do I make?

Dev1ce
  • 5,390
  • 17
  • 90
  • 150
  • Is it correct to show Server, Camera, Motor or Pesticide bottle as Actors? Or is there some other way to represent non human components? – Dev1ce Feb 28 '16 at 12:54
  • Our lecturer taught us, that some times you can use rectangular to represent non human actors ex-inventory systems, I think your diagram looks fine – AVI Feb 28 '16 at 13:03
  • Yes there is some Blockhead symbol right? Unfortunately StarUml has no such a thing, that's why the confusion. – Dev1ce Feb 28 '16 at 13:11
  • Here's the slides of our lecturer http://imgur.com/a/SEyLs – AVI Feb 28 '16 at 13:15
  • Thank man , big help :) – Dev1ce Feb 28 '16 at 13:22

1 Answers1

3
  1. Login is no use case at all. It is a constraint you can apply to other UCs. Remove it.
  2. Generalizing UCs is a bad idea. Each UC needs to describe a separate added value the system returns to the actors. I also doubt that Motor on/off is a UC. Rather { motor must be on } is a constraint you can apply to other UCs.
  3. Remove the <<includes>> in Supply pesticides. You are using them as functional decomposition. Rather rename the UC as to what it's meant to be: Reduce insect attack. Then the application of pesticides is a result of doing the actions inside the UC.
  4. Online streaming is no meaningful UC. Think about what you are streaming and express that in the name of the UC (e.g. Stream <whatever is so nice to be streamed>).
  5. Similarly Scheduling. Tell the reader what you schedule (so he get's an idea of the why and the goal behind).
  6. Logout is as much as UC as Login. Remove it.
qwerty_so
  • 35,448
  • 8
  • 62
  • 86
  • Thanks for the necessary changes, And Do I keep Server, Motor , Pesticide bottle, Camera and Microcontroller as Actors ? Or should the use case must only be about User interaction? – Dev1ce Feb 28 '16 at 18:35
  • Yep. It's a bit strange indeed to show machines as stickmen. But that's how it's done in standard UML (the word actor is taken in its original sense as person acting, but today machines do that more often than humans). You are free to invent your own images. Stereotype your class (e.g. as <> or whatever) and assign an image. You shouldn't overdo this as it might end up in Powerpoint slides rather than UML diagrams. – qwerty_so Feb 28 '16 at 20:12
  • Thanks :) describing the Stereotype for non human components made sense, thanks a lot for all of your advice :) – Dev1ce Feb 29 '16 at 09:11