1. CSE Senior Design I Fall 2011 Day 1: Getting Organized Instructor: Mike O’Dell

2. 1 CSE 4316 2 What’s This Class About? capstone course put it all together. In this course you will:  This is the CSE capstone course, where you put it all together. In this course you will: team  Work on a team with your fellow students software product development cycle  Learn a lot about the software product development cycle by actually experiencing it phased development process  Study and implement a “real world” phased development process  Develop a working product  Develop a working product “from scratch” planning and requirements  In CSE 4316 - prepare and present planning and requirements documentation for your project. complete the project  In CSE 4317 - continue and complete the project and demonstrate your working prototype

3. 1 CSE 4316 3 What’s This Class About? Acquire, Define, Distinguish, Draw, Find, Label, List, Match, Read, Record Compare, Demonstrate, Differentiate, Fill in, Find, Group, Outline, Predict, Represent, Trace Convert, Demonstrate, Differentiate between, Discover, Discuss, Examine, Experiment, Prepare, Produce, Record Classify, Determine, Discriminate, Form generalizations, Put into categories, Illustrate, Select, Survey, Take apart, Transform Argue, Award, Critique, Defend, Interpret, Judge, Measure, Select, Test, Verify Synthesize, Arrange, Blend, Create, Deduce, Devise, Organize, Plan, Present, Rearrange, Rewrite Higher order learning: Bloom’s Taxonomy (rev.)

4. 1 CSE 4316 4 Cognitive Levels Defined Critical Thinking Activity [arranged lowest to highest]Relevant Sample Verbs 1. Remembering: Retrieving, recognizing, and recalling relevant knowledge from long-term memory, eg. find out, learn terms, facts, methods, procedures, concepts Acquire, Define, Distinguish, Draw, Find, Label, List, Match, Read, Record 2. Understanding: Constructing meaning from oral, written, and graphic messages through interpreting, exemplifying, classifying, summarizing, inferring, comparing, and explaining. Understand uses and implications of terms, facts, methods, procedures, concepts Compare, Demonstrate, Differentiate, Fill in, Find, Group, Outline, Predict, Represent, Trace 3. Applying: Carrying out or using a procedure through executing, or implementing. Make use of, apply practice theory, solve problems, use information in new situations Convert, Demonstrate, Differentiate between, Discover, Discuss, Examine, Experiment, Prepare, Produce, Record 4. Analyzing : Breaking material into constituent parts, determining how the parts relate to one another and to an overall structure or purpose through differentiating, organizing, and attributing. Take concepts apart, break them down, analyze structure, recognize assumptions and poor logic, evaluate relevancy Classify, Determine, Discriminate, Form generalizations, Put into categories, Illustrate, Select, Survey, Take apart, Transform 5. Evaluating : Making judgments based on criteria and standards through checking and critiquing. Set standards, judge using standards, evidence, rubrics, accept or reject on basis of criteria Argue, Award, Critique, Defend, Interpret, Judge, Measure, Select, Test, Verify 6. Creating : Putting elements together to form a coherent or functional whole; reorganizing elements into a new pattern or structure through generating, planning, or producing. Put things together; bring together various parts; write theme, present speech, plan experiment, put information together in a new & creative way Synthesize, Arrange, Blend, Create, Deduce, Devise, Organize, Plan, Present, Rearrange, Rewrite

5. 1 What will we do? CSE 4316 5 Build a TEAM TEAM PLAN PLAN Establish Product REQUIREMENTS & FEASIBILITY Establish Product REQUIREMENTS & FEASIBILITY DESIGN Your Product DESIGN IMPLEMENT & TEST Your ProductIMPLEMENT Product DEMONSTRATE Your Product Your ProductDEMONSTRATE Senior Design 2 Senior Design 1

6. 1 CSE 4316 6 Instructor  Mike O’Dell  Office – 631 ERB  Office Hours - 2:00 PM - 3:30 PM, Tuesday and Thursday  Other times: when available in the lab (208A ERB), or by appointment  Email: odell@uta.eduodell@uta.edu  Include “CSE4316” in the subject line  I typically will reply to your emails within one business day

7. 1 CSE 4316 7 Who is this guy?  Retired Navy Commander  IBM: lead programmer, project manager, program manager, development manager (~ 10 years)  Product development senior management (~11 years), public and private companies  Dell, VP Development (laptops, desktops)  VTEL General Manager, Systems  eOn Communications, President and CEO  Bynari, Inc – Chairman and CEO  Senior Lecturer at UTA since 2001

8. 1 CSE 4316 8 Teaching/Lab Assistant  GTAs  Chris McMurrough & Jonathan Rich  GTA should be a part of your teams  consultant  evaluator  observer  expert  Office hours in lab, times on Class WebsiteClass Website

9. 1 CSE 4316 9 Scheduled Lectures (Mondays & Wednesdays) Rapid Development: Taming Wild Software Schedules  Textbook: Rapid Development: Taming Wild Software Schedules, Steve McConnell, Microsoft Press, 1996 (ISBN: 1-55615-900-5)  Prepared lectures (instructor) on key topics case studies  Class discussion (student and instructor led) of case studies.  Class exercises

10. 1 CSE 4316 10 Scheduled Labs (Friday)  In ERB 103,  In ERB 103, or lab (208 ERB)  Team Status Presentations ENB  Individual Status Reports and ENB Reviews  Deliverable Review  Deliverable Review Presentations  Class Exercises, Special Topics  Working sessions overlap  Note: will occasionally overlap with CSE 4317 lab period, on occasion

11. 1 CSE 4316 11 Class Syllabus  YOU  YOU are responsible for understanding the information in the class syllabus  Ask questions if you are unclear on things  The syllabus may evolve web copy of the syllabus  The web copy of the syllabus is the current version  SDI and SD II use the same syllabus

12. 1 CSE 4316 12 Class Attendance It is a part of your grade  Attendance is expected at any and all scheduled activities: class, lab, team meetings, etc. It is a part of your grade.  Experience shows that grades are directly related to class attendance.  It’s better to come to class late than miss the class altogether.  N.B. - If you don’t come to class, you can’t participate in the learning process.  Do you get to skip work when you don’t want to go?

13. 1 Course Plan Rules: Senior Design substantially completed  Must have substantially completed upper- division courses prior to CSE 4316  Specified prerequisites: CSE 3310, 3320, 3322  Co-requisite: CSE 3316 (beginning Fall 2010) on same project and team  Must complete CSE 4316 followed by CSE 4317 in a two consecutive semester sequence (on same project and team)  Must pass CSE 4316 to enroll in CSE 4317 ABET outcomes  Must pass all specified ABET outcomes CSE 4316 13

14. 1 CSE 4316 14 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)

15. 1 CSE 4316 15 Grading: Components/Weights  Individual Deliverables (30%)  Items for which you are individually responsible  Team Deliverables (30%):  Items for which the team is responsible  Final Exam (30%)

16. 1 CSE 4316 16 Major Individual Deliverables (30%)– Senior Design I  All homework or class work, as assigned  Individual Status Reports (information content, completeness, accuracy)  Individual Earned Value (your contribution to the project as evaluated by instructor & teammates – more later)  Engineering/Project Notebook Reviews (random spot reviews by your GTA/ Instructor)

17. 1 CSE 4316 17 Major Team Deliverables (30%) – Senior Design I  Team Assessment  Team Status Reports (Presentations)  Project Charter (Draft and Final)  Plan Review (informal)  Your MS Project File (baseline plan)  SRD (Draft and Final)  SRD Review (Presentation) Requirements: about 50% Plan: about 25%

18. 1 CSE 4316 18 Grading: Overall Grade  Each course component will have some number of possible points  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  Final grading is based on standard 10% scale  See the syllabus for other details

19. 1 CSE 4316 19 Exams/Exercises  The final will be comprehensive, essay format.  No midterm is planned.  There may be short, unannounced class exercises from time to time.  Makeup exam is possible only in an emergency situation.  NO EARLY FINALS!

20. 1 CSE 4316 20 Homework & Lab Assignments  Due at the beginning of the assigned class (unless specifically noted otherwise). This means when the class is supposed to start, not when you get here.  If turned in during class (ie, after the class has started), there will be at least a 20% penalty  Will be accepted late until 5PM on due date. After due date, grade is zero.  All out-of-class work must be “typed” – handwritten work is not acceptable.

21. 1 CSE 4316 21 Your first assignment  Write 2 short papers as follows:  Paper #1 - In one page. tell me about yourself: what’s important to you, what’s not, what your strengths and weaknesses are. qualified to lead Specifically comment on why you would or would not be qualified to lead a Senior Design project team.  Paper #2 - A one page paper describing your individual goals and expectations for this course, through Senior Design II. type of project Include your ideas on the type of project you would like to complete over the next two semesters. Be specific!  Papers should be formatted according to Senior Design Standard 001 (see website)  Due: Beginning of class on TUESDAY, AUGUST 30 th  Submit via email attachments to odell@uta.eduodell@uta.edu

22. 1 CSE 4316 22 Engineering Notebook  You are required to maintain an Engineering/ Project Notebook throughout the project. your grade on Individual deliverables  Your records are 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. brought with you  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 leader will be asked to review occasionally

23. 1 CSE 4316 23 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, or copy theirs.  Unauthorized  Unauthorized shared work will be treated as cheating.

24. 1 CSE 4316 24 Class Website  http://ranger.uta.edu/~odell http://ranger.uta.edu/~odell every class day  Check it at least every class day  All presentations and class materials are posted there  Assignments will be posted there when assigned.  Also: supporting info, relevant standards, required forms, etc.

25. 1 CSE 4316 25 The Projects – General Guidelines  Maximum size of a project is one cubic yard – 3’ x 3’ x 3’ (guideline only, verify)  Projects MUST be approved and assigned by me before work begins.  Each team has a budget of $800 for required product components

26. 1 CSE 4316 26 The Projects – General Guidelines  What you may not have:  Security systems or parts thereof i.e., anything that might ‘mess with” campus network  Unsponsored “smart home” projects  Research projects  Remote-control vehicle projects This does not include remote-controlled testing of autonomous vehicles, or autonomous additions to RC vehicles.

27. 1 CSE 4316 27 Sponsored Projects  It is expected that you will have an external “customer” for your project.  Encourages a more realistic project  Injects outside feedback  Some sponsors may even fund project

28. 1 CSE 4316 28 Lab/Work Area  New Senior Design Lab is in 208 ERB  Each team will have:  a dedicated area (cubicle) of about 160 sq feet in the lab for your team.  adequate chairs and table space  a lockable cabinet for storage of parts, etc.  a team computer  READ and understand “Lab Rules of Etiquette” paper

29. 1 CSE 4316 29 Lab/Work Area  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/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

30. 1 CSE 4316 30 Tools  You may be required to learn and use the following:  MS Office 2007/2010  MS Project  MS Visio  MS Visual Studio  MS SourceSafe  Others as required to complete your specific project

31. 1 CSE 4316 31 Project Team Composition  4-5 members (5 for this class)  Multidisciplinary - equitable distribution of male/female, CS/CSE/SwEng will be enforced, except as specified for special projects  No dating/married couples allowed on teams  DON’T build a team from your friends  They probably won’t be your friends by the end of the project!  BALANCE the skills of your teammates  I am the final arbiter on team membership, and project assignments, but will consider your recommendations  BEGIN TODAY!

32. 1 CSE 4316 32 Fall 2011 Team Composition (as of 8/26/2010)  Current roster shows:  12 Computer Engineers  7 Software Engineers  8 Computer Scientists  1 Engineering (Intended)  6 Project teams of 4 or 5 students. Each team should have:  Exactly 2 CpE students  At least 1 CS students  At least 1 SE students A A CpE CS CpE SE D D CpE CpE SE CS E E SE CpE CpE SE CS B B CpE CpE SE CS C C CpE CpE SE CS F F SE CpE CpE CS CS Example Arrangement Eng CS

33. 1 CSE 4316 33 How We’re Going to Do Things Superior Designs, Inc.  This a small company: “Superior Designs, Inc. ”  You are the development department  Divided into teams for various projects (products)  Each team has a team lead  We use a proven, phased development process  You develop and get approval for the roadmap to deliver your product on time  Weekly “staff” meetings to review project status/progress (generally, Friday lab period)  Failure of one team => failure of company

34. 1 CSE 4316 34 How We’re Going to Do Things  I am the “boss” (development manager)  I will mentor you & help you learn how to do your job  I will approve your plans  I will approve your project expenses  I am available for consultation anytime I’m available Note: I will take trips, attend off-site meetings, etc., but the projects must continue... don’t delay critical work  I believe every question is worth answering  I don’t do your work for you  I don’t do your research for you  I don’t know everything about anything  I expect you to do your job, and will measure you on how well you do it

35. 1 CSE 4316 35 How We’re Going to Do Things  This semester you will: build your team  Establish and build your team project  Be assigned to a team project (product) plan  Establish your plan (schedule, budget, etc.) Requirements  Complete your Requirements Document (SRD) and a successful Requirements Gate Review feasibility analysis  Conduct feasibility analysis Charter  Complete your team’s Project Charter Architecture  Get started on Architecture/Design  Next semester you will complete the project  architecture/design, implementation, test, prototype delivery and final acceptance

36. 1 CSE 4316 36 Work Load 5-6 months of calendar working time  You have roughly 5-6 months of calendar working time for your project.  That’s, at most, around 500 man-hours per team member  A 5 person team has 2500 man-hours to complete the project (4 people => 2000 man-hours) Equivalent of about one man-year, or 5 K delivered lines of source code by typical metrics  Don’t pad your schedule trying to make it easy on yourself outside of the classroom  Expect to spend 10-15 hours every week outside of the classroom on the project  Failure to expend the required time will result in failure to complete the project (with a similar effect on your course grade)

37. 1 CSE 4316 37 Work Load  Planthen work  Plan your work, then work your plan tools  Learn your tools well, and the work load will be lighter. less time  Do it the way we talk about in class, and you’ll spend less time redoing things. by industry  Remember: the methods we discuss are time-tested by industry… they work!

38. 1 CSE 4316 38 ABET ABET  Must pass all ABET (Accrediting Board for Engineering and Technology) Outcome Assessments to pass this class.  SD I ABET Outcome is: multi-disciplinary team  Ability to function on a multi-disciplinary team