1 / 12

Design Through Curriculum on Embedded Systems

Design Through Curriculum on Embedded Systems. Team: Aisha Grieme, Jeff Melvin, Dane Seaberg Advisors: Dr. Tyagi and Jason Boyd Client: Dept. of Electrical and Computer Engineering. Conceptual Diagram. Use Case Scenario.

triage
Download Presentation

Design Through Curriculum on Embedded Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Through Curriculum on Embedded Systems Team: Aisha Grieme, Jeff Melvin, Dane Seaberg Advisors: Dr. Tyagi and Jason Boyd Client: Dept. of Electrical and Computer Engineering

  2. ConceptualDiagram

  3. Use Case Scenario • Junior student interested in getting a birds eye view of the junior curriculum through a design exercise • Goal: appreciation of role of compartmentalized course topics in some system level design. (in this case a robot). • Precondition: student's learning style requires him/her to appreciate the global view before being able to learn the detailed topics

  4. Functional Requirements • The project will show students how to apply concepts learned in other classes • The course must be able to be reused for several semesters. • The course will be based on CprE 308 (Operating Systems: Principles & Practice) and Com S 311(Algorithm Design) and will utilize pre-emptive scheduling, multithreading and algorithms

  5. Non-Functional Requirements • Programming robot instructions should be clear easy to follow • Project rules should be fun and not just seem like requirements for the class • Competitiveness should be at least somewhat fair • There should be checkpoints in the curriculum • Learning LabVIEW and implementing games can be completed in a semester as a group project

  6. Assumptions • Students will be working in groups • The class size will not exceed the capacity of the lab • The student will have taken CprE 288, 310, 381, EE 230, ComS 228, 311 and 309.

  7. Constraints • There is a cost associated with the components and supporting software. • The platform must support threading and process scheduling • The robots must be standardized for each team

  8. Tasks Breakdown Learn Labview as a Group Learn Hardware Capabilities Develop Course Requirements Documentation Construct Hardware Write Software

  9. Project Schedule – Spring Sem. • Decide whether or not to use same system for second level class • Think of new team oriented game or adapt current one to be team oriented • Write project plan • Design rules and grading criteria • Make design document

  10. Project Schedule – Fall Sem. • Implement game • Construct Robot • Write Code • Make clear guide on how to set up and program robot • Write project report

  11. Cost Estimate

  12. Risks and Mitigation Plan Time • Risk: The student may not be able to complete the project within the allotted time • Mitigation: Create a detailed timeline for the students to follow and perform the project ourselves Lack of Background • Risk: Students may lack the background to be able to follow the curriculum • Mitigation: Define a specific skill set and course background to take the class.

More Related