Computer Science 340
Exam 1 Review
Disclaimer: I have attempted to be comprehensive in the
following, but important items may have been omitted by mistake. If
you see such an omission, please let me know, but you are responsible
for all of the lecture material to date.
The first hour exam will be held on Thursday, Oct. 7 and will cover
chapters 1 - 8 of the textbook. (Please note the change of exam
date)
- Basic definitions
- Be prepared to say what software engineering is about, and
why it is important.
- Be prepared to describe what a system is and how it relates
to software engineering
- Be prepared to describe the lifecycle model, iterative
prototyping, and Boehm's spiral model.
- Be prepared to describe the management activities involved
in software engineering, and be able to construct an activity
network and activity bar chart, identifying a critical
path.
- Requirements and Specification
- Be prepared to describe the requirements engineering
process. Be able to describe viewpoint-oriented and
method-based techniques for requirements analysis (and say what
requirements analysis is). Be able to sketch simple data flow
models, entity-relationship diagrams, and object diagrams.
- Be able to describe the three levels of requirements
specification (requirements definition, requirements
specification, software specification).
- Be able to distinguish between functional and
non-functional requirements.
- Be able to explain prototyping, the difference between
evolutionary and throw-away prototyping, and when each could be
used.
- Formal specification will not appear on this exam (but
may appear on the next one).