Test Equipment Product Line Josh Bowen Capstone Project
Test Equipment Product Line Josh Bowen Capstone Project - 2009 Presentation 3
Outline l l l Action Items Brief Overview of Project Implementation Work Products Demonstration Assessments Project Evaluation
Action Items from Presentation 2 l l Create several testers from core assets Fulfill capstone project requirements
Project Overview l Develop Sample Product Line Core Assets – – l Demonstrate Product Line Process Produce Significant Prototype Fulfill Requirements of Capstone Project
Implementation
Implementation l Product line implementation includes an instance of: – – – l Configuration type product line member Subsystem Replacement type product line member Subsystem Inclusion type product line member Demonstration
Implementation-Variability Binding Add Types* Configured by Configuration Overridden by Subsystem Replacement Used by Subsystem Inclusion Tester √ Test. Run Part √ √ √ Limits Result √ √ Results Test √ √ √ Test. Instance Test. Code √ Test. Codes Additional. Input Test. Data √ Classes *Add Types refers to the ability to add new types as well as replacing existing types
Implementation-Variability Binding Add Types Configured by Configurati on Overridden by Subsystem Replaceme nt Used by Subsystem Inclusion Devices Tester. Devices Device √ Device. Command √ Device. Form √ frm. Device. Panels Classes
Implementation-Variability Binding Add Types Configured by Configuration Overridden by Subsystem Replacement Used by Subsystem Inclusion Forms Utilities. Form Main. Form √ Device. Checkout. Form Data. Analyzer. Form Log. Viewer. Form Historical. Data. Form Data. Transmit. Form Data. Backup. Form Test. Parameters. Form Verify. Parameters. Form Testing. Form √ Classes Tester. Menu. Form
Assessments l Peer Evaluations – l Software Metrics – l Used checklist based on the 29 practice areas from the SEI Used tools provided by IDE to calculate metrics. Software Performance – – – Software generally not the limiting performance of a tester To prove this the speed at which the software can calculate test result dispositions was measured This was the purpose of the Subsystem Inclusion project.
Assessments Software Performance Measurement Type Description Performance All Pass Integers, floats, attributes and Booleans all passing. 12820 Limit Checks/m. S All Fail Integers, floats, attributes and Booleans all failing. 12820 Limit Checks/m. S Mixed Integers, floats, attributes and Booleans half passing, half failing. 9174 Limit Checks/m. S In a product line all members use the same core assets and have the same amount of reused code. A more important metric is the amount of unique code. Source Code Metrics Measurement Description Production Tester Core Assets Product Line Member Maintainability Index Compilation of the other metrics based on work at Carnegie Mellon University and normalized to a 0 -100 scale. Anything above 20 is acceptable. 57 82 89 Cyclomatic Complexity Measure of the number of paths through a method. 6827 1584 8 Depth of Inheritance The maximum depth of the inheritance tree for the solution. 8 9 2 Class Coupling Measure of the dependencies between classes in the solution. 242 223 13 Lines of Code Total lines of code without comments. 27486 4185 17
Project Evaluation l Did the software accomplish the goals – l Project Estimation – l Estimates were poor due to complicating factors Challenges – l Created a sample implementation that is being used in an ongoing product line adoption Limited time available, tool availability Potential Improvements – Implement more functions, More unit testing, Create template project plan based on PL members
- Slides: 13