Exercise 2, SWE 2410: Trained Delivery

Office mail delivery robots have been around since the 1980s. One of the early ones is shown to the right. Your group is tired of them not being on your residence hall floor, so you have decided to build a simple one that uses a track to deliver the mail. Draw a domain diagram for this system:

• The robot rides on a track with bumpers at each end that stop the robot. The robot has sensors to determine when it has reached the end of the track and needs to reverse direction.
• There is a tab at each room, and the robot has an electronic reader to determine when it is in front of a particular room.
• The robot has a small arm that can be used to deposit mail into a tray for each room.
• There is a camera on the robot that can be used to check for the room number for each item.
• Mail can be in the form of either envelopes or small boxes. Boxes are placed into one basket and letters into another.
• Each basket has a weight sensor that is used by the robot to detect new mail being placed into it. When that happens, the robot uses its arm and camera to order the items in the same order as the rooms. It then travels to the room, first going to one side of the track and then the other.
• Reading room numbers on letters is done by holding the letter in (with the arm) front of the delivery camera and reading both sides. Reading room numbers on boxes is done by using the arm to rotate each of the six sides to the camera.
• Undeliverable items are placed in a reject basket.
• If the robot has no more mail to deliver, it goes to the nearest end of the track and waits for new mail.

As for exercise 1, create a domain diagram for this description. The diagram must be drawn using Enterprise Architect and all students must submit their own diagram. You may work with another student on the model, but you must document who you work with as a note on the diagram.

Include classes, attributes, operations, associations, generalizations (including abstract classes or interfaces), multiplicities, and role names. Using EA, draw a class diagram capturing this information. In addition, satisfy the following:

• Use proper naming conventions (upper case class names, lower case attributes and methods). Ensure all names are meaningful.
• The diagram must include inheritance, associations, and multiplicities other than 1. There should be no part of the diagram that is completely disconnected from another part - that is, you should be able to trace a path from any class to any other by following associations and generalization arrows.
• Give key attributes and methods for several classes, but you do not have to be comprehensive. Think in terms of operations the hardware residents would recognize like arm and bumper.

Follow the directions in exercise 1 to remove all types. Then export the model as a png, convert that to a readable pdf that minimizes whitespace, and upload that to Canvas.