b. cause elimination
c. brute force d. code restructuring e. a, b and c
1. Which of the following are characteristics of testable software? Answer: d
a. observability b. simplicity c. stability
d. all of the above
2. The testing technique that requires devising test cases to demonstrate that each program
function is operational is called? Answer: a
a. black-box testing b. glass-box testing c. grey-box testing d. white-box testing
3. The testing technique that requires devising test cases to exercise the internal logic of a
software module is called? Answer: d
a. behavioral testing b. black-box testing c. grey-box testing d. white-box testing
4. The cyclomatic complexity metric provides the designer with information regarding the
number of
a. cycles in the program b. errors in the program
c. independent logic paths in the program d. statements in the program
Answer: c
5. Black-box testing attempts to find errors in which of the following categories Answer: d
a. incorrect or missing functions b. interface errors c. performance errors d. all of the above e. none of the above
6. Testing OO class operations is made more difficult by Answer: d
a. encapsulation b. inheritance c. polymorphism d. both b and c
7. What is the differences between black-box testing and white-box testing?
Answer: Black-box testing involves testing the functionality of a software component without knowing the details of its internal logic. White-box testing involves testing the
independent logic paths with full implementation knowledge.
8. What is equivalence partitioning as it applies to software testing? What is scenario-based testing?
Answer: Equivalence partitioning technique divides the input domain into classes of equivalent data items. Test cases are derived from combinations of elements from each equivalence class. Exhaustive testing of all input domain values is not necessary. Scenario-based testing: The user tasks described in the use-cases are used to construct the test cases. It is used to uncover errors that occur when actors interact with the software (focus is on user behavior, not product behavior).
? Introduction To Software Engineering
? What is software engineering?
? The differences between software and hardware
? Software is developed, not manufactured.
? Software does not wear out, but it can deteriorate.
? Most software is custom build, not assembled out of components.
? Software Process
? Generic View
? Software Engineering Layers: Process, Methods, Tools ? Generic Software Engineering Framework Activities:
Communication, Planning, Modeling, Construction, Deployment
? CMMI : Incomplete, Performed, Managed, Defined, Quantitatively
managed,
Optimized
? Process Models
? Waterfall Model (Linear Sequential Model) ? Incremental Model ? Prototyping Model ? Spiral Model
? Extreme Programming (XP)
? Framework Activities: planning, design, coding, test
? Software Engineering Practice
? Requirements Engineering
? The definition of requirements engineering
Inception, Elicitation, Elaboration, Negotiation, Specification, Validation
? Structural Analysis
? Data dictionary ? ERD
? Object-oriented Analysis
? Diagrams of UML for analysis modeling
? Use-case diagram: visualizes the interaction of your
system with the outside world
? Activity diagram: shows the flow of events within your
system
? Class diagram: describes the structure of system by
showing system’s classes, their attributes, and the relationship between the classes
? State diagram: represents active states for each class
and the events that cause changes between these active states
? Software Engineering Practice
? Design Engineering
? Four Design Models
Data Design, Architectural Design, Interface Design, Component-level Design
? Structural Design
? Cohesion ? Coupling
? Object-oriented Design
? Information Hiding ? Polymorphism
? Software Engineering Practice
? Test Strategies
? Unit Test
? Integration Test
? Top-down Integration ? Bottom-up Integration
? Validation Test ? System Test
? Test Tactics
? White-box Test
? Basic Path Testing
? Black-box Test
? Equivalence Partitioning
? OO Test
? Scenario-based Testing
