CRN# 14190 CPET 491A-01 Senior Design Project, Phase II
CRN# 12688 ECET 491A-01 Senior Design Project, Phase II
Fall 2008
Paul I. Lin

Professor of Electrical and Computer Engineering Technology
Indiana University-Purdue University Fort Wayne

Course Description
P: 490. Phase II includes, but is not limited to: (1) continued research and finalized design, (2) oral presentation to faculty and other interested parties, (3) standard-format written technical report.

Instructor Information:

Paul Lin, P.E. (EE)

Professor of Electrical and Computer Engineering Technology

Indiana University-Purdue University Fort Wayne

Office ET 205C             Email: lin@ipfw.edu       (O) 260-481-6339

Course Web site: www.ecet.ipfw.edu/~lin

Office Hours:    

  • Tuesday            8:30 - 10:30 AM  & 3:30 – 4:30 PM
  • Wednesday      3:00 - 5:00 PM
  • Thursday          8:30 - 10:30 AM  & 3:30 – 4:30 PM
  • Other weekday hours – by appointment

Class Meeting Dates/Time
Monday
8:00-9:20PM (ET 346)

Aug. 25

Sept. 8*, 15, 22, 29

Oct.   6*, 27, 31

Nov.  3, 10, 17, 24

Dec.   1, 8

Dec. 11/12 - Senior Design Presentation

Important Dates:
Sept. 1 – Labor Day
Oct. 13 & 14 – Class suspended (Fall Break)
Nov. 26 – 28 Thanksgiving Recess

Recommended Text Book
System Engineering Management, 3rd, 2004, by Banjamin S. Blanchard, from John Wiley & Sons, Inc, ISBN 0-471-29176-5

Grading Policy: (No late reports will be accepted)                      

Project Design (meeting & discussion, communications, project-specific technical details, knowledge and abilities, reports, etc) 50%
Project Implementation/Operation (reports) 20%
Oral Presentation           10%
Final Report                  20%

Grading scale: A: 90 -100, B: 89 – 80, C: 79 – 70, D: 69 – 60, F: 59 and below.

* Purdue University’s new grading scale with + and – will not be used.

 

 

 

Course Outcomes:

 

A student who successfully fulfils the course requirements will have demonstrated the ability to:

1. Use of knowledge and skills:

1.1 Prototype product and assembly drawings (TAC/ABET, item a1)

1.2 System architecture/subsystem/PCB circuit layout and drawings (TAC/ABET, item a2)

1.3 Use of modeling/simulation (MATLAB, Multisim, etc.) techniques (TAC/ABET, item a3)

1.4 Use of project management (TAC/ABET, item a4)

1.5 Use of modern software and development methodologies (TAC/ABET, item a5)

1.6 Application of mathematics (TAC/ABET, item b1)

1.7 Application of system engineering and management concepts (TAC/ABET, item b2)

1.8 Use current and emerging knowledge (TAC/ABET, item b3)

1.9 Apply creativity in hardware system/subsystem/circuit design (TAC/ABET, item d1)

1.10 Apply creativity in software system/subsystem/program design (TAC/ABET, item d2)

1.11 Problem solving knowledge and skills (TAC/ABET, item f1)

 

2. Conduct unit and system testing, collect testing data and interpret results

2.1 Valid and appropriate subsystem testing results (signal acquisition, processing, reporting, HMI, etc) TAC/ABET, item c1)

2.2 System construction and integration testing results (TAC/ABET, item f2)

 

3. Write progress and project reports - clear and concise technical content, well-organized, professional written report (TAC/ABET, item g1)

 

4. Make oral presentations - professionalism, preparation and use of visual aids (TAC/ABET, item g2)

 

5. Demonstrate project performance

5.1 Experimental circuits setup and data analysis (TAC/ABET, item c2)

5.2 Creativity in design (TAC/ABET, item g2)

5.3 Teamwork - stakeholders: project sponsor, faculty advisor, etc (TAC/ABET, item e)

5.4 Project related research work (TAC/ABET, item h)

5.5 Application of ethics - health, safety, wellbeing, etc. (TAC/ABET, item i)

5.6 Diversity in knowledge & solution (TAC/ABET, item j1)

5.7 Knowledge of societal issues - economic, productive, growth, etc. (TAC/ABET, item j2)

5.8 Knowledge of global issues - environment, cultural needs, etc. (TAC/ABET, item j3)

5.9 A commitment to project quality (TAC/ABET, item k1)

5.10 A commitment to project timeliness - project progress, completion times, etc. (TAC/ABET, item k2)

5.11 Project is operational and meet or exceed specifications (TAC/ABET, item f3)

5.12 Familiarity with the project (include ability to answer questions) (TAC/ABET, item f4)

 

 

Accreditation Board of Engineering Technology (ABET/TAC) 2008-2009 Criteria for Accrediting Engineering Technology: Criterion 3. Program Outcomes (a – k)

a.      an appropriate mastery of knowledge, techniques, skills, and modern tools of their discipline

b.      an ability to apply current knowledge and adapt to emerging applications of mathematics, science, engineering and technology,

c.      an ability to apply to conduct, analyze and interpret experiments and apply experiments results to improve processes,

d.      an ability to apply creativity in the design of systems, components or processes appropriate to program objectives,

e.      an ability to function effectively on teams,

f.       an ability to identify, analyze and solve technical problems,

g.      an ability to communicate effectively,

h.      a recognition of the need for, and an ability to engage in lifelong learning,

i.       an ability to understand professional, ethical and social responsibilities,

j.        a respect for diversity and knowledge of contemporary professional, societal and global issues, and

k.      a commitment to quality, timeliness, and continuous improvement”

 

Disabilities Statement: If you have a disability and need assistance, special arrangements can be made to accommodate most needs. Contact the Director of Services for Students with Disabilities (Walb, room 113, telephone number 481-6658), as soon as possible to work out the details. Once the Director has provided you with a letter attesting to your needs for modification, bring the letter to me. For more information, please visit the web site for SSD at http://www.ipfw.edu/ssd/

 

Tentative Schedule/Activities

 

1. ECET/CPET 491 First Meeting (8:00-9:20 p.m., Monday, Aug. 25, in ET 346)

·        Phase I Project Design review/update

  • An updated progress report, due on Sept. 8 (before 9:00PM), including the following required sections: cover page (project title, student name, advisors, date, affiliation), problem statement, proposed solution (with appropriate block diagrams), system requirement and specifications, required resource and estimated cost, project tasks and schedule (MS Project 2003/2007), and references.
  • Meet with your technical advisor and make a phase II meeting schedule

1st progress report due Sept. 8, your project schedule (MS Project format), and advisor meeting schedule due Sept. 8 before 9:00 PM, send your report electronically to lin@ipfw.edu, and copy your Faculty advisors.

 

2. Iterative Design Phase (Sept. 8 – Oct. 6)

  • Detailed System Design
    • Define detailed requirements and specifications (hardware/software subsystems and interface, I/O interface, timing, events, constraints, etc) and overall characteristics of your proposed project for implementation
    • Consider system usability (human factor), performance, reliability, supportability, off-the-shelf parts, assembly time, power, weight, size, cost, tradeoff, etc
    • Design a System Architecture (software and/or hardware)
  • Perform circuit simulation, system simulation, and/or mathematical modeling: MATLAB, PSpice, Muitisim, etc; log and gather simulated data; analyze, and document the simulation and/or testing results
  • System function modeling (flow chart, data flow diagram, state transition diagrams, activity diagrams, collaboration diagrams, block diagrams, etc); MS Visio, Unified Modeling Language
  • Make sure all the needed hardware and/or software are ordered

The Design Report (2nd report) due to both your technical advisor and Prof. Lin on Oct. 6, before 5:00 PM, for critical review. If the system design is incomplete and is assessed that the student is not able to make significant progress toward the project objectives, a “F” course grade or withdraw from the course  will be recommended by both your technical advisor and Prof. Lin.  

 

3. Design Project Prototyping and/or Development: (Oct. 7 – Nov. 10)

  • Define/refine implementation plan and timeline for project management
  • Prioritized hardware/software co-construction
  • Incrementally build and test your prototype system
  • Document your activity, unit testing results (signal measurement, observation, program running, etc)

System construction and unit testing report (3rd report) due Nov. 10, before 5:00 PM

 

4. Testing and Evaluation (Nov. 11 – Dec. 1)

  • Complete the system construction
  • Final testing and gathering testing results for final report

First testing report (4th report) due on Nov. 24  

Second testing report (5th report) due on Dec.1

 

5. Final Report (due Dec. 8)

·        All ECET Faculty members and the ENGW421 professor are invited to attend your presentation.

·        The ECET/CPET 491 Senior Design II Assessment Form will be used for evaluation.

One hard copy  and one soft copy of your final report are due on Monday, December 8, 2008

 

6. Project Presentation (Room ET 226, 8:30am-5:00pm, Friday, December 12, 2008)

  • Submit a CD contains all soft copies of project design meeting & communication memos, progress reports, testing reports, programs, data sheets, final project report, presentation slides, due December 10 (Design Portfolio CD)
  • Final project presentation:
    • Microsoft PowerPoint presentation is recommended. A soft copy of this presentation should also send to Prof. Lin.
  • Best Senior Design Projects will be selected by faculty members