CSC 4700 Software Engineering Final Exam Study Guide, Exams of Software Engineering

A study guide for the final exam of the csc 4700 software engineering course. It includes a preparation checklist, definitions and examples of various software engineering concepts, and figures to be explained. The exam consists of two sections, with different dates and times. The preparation checklist advises students to review specific chapters and their corresponding lecture slides and notes.

Typology: Exams

Pre 2010

Uploaded on 08/13/2009

koofers-user-grq
koofers-user-grq 🇺🇸

10 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CSC 4700 Software Engineering 1 Final Exam Study Guide
Final Exam Study Guide
CSC 4700 Software Engineering
April 20, 2004, Dr. Thomas Way Exam: Section 1 - Wed. May 5, 2004, 10:45am-1:15pm
Section 2 - Tues. May 4, 2004, 1:30pm-4:00pm
Preparation checklist:
ü Review chapters 8, 10, 11, 12, 15, 19, 20, 22, 23, 28, 29
ü Review the lecture slides and notes you took for those chapters
ü Although much of this material has been covered in class, some has not so these items may require
additional preparation effort
ü Make sure you know and understand the following:
1. Be able to define (words/sentence):
abstract machine model
ADL
administrator’s manual
architectural design
black-box testing
broadcast model
call-return model
cleanroom software development
client-server model
cluster testing
concurrency
concurrent objects
configuration management
control flow analysis
CORBA
data re-engineering
data use analysis
database programming
DCOM
defect testing
equivalence partitioning
event
evolutionary prototyping
fat-client model
fault tolerance
forward engineering
functional description
GUI
information flow analysis
installation document
integration testing
interface analysis
interface testing
interrupt-driven model
introductory manual
manager model
middleware
modular decomposition
module
object
object class testing
object interface
object-oriented
object-oriented testing
openness
path analysis
path testing
program inspections
program modularization
program structure improvement
prototype
rapid prototyping
reference manual
release
repository model
resource sharing
reverse engineering
scalability
semantic knowledge
software architecture
software engineering
software inspections
software re-engineering
software testing
source code translation
statistical testing
stress testing
structural testing
sub-system
syntactic knowledge
system building
testing workbench
thin-client model
throw-away prototyping
transparency
UML
user interface prototyping
V & V
validation
variant
verification
version
pf2

Partial preview of the text

Download CSC 4700 Software Engineering Final Exam Study Guide and more Exams Software Engineering in PDF only on Docsity!

CSC 4700 Software Engineering 1 Final Exam Study Guide

Final Exam Study Guide

CSC 4700 Software Engineering April 20, 2004, Dr. Thomas Way

Exam: Section 1 - Wed. May 5, 2004, 10:45am-1:15pm

Section 2 - Tues. May 4, 2004, 1:30pm-4:00pm

Preparation checklist:

¸ Review chapters 8, 10, 11, 12, 15, 19, 20, 22, 23, 28, 29 ¸ Review the lecture slides and notes you took for those chapters ¸ Although much of this material has been covered in class, some has not so these items may require additional preparation effort ¸ Make sure you know and understand the following:

1. Be able to define (words/sentence):

  • abstract machine model
  • ADL
  • administrator’s manual
  • architectural design
  • black-box testing
  • broadcast model
  • call-return model
  • cleanroom software development
  • client-server model
  • cluster testing
  • concurrency
  • concurrent objects
  • configuration management
  • control flow analysis
  • CORBA
  • data re-engineering
  • data use analysis
  • database programming
  • DCOM
  • defect testing
  • equivalence partitioning
  • event
  • evolutionary prototyping
  • fat-client model
  • fault tolerance
  • forward engineering
  • functional description
  • GUI
  • information flow analysis
  • installation document
  • integration testing
  • interface analysis
  • interface testing
  • interrupt-driven model
  • introductory manual
  • manager model
  • middleware
  • modular decomposition
  • module
  • object
  • object class testing
    • object interface
    • object-oriented
    • object-oriented testing
    • openness
    • path analysis
    • path testing
    • program inspections
    • program modularization
    • program structure improvement
    • prototype
    • rapid prototyping
    • reference manual
    • release
    • repository model
    • resource sharing
    • reverse engineering
    • scalability
    • semantic knowledge
    • software architecture
    • software engineering
    • software inspections
    • software re-engineering
    • software testing
    • source code translation
    • statistical testing
    • stress testing
    • structural testing
    • sub-system
    • syntactic knowledge
    • system building
    • testing workbench
    • thin-client model
    • throw-away prototyping
    • transparency
    • UML
    • user interface prototyping
    • V & V
    • validation
    • variant
    • verification
    • version

CSC 4700 Software Engineering 2 Final Exam Study Guide

2. Be able to briefly example (sentence/paragraph):

  • Give at least 4 benefits of using prototyping in the software process. (8)
  • Compare evolutionary and throw-away prototyping. (8)
  • List 3 advantages of explicitly designing and documenting a software architecture. (10)
  • Briefly compare the three major architectural models: repository, client-server, & abstract machine. (10)
  • Describe 4 disadvantages of distributed systems. (11)
  • Compare client-server and distributed object architectures. (11)
  • Under what circumstances might it be appropriate to develop a design where objects execute concurrently? (12)
  • Describe 3 advantages of GUIs. (15)
  • Discuss the principles of good user interface design (Fig. 15.3)
  • Explain how error messages should be designed to best assist users. (15)
  • Describe the techniques for evaluating a user interface. (15)
  • State and explain the ultimate goal of the verification and validation process. (19)
  • Compare the top-down and bottom-up approaches to integration testing. (20)
  • Explain why the organization of human memory in terms of short-term, working and long-term memories is important for a software engineer to understand. (22)
  • List the 4 factors that influence group working, and briefly explain each. (22)
  • List and explain the 3 most important working environmental factors to boost your programming staff’s satisfaction with their working conditions. (22)
  • Explain why measuring productivity is not always a simple matter. (23)
  • Describe an approach you would take to estimate the cost (in dollars and staff) to produce a commercial version of the Novasoft JavaGP game playing software. (23)
  • Explain the 4 principal factors that affect the cost of re-engineering. (28)
  • Explain why a “release” is not just the executable code of the system. (29)

3. Be able to explain the following figures:

For example, you will be presented with a figure and told what it represents, and then be

asked to explain it thoroughly.

  • Chapter 8: 8.
  • Chapter 10: 10.5, 10.7, 10.
  • Chapter 11: 11.
  • Chapter 12: 12.
  • Chapter 19: 19.
  • Chapter 20: 20.
  • Chapter 22: 22.
  • Chapter 23: 23.
  • Chapter 28: 28.
  • Chapter 29: 29.