1. Spring 2011 Day 1: Getting Organized
Instructor: Mike O’Dell

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

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

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

6. Instructor Mike O’Dell Office – 631 ERB
Office Hours - 2:00 PM - 3:30 PM, Monday and Wednesday
Other times: when available in the lab (208A ERB), or by appointment
Include “CSE4316” in the subject line
I typically will reply to your s within one business day
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
CSE 4316

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

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

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

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

12. Class Attendance
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?
CSE 4316

13. Course Plan Rules: Senior Design
Must have substantially completed upper-division courses prior to CSE 4316
Specified prerequisites: CSE 3310, 3320, 3322
Co-requisite: CSE 3316 (beginning Fall 2010)
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
Must pass all specified ABET outcomes
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)
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%)
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)
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)
Plan:
about
25%
Requirements:
about 50%
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
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!
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.
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.
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.
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 Monday, January 24th
Submit to
CSE 4316

22. Engineering Notebook
You are required to maintain an Engineering/ Project Notebook 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 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.
Notebooks are subject to inspection and grading by the GTA/Instructor at any time, without notice.
Team leader will be asked to review occasionally
CSE 4316

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

24. Class Website http://ranger.uta.edu/~odell
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.
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
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.
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
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
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
clicking “VIEW INFORMATION ABOUT YOUR ACCOUNTS”,
logging in with your MavID and password
Your PIN will be shown with other account information
CSE 4316

30. Tools You may be required to learn and use the following:
MS Office 2007
MS Project
MS Visio
MS Visual Studio
MS SourceSafe
Others as required to complete your specific project
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!
CSE 4316

32. Spring 2011 Team Composition (as of 1/17/2010)… TBD
Current Roster shows:
x Software Engineers
y Computer Engineers
z Computer Scientists
Four Project Teams. Each team will have:
At least xxx CS students
At least yyy CE students
Possibly zzz SE students
CS CS
CE SE CE C
CS CE D
CS SE B A
CSE 4316

33. How We’re Going to Do Things
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
CSE 4316

34. How We’re Going to Do Things
I am the “boss” (development manager)
I will help you get trained to do your job
I will approve your plans
I will approve your project expenses
I am available for consultation anytime I’m here
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
CSE 4316

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

36. Work Load
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
Expect to spend 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)
CSE 4316

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

38. ABET
Must pass all ABET (Accrediting Board for Engineering and Technology) Outcome Assessments to pass this class.
SD I ABET Outcomes are:
Effective oral and written communications
Subordinate outcome: Critical thinking skills
Ability to function on a multi-disciplinary team
CSE 4316