1. CSE Senior Design I Fall 2015 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 development process  Study and implement a modern “real world” development process  Develop a working product  Develop a working product “from scratch” planning, requirements, design and preliminary prototyping of  In CSE 4316 - focus planning, requirements, design and preliminary prototyping of your product. complete the project  In CSE 4317 - continue and complete the project and demonstrate your working product

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 Instructor  Mike O’Dell  Office – 647 ERB  Office Hours - 2:00 PM – 3:30 PM, Tuesday & 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

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

6. 1 CSE 4316 6 Teaching/Lab Assistant  GTA  TBD  GTA should be a part of your teams  consultant  evaluator/reviewer  observer  helper  Office hours conducted in lab (ERB 208), times on Class WebsiteClass Website

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

8. 1 CSE 4316 8 Scheduled Labs (Friday)  Team spaces in SD lab (208 ERB)  Will occasionally meet in assigned lab period classroom (section 003/004 in NH 111, 005/006 in ERB 103)  Lab activities may include: Scrum sessions  Observed Scrum sessions working sessions  Team working sessions  Engineering Notebook (ENB)  Engineering Notebook (ENB) Reviews  Class exercises

9. 1 CSE 4316 9 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 as the course structure evolves web copy of the syllabus  The web copy of the syllabus is the current version  Same syllabus  Same syllabus for SDI and SD II

10. 1 CSE 4316 10 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?

11. 1 CSE 4316 11 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 (occasionally contributes)  25 – 50% = 70 (seldom contributes, but sometimes)  <25% = 0 (barely noticeable)

12. 1 CSE 4316 12 Grading: Components/Weights  Individual Deliverables (25%)  Deliverables for which you are individually responsible  Team Deliverables (40%):  Deliverables for which the team is responsible  Final Deliverables (25%)  SRS, project charter, design document, final Scrum artifacts

13. 1 CSE 4316 13 Major Individual Deliverables (25%)– Senior Design I  Any homework or class work, as assigned  Observed participation in class exercises  Individual contribution (your overall contribution to the project as evaluated by instructor & teammates – more later)  Engineering/Project Notebook Reviews (random spot reviews by your GTA/ Instructor)  Individual Sprint Retrospective Reports

14. 1 CSE 4316 14 Major Team Deliverables (40%) – Senior Design I  Team Assessment  Scum artifacts per defined sprint schedule  Product backlogs & Sprint backlogs  Project charter (draft and end of semester)  SRS (end of semester)  Detailed design document (end of semester)

15. 1 CSE 4316 15 Exams/Exercises  This is a project/capstone course so NO exams are scheduled.  Major scheduled SD1 class exercises consist of:  Team Skills Assessment  Design Exercise  Scrum reviews  There may be short, unannounced, graded class exercises on occasion

16. 1 CSE 4316 16 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 submitted work must be “typed” – handwritten work is not acceptable.

17. 1 CSE 4316 17 Your first assignment  Write a short paper as follows (10 point Individual Deliverable):  Tell me about yourself: What’s important to you? What’s not? What are your strengths and weaknesses?  Specifically comment on why you would or would not be qualified to lead a Senior Design project team.  Discuss your individual goals and expectations for this course, through completion of Senior Design II.  Include your ideas on the type of project you would like to complete over the next two semesters.  If you have a project idea for senior design, suggest it here. Be as specific as possible!

18. 1 CSE 4316 18 Your first assignment (cont.)  Papers should be formatted according to Senior Design Standard 001 (see website)  Due: By email prior on THURSDAY, September 3 rd  Submit via email attachments (pdf) to odell@uta.eduodell@uta.edu  See: http://ranger.uta.edu/~odell/Fall2015_CSE4316.htm http://ranger.uta.edu/~odell/Fall2015_CSE4316.htm

19. 1 CSE 4316 19 Engineering Notebook  You are required to maintain an Engineering Notebook (ENB) 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

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

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

22. 1 CSE 4316 22 The Projects – General Guidelines  No drones or remote controlled vehicles  Nothing that requires construction or use of large supporting items for demonstration, e.g.  door frames  basketball goals  theater seats  Each team has a budget of $800 for required product components

23. 1 CSE 4316 23 The Projects – General Guidelines  No projects involving:  UTA security systems or parts thereof i.e., anything that might “mess with” the campus network  Potential violations of individual privacy  Unsponsored “smart home” systems  Live animal or human testing  All industry-sponsored and multi- disciplinary projects will be assigned (even if not selected).

24. 1 CSE 4316 24 Sponsored Projects  It is expected that you will have an external “customer” (Product Owner/sponsor) for your project.  Encourages a more realistic project experience  Provides opportunity for “real world” requirements analysis  Insures external customer feedback in the development process  Some sponsors may even fund portions of your project (but NOT required)

25. 1 CSE 4316 25 Lab/Work Area  Senior Design Lab is 208 ERB (+203 ERB?)  Each team will be assigned adequate space for team meetings/activities  Each team space has a computer:  Dual boot Win 7 and Ubuntu 14.04 LTS  Win 7 partitions are set up with Deep Freeze (thaw is required to make persistent changes)  Ubuntu partitions are set up with user accounts, root login is required to make install changes (NOT Deep Freeze, you can still save files)  READ and understand “Lab Rules of Etiquette” paper

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

27. 1 CSE 4316 27 Project Team Composition  4-5 members (-005), 5 members (-003)  Multidisciplinary – an 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!

28. 1 CSE 4316 28 Fall 2015 Team Composition – Section 003  Current roster shows:  8 Computer Engineers  6 Software Engineers  16 Computer Scientists  SIX project teams of 5 students. Each team must have:  1 or 2 CpE students  1 SwE student  2 or 3 CS students Possible Team Arrangement A A SE CS CS CpE C C CpE CS CS CS B B CpE CS CS CS CS SE SE SE E E CpE CS SE CpE D D CpE CS SE CS F F CS CS SE CS CS CpE CpE

29. 1 CSE 4316 29 Fall 2015 Team Composition – Section 005  Current roster shows:  4 Computer Engineers  8 Software Engineers  5 Computer Scientists  4 project teams of 4 - 5 students. Each team must have:  1 CpE students  2 SwE student  1 or 2 CS students Team Arrangement A A SE CS CpE C C CpE CS B B CpE CS CS SE SE SE D D CpE CS SE SE SE SE

30. 1 CSE 4316 30 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  Teams are self-organizing and self-directed within the boundaries of the specified SDI development methodology  Failure of one team => failure of company  Learn to depend on and help your peers

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

32. 1 CSE 4316 32 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)  Execute several stages of the development process (i.e. “Scrum Sprints”)  Demonstrate your working prototypes at completion of each stage  Prepare and maintain product/project documentation  Next semester you will continue work and complete the project, then demonstrate your final (“potentially shippable”) prototype

33. 1 CSE 4316 33 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, 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-6 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)

34. 1 CSE 4316 34 Work Load  Planthen work  Plan your work, then work your plan for each Sprint 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!

35. 1 CSE 4316 35 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  Primary: Ability to function on a multi- disciplinary team Will be assessed by peer evaluation at end of semester in SD1  Secondary: Ability to design a software systems product to meet desired needs