CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber

1 2 Instructor/GTAs  Manfred Huber  Office – 522 ERB (or 128 ERB)  Office Hours: Tuesdays, Thursdays, and Fridays 11:00 am – 12:00 pm  Other times: when available in lab (208A ERB), or by appointment   Include “CSE4317” in the subject line  GTA: TBD

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: 10% of grade

1 4 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  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 II  Team Status Reports  Baseline Architectural Design Specification (System)  Detailed Design Document and Review (Module/Component)  System Test Plan Document and Review  Prototype preview  Final Product (working prototype)  Wrap-up Materials ~10% ~15% ~20% ~15% ~10% ~30% P/F

1 7 Architectural 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 Detailed Design Specifications  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 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.  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 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  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 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 14 Class Website   All presentation materials and class information are posted here  Check it at least every class day

1 15 Assignment for First Lab  SD I Post-Mortem/Lessons Learned  Come 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 in lab on Friday, 1/23/2015.

1 16 REMEMBER  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. reengaged  I strongly recommend that each team meet now to make sure everyone is reengaged and on the same page concerning schedules and commitments.

1 CSE 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  clicking “VIEW INFORMATION ABOUT YOUR ACCOUNTS”,  logging in with your MavID and password  Your PIN will be shown with other account information