CS 562: Applied Software Engineering

Instructor: Prof. Carlos Jensen Email: cjensen@eecs... Office hours: MW 11-1pm, or by appointment Office: KEC3061

Mailing list: cs562-W09@engr. Website: http://classes.engr.oregonstate.edu/eecs/winter2009/cs562 Location: COVL 218 (KEC 3114) Meeting time: TR 12:00 - 13:20

Course Description

 The goal of this class is to give you, the student, hands-on experience in software engineering and project management by working on a real, long-term team project. While doing so, students will be introduced and research advanced topics in Software Engineering techniques, topics, and tools. This is the second course in a 2 course sequence. CS561 is an enforced prerequisite. This class is meant to build on the requirements and project ideas derived by teams in the first course. The focus of this course is on the second half of the design and software engineering cycle; team management, development & testing.

Schedule (subject to change)

	Tuesday		Thursday
Week 1	1/6	Welcome & intro Project review	1/8	Code & Project Management tools Slides
Week 2	1/13	Code & Project Management Tools - Launchpad - MS Team Foundation Server (?) - Sourceforge	1/15	Joining, Sketching & Visualization - Group awareness in distributed software development - Information Needs in Collocated Software Development Teams - Questions Programmers Ask During Software Evaluation Tasks
Week 3	1/20	Joining, Sketching & Visualization - Let's go to the whiteboard: How and why software developers draw code - Code thumbnails: using spatial memory to navigate source code - Understanding How and Why Open Source Contributors Use Diagrams in the Development of Ubuntu	1/22	Team Management, Communication & Coordination - Peopleware Revised Project Document
Week 4	1/27	Team Management, Communication & Coordination	1/29	Team Management, Communication & Coordination
Week 5	2/3	Requirements  Engineering Requirements Engineering in the Year 00	2/5	Requirements Engineering i* GBRAM
Week 6	2/10	Testing Agile Testing	2/12	Project presentations Revised Project Document
Week 7	2/17	Testing Project Presentations (continued) Reviewing 25 years of testing technique experimentsAutomated Whitebox Fuzz testing Swarm Verification	2/19	Engineering for Privacy and Security  Unpacking "privacy" for a networked world Experimental Evaluation of a Lightweight Method for Augmenting Requirements Analysis
Week 8	2/24	SE Disasters & Causes     - Mythical Man Month	2/26	SE Disasters & Causes
Week 9	3/3	Usability Evaluation	3/5	End-User Software Engineering *
Week 10	3/10	End-User Software Engineering	3/12	Prototype & Final presentation

Project links:

- BeaverStatus

- EECS web-page

- Mosaic

- Truffle

- Olympic CIS