ENTC 4600 Technology Practicum Dr Hugh Blanton 439

ENTC 4600 Technology Practicum Dr. Hugh Blanton 439 -4177 blanton@etsu. edu

Projects • • • Baby locator ($100, 000) DSP Contest ($$$) IEEE Contest ($$$) DSP Circuit Board Love Lamp

Grading • • Written Proposal (15%) Oral Proposal Presentation (10%) Status Reports (5%) Final Written Report (15%) Final Oral Presentation (10%) Project Check Off (25%) Difficulty (5%) Professionalism/Attendance (15%)

Written Proposal Format • • Letter of Transmittal Title Page Table of Contents Introduction Technical Approach (max. 3 pages) Management Approach (approx. 3 -4 pages) Conclusion (approx. 1 page) Attachments

Report Content • Reports graded for: – Required content – Spelling, grammar, appearance, etc. (Quality) • all figures, charts, etc. must be computer generated; not hand drawn.

Introduction • • • Project description Objectives Nature of end product Performance and design specs Schedule summary Budget summary (Total cost)

Technical Approach • • Alternative technical approaches Selection criteria Technology and method to be used Approach to testing

Management Approach • Project schedule (Gantt Chart) • Tracking chart (team hours) • Responsibility matrix - grid showing who’s responsible for each task • Budget estimate - parts, labor, etc. • Facilities used

Attachments • • References Technical support material User’s manual(s) Software – printed source or disk

Oral Presentations • • Based on written report Sign up for time Bring video tape “How To” covered in later lecture

Managing Your Project • • What needs to be done? (Task list) Who knows how to do it? Who will commit to doing it? When will it be done?

Tasks: What needs to be done • Start date • Duration • Dependencies – Start time – On other tasks • Operate under assumptions • Shows consumption of resources – Time, money, facilities, etc.

Responsibility Matrix: Who is going to do it • List all tasks • Divide tasks among group members – Use member specialization's • Designate one (and only one) person as the primary person for the task. • Include key to decipher matrix (no matter how obvious it may seem).

Responsibility Matrix: Example

Scheduling, Tracking, and Control • Time dependence of tasks • Resource allocation – human, fiscal, facilities • Track measurable quantities – Time, money, parts • In this class, track team time – Module/Subsystem completion

Scheduling • End to End Approach – Takes too long – Run out of resources • Success Oriented – Simultaneous tasking – Filled with risks – Timing is everything

Gantt Chart • List tasks/milestones vs. . time • Show current date • Show status of tasks – When started – Estimate completion – Percentage complete

Gantt Chart Example: Building an RF Tx & Rx

Tracking Chart • Keep track of TEAM hours spent – Example: 1 hour team meeting x 4 people = 4 hrs. • Include any and all hours spent on project related tasks – – – Meetings, Writing reports/Preparing oral presentations, Designing, Building, Calling vendors, . . .

Tracking Chart Example Team Hours Week

Estimating the Budget Direct Costs • Labor – – – Consultant (Instructor) Lead Engineer Sr. Eng. . Jr. Eng. . Drafting Clerical $200/hr. $150/hr. $100/hr. $50/hr. $30/hr. $20/hr. • Parts – Hardware breakdown – Software – Misc. . - solder, wires, PCB, packaging, . . .

Other Direct Costs • Facilities/Rentals – Equipment (Time) – Labs/Rooms • Misc. . – Phone calls – Travel expenses – Misc. supplies - copies, binding, . . .

Indirect Costs • Indirect Costs (overhead) – 100% of direct costs

Performance • Evaluating the options – Options: brainstorming, research, client, … – Criteria: team, client – Form matrix and evaluate numbers

Verification and Validation • • • Requirements Functional specs. Hardware/Software specs. Test specs. Subsystems and complete system Delivery of product – Report – Hardware/Software

Status Reports • • Group name/Member names Project/Solution summary Tasks scheduled to be completed soon Tasks to be started before next report Problems (new or ongoing) and solutions Current Gantt chart Current tracking chart Conclusion - Impact on CSP