CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell

1 2 Instructor/GTAs  Mike O’Dell  Office – 647 ERB  Office Hours: MWF, 12:30 pm – 1:30 pm  Other times: when available in lab (208A ERB), or by appointment   Include “CSE4317” in the subject line  GTA: Meenashree Chandan

1 3 Class 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: 15% of grade

1 4 Grading: Components/Weights  Attendance (10%): All classes and labs  <= 2 unexcused absent/tardy = 100  3 – 4 unexcused absent/tardy = 80  >4 unexcused absent/tardy, 0  Participation (5%): 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  Individual Deliverables (25%):  Engineering Notebook reviews  Individual Retrospective Reports  Final peer review  Your assessed contribution to your team/project  Any other individual assignments or classroom exercises as assigned  Team Deliverables (35%):  Development deliverables per slide that follows  Final Product Deliverable and Poster board (25%)

1 6 Major Team Deliverables for SD II  Team Status Reports (informal)  Note: replaces Team Retrospective Presentations  Design Specification (System)  Detailed Design Document  Scrum Artifacts  Product Backlog and Burndown Chart  Sprint Backlogs  Spring Product Increments (demos)  Final Product Demonstration  Final Project Poster board and discussion

1 7 Design Specification overall structure integrity for a system  Specifies “the overall structure of the software and the ways in which the structure provides conceptual integrity for a system” (Pressman) framework  Provides the framework for detailed design: hierarchical structure  the hierarchical structure of the system components (modules) relationships and interactions  the relationships and interactions of these components data  the elements and structure of data used by the components

1 8 Design Specification  Interface  Interface specifications for each module (sub-program) prologue  Documentation prologue for each routine  Pseudo-code  Pseudo-code for each routine data structure and data file  Physical data structure and data file specifications  Packaging  Packaging specifications  Test plan  Test plan for each module and sub- system

1 9 System Test Plan (not separately graded) requirements  A System Test Plan validates that all requirements have been met  It includes:  Introduction;  Approach;  Test items;  Features/requirements to be tested; not  Features/requirements not to be tested;  Item pass/fail criteria; deliverables  Test deliverables; tasks  Testing tasks;  Environmental needs;  Responsibilities;  Test Schedule;  Risks and contingencies;  Approvals required.

1 10 Exams/Quizzes  No exams or quizzes are planned for Senior Design II.  Final product and demo is your final exam!  25% of your final grade  You will receive team and individual scores

1 11 Homework & 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 Notebook  You are required to maintain an Engineering/ Project Notebook through the project. your grade on Individual deliverables  This is an integral part of your project, therefore it will be used as a component of your 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. inspection and grading  Notebooks are subject to inspection and grading by the GTA/Instructor at any time, without notice.  Team leaders will review, on occasion

1 13 Grading: Overall Grade  Each course component has a certain number of points assigned  Grading is based on standard 10% scale  Example: 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 Ethics assume that you all are honest and ethical  Today, I assume that you all are honest and ethical  If you give me reason to believe that you are not, the UTA Engineering College Code of Ethics will be enforced. may assist your fellow students  You may 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.  Unauthorized  Unauthorized shared work will be treated as cheating.

1 15 Class Website   All presentation materials and class information are posted here  Check it at least every class day