130 likes | 233 Views
This project presentation outlines the action items, overview, implementation work products, demonstration, assessments, and evaluation of a test equipment product line project by Josh Bowen. The project aimed to develop core assets, demonstrate the product line process, create a prototype, and fulfill capstone project requirements. The implementation included configuration-type and subsystem replacement-type product line members. Assessments involved peer evaluations, software metrics, and software performance evaluations. Project evaluation focused on goal accomplishment, sample implementation, project estimation challenges, and potential improvements.
E N D
Test Equipment Product Line Josh Bowen Capstone Project - 2009 Presentation 3
Outline • Action Items • Brief Overview of Project • Implementation Work Products • Demonstration • Assessments • Project Evaluation
Action Items from Presentation 2 • Create several testers from core assets • Fulfill capstone project requirements
Project Overview • Develop Sample Product Line Core Assets • Demonstrate Product Line Process • Produce Significant Prototype • Fulfill Requirements of Capstone Project
Implementation • Product line implementation includes an instance of: • Configuration type product line member • Subsystem Replacement type product line member • Subsystem Inclusion type product line member • Demonstration
Implementation-Variability Binding *Add Types refers to the ability to add new types as well as replacing existing types
Assessments • Peer Evaluations • Used checklist based on the 29 practice areas from the SEI • Software Metrics • 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 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
Project Evaluation • Did the software accomplish the goals • Created a sample implementation that is being used in an ongoing product line adoption • Project Estimation • Estimates were poor due to complicating factors • Challenges • Limited time available, tool availability • Potential Improvements • Implement more functions, More unit testing, Create template project plan based on PL members