Progress Report and Presentation

EECE404 Senior Design II Department of Electrical and Computer Engineering

Howard University

Spring 2013

Dr. Charles Kim

Progress Toward Final Product• Or Transform from a Bison to a Fish or a Chicken?

Charles Kim – Howard UniversityECE Day Luncheon at the Blackburn Center April 2012ECE Day Luncheon at the Blackburn Center April 2012

Charles Kim – Howard University

Project Tracking

• Successful Project– On Time– Within Budget, and– To the Required Level of Quality

(Satisfaction of Design Requirements)

Risk Management

– Risk Identification– Risk Monitoring and Control

Charles Kim – Howard University

5

ApproachM - Mitigate W - WatchA - AcceptR - Research

5

4

3

2

1

1

Like

lihoo

d

CONSEQUENCES

Med High

Low

Criticality L x C Trend More flight testing may be required for Homing

R DFRC-02 4

Limited communication reception

WDFRC-04 7

Beacon circuit issues R DFRC-11 3

FPGA software behind schedule

W DFRC-01 5

Resources insufficient A DFRC-24 8

Cost growth for parts ADFRC-07 6

Motion detector malfunctionVideo feed incompatible

RDFRC-12 2

Motor Controller Failure R DFRC-34 1

Risk Title ApproachRisk

ID Rank

1

2

3

4 5 6

7 8

Risk Management Example

2 3 4 5

SOFIA Risk Matrix

Charles Kim – Howard University

Progress Presentation• Progress Presentation Purpose

– Review Team’s Works– Describes Progress (Milestone vs Outcome)– Present important highlights– Resolve issues– Risk Monitoring and Management

• Progress Presentation Overview– 10 -minute presentation (including Q&A)– 9 – 10 slides

• Submission of the presentation file (PPT or PPTX)-bring it to the class in a thumb drive on the presentation day – Keep hardcopy in your project folder

Charles Kim – Howard University

Progress Presentation Format • Slide 1: Cover Page

– Project Title / Member Names/Date

• Slide 2: Background and Problem Definition– Background– Problem Definition

• Slide 3: Design requirement– Quantified requirement

• Slide 4: Final Solution Schematics– Final Design Schematics

• Slide 5: Highlights of the Period– What went well over the last period– Key findings and results (with diagrams)– Any Changes made from the previous period– Explanation of the demo/hardware (completed so far) details– Photos and/or video clips of the hardware in action

Charles Kim – Howard University

Progress Presentation Format (-Continued)

• Slide 6: Lowlights of the Period– What did not go well during the period– Key problems faced (with drawing, photo, video, etc)

• Slide 7: Outcome vs. Milestone

• Slide 8:Issues & Risk Control and Management– Issues responsible to the lowlights– Barrier to be removed– Problems beyond team’s scope or authority– Identified Risks– Risk identification and control activity table

• Slide 9: Focus of Next Week Activities– How lowlights and issues are to be resolved– Changes to be made in the approach– The next major milestone to achieve

Charles Kim – Howard University

Progress Presentation Schedule• Grading of Progress Report Presentation

– Team scores• Presentation contents (the amount of progress)• Effective Use of Slides (Color contrast, Font Size, Etc)• Subject understanding• Communication skill

• Upcoming Progress Presentation Schedule– W FEB 12: Today. Final BOM (Bill of Materials)– W FEB 19: “Progress Week” No formal class

• Submission of recorded elevator pitch on “what is your project about?” Max 45 seconds; 1 representative member; Video clip with audio; email submission; due: 11:59pm Wed February 19, 2014

• Team meetings – Record and file in your project binder• Team-instructor meeting – for discussion on improvement and progress

– W FEB 26: 1st Progress Presentation – W Mar 5: 2nd Progress Presentation– W Mar 12: Spring Break Week– W Mar 19: 3rd Progress Presentation + Demonstration

Elevator Speech (or Pitch)

Elevator Speech/Pitch

• The name was actually coined from the idea that we sometimes meet the important people in our lives in elevators.

• The odd situation we encounter in most elevators is that nobody speaks to or looks at anyone else, and yet we have a captive audience for that short period of time.

• The idea of an “elevator speech” is to have a prepared presentation that grabs attention and says a lot in a few words.

• By telling your core message, you will be marketing yourself and/or your business, but in a way that will make them want to know more about you and your business [and your project].

Formula for Composing an elevator speech

• Define your audience universe. • Define your content or subject

matter. • Define your objective. • Define your desired image or style. • Define your key message.

Do’s for Elevator Speech• Do make your Elevator Speech

sound effortless, conversational, and natural.

• Do make it memorable and sincere.

• Do write and rewrite your speech, sharpening its focus and eliminating unnecessary words and awkward constructions.

• Do deliver the important aspects of your project/experiences

Don’ts for Elevator Speech• Don't let your speech sound

canned.• Don't ramble. Familiarizing

yourself as much as possible with your speech will help keep you from getting off track.

• Don't get bogged down with industry jargon or acronyms that your listener may not comprehend.

• Don't focus just on yourself: connect with the person you talk to.

Elevator Speech Practice• Practice

– 1. Know the situation (subject: team project)“In a job interview, your interviewer [a human resources administrator – non-engineer] asks about your significant project experiences and achievement.”

– 2. Team speech writing: – 3. Randomly pick a speaker from each team.– 4. Internal practice of the speech – 5. Giving the speech [45 sec. max] & Record

(Audio/Video) – 6. Submission of the recorded (Video) speech (via

email)

Example Progress Report/Presentation

Charles Kim – Howard University

Team “SMART BACKPACK”

Progress Report/Presentation

EECE404 Senior Design IIElectrical and Computer Engineering

Howard UniversityInstructor: Dr. Charles Kim

Spring 2013

03/08/2013

Table of Contents• Challenge definition – Background &Problem Definition

• Project entry solution – Design Requirements

• Final Solution Schematics

• Highlights of the period

– System integration explanation

– Demo and/or screen captures

• Lowlights of the period

• Milestones vs. outcome

• Risk control and Management

• Focus of Next Week Activities

2/12/2014

2. Challenge Definition – “Background & Problem”

2/12/2014

How do people ensure they have all items needed for an event?REMINDERS CHECKLISTS

What’s Wrong?-No Active Monitoring of items- Frustration of losing/forgetting important items

What we Plan to do – Problem StatementWe want to design a system that monitors and keeps track of items needed based on a user’s schedule and notifies the user whenever an item needed for any of the day’s activities goes outside a certain range of the system.

The system therefore crosschecks that a user’s essential items are within close proximity to the user.

Project Entry Solution

Description

Functionality Issue warning if user attempts to leave without an item needed at their projected destination.

User Interface Allow user to specify which items are needed for each event Allow user to view/modify item inventory

Capabilities Communication link for the monitoring system (Wireless)Automatically update inventory

Compliance Adhere to the relevant standards (FCC, ISO, AIAG)

Others Low Noise level (20db)Light weight system (3lb)Optimum battery life (8hrs)Ease of use (10mins setup, 10mins learning)

2/12/2014

3. Design Requirements

4. Final Solution Schematic Diagram

5. Highlights of the period

• Finally received Cornell Cup funds from Howard

• Diagnosed the problem causing Intel Board not to boot previously

• We received & set up the RFID reader (ZK-RFID-107) and antenna– The antenna increases the reader range to about 2-3 metres

• Made some progress with the Android app(see pictures on next slide)– Improved calendar UI– Activated Bluetooth file transfer– Created pop-up menu– Implemented file read and write

• Implemented text output to LCD screen• Schematics and Screen Shots floow

2/12/2014

Highlights of the Period – Android App

App Progress

Highlights of the Period - Bluetooth

Demonstration: Quartus II System Builder with System on Chip(SOPC) Application

Demonstration: Quartus Programmer -Importing FPGA designations for usage in Nios II C++ environment

Demonstration: Printing Text to LCD screen

6. Lowlights of Period• Challenges in rectifying Calendar App Code obtained from

open source still persist– We have to consider the necessity of creating (importing) the

entire android platform as well to be abe to take full advantage of said app code

• Discovery that the team is going to need substantial knowledge of Verilog or VHDL for the FPGA programming– Team members’ expertise is more focused on other languages

• Realization that the presence of certain materials such as metal on laptops may significantly impact the frequency range of our RFID reader– The team may have to set this property to a dynamic range on the

reader

7. Milestones Vs. OutcomesMilestone Outcome

1 Receive RFID reader DONE

2 Receive Intel funds DONE

3 Create inventory menu for application DONE

4 Implement file read and write for application DONE

5 Set-up Bluetooth file transfer In Progress

6 Determine current draw fromRFID reader and DE2i-150 board

In Progress

7 Program LCD functionality In Progress

8 Program RFID reader In Progress

8. Risk Control and ManagementRisk Probability Impact Risk Control and

Management

Intel Board fails to turn on .2 5 • Research the

capabilities of the Intel Board such as the boot manager

RFID reader fails to scan tags withindesired region

.2 5 • Test the reader in varioussituations(stationary, mobile, different environments)

• Test the reader when its trying to scan different items

Information not successfully transmitted from RFID to board

.1 5 • Test the board in varioussituations(stationary, mobile)

Battery life does not allow system to operate throughout a normal day

.1 3 • Recharge battery daily• Use battery with

sufficient mAh

9. Focus of Next Week ActivitiesHow the Low Points are to be Resolved

New Approach Next Major Milestone

• Explore the codes controlling the RFID reader to read multiply tags

• Divide the system into individual components and explore each workings/functions

RFID• Customize software code for the RFID reader• Ensure RFID is reading multiple tags within

proximity• Import tags read to a list /file that can be

manipulated by Intel Board and smart phone application

• Integrate RFID reader with the Intel board

• Read more about android platform/ development

• Build on android 4.2 stocked calendar application

• Tie the created inventory to the existing calendar application

INTEL BOARD• Continue learning the design suite• Continue figuring out the workings of the LCD

and accelerometer• Sync controls between RFID reader, LCD and

accelerometer• Establish Bluetooth connectivity feature for

the board

• Use weekly meetings more effectively to achieve measurable progress

• Use C# to program the RFID reader

SOFTWARE• Continue calendar and inventory app

development• Establish Bluetooth reception on board

OTHERS• Order all other hardware components