Instructor

Roshanak Roshandel, Ph.D.

Office: Engr 507

Phone: (206) 296-5512

Office Hours: T,TH 1:30-2:30pm, W 10:00-11:00am, Th 5:00-6:00pm or by appointment (Note: Come on in if my door is open anytime!)

Email: roshanak@seattleu.edu

Course objective

The objective of the course is to introduce students to software engineering concepts that will enable them to complete their senior project.

Overview

The class meets regularly in the fall quarter, to cover the principles of software engineering, and to initiate software project activities. Topics covered in class include Software Development Lifecycle (SDLC), understanding and documenting business requirements, formal requirements gathering and documentation techniques, requirements validation techniques, introduction to architecture design, and high-level discussions on user interface design, testing, cost estimation, and configuration management.

Textbook and Readings

“Software Engineering, A Practitioner’s Approach”, Roger S. Pressman, Seventh Edition, McGraw-Hill Science/Engineering/Math, ISBN-10: 0073375977, ISBN-13: 978-0073375977

Grading

Exams
	· Midterm	15%
	· Final	20%
Team Project
	· Teamwork · Vision and Scope	5% 15%
	· Requirements	15%
	· High-level Architecture & Design	10%
Assignments
	· Individual assignments	15%
Participation
	· Class Participation and discussion	5%

Class Format

Class participation is critical to your success in this class. You are expected to participate in the class activities. There may also be in-class assignments pertaining to the current lecture.

You will be assigned to a capstone project team by about week 3. By about mid-quarter, teams will a produce a Vision and Scope Document outlining high level business objectives of their projects. Document templates will be provided and described in class.

By the end of the quarter, each team needs to produce a comprehensive requirements and vision and scope document for their projects. Furthermore, a high-level preliminary architectural design for the system must be produced. Templates will be provided and described in class.

Finally, at the end of the quarter, students must provide an oral presentation in class on your project requirements and design. Feel free to invite your company sponsors and faculty advisor to this presentation. Specific content and format for the presentation will be discussed in class.

Note that you may (and are encouraged to) update any of the documents previously submitted throughout the quarter.

Exams: The midterm and final exams will test your understanding of basic software engineering tools and techniques, and your understanding of key issues in software design. The final exam is non-cumulative and only covers material presented in the second half of the class.

Late Submission

A 5% late submission penalty will be deduced for late assignments for every 24 hours. Assignment over a week late will not be accepted.

General Criteria for Written Assignments

Your work will be graded based on its clarity, organization, balance, amount of pertinent detail included, depth and clarity of evaluative and analytical comments, and preparation. It will also be graded on the extent to which a good understanding of the material presented in the course is shown and on the extent to which directions are followed. If you make evaluative and analytical comments, they should be supported by factual evidence, either from readings or other references. Other aspects of individual assignments may also be included in the grading.

Work that shows a lack of understanding of subject matter, is unclear or poorly organized, contains few or irrelevant details, does not follow directions, contains little or unsubstantiated evaluative commentary or is poorly written or prepared (e.g., typos, grammatical errors) will receive low grades. Students may want to plan to take draft versions of their writing to the Writing Center for assistance with meeting these criteria and sharpening their technical writing skills.

Academic Integrity

Plagiarism is the unacknowledged use of the work or intellectual property of other persons, published or unpublished, presented as one’s own work. All students are expected to work on all individual assignments independently. Collaboration on individual assignments is considered cheating and will be penalized accordingly. Other examples of behavior that is not tolerated in this class include copying all or part of someone else’s work and submitting it as your own, sharing your assignment solution with other students in the class, consulting with another student during an exam, and copying text from published literature without proper attribution. If you have questions about what is allowed, please discuss it with the instructor. All students are responsible for reading and following the Seattle University Academic Honesty Policy. Students who violate University standards of academic honesty are subject to disciplinary sanctions, including failure in the course and suspension from the University.

Tentative Schedule (Subject to change)

Week	Date	Topic	Reading	Assignments
W1.	TH 9/24	Course Intro; Intro to SDLC, Intro to software processes	Ch 1-4	HW 1 assigned
W2.	T 9/29 TH 10/1	Interviewing, Basic principles Class only meets 10:00-10:30 Vision and Scope Document	Ch 7 and handout	HW 1 due HW 2 assigned
W3.	T 10/6 TH 10/8 F 10/9	*Project Center Joint Session (Resume and Interviews- Bannan 401, 11 am - noon)* Requirement Elicitation and Documentation Vision and Scope Document System Requirement Specification Document *Fall Workshop (12:00-2:00pm)* Client Meetings – Philips Project		HW2 due Prepare for the interview
W4.	T 10/13 TH 10/15	Client Meetings – Neighborhood House Project Developing use cases, risks, iterations, project planning, software estimation	Ch 4, 5 and handout	Prepare for the interview
W5.	T 10/20 TH 10/22	Midterm Review *Project Center Joint Session (Team Dynamics Bannan 401, 11 am - noon)* *Midterm*		TA1: Vision and Scope Draft Due Midterm
W6.	T 10/27 TH 10/29	Requirement Modeling Web Applications	Ch 7	(Vision and scope presentation @308) Vision and Scope Final Due
W7.	T 11/3 TH 11/5	Design Principles Architecture Design	Ch 8, 9	Requirements draft due (Friday 11/6 midnight)
W8.	T 11/10 TH 11/12	Component level Design, UI Design Designing Web apps	Ch 10, 11, 13	TA2: Team (Team Requirements presentation @308 11/13/2009)
W9.	T 11/17 TH 11/19	Testing Test driven development	Ch 17, 18, 19, 20
W10.	T 11/24 TH 11/26	Testing cont Thanksgiving Recess	Ch 17, 18, 19, 20	TA3: Team Architecture draft due
W11.	12/1 12/3	Final Review Metrics		TA4: Team project (SRS + Architecture + Test plan) package – final version due
Monday 12/7		Final Exam

Instructor

Exams

Team Project

Assignments

Participation