Junior Design Course

Course Description

This is an intermediate level design course taken by students after a student has gathered sufficient experiences on programming, algorithms, data structures up to 200 level core courses, core math, and core science courses.

This "Junior Design Course" involves formation multidisciplinary teams of students who build and test IOT devices, websites, mobile apps (IOS and android) or engineering processes. Design projects can be selected from the proposals submitted by the students, or the list recommended by the course instructor, or text book design problems. The instructor acts as supervisor and assists the students in team formation and organization, preparing proposal preparation, writing reports, implementation of design process, project scheduling and management, design reviews, design simulation and testing, preparation of drawings, specifications, etc.

Performances are evaluated by oral presentation of proposal and demonstration of completed projects, report writing, effective use of computing knowledge, design process, project management and scheduling etc.

General Policy

The instructor will supervise projects on a diverse array of topics, some of which may be completely out of the instructor’s areas of expertise. The instructor will focus more on project methodology and guide the students accordingly. The instructor may give lectures on project development methodologies. Students must focus on the following things:

1. Creativity

2. Design Process

3. Design Planning

4. Social Context of Design

5. Engineering Ethics

6. How to Write Project Proposal/Reports/Technical Manuals etc.

Course Outcomes

Upon successful completion of this course, students should be able:

• To identify an engineering and/or computing problem, build appropriate platform/software to solve the problem in a systematic way with given constraints of resources, budget, time etc.

• To select appropriate software/tools to implement the solution.

• To form project group to develop a product or solve engineering problem, be responsible and exercise leadership for fulfilling project goal

• To write proposal and completed project reports, give presentation and demonstrate project findings

• To manage finances and develop realizable timeline for a successful completion of project in a multidisciplinary team.

Course Topics

Attendance Policy

Attendance in classes is integral to the success of a student in this course. Nevertheless, if a student needs to miss a class for unavoidable reasons, the student must email the instructor prior to the class period stating the reason for being absent. In case the student fails to notify the instructor because of illness or other unavoidable reasons, certification such as a doctor’s certificate may be necessary to get the absence excused.

Distribution of Points

Class Structure

1. Lectures: Attendance and participation of all of them is strongly encouraged.

2.Team Work: Students will work in a small group.

3. Report: Students will have to submit at least two reports

4. Projects: You will have to submit a hardware design project at the end of the semester. You will work on the project as a group.

5. Presentation: There will be several presentations throughout the semester.

Presentation Details

Presentation Duration: 10 min x No. of Members (followed by Q&A)

Presentation Type: Individual

Demonstration: Demonstration where applicable

Date: TBA

Time: TBA

Location: TBA

Weekly Presentation

Presentation Duration: 5 min (max)

Presentation Type: Individual (using PPT slide)

Group Score : Content + Slide+Progress

Individual Score: Presentation

Final Presentation Scoring

Scoring: Scoring will be based on the following criteria:

1. Content - How much details of your work has been presented. This includes details of the methodology, experiment design, circuit design, algorithm details. This part reflects how much you have learned from this project. Just don't say I have used this and that technique, try to answer why and how

2. Results - How many different experiments have been done. This may include a simulation result, the real experiment result, their statistical measures. Don't say this model can detect this phenomenon. Tell us with what accuracy and how precisely it can detect.

3. Discussion - How well you have understood the results. This includes an analysis of the results presented earlier, the relationship between the techniques and the results achieved. Don't say that after applying this technique we got this result rather tell why that technique produced good results, present your own comment/ judgment.

4. Clarity - How clear and readable the images and texts are. Negative marking will be done for any unclear images or texts. Also don't just put a figure, add few adjectives on the graphs (poor, good, noisy etc.)

Report 1 Scoring

Scoring: Scoring will be based on the following criteria:

Marks Distribution for Formatting:

1. Font Size, Style - 10

2. Alignment of Texts, Spacing - 10

3. Total sections covered - 10

4. Reference Formats, Citation style - 10

5. Figure Quality, Captions -10

Marks Distribution for Contents:

1. How well the problem has been explained ?- 20

2. The quality of the literature study - 20

3. How much technical details were covered and how well they were organized ?- 20

Total score = (Formatting + content)*(100-Turnitin Score)/100

Final Report

Scoring: Scoring will be based on the following criteria:

1. Content - How much details of your work has been presented. This includes details of the methodology, experiment design, circuit design, algorithm details. Use as many diagrams as you want to help people understand the technical details.

2. Background - How well you covered the background. This includes how well you studied other people's work

3. Results - How robust you tested your prototype and what are the statistical measures. This include simulation results, the real experiment results (if any), their statistical measures. Tell us with what accuracy and how precisely your prototype works.

4. Discussion - How well you have understood the results. This includes an analysis of the results presented earlier, the relationship between the techniques and the results achieved. Don't say that after applying this technique we got this result rather tell why that technique produced good results, present your own comment/ judgment.

5. Organization - How well you organized the chapter

6. Style and Formatting - How clear and readable the images and texts are. Font size and style should be consistent. Spacing should comfortable for the readers. Texts should be aligned with the border. Format the references according to the IEEE standard. Every reference must be mentioned inside the text with relevance.

Special Notes:

• Focus on the quality of writing and discussion. Don't include unnecessary pages with useless images.

• The report must not exceed 35 pages

• There should not be more than five chapters. Too many chapters might not be helpful for the readers.

Final Submission

Softcopy:

1. Report

2. Final Presentation Slide (with a page for Member's Contribution)

3. Code (With proper commenting and a README file)

4. Data (Proper labelling and a README file)

5. Circuit Schematic (if any)

7. Picture of the Prototype (if applicable)

8. Video (if applicable)

Hardcopy:

Report Spiral Binding (1 copy)

Class Resources

1. Course outline