ECET 365 Week 3 Lab DeVry
Just Click on Below Link To Download This Course:
ECET 365 Week 3 Lab DeVry
Lab 3:
Converting Requirements to a Work Schedule
Objectives
- Develop a map showing which hardware subsystems from the kit will be used to meet each requirement. Determine if additional parts are required.
- Determine which hardware subsystems will require software support to control the subsystems or provide communications between subsystems.
- Produce a set of tasks needed to meet the requirements. Assign tasks to team members.
- Develop a work schedule for a presentation to the class. Include serial and parallel scheduling of tasks to meet the time requirements.
Parts List
- Robotics Car Kit or Other Provided Kit
- Freescale Tower Kit with S12G128 CPU board or Other Provided CPU Board
- PC with IDE software (e.g. CodeWarrior Development Studio V5.1)
- Scheduling software (e.g. Microsoft Project)
Introduction
- The purpose of this course is to prepare you for the Senior Project. If you think this course is intense, consider that, in the Senior Project, you will not be given a kit to build. You will have to determine what you will build. In this course, the kit will be determined, although you may find that additional materials are required.
- You will also be given a set of requirements for this course. In the Senior Project, you will develop your own requirements. This course will give you an idea of how requirements are met.
- You will also learn how to develop a work schedule for a project. This knowledge will serve you well in the Senior Project.
- Finally, you will learn how to develop techniques to build the system so that you have a test plan that can be used to troubleshoot should any malfunctions occur. It is rare when nothing fails. Having a test plan will greatly maintain your sanity as the project deadline approaches.
- The lab for this week consists of mapping the hardware subsystems to the requirements, determining what software modules are required to support the subsystems, assigning work tasks to team members, and producing a work schedule that will be presented to the class at the end of the week.
Deliverables
Answer all
questions in Week 3 Lab Cover Sheet here (Links
to an external site.)Links to an external site..
Submit
your Week 3 Lab Assignment.
You
can also download the cover sheet for Week 3 Lab in the Files section of the
Course Menu.
Required
Software
CodeWarrior
Development Studio for S12(x) V5.1
Lab Steps
STEP 1:
Procedures
- Determine the project requirements.
- Read the ECET365 Smart Car Contest Rules in the Files section of the Course Menu.
- For each relevant item in the Rules, determine what subsystems are required to meet the requirement. For example, the following items may be relevant:
- The Robotic Car must follow a 1-inch-wide black stripe down the middle of the track.
- The track curves will have a bending radius not less than 500 mm. Therefore, the Robotic Car must be able to follow a curve of 500mm radius.
- The track width will be at least 600 mm, so the Smart Car must stay on the track, even as it goes around the curves.
- The Robotic Car must go around the track twice.
- The Robotic Car must stop within 3 meters after completing two laps.
- The fastest Robotic Car wins. The time is the fastest lap time for either of the two laps.
- The Robotic Car is autonomous. It is not controlled by an external driver or computer.
There
may be other requirements hidden in the rules, especially about the type and
number of microprocessors allowed.
- Determine alternative subsystems to meet the requirements.
- Create a table of requirements and alternative subsystems. A brief example is shown below:
|
Table 1
|
|||
|
Requirement
|
Alternative
1
|
Alternative
2
|
Alternative
3
|
|
Follow centerline on track
|
Linear array subsystem
|
Webcam subsystem
|
Photodiode subsystem
|
|
Make two laps, then stop at finish line
|
Counter/timer subsystem
|
Video/counter subsystem
|
Voltage monitor subsystem
|
- You may not need as many as three alternatives, or you may find that you can think of more alternatives. Use the “brain-storming” technique at this point, which means that no idea is discounted. At least, it is not discounted yet.
- Determine a set of alternatives for the actual plan. Note that there are different possible sets of alternatives, but some will come together because of their similarities and use of common resources. Consider the following:
- Time and expense to use the alternative. If the kit contains a module, that may save expense, but buying something else may save you time.
- Ordering items can be more expensive for overnight delivery, or it may cost you time to choose less expensive shipping.
- Using items with a common voltage requirement may save you development time and expense. Otherwise, you may need multiple power supplies.
- Capability of team members. Some members may be skilled at certain circuit building, sensor, or motor control techniques. This might lead you to choose an alternative.
- Prepare a work schedule.
- This is the part of the process that uses the most guesswork. You must estimate the amount of time required to assemble each subsystem, test it, connect the subsystems, test them, assemble the final prototype, and test it. Note that some subsystems require both hardware and software to be developed.
- You need to decide the order in which the subsystems will be developed and which tasks can be performed in parallel. Consult the Outline of Smart Car Project in the Files section of the Course Menu. It gives a rough idea of how much time each task requires, but it does not show you which tasks could be done with more people.
- You need to assign people to the tasks and responsibilities to the team members. Microsoft Project is suitable for building the work schedule, but of course, there are alternatives.
- Observations – Complete the following questions in the Week 3 Lab Cover Sheet and submit your Lab assignment.
- The class may have suggestions for improving your work schedule.
- You may find ideas from other schedules.
- A sanity test is best done by others outside your team.

Comments
Post a Comment