The document describes a moon rover system using UML diagrams. It includes a class diagram showing the system's classes like Mission Control, Position, and Mineral, along with their attributes and relationships. It defines stereotypes for each class. Sequence and state diagrams are also included. The sequence diagram shows the process of creating a mission plan, uploading it, and performing the rover mission. State diagrams depict the states and transitions for state-dependent classes like the Communication Unit, Camera, and Rover.

1. MOON DISCOVER ROVER SYSTEM
By:
 Raed ALDahdooh
 Mahmoud El Zaalan
 Mohammad El Tibi
SYSTEM MODEL

2. Contents
•Class diagram
•Class stereotype
•Sequence diagram
•State diagram

3. CLASS DIAGRAM
• The most important thing about class diagrams is
that they are a static view of the system.
• Classes don’t exist at runtime, only objects.
• A class diagram tells us about the structure of a
system.
• Showing the system's classes,
• their attributes,
• Methods
• Relationships between the classes.

4. Classes of the system
• We extract the classes of the system by looking in the use
cases, or we can go back to system requirements,
actually we use both to get a deep look inside the system.
Mission Control:
This class acts as a controller
to Mission Base in the earth
so it will handle the operations
of the Mission Base.

5. Classes of the system ….[ cont. ]
Mission Plan:
Acts as entity class that encapsulate data needed in the mission plane, plus some
operations on mission plane.
Position
Contains data need to store information
about positions.

6. Classes of the system ….[ cont. ]
Report
Entity class that contains reports data, as
rover id, rover state, etc.
Map
Map class contains the mapped
minerals, and obstacles along the rover
path.

7. Classes of the system ….[ cont. ]
Traversal Algorithm
Algorithm class defines the abstract data
needed to traverse, and the algorithm
which will used to enable a rover to know
how to walk through its path.
Mineral Algorithm
This class defines the algorithm data
and operations that will be used to
detect minerals.

8. Classes of the system ….[ cont. ]
Mineral
Entity class holds the data for
minerals, as width, height, weight,
color, etc.
Obstacle
Entity class encapsulates the data
gathered about obstacles.

9. Classes of the system ….[ cont. ]
Camera
This class is responsible of communication
with physical camera.
Communication Unit
Communication unit class manage the communication events between the
earth, and the rover base.

10. Classes of the system ….[ cont. ]

11. Class Stereotype
• Define stereotype for each class
• Notation from the book [H. Gomaa, Designing Concurrent, Distributed, and
Real-Time Applications with UML, Addison-Wesley, 2000] (page 161).
Class Name Stereotype Description
Mission Control <<Control>> Control the operation belongs to missions.
Mission Plan <<Control>>
It holds plan’s data plus a lot of operations
belongs to plans.
Position <<Entity>> Encapsulate position’s data
Traversal Algorithm <<Algorithm>> Algorithm class
Mineral Algorithm <<Algorithm>> Algorithm class
Report <<Entity>> Encapsulate report’s data
Map <<Entity>> Encapsulate map’s data
Mineral <<Entity>> Encapsulates mineral’s data

12. Class Name Stereotype Description
Obstacle <<Entity>> Encapsulate obstacle’s data
Rover Base <<Coordinator>> Acts as coordinator between earth and rovers
Camera
<<State Dependent
Control>>
Control class but depends on previous states
Communication
Unit
<<State Dependent
Control>>
Control the communications but it depends on
his previous states
Transceiver Unit
<<State Dependent
Control>>
Control the communications but it depends on
his previous states
Rover
<<State Dependent
Control>>
Control the operations of the rover
Rover Movement <<Control>>
Control the motors of the rover it may be
<<interface>> but its main job is to control
than to interface.
Spectrometer <<Interface>> Interface with the physical sensor
Sensor <<Interface>> Interface with the physical sensor
Timer <<Timer>> Timing operations
Class Stereotype

13. Class Diagram

14. SEQUENCE DIAGRAM
• A sequence diagram is an interaction diagram
that emphasizes the time ordering of messages.
It shows a set of objects and the messages sent
and received by those objects.
• Graphically, a sequence diagram is a table that
shows objects arranged along the X axis and
messages, ordered in increasing time, along the
Y axis.
- The UML User Guide, [Booch,99]

15. Create Mission Plan

16. Upload New Plan

17. Perform Rover Mission

18. STATE DIAGRAM
• State diagrams are used to describe the behavior
of some specific objects on a system.
• State diagrams describe all of the possible states
of an object and the transitions between those
states.
• State diagram shows how an object responds to
various events by changing from one state to
another.

19. State Dependent Classes
• Communication Unit
• Transceiver Unit
• Camera
• Rover
• Next slide view the state diagram for each object from
above classes = = = =

20. Communication Unit

21. Camera

22. Rover