CSE Senior Design IICSE Senior Design II

Day 1: Getting OrganizedDay 1: Getting OrganizedSpring 2015Spring 2015

Instructor: Mike O’DellInstructor: Mike O’Dell

1

2

Instructor/GTAsInstructor/GTAs

Mike O’DellOffice – 631 ERBOffice Hours: Tuesdays & Thursdays,

11:00 am – 12:30 pmOther times: when available in lab

(208A ERB), or by appointmentEmail: odell@uta.edu

Include “CSE4317” in the subject lineGTA: TBD

1

3

Class Attendance and ParticipationClass Attendance and Participation

Attendance is expected for all classes and labs (and all of your team activities)

It’s better to come to class late than to not come at all

Participation (engaging in discussion, asking questions, etc.) is expected

As in Senior Design I, both of these will affect your grade for this class Total: 10% of grade

1

4

Grading: Components/Weights Grading: Components/Weights

Attendance (6%): All classes and labs <= 2 unexcused absent/tardy = 100 3 – 4 unexcused absent/tardy = 80 >4 unexcused absent/tardy, 0

Participation (4%): All classes and labs >90% = 100 (actively contributes most every day) 75 – 90% = 90 (actively contributes every week) 50 – 75% = 80 (sometimes contributes) 25 – 50% = 70 (seldom contributes, but

sometimes) <25% = 0 (barely noticeable)

1

5

Grading: Components/Weights Grading: Components/Weights Individual Deliverables (30%):

Individual Status Reports Engineering Notebook reviews Final peer review Earned Value (your contribution to your team/project) Any other individual assignments or classroom

exercises as assigned

Team Deliverables (30%): Team Status Reports Development deliverables per slide that follows

Final Project Review/Final Exam (30%)

1

6

Major Team Deliverables for SD IIMajor Team Deliverables for SD II

Team Status ReportsBaseline Architectural Design

Specification (System)Detailed Design Document and Review

(Module/Component)System Test Plan Document and ReviewPrototype preview Final Product (working prototype)Wrap-up Materials

~10%

~15%

~20%

~15%

~10%

~30%

P/F

1

7

Architectural Design SpecificationArchitectural Design Specification

Specifies “the overall structureoverall structure of the software and the ways in which the structure provides conceptual integrity for integrity for a systema system” (Pressman)

Provides the frameworkframework for detailed design: the hierarchical structurehierarchical structure of the system

components (modules) the relationships and interactionsrelationships and interactions of these

components the elements and structure of datadata used by

the components

1

8

Detailed Design SpecificationsDetailed Design Specifications InterfaceInterface specifications for each

module (sub-program)Documentation prologueprologue for each

routinePseudo-codePseudo-code for each routinePhysical data structure and data filedata structure and data file

specificationsPackagingPackaging specificationsTest planTest plan for each module and sub-

system

1

9

System Test PlanSystem Test PlanA System Test Plan validates that all

requirements requirements have been metIt includes:

Introduction; Approach; Test items; Features/requirements

to be tested; Features/requirements

notnot to be tested; Item pass/fail criteria;

Test deliverablesdeliverables; Testing taskstasks; Environmental needs; Responsibilities; Test Schedule; Risks and

contingencies; Approvals required.

1

10

Exams/QuizzesExams/QuizzesNo exams or quizzes are planned for

Senior Design II.However, some classroom exercises will

be graded as individual deliverables. Eg: Ethics exercise Team assessment exercise

Final Project Presentation and product demo is your final exam! 30% of your final grade You will receive team and individual scores

1

11

Homework & Lab AssignmentsHomework & Lab Assignments

Due as specified in the assignment document, or as specified in class

If turned in after due date/time there will be at least a 20% late penalty

Will be accepted late until 5PM of the date due. After due date, grade is zero.

Any out-of-class work must be “typed” per specified standard – handwritten work will not be accepted.

1

12

Engineering NotebookEngineering Notebook You are required to maintain an Engineering/

Project Notebook through the project. This is an integral part of your project,

therefore it will be used as a component of your grade on Individual deliverablesyour grade on Individual deliverables. Good record keeping is necessary for process

improvement, and process improvement is necessary to be a good engineer/developer.

Your notebook should be brought with you to all lab/class sessions. Notebooks are subject to inspection and gradinginspection and grading

by the GTA/Instructor at any time, without notice. Team leaders will review, on occasion

1

13

Grading: Overall GradeGrading: Overall Grade

Each course component has a certain number of points assigned

Grading is based on standard 10% scaleExample: if there are 400 points

available for Team Deliverables, then: 360 – 400 points is an A for that component 320 – 359 points is a B 280 – 319 points is a C 240 – 279 points is D < 240 points is failing

See the syllabus for other details

1

14

EthicsEthicsToday, I assume that you all are honest assume that you all are honest

and ethicaland ethical If you give me reason to believe that you

are not, the UTA Engineering College Code of Ethics will be enforced.

You may assist your fellow studentsmay assist your fellow students, (in fact, this is encouraged and expected)

You may not allow your fellow students to copy your work, and you may not copy theirs.

UnauthorizedUnauthorized shared work will be treated as cheating.

1

15

Class WebsiteClass Website

http://ranger.uta.edu/~odellAll presentation materials and class

information are posted hereCheck it at least every class day

1

16

Assignment for First LabAssignment for First LabSD I Post-Mortem/Lessons LearnedCome prepared to discuss the lessons

YOU learned in SD I and your plans to utilize those lesson in SD II

This is an INDIVIDUAL assignment Hand in one-page summary of your “Top 3”

lessons learned (typed per SD standard). Make a copy!

Each person will be given 2-3 minutes to discuss lessons learned with the class (SD1 and SD2) in lab on Friday, 1/23/2015.

1

17

REMEMBERREMEMBER Your Baseline ADS is due on 1/29/2015.

Consider/incorporate all reviewer comments Continue discussion/walk-through/refinement Prepare to discuss actions taken in ADS based on

reviews in next Team Status Report Review dates/due dates for other SD2

deliverables are published on the class website. I strongly recommend that each team meet now

to make sure everyone is reengagedreengaged and on the same page concerning schedules and commitments.

1

CSE 4316 18

Lab/Work Area (ERB 208)Lab/Work Area (ERB 208)

For lab access you will need your badge/ ID and your self service PIN number. Swipe your badge, then key in 5-digit PIN

If you don’t know your PIN, you can get it by: going to https://webapps.uta.edu/oit/selfservice/ clicking “VIEW INFORMATION ABOUT YOUR

ACCOUNTS”, logging in with your MavID and password Your PIN will be shown with other account information