1 / 23

CMMI Validation Kristof Vandermeeren Ruben Verborgh

CMMI Validation Kristof Vandermeeren Ruben Verborgh. Validation Purpose. Purpose Fullfill intended use in intended environment “Building the product right”  “Building the right product” verification  validation Benefits Detect feature problems early in development lifecycle

maia
Download Presentation

CMMI Validation Kristof Vandermeeren Ruben Verborgh

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. CMMIValidation Kristof VandermeerenRuben Verborgh

  2. ValidationPurpose • Purpose • Fullfillintendeduse in intended environment • “Building the product right”  “Building the right product”verification  validation • Benefits • Detect feature problemsearly in developmentlifecycle • Continuouslyimprovingrequirementsagile

  3. ValidationSpecific Goals [1] Prototype [2] Test Plan [3] State of the Joomla! Community [4] Customer interfaces • SG 1 Prepare for Validation • SP 1.1 Select products for Validation • All • Alpha version / Prototype [1] • WAFL • Layout of delivered page (-> User Interface) [2] • Extension must comply with Joomla! Listing Rules [3] • Hadra • Marketer and publisher interfaces [4]

  4. ValidationSpecific Goals [1] Status presentation [2] Test Plan [3] Interview • SG 1 Prepare for Validation • SP 1.2 Establish the Validation Environment • People • All • Review meetings with prof. Gielen [1] • Coaching by assistants • WAFL • Acceptance testing with Sinyate [2] • Contact with Sinyate-developer [2] • Hadra • Marketing agency MarKoMO [3] • Channel GUIDO (planned) [3] • TultiMouch • Communication-driven acceptance testing [3]

  5. ValidationSpecific Goals [1] Server • SG 1 Prepare for Validation • SP 1.2 Establish the Validation Environment • Infrastructure • All • Server with demo application [1] • University or stakeholder location with internet access

  6. ValidationSpecific Goals [1] Demos [2] Test Plan [3] Architecture document • SG 1 Prepare forValidation • SP 1.3 Establish Validation Procedures and Criteria • All • Prepare demos for review meetings [1] • WAFL • Specification of acceptance testing requirements [2] • Hadra • Use cases [3] • Mashedup • Formal requirement checklists [3]

  7. ValidationSpecific Goals [1] Demos [2] Test Plan [3] Interview • SG 2 Validate Product or Product Components • SP 2.1 Perform Validation • All • Demos during review sessions [1] • WAFL • Acceptance Testing with Sinyate (planned) [2] • TultiMouch • Customer continuously monitors software [3]

  8. ValidationSpecific Goals [1] Meeting reports [2] Test Plan [3] Interview reports • SG 2 Validate Product or Product Components • SP 2.2 AnalyzeValidationResults • All • Analyze review meetings [1] • WAFL • Acceptance testing: none yet (but planned) [2] • Hadra • Analyze interview results [3]

  9. Validation Generic Practices • GG 2 Institutionalize a ManagedProcess • GP 2.1 Establish an Organizational Policy • Nothing found yet • GP 2.2 Plan the process • Nothing found yet • GP 2.3 Provide Resources • Nothing found yet

  10. Validation Generic Practices [1] Test Plan [2] Meeting reports [3] Interview reports • GG 2 Institutionalize a ManagedProcess • GP 2.4 Assign Responsibility • WAFL • Testing team is responsible for acceptance testing [1] • Hadra • Testing manager coordinates test plan creation [1] • GP 2.5 Train People • WAFL • Follow guide set up by Sinyate developer [1] • GP 2.6 Manage Configurations • All • Maintain reports on project website [2] [3]

  11. Validation Generic Practices [1] Test Plan [2] State of the Joomla! Community [3] Interview • GG 2 Institutionalize a Managed Process • GP 2.7 Identify and Involve Relevant Stakeholders • All • Contact with customer during review meetings • WAFL • Contact with Sinyate developer [1] • Request for contribution on Joomla conference • TultiMouch: • On-site customer” [3] • Mailing list • Has SVN access  running and debugging • Contacts with IBBT, entertainment sector, board game industry [3]

  12. Validation Generic Practices [1] Test Plan [2] State of the Joomla! Community [3] Interview • GG 2 Institutionalize a Managed Process • GP 2.7 Identify and Involve Relevant Stakeholders • Hadra • Regular contacts with MarKOMo [3] • Regular contacts with GUIDO [3] • Mashedup • Regular contacts with supervisors

  13. Validation Generic Practices • GG 2 Institutionalize a ManagedProcess • GP 2.8 Monitor and Control the Process • Nothing found yet • GP 2.9 ObjectivelyEvaluateAdherence • Nothing found yet • GP 2.10 Review Status withHigher Level Management • Nothing found yet

  14. Validation Generic Practices • GG 3 Institutionalize a Defined Process • GP 3.1 Establish a Defined Process • Nothing found yet • GP 3.2 Collect Improvement Information • Nothing found yet

  15. ValidationProcess Assets Interview report (Hadra)

  16. ValidationProcess Assets Interview report (TultiMouch)

  17. ValidationProcess Assets Demo (Hadra)

  18. ValidationProcess Assets Demo (WAFL)

  19. ValidationProcess Assets Meeting Reports

  20. ValidationProcess Assets WAFL & Hadra Test Plan

  21. ValidationFindings • Strengths • Goodstakeholdercontacts • Demo applications • OpportunitiesforImprovement • Define and manage validation process • Proposed Actions • Performacceptancetesting

  22. ValidationGlossary • CMMI Capability Maturity Model Integration • …

  23. ValidationReferences • CMMI for Development version 1.2http://www.sei.cmu.edu/publications/documents/06.reports/06tr008.html • …

More Related