Search | Directories | Reference Tools
UW Home > Discover UW > Student Guide > UW Bothell Course Catalog 

Instructor Class Description

Time Schedule:

Robert C Shields
CSS 360
Bothell Campus

Software Engineering

Surveys the software engineering processes, tools, and techniques used in software development and quality assurance. Topics include life-cycle models, process modeling, requirements analysis and specification techniques, quality assurance techniques, verification and validation, testing, project planning, and management. Prerequisite: either CSS 263, CSS 341 or CSS 342 which may be taken concurrently; may not be repeated.

Class description

Draft Syllabus Professor: Robert Shields; office hours: T&TH 7:30-8:00PM in 3rd floor lobby or computer labs Email: (do not use Canvas messages); I plan to check email once a day Monday and Wednesday and can usually respond within a day of reading messages. Due to FERPA privacy requirements, I only send to and respond to mail from your email account as recorded by the registrar in the class enrollment list for all communication about this class. You are responsible for reading such email for this class. Course Description: CSS 360 surveys the software engineering processes, tools, and techniques used in software development and quality assurance. Topics include life‐cycle models, process modeling, requirements analysis and specification techniques, quality assurance techniques, verification and validation, testing, project planning, and management.

CSS 360 serves as an introduction to software engineering concepts that are necessary for students that wish to pursue a software engineering position in industry.

Prerequisites: Any of CSS 263, CSS 341 or CSS 342 that may be taken concurrently; may not be repeated.

Course Outcomes: CO‐1: Be able to define and describe software development projects, lifecycle methods, roles, practices, and ethical responsibilities CO‐2: Be able to compare and contrast classical and agile development processes CO‐3: Be able to use knowledge about the software process and software engineering practices to select and justify approaches to use given a project, its teams, and its constraints. CO‐4: Be able to examine trade‐offs between software engineering techniques and methods CO‐5: Be able to work with a team on creating software artifacts or work products

Required Textbook: Software Engineering, 9th. Ed., Ian Sommerville, ISBN: 0-13-703515-2, Addison-Wesley, 2011. + web chapters:

Required Readings: 1. See syllabus and class website for links to other required reading

Online Resources:

Course Goals: The overall goal of CSS 360 is to learn and apply essential topics (knowledge areas): terms, principles and concepts of software engineering. As with most technical courses, besides ability and motivation, it takes time to learn and master the subject. Expect to spend an additional 15 hours a week outside of class time on the average.

CSS 360Course topics (knowledge areas) students need to master: see syllabus on Canvas

Grading: students must demonstrate a good understanding of the SDLCs and the listed mandatory topics before they can earn a grade of 2.0 or better.

Course Work Percentage Exams/tests 55% Group Project 35% Participation, quizzes & Assignments 10% Total 100%

Earned Scores ~ Grade Range 90s 3.5 -- 4.0 80s 2.5 -- 3.4 70s 1.5 -- 2.4 60s 0.7 -- 1.4 Policies: Accommodations: To request academic accommodations due to a disability, please contact Disability Resources (DRS) at 425.352.5307, 425.352.5303 TDD, or . You will need to provide documentation of your disability as part of the review process prior to receiving accommodations. (You should do so by the third week of the quarter).

Assigned Work: Work assigned as group work must be done with your group; names (and average contribution level) of all participating group members must appear at the top of the work to earn credit for the work and all those listed on the work will be held responsible for the content of such work. For each work product your group delivers, you must each assess the quality/level (Excellent=100%, Good=90%, Limited=80%, Poor=70%, None=0%) of the contribution made by each participating group member (including yourself). To earn full points for a group work product, you must provide the average of all such contribution assessments next to each name appearing at the top of the work product submitted.

Academic integrity: You must do work independently unless directed otherwise; collaboration on individual work is NOT acceptable. You may discuss the problem statement with each other, but you must do all work to submit by yourself. The instructor must assign any group work. By enrolling this class, you agree you will not collaborate on any work unless assigned. Some cultures hold family relationships and their loyalty more important than all other considerations. In this course, we are an academic family and you would betray the instructor’s and university’s trust should you engage in Academic misconduct (such as, cheating, plagiarism). It is a serious offence and will be reported to Office of Academic Affairs. See the Student Conduct Code:

Computer use during lecture is limited to taking notes ONLY; you must not use social networks, email, games, etc. You must not display any images on your screen during lecture, as it is distracting. Do not use cell phones during class. If you distract others, you will have to move.

You must meet posted due dates. Note that canvas and catalyst can be slow, so do not wait for the last minute. Late assignments receive a grade of zero (unless the instructor has agreed on prior arrangements). I only give make‐up exams under documented, exceptional circumstances. Soft (electronic) copies of assignment work are due as specified by the beginning of class on the due date. No late submissions will be accepted except for documented special circumstances such as medical and other emergencies. Barring emergencies, you must inform me before the assignment due date. Note that disk crash is not an emergency since you should use backups and a way to use them on time. Exams and quizzes: Each quiz/test/exam occurs in the same classroom on time. Do not be late for class. I do not give makeup quizzes/test/examinations without documented medical/family/business emergency. Work Products: You must ensure that I receive all work on time in the format specified in the assignment to earn any points and the instructor must be able to read your work. You should test readability by sending it to yourself and/or group-mates and ensure everyone can read it. − Follow all directions given for each assignment. Include full names an page numbers. −.Your work products must look professional and present a quality level appropriate for a work portfolio. − Do not email your softcopy to the professor unless the server is broken. Canvas EPost (Message Board): You can access the message board link on the class website to exchange messages with your classmates. Please use this board for only discussions. No junk email. Note that the professor will not keep track of all messages. The professor monitors this board once a week. Topics covered and tentative schedule: This is an approximate ordering of topics. Material will take about the allotted time; we do not cover all sections in all chapters. See website for updates. SE means chapters in Sommerville, 9th. ed. See Website for other weekly topic readings. week Date Topic (topics and work are subject to change by instructor as needed) Study this Material before class Work Due before class on the day listed 1 1 April Tues. Introduction, syllabus quiz, What is in a project & a proposal? Read syllabus & SE 1 3 April Thur. Quiz, SW Engineering teams (p.602-614), proj. planning, improvement/CMMI p.24: Brooks: No Silver Bullet, SE 22.2-22.3, MK notes,23.2-23.5, 26 Individual resume, prepare for quiz 2 8 Quiz, Sociotechnical systems, set groups, SWEBOK, Iverson's SEMAT SE 10, MK notes, SEMAT material, resumes & proj. ideas Individual project ideas, prepare for quiz 10 Software processes: Prescriptive, e.g. SDLC Project negotiation/assessment SE 2, MK notes team & Org. status reports: with Project Proposals, roles 3 15 Quiz, Software processes Agile SE 3, MKnotes 17 Requirements engineering SE 4, 21.3.1, MK notes status reports 4 22 Quiz, Sys.Modeling & specification SE 5, 12 prepare for quiz 24 Change Management (Start now to complete next week's quiz) SE 25, 13.1-13.2; p. 25: Boehm: A View… status reports, draft Requirements portfolio 5 29 Quiz on Canvas, Questions & feedback prep. complete quiz before class 1 May Midterm exam, in class: all material so far Use free, 8th ed. Online quizzes to study Requirements peer feedback, status reports 6 6 Architectural Design (use cases, p. 180) Design (descriptions,p.181), Implementation SE 6, 7,+ links 8 more Design & Software Reuse SE 16 + links Requirements portfolio due 7 13 Software Evolution, Risk & Configuration Management SE 9, 22.1, 25+links status reports 15 Work with team on portfolio preparation during class time 12, 14.1: Security Specs. 8 18 May Last day to drop a course (& a fee is assessed) (19May: last day to change to S/NS) draft Design, Test & Implementation plan 20 More configuration, Implementation & QA SE 7, 11+ links 22 More Implementation/construction & QA SE 7, 11+ links status rpt 9 27 More Implementation, QA & Testing SE 8,9,24 Pressman 17,18 Design etc. peer feedback 29 Professionalism & Ethics SE1.3 +links status rept. Pre-questionnaire 10 3 June Process improvement SE 10,26,13.2,15.4 Design etc. portfolio 5 Review and last day material status rept. Post-questionnaire 11 10 June Final exam, Tuesday, in class SE 6-8, 11,12, 22 26 Process Improvement Rpt.

Student learning goals

General method of instruction

Recommended preparation

Class assignments and grading

The information above is intended to be helpful in choosing courses. Because the instructor may further develop his/her plans for this course, its characteristics are subject to change without notice. In most cases, the official course syllabus will be distributed on the first day of class.
Last Update by Robert C Shields
Date: 02/20/2014