1 / 13

Day 1: Getting Organized

Day 1: Getting Organized. 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

ita
Download Presentation

Day 1: Getting Organized

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Day 1: Getting Organized

  2. 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

  3. Grading: Components/Weights • Attendance (6%): All classes and labs • <= 2 absent/tardy = 100 • 3 – 4 absent/tardy = 80 • >4 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)

  4. Grading: Components/Weights • Individual Deliverables (30%): • Individual Status Reports • Earned Value (your contribution to the Project) • Engineering Notebook reviews • Panel Presentation • 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%)

  5. Major Team Deliverables for SD II • Team Status Reports • Architectural Design Specification (System) • Detailed Design Document and Review (Module/Component) • System Test Plan Document and Review • Final Product (working prototype) • Wrap-up Materials ~15% ~25% ~20% ~15% ~25% P/F

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

  7. Detailed Design Specifications • Interface specifications for each module (sub-program) • Documentation prologue for each routine • Pseudo-code for each routine • Physical data structure and data file specifications • Packaging specifications • Test plan for each module and sub-system

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

  9. 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

  10. Ethics • 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. • 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 shared work will be treated as cheating.

  11. 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 • Submit a one-page summary of your “Top 3” lessons learned. • Each person will be given 2-3 minutes to discuss lessons learned with the class (SD1 and SD2) in lab this Friday, 1/18/2013.

  12. REMEMBER • Your ADS Reviews are scheduled beginning next week, so check your dates and start getting ready today. • Other review dates are published on the class website. • I strongly recommend that each team meet now to make sure everyone is reengaged and on the same page concerning schedules and commitments.

  13. 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 CSE 4316

More Related