Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
38 Cards in this Set
- Front
- Back
|
Life cycle
|
Planning, Development, Maintenance
|
|
|
Definition of software engineering
|
production of fault-free, fault-tolerant software that satisfies user needs
|
|
|
Waterfall model steps
|
1. Requirement
2. Specification 3. Planning 4. Design 5. Implementation 6. Testing 7. Maintenance 8. Retirement |
|
|
Most costly phase
|
Maintenance
|
|
|
Most costly activity
|
communication
|
|
|
3 types of teams
|
Chief, heirarchial, democratic
|
|
|
Two types of risk
|
Technical risk, managerial risk
|
|
|
What doesn COCOMO stand for?
|
Constructive Cost Model
|
|
|
If the cost is lower, the risk is....
|
higher
|
|
|
What do requirements need to be?
|
comprehensive, verifiable, timely
|
|
|
Definition of reuqirements
|
Collection of verifiable statements
|
|
|
Who wil verify requirements
|
end users, service provideers, developers...
|
|
|
What are IC cards used for
|
facilitate task identification
|
|
|
Software design approaches
|
Top down, bottom up
|
|
|
When and how to use top down software design?
|
Problem well understood, divide and conquer
|
|
|
When and how to use bottom up software design?
|
problem less well understood, assemble from parts
|
|
|
Should cohesion be low or high?
|
high
|
|
|
What is cohesion
|
meaure of the relative functional strength of a module
|
|
|
Coupling definition
|
meaure of the interdependence among software modules
|
|
|
Verification definition
|
Confirms software works correctly
|
|
|
Validation definition
|
software works according to specification
|
|
|
Execution-based testing
|
running the program
|
|
|
Non-execution based testing
|
reviews, formal analysis
|
|
|
Two ways to conduct a walkthrough
|
participant driven, document driven
|
|
|
black box testing examples (3)
|
functional tests, performance tests, stress tests
|
|
|
White box testing examples (1)
|
structure tests
|
|
|
Types of coverage
|
Statement, branch, conditional, multiple contional, path
|
|
|
Equivalence class definition
|
set of test cases where any one member is as good as any other to test
|
|
|
Boundary value analysis
|
test edge cases, not in equivalence class
|
|
|
What does CRC stand for?
|
Class, responsibilities, collaborators
|
|
|
Three steps of OOA
|
class modeling, dynamic modeling, functional modeling
|
|
|
How is each OOA step derived
|
Class modeling - requirements spec
Dynamic modeling - scenarios Function modeling - requirements spec |
|
|
How to construct finite state diagram
|
current state + event + predicate = next state
|
|
|
Three steps of OOD
|
Determine the actions of the classes, design product in terms of clients, proceed to detailed design
|
|
|
What is a robustness test
|
When the system fails is the recover easier
|
|
|
What is an invariant?
|
When the pre-condition and post-condition are the same
|
|
|
What are the two types of test automation
|
code-driven, graphical user integration
|
|
|
What is test driven development
|
Define unit tests before writing code. code is done when tests pass
|
