17Jan06

COMP 145 SPRING ‘06: 

COMP 145 SPRING ‘06 Logistics and Introduction 17 January

Contact information: 

Contact information Best methods (in order) are AIM: dianepozefsky don’t use to send me files or information that I need to save email: pozefsky@cs.unc.edu phone (cell): 824-9073 Dropping in is fine but besides Sitterson, I work in Carr, Europa, Beard, …

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

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

Course Objectives: 

Course Objectives Overview of the practice of software engineering: why software development is more than coding Hands on experience of the full process and working on a team Awareness of software engineering failures in the real world

Teams: 

Teams

About the Projects: 

About the Projects Service Learning Does not require that all projects be service learning Leslie Parkins will stop by for a few minutes today Carolina Challenge Amount of participation your choice Web site: www.carolinachallenge.org Meetings Interest meeting: Jan 19, 7pm, Student Union 3105 Prep session on writing a business plan: Jan 24, 7 pm

Let’s take 5 minutes: 

Let’s take 5 minutes Problems Identify, not solve Schedule time with your team and me

Logistics: 

Logistics All meetings are in my office (Sitterson 327) I would like to attend your first meeting with your client If not the first, shortly thereafter I’m flexible about rescheduling meetings But I get grumpy when I’m stood up Feel free to contact me at any time by email, phone, or IM Class attendance is expected

Inclement weather policy: 

Inclement weather policy Generally follows university If not having class on a day the university is open, I will email class before 9 am Possible exceptions University open and busses not running University re-opens at 11 and sidewalks aren’t cleared until then We win another national championship

Class Material: 

Class Material All content available on web site Slides Templates http://www.cs.unc.edu/Courses/comp145-s06/ Sections for each project Should be repository of all material Public site Will give access as soon as I have your cs id

Readings: 

Readings No class text No assigned readings References when at all possible However, if you are going to go into the software engineering field, consider reading Brooks, The Mythical Man-Month

How the Course Will Run: 

How the Course Will Run Classes are planned for the full semester Classes will lighten toward the end of the semester drop to 50 minutes classes cancelled Additional time to be used for team meetings After spring break, guest speakers Meetings Weekly team meetings with me: organizational and technical Meetings with the client as appropriate (probably weekly) Weekly team meetings Regular deliverables Description posted on web Initial dates are class-wide; later dates are team-defined Draft schedule as starting point But the items are fixed Multiple executable deliverables to client

Beyond the Project: 

Beyond the Project Tests One or two virtual in-class quizzes (open book, note, computer) Must be done electronically Covers the broader issues Depending on class performance, second may be cancelled or for extra credit Presentations Midterm: what the project is aboutl Final: show and tell

End of the Semester: 

End of the Semester Project completed Additional documents Critique of another team’s documentation Evaluation of team performance Final presentation Show and tell In lieu of final exam Clients invited

Significant Changes: 

Significant Changes Each week, I’ll ask each team member to fill in a form with hours for Meetings Documentation Code Design Final project will be due 2 weeks before the end of class Last two weeks, the client and I get to test the project Errors posted on Bugzilla Final grade is on the FIXED code

Deliverables: 

Deliverables Contract Project schedule Functional specification User interface sketches Architecture Implementation manual User guide Code Running system Presentations

First Deliverables: 

First Deliverables Web Site: 23 January I’ll send an email out as soon as access is granted Team rules: 23 January First meeting with client should be this week Contract 30 January initial 10 February signed Project plan 6 February initial Adjusted frequently: changes must be tracked

Web Site: 

Web Site Contact information Overview of project Related links Repository for all documents Most important early documents are Team rules Contract Schedule Journal or log of decisions made and reasoning … or you’ll keep revisiting the same decisions

Additional Deliverables: 

Additional Deliverables Adjusted based on individual projects Technical differences Is architecture predetermined? How significant is the user interface? Project differences Customer requirements and deadlines What they need

Documentation: 

Documentation All electronic documentation will be linked from the web site Commonly used software packages only Recommend against 90-day free trials Spelling matters as does grammar Deadlines are expected to be met Adapting the schedule is different than missing deadlines

Professionalism: 

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

Team Rules: 

Team Rules Establish them now … before problems arise Team behavior Notifying team members if you’re going to be late Ways to contact and communicate Responses to emails Expected times Meaning of no response Coding practices Style Prologue How to maintain current state Strongly recommend using a formal mechanism CVS, Subversion, … More than one project has accidentally regressed in the last two days

Grading: 

Grading 80% project individual contribution multiplier (.8 – 1.1) 40% code 30% documentation 5% on time delivery 5% professionalism 10% team presentations 10% quizzes and critique 7.5% quizzes 2.5% other team critique

Individual Contribution: 

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 Weekly record of hours Peer evaluations My evaluation Client evaluation Consultant evaluations

First Task: Contracts: 

First Task: Contracts What will be accomplished by the team Constraints Base function Prioritized functions Support and materials to be provided by client Documentation required for client Checkpoints with client REQUIRED: at least 2 code demonstrations before final deliverable

Contracts: 

Contracts Look at examples from last year http://www.cs.unc.edu/Courses/comp145-s05/ I’ll post a template Agreement between You and the client You and me Establish appropriate expectations Do not over commit. Primary goals are to be completed. Primary and secondary goals are to be defined

Contract Content: 

Contract Content What needs to be included Software Testing Documentation User Administrative Maintenance Meetings (when and with whom) Deliverable dates (milestones) Be sure to include Key goals and requirements Constraints Risks and Dependencies

Contract Considerations: 

Contract Considerations Are you building off of an existing base? Resources required Software Hardware Materials Skills Are there people that you need access to? Books and training

All software projects are different: 

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

Common Mistakes: 

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

Clients vs. Users: 

Clients vs. Users The client is the person “paying the bill” The users are the ones that will Use your system Maintain your system Administer your system Know their Skill level Time constraints Tolerances Expectations