Department of Computer Science

College of Engineering

University of Nevada, Reno

 

CS 425/625 Software Engineering

 

Fall 2003

 

Study required for the Final Exam

 

The final exam will be a comprehensive, 105-minutes (1 hour and 45 minutes) closed-book exam (no supporting material is allowed). It will take place on Monday, December 15, 2003 from noon, in FA-253, for the CS 425/625 section with regular classes on MWF from 1:00 pm, and on Monday December 15 from 4:30 pm, in SEM-326, for the CS 425/625 section with regular classes on MWF from 4:00 pm. The exam’s weight is 29% of the course grade.

 

For this final exam, you are required to study the textbook, the presentations, the class notes (“chalk notes”), your homework (assignments, project), and additional material provided by the instructor via the course’s web-page, all related to the following chapters of [Somm00]:

 

Chapter 3                     Software processes       

Chapter 4                     Project management     

Chapter 5                     Software requirements   

Chapter 6                     Requirements engineering processes      

Chapter 7                     System models

Chapter 10                   Architectural design      

Chapter 15                   User interface design     

Chapter 20                   Software testing

Chapter 22                   Managing people

Chapter 26                   Legacy systems           

Chapter 27                   Software change           

 

From the above, the following sections or sub-sections are not required:

 

Subsection 3.7             Automated process support

Subsection 4.4.4          Risk monitoring

Section 5.4                   The software requirements document

Subsection 6.2.1          Viewpoint-oriented elicitation (the beginning of Section 6.2 is required)

Subsection 6.2.3          Ethnography

Subsection 6.4.3          Requirements change maangement

Section 7.5                   CASE workbenches      

Subsection 10.4           Domain specific architectures

Section 20.4                 Testing workbenches

Section 22.4                 The People Capability Maturity Model

Section 27.1                 Program evolution dynamics

Section 27.3                 Architectural evolution