University of California, Santa Cruz
T Th, 8:00-9:45AM
Porter College 144
Lab: Jack Baskin, 213
| Instructor: | Jim Whitehead |
|---|---|
| Teaching assistant: | Donna Stidolph |
| Office: | 123 Baskin Engineering |
| Phone: | 459-1227 |
| Email: | ejw@cse.ucsc.edu |
| Office Hours: | Tuesdays 10:00-12:00pm and by appointment |
| Text: | Software Engineering: A Practitioner's Approach, 5th Edition, Roger S. Pressman, McGraw-Hill, 2000 |
|---|
List of abbreviations and acronyms used in the syllabus:
| Class | Date | Reading or Location | Topic or Task* |
|---|---|---|---|
| 1 | Jan. 4 | Text, Chapter 2 (pp. 19-47, 29 pages) | Software engineering introduction |
| 2 | Jan. 9 | Text, Chapter 3 (pp. 55-74, 20 pages) | Overview of project management |
| 3 | Jan. 11 | Text, Chapter 11 (pp. 271-294, 24 pages) | Requirements analysis, prototyping, and specification. Groups and projects chosen |
| Lab 1 | Overview of project/lab, Team and project selection, Selection of RSD template |
||
| 4 | Jan. 16 | Text, Chapter 11 | Requirements analysis, prototyping, and specification (cont'd) |
| 5 | Jan. 18 | Text, Chapter 15 (pp. 401-418, 18 pages) |
RSD due, User Interface Design |
| Lab 2 | Prototype, User manual creation |
||
| 6 | Jan. 23 | Review | Quiz #1 |
| 7 | Jan. 25 | Text, Chapter 14 (pp. 365-378, 13 pages) Text, Chapter 12 (pp. 299-315, 17 pages) |
Software Architecture, Design Modeling and Analysis |
| Lab 3 | Tracking requirements to design |
paper prototype,
user
manual, and Error messages due |
|
| 8 | Jan. 30 | Text, Chapter 21 (pp. 571-598, 27 pages) | Object Oriented Design |
| Class | Date | Reading or Location | Topic or Task* |
|---|---|---|---|
| 9 | Feb. 1 | Text, Chapter 13 (pp. 335-359, 25 pages) | Principles of Design |
| Lab 4 | Consulting, as required | PDD due | |
| 10 | Feb. 6 | Text, Chapter 17 (pp. 437-472, 36 pages) | Software testing |
| Feb. 8 | Advising Day - NO LECTURE | ||
| Lab 5 | Test plans, procedures | DDD due | |
| 11 | Feb. 13 | Text, Chapter 18 (pp. 477-502, 26 pages) | Software testing strategies |
| 12 | Feb. 15 | Review | Quiz #2 |
| Lab 6 | Testing review, if necessary | TP, UTR | |
| 13 | Feb. 20 | Text, Section 8.5 (pp 205-209, 3.5 pages) | Software Inspections Video: Scenes of Software Inspections |
| 14 | Feb. 22 | Software Project Failures | Analysis of items from Risks column of Software Engineering Notes |
| Lab 8 | Inspection checklists | C, TS due | |
| 15 | Feb. 27 | Student inspections | Walkthroughs and inspections |
| Class | Date | Reading or Location | Topic or Task* |
|---|---|---|---|
| 16 | Mar. 1 | Student inspections (cont.) | Walkthroughs and inspections |
| Lab 9 | Project completion management | STR, ER can be submitted for feedback | |
| 17 | Mar. 6 | Text, Chapter 9 (pp. 225-239, 25 pages) | Software Configuration Management |
| 18 | Mar. 8 | Review | Quiz #3 STR, ER can be submitted for feedback |
| 19 | Mar. 13 | Meet in lab!!! | project display, STR, ER, project disk, and EPN due |
| Final | Final | Mar. 16, 8 - 11 AM | Final exam |
Acnowledgements: I would like to thank Linda Werner, whose syllabus for CMPS 115 was directly reused in the creation of this course.