1. COMP 523 Diane pozefsky
24 August 2016

2. Agenda Introductions Logistics Selecting a project
Software Engineering Overview

3. Logistics NO INCOMPLETES 4 credits EE APPLES
Web Site (needs some restructuring but all the info should be there):
This course is
4 credits EE APPLES
CI (Implication: document iterations)
Final is project presentations MON, DEC 12
Weekly team meetings with me, client, team
NO INCOMPLETES

4. Class times Fridays Why First 2 weeks
Need you to get some extra information early
Guarantee that you have a time that all can meet

5. Dropping the Course I can’t stop you from dropping
But if you drop after teams have been assigned (for non-medical reasons)
You will incur the wrath of teammates
You will not be permitted to take it later

6. How much work is it Designed to preclude a last minute miracle drive
Depends on the project
Depends on your passion
Design, writing, development
Designed to preclude a last minute miracle drive

7. How the Course RunS Weekly Team Meetings Regular deliverables
With me: organizational and technical
With client: content and design
Team
Regular deliverables
6 sprints (first is requirements)
EQUALLY WEIGHTED
Full set of deliverables

8. ATTENDANCE Expected Required when your classmates are demo’ing
There is a guest speaker

9. Meetings with me Review the past week’s work Documents Code
Review team and individual performances
Meeting commitments
Responding to feedback

10. Course Objectives why software development is more than coding
Overview of the practice of software engineering
Awareness of software engineering (and failures) in the real world
why software development is more than coding
Hands on experience of the full process
Working on a team
Individual assignments: broader view

11. Grading 80% project (6 sprints equal) 5% final presentation
individual contribution multiplier (.7 – 1.1)
30% process (includes professionalism)
35% code
35% documentation
5% final presentation
15% individual assignments

12. Individual assignments
Weekly reading from the classical literature
More general software engineering topics
Short answer all on Sakai
Begins after Labor Day
No lates

13. Individual Contribution
Rare that it will go over 1.0
Basically, you can’t do better than the project
But there are always exceptional circumstances
Inputs
Peer evaluations
My evaluation
Client evaluation
Consultant evaluations

14. Professionalism
You are representing the university, the department, this class and yourself
You are expected to
show common courtesy
make it to meetings promptly or notify people
meet your commitments
Remember that your web site is publicly available and may be accessed by outside people

15. Selecting a Project

16. Process Written descriptions available Sunday Presentations on Monday
Preferences by 1 pm Tuesday (Google doc)
Assignments by 8 am Wednesday
Finalized by 3 pm Wednesday
First client meeting in class on Friday

17. details May sign up as team or individual
Will ask you to identify the times you can meet with me
Will be used to assign teams
Trying to avoid Monday morning and Friday meetings
If you don’t submit on time, I assume that you are dropping the course

18. Considerations Does the topic interest you?
Do you think you can work with the client?
Platform to be used
Web, mobile, language, OS, …
Learn new or strengthen skills

19. Software engineering

20. Engineering Turning ideas into reality Creating something useful
from other things
using science and math

21. Software Engineering vs. Other Engineering Disciplines
Maturity
Roman aqueducts 2000 years ago
Software engineering 50 years ago
Startup costs
Barriers to entry
Rate of change

22. Software Engineering Objective
The right software
delivered defect free,
on time and
on cost,
every time.
Carnegie Mellon Software Engineering Institute

23. Software Engineering Processes
Differ by how often you do the steps
Points on the spectrum
Differences in overhead
Three fundamental models
Waterfall
Spiral
Iterative
Widely used models
Integrated Product Development
Unified Software Development Process
Extreme Programming

24. Fundamental Steps Step Documentation Requirements Design
Implementation
Test
Deployment
Maintenance
Functional Spec
Design Document
Code
Test Plan
User Documentation

25. Transparency Track what you do AND document it …not as an afterthought
Living, heavily-used documentation

26. Documentation Principles
Need to reflect changes
Not just change, but CAPTURE change
Version control
Need to keep all documents synchronized
Only say it once
Danger of shared ownership: If many own, no one owns
Practical consideration: Responsibility vs. authority

27. Common Mistakes Over committing (“big eyes”) Unrealistic schedules
Training
Access to people or materials
Hours in the day
Level of detail
Vague descriptions
Over specification
Not knowing your user
Assuming that you’ll get it right the first time

28. Different Types of Projects
Consider 4 different types of systems
COMP 523 projects
Productivity suites
Commercial web sites
Airplane systems
Pacemakers
How do they differ in criticality?
What does that mean for the development process?

29. All software projects are different
but …
Requirements will change.
Surprises will happen.
Schedules will slip.
Life will happen.