1 / 13

Test Equipment Product Line: Implementation and Evaluation

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.

nova
Download Presentation

Test Equipment Product Line: Implementation and Evaluation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Test Equipment Product Line Josh Bowen Capstone Project - 2009 Presentation 3

  2. Outline • Action Items • Brief Overview of Project • Implementation Work Products • Demonstration • Assessments • Project Evaluation

  3. Action Items from Presentation 2 • Create several testers from core assets • Fulfill capstone project requirements

  4. Project Overview • Develop Sample Product Line Core Assets • Demonstrate Product Line Process • Produce Significant Prototype • Fulfill Requirements of Capstone Project

  5. Implementation

  6. 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

  7. Implementation-Variability Binding *Add Types refers to the ability to add new types as well as replacing existing types

  8. Implementation-Variability Binding

  9. Implementation-Variability Binding

  10. 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.

  11. 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

  12. 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

More Related