Use Case Diagram

Here's what I have so far based on other groups' APIs. Is it too redundant to say, for example, that the GUI "uses" the communication system to send the fire command and that the gun "uses" the communication system to receive the fire command? I thought it was so I only did the commands from the GUI's perspective, but I have never made a use case document so I might be wrong.



Apparently there is a limit to the width of an image on these forums, so just pretend that there are two little men connected to the lines that go off the right side of the picture, and pretend that one of those little men is named Camera and the other is named Sensor. Here's a link to the full picture if you can't picture that:

https://s702.photobucket.com/albums/ww22/rbrenan/?action=view&current=UseCase.jpg

is this the uml or the use case or is that the same thing?

UML is kind of a standard for drawing diagrams of programs. The use case diagram is one of the UML diagrams that can be drawn, and it is the one he asked for. At least that is how I understand it.

OK...let's try this one

https://s702.photobucket.com/albums/ww22/rbrenan/?action=view&current=UseCase-3.jpg

Are rover cameras no longer moving up, down, left, right? The camera group has given me a camera movement command but they haven't given me a function for zoom in/zoom out.

swesson wrote:Are rover cameras no longer moving up, down, left, right? The camera group has given me a camera movement command but they haven't given me a function for zoom in/zoom out.

nope they are not moving the camera anymore

Ok well I gotta change our API. Has it been turned in yet? I wont be back home from work until midnight.

And finally...one Use Case to rule them all:

https://2img.net/h/i702.photobucket.com/albums/ww22/rbrenan/UseCase-1.jpg