Project #1

Adaptive Cruise Control (ACC)

 

This project will be divided into a series of assignments. Each assignment will have a separate due date.

Assignment #1

Develop requirements statement including product qualities. This will be the basis for developing the architecture for an ACC. I would suggest using a use case diagram and a set of use case descriptions (although they can be abbreviated). One template for a use case description is given here. A number of tools are available for drawing the use case diagram including the Omondo plug-in for Eclipse. It can be found at www.omondo.com. This assignment is for a team of 4.

Due: February 1, 2005 by 9am via email. Submit the list of team members, the use case diagram, and the use case descriptions.

Assignment #2

Develop the context for the architecture by performing a domain analysis and establishing the boundaries of the system. Use a UML class diagram to show the concepts and relationships. Then use AADL to (1) represent those domain classes that are on the boundary of the system (those that are touched first by a use case scenario) and one layer outside the system. Use AADL "system" structures to represent these. Be sure to incorporate any changes that this activity produces to your requirements and qualities. Be certain that by the end of this exercise you have the qualities in a priority order.

Due: February 8, 2005 by 9am via email. Submit the list of team members, the diagrams and definitions and any changes to the previous assignment based on this assignment.

 

Assignment #3

Embedded systems virtuall always have a hardware abstraction layer. For this assignment begin the development of the architecture by separating the components identified inside the system for the last assignment and develop a layered style in which one layer is the hardware abstraction layer and all else is in a separate layer. Use AADL to show this. Every externally identified component should be considered for inclusion in the hardware abstraction layer.

Due: February 15, 2005 by 9am via email. Submit the list of team members, the diagrams and definitions and any changes to the previous assignments based on this assignment.

 

Resources: The following is a set of reference material. Some give direct information that will be useful on the assignment and some are more background in nature.

1

2

3

4

5

6

7

8

 

The CAN page at Bosch

 

A specific ACC product including block diagram

 

MC33989 Product

 

MC33989 Block Diagram

 

MPC5200 Product

 

MPC5200 Block Diagram

 

Here is a set of constraints (from a similar assignment given at the University of Michigan)

The radar unit has a range of about 500 feet. The radar unit provides three data items:

1. A ``lead vehicle detected'' signal when a vehicle is present. ``Lead vehicle detected'' is not present when no vehicle is within detection range.

2. The distance to the lead vehicle.

3. The closing speed between the car and the lead vehicle.

The car shall never close closer to the lead vehicle than 2 seconds of separation.

Brakes can be applied with deceleration of 0 to 12 ft/sec2 in increments of 1 ft/sec2.

The engine control module will accept a digital speed message to hold the car at a given speed. A release signal resumes manual throttle control.

The driver's accelerator can be overridden with the speed control.

Either the cruising speed (if cruise is set) or the speed determined by the driver's accelerator must be resumed when possible.

A signal is present when cruise is engaged.

The system must not be active at or under 25 M.P.H.

A driver's display must indicate when automatic braking is occurring and when speed is being limited to avoid the danger zone.