CSE Senior Design ICSE Senior Design I

Fall 2015Fall 2015Day 1: Getting OrganizedDay 1: Getting Organized

Instructor: Mike O’DellInstructor: Mike O’Dell

1

CSE 4316 2

What’s This Class About?What’s This Class About?This is the CSE capstone coursecapstone course, where

you put it all together. put it all together. In this course In this course you will:you will: Work on a team team with your fellow students  Learn a lot about the software product software product

development cycle development cycle by actually experiencing it Study and implement a modern “real world”

development processdevelopment process Develop a working productDevelop a working product “from scratch” In CSE 4316 - focus planning, requirements, planning, requirements,

design and preliminary prototyping design and preliminary prototyping ofof your product. 

In CSE 4317 - continue and complete the projectcomplete the project and demonstrate your working product

1

CSE 4316 3

What’s This Class About?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 Higher order learning: Bloom’s Taxonomy (rev.)(rev.)

1

CSE 4316 4

InstructorInstructorMike O’DellOffice – 647 ERBOffice Hours - 2:00 PM – 3:30 PM, Tuesday

& ThursdayOther times: when available in the lab

(208A ERB), or by appointmentEmail: odell@uta.edu

Include “CSE4316” in the subject line I typically will reply to your emails within

one business day

1

CSE 4316 5

Who is this guy?Who is this guy?Retired Navy CommanderIBM: 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

1

CSE 4316 6

Teaching/Lab AssistantTeaching/Lab AssistantGTA

TBDGTA should be a part of your teams

consultant evaluator/reviewer observer helper

Office hours conducted in lab (ERB 208), times on Class Website

1

CSE 4316 7

Scheduled Lectures (Mondays Scheduled Lectures (Mondays & Wednesdays)& Wednesdays)Textbook: Rapid Development: Rapid Development:

Taming Wild Software SchedulesTaming Wild Software Schedules, Steve McConnell, Microsoft Press, 1996 (ISBN: 1-55615-900-5)

Prepared lectures (instructor) on key topics

Class discussion (student and instructor led) of case studiescase studies.

Class exercises

1

CSE 4316 8

Scheduled Labs (Friday)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: Observed Scrum sessionsScrum sessions Team working sessionsworking sessions Engineering Notebook (ENB)Engineering Notebook (ENB) Reviews Class exercises

1

CSE 4316 9

Class SyllabusClass Syllabus

YOUYOU 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

The web copy of the syllabus web copy of the syllabus is the current version

Same syllabus Same syllabus for SDI and SD II

1

CSE 4316 10

Class AttendanceClass Attendance

Attendance is expected at any and all scheduled activities: class, lab, team meetings, etc. It is a part of your gradeIt 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?

1

CSE 4316 11

Grading: Components/Weights 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)

1

CSE 4316 12

Grading: Components/Weights Grading: Components/Weights

Individual Deliverables (25%) Deliverables for which you are

individually responsibleTeam Deliverables (40%):

Deliverables for which the team is responsible

Final Deliverables (25%) SRS, project charter, design document,

final Scrum artifacts

1

CSE 4316 13

Major Individual Deliverables Major Individual Deliverables (25%)– (25%)– Senior Design ISenior Design IAny homework or class work, as assigned

Observed participation in class exercisesIndividual 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

1

CSE 4316 14

Major Team Deliverables (40%) –Major Team Deliverables (40%) –Senior Design ISenior Design I

Team AssessmentScum 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)

1

CSE 4316 15

Exams/ExercisesExams/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

1

CSE 4316 16

Homework & Lab AssignmentsHomework & Lab AssignmentsDue 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.

1

CSE 4316 17

Your first assignmentYour 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!

1

CSE 4316 18

Your first assignment (cont.)Your first assignment (cont.)

Papers should be formatted according to Senior Design Standard 001 (see website)

Due: By email prior on THURSDAY, September 3rd Submit via email attachments (pdf) to odell@uta.edu

See: http://ranger.uta.edu/~odell/Fall2015_CSE4316.htm

1

CSE 4316 19

Engineering NotebookEngineering Notebook You are required to maintain an Engineering

Notebook (ENB) throughout the project. Your records are an integral part of your

project, therefore it will be used as a component of your grade on Individual your grade on Individual deliverablesdeliverables. 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 youbrought with you to all lab/class sessions. Notebooks are subject to inspection and gradinginspection and grading

by the GTA/Instructor at any time, without notice.

Team leader will be asked to review occasionally

1

CSE 4316 20

EthicsEthicsToday, I assume that you all are honest assume that you all are honest

and ethicaland 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 studentsmay 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.

UnauthorizedUnauthorized shared work will be treated as cheating.

1

CSE 4316 21

Class WebsiteClass Website

http://ranger.uta.edu/~odellCheck it at least every class dayevery class dayAll presentations and class materials

are posted thereAssignments will be posted there

when assigned. Also: supporting info, relevant standards,

required forms, etc.

1

CSE 4316 22

The Projects – General The Projects – General GuidelinesGuidelines

No drones or remote controlled vehiclesNothing 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

1

CSE 4316 23

The Projects – General The Projects – General GuidelinesGuidelines

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

1

CSE 4316 24

Sponsored ProjectsSponsored ProjectsIt 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 processSome sponsors may even fund portions of

your project (but NOT required)

1

CSE 4316 25

Lab/Work AreaLab/Work Area

Senior Design Lab is 208 ERB (+203 ERB?)Each team will be assigned adequate space

for team meetings/activitiesEach 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

1

CSE 4316 26

Lab/Work AreaLab/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/ clicking “VIEW INFORMATION ABOUT YOUR

ACCOUNTS”, logging in with your MavID and password Your PIN will be shown with other account information

1

CSE 4316 27

Project Team CompositionProject 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!

1

CSE 4316 28

Fall 2015 Team Composition – Fall 2015 Team Composition – Section 003 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 ArrangementPossible Team Arrangement

AASESECSCS

CSCS CpECpE

CCCpECpECSCS

CSCSCSCS

BBCpECpECSCS

CSCSCSCS

CSCSSESE

SESE

EECpECpECSCS

SESE CpECpE

DDCpECpECSCS

SESECSCS

FFCSCSCSCS

SESECSCS

CSCS

CpECpE

CpECpE

1

CSE 4316 29

Fall 2015 Team Composition – Fall 2015 Team Composition – Section 005 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 ArrangementTeam Arrangement

AASESECSCS

CpECpE

CCCpECpECSCS

BBCpECpECSCS

CSCS

SESE

SESE

DDCpECpECSCS

SESE

SESE

SESE

SESE

SESE

1

CSE 4316 30

How We’re Going to Do ThingsHow We’re Going to Do Things This a small company: “Superior Designs, Superior Designs,

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

1

CSE 4316 31

How We’re Going to Do ThingsHow 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

availableNote: 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

1

CSE 4316 32

How We’re Going to Do ThingsHow We’re Going to Do ThingsThis semester you will:

Establish and build your teambuild your team Be assigned to a team project 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

documentationNext semester you will continue work and

complete the project, then demonstrate your final (“potentially shippable”) prototype

1

CSE 4316 33

Work LoadWork Load You have roughly 5-6 months of calendar 5-6 months of calendar

working timeworking 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

Expect to spend 10-15 hours every week outside of the classroomoutside 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)

1

CSE 4316 34

Work LoadWork Load

PlanPlan your work, then workthen work your plan for each Sprint

Learn your tools tools well, and the work load will be lighter.

Do it the way we talk about in class, and you’ll spend less time less time redoing things.

Remember: the methods we discuss are time-tested by industryby industry… they work!

1

CSE 4316 35

ABETABET

Must pass all ABETABET (Accrediting Board for Engineering and Technology) Outcome Assessments to pass this class.

SD I ABET Outcome is: Primary: Ability to function on a multi-multi-

disciplinary teamdisciplinary teamWill be assessed by peer evaluation at end of

semester in SD1

Secondary: Ability to design a software systems product to meet desired needs