CS2013-final-report

[Elective]
• Static approaches and dynamic approaches to verification
• Test-driven development
• Validation planning; documentation for validation
• Object-oriented testing; systems testing
• Verification and validation of non-code artifacts (documentation, help files, training materials)
• Fault logging, fault tracking and technical support for such activities
• Fault estimation and testing termination including defect seeding
Learning Outcomes:
[Core-Tier2]
1. Distinguish between program validation and verification. [Familiarity]
2. Describe the role that tools can play in the validation of software. [Familiarity]
3. Undertake, as part of a team activity, an inspection of a medium-size code segment. [Usage]
4. Describe and distinguish among the different types and levels of testing (unit, integration, systems, and
acceptance). [Familiarity]
5. Describe techniques for identifying significant test cases for integration, regression and system testing.
[Familiarity]
6. Create and document a set of tests for a medium-size code segment. [Usage]
7. Describe how to select good regression tests and automate them. [Familiarity]
8. Use a defect tracking tool to manage software defects in a small software project. [Usage]
9. Discuss the limitations of testing in a particular domain. [Familiarity]
[Elective]
10. Evaluate a test suite for a medium-size code segment. [Usage]
11. Compare static and dynamic approaches to verification. [Familiarity]
12. Identify the fundamental principles of test-driven development methods and explain the role of automated
testing in these methods. [Familiarity]
13. Discuss the issues involving the testing of object-oriented software. [Usage]
14. Describe techniques for the verification and validation of non-code artifacts. [Familiarity]
15. Describe approaches for fault estimation. [Familiarity]
16. Estimate the number of faults in a small software application based on fault density and fault seeding.
[Usage]
17. Conduct an inspection or review of software source code for a small or medium sized software project.
[Usage]
SE/Software Evolution
[2 Core-Tier2 hour]
Topics:
• Software development in the context of large, pre-existing code bases
o Software change
o Concerns and concern location
o Refactoring
• Software evolution
• Characteristics of maintainable software
• Reengineering systems
• Software reuse
- 183 -