Mapping the Software Testing Deliverable to the RTM Test Metrics
6.7 Mapping the Software Testing Deliverable to the RTM
Once a component is implemented, the test specification and test cases must be developed. We need to keep track of it, and at the same time, assure that each test is traced to a requirement. Additional RTM components are added. The following list the recommended elements for software testing in the RTM. RTM Software Testing Components Description Test Specification The filename of the document that contains the plan on how to test the software component. Test Cases The filename that contains the test cases to be performed as part of the test specification. Table 32: Software Testing RTM Elements These components should be related to a software component defined in the RTM. Software Engineering 300 J.E.D.I6.8 Test Metrics
The metrics used for object-oriented design quality mentioned in Design Engineering can also provide an indication of the amount of testing effort is need to test object-oriented software. Additionally, other metrics can be considered for encapsulation and inheritance. Example of such metrics are listed below. 1. Lack of Cohesion in Methods LCOM. If the value of LCOM is high, the more states of the class needs to be tested. 2. Percent Public and Protected PAP. This is a measure of the percentage of class attributes that are public or protected. If the value of PAP is high, it increases the likelihood of side effects among classes because it leads to high coupling. 3. Public Access To Data Members PAD. This is a measure of the number of classes or methods that an access another class’s attributes. If the value of PAD is high, it could lead to many side effects. 4. Number of Root Classes NOR. As the number of root classes increases, testing effort also increases. 5. Number of Children NOC and Depth of the Inheritance Tree DIT. Superclass methods should be re-tested for every subclass. Software Engineering 301 J.E.D.I6.9 Exercises
Parts
» | Komputasi | Suatu Permulaan
» Quality Focus Process Method Tools
» What is quality? How do we define quality?
» Software Quality Characteristics of a Well-engineered Software
» Software Quality Assurance Activities Formal Technical Reviews
» Types of Software Process Models
» Understanding Systems | Komputasi | Suatu Permulaan
» End-users Understanding People in the Development Effort
» What is documentation? Criteria for Measuring Usability of Documents
» Abstraction Encapsulation Review of Object-oriented Concepts
» Modularity Hierarchy Review of Object-oriented Concepts
» Project Assignment Object-oriented Process Model
» Modeling Activity Unified Modeling Language UML
» UML Baseline Diagrams Unified Modeling Language UML
» Requirements Engineering Concepts | Komputasi | Suatu Permulaan
» Inception Requirements Engineering Tasks
» Elaboration Negotiation Requirements Engineering Tasks
» Specification Validation Requirements Engineering Tasks
» Management Requirements Engineering Tasks
» Scenario Modeling Requirements Analysis and Model
» Requirements Model Validation Checklist
» InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
» Ternary association which is a relationship of three or more objects of
» The Analysis Model Analysis Model Validation Checklist
» Requirements Traceability Matrix RTM
» Requirements Metrics | Komputasi | Suatu Permulaan
» The Design Model Design Engineering Concepts
» Describing the Package Diagram Developing the Architectural Design
» Software Architecture Validation Checklist
» Developing the Data Design Model
» Report Design Interface Design
» Forms Design Interface Design
» Basic Component Design Principles Component-level Design Guidelines
» Component Diagram Developing the Software Component
» Project Assignment Design Model Validation Checklist
» Mapping the Design Deliverables to the Requirements Traceability Matrix Design Metrics
» Creating the Data Design Model Creating the Interface Design Creating the Control Design
» Project Assignment Programming Standards and Procedures
» Using Pseudocodes Control Structure Guidelines Documentation Guidelines
» Implementing Packages | Komputasi | Suatu Permulaan
» Abstract Classes Implementing Controllers
» Interfaces Why do we use Interfaces?
» Interface vs. Abstract Class Interface vs. Class Creating Interfaces
» Relationship of an Interface to a Class Inheritance among Interfaces
» Implementing Java Database Connectivity JDBC
» AWT GUI Components Implementing the Graphical User Interface
» Layout Managers Implementing the Graphical User Interface
» Controlling the Version of the Software
» Introduction to Software Testing
» White-Box Testing Techniques Software Test Case Design Methods
» Black-Box Testing Techniques Software Test Case Design Methods
» Testing your Programs | Komputasi | Suatu Permulaan
» Test-driven Development Steps Test-driven Development Methodology
» Testing Java Classes with JUnit
» Testing the System | Komputasi | Suatu Permulaan
» Mapping the Software Testing Deliverable to the RTM Test Metrics
» Project Assignment Software Project Management
» Problem Identification and Definition
» The Project Team Structure Project Responsibility Chart
» Project Work Breakdown Structure WBS
» Work Breakdown Schedule Format
» Size-oriented Metrics- Lines of Codes LOC Function-Oriented Metrics: Function Points FP
» Project Estimations | Komputasi | Suatu Permulaan
» The Risk Table Risk Management
» Risk Identification Checklist Risk Management
» Baseline Software Configuration Tasks
» Writing the Project Plan Project Assignment Case Tools
Show more