1 / 18

T-76.4115 Iteration Demo

T-76.4115 Iteration Demo. Software Trickery I2 Iteration 5.3.2008. Project status ( 5 min) Achieving the goals of the project Project metrics Work results ( 25 min) Brief overview of the system Demo of TMS Quality Assurance ( 10 min) Continuous integration

simone-gaines
Télécharger la présentation

T-76.4115 Iteration Demo

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. T-76.4115 Iteration Demo Software Trickery I2 Iteration5.3.2008

  2. Project status (5 min) Achieving the goals of the project Project metrics Work results (25 min) Brief overview of the system Demo of TMS Quality Assurance (10 min) Continuous integration Automated unit and acceptance tests Agile methods, and used practices Agenda for presentation

  3. Introduction to the project:Tournament Management System • Module for Party management system v2.0 (PMS) • Modular web-based system for managing party events • E.g. used in Assembly events • Tournament management system module (TMS) • Replaces existing system (non PMS-module) • A solution for managing game tournaments • Main user groups • Administrators • Tournament players • Outside spectators • Will be first used at Winter Assembly 2008 gaming festival • Estimated 1500 users at this event

  4. Status of the project’s goals • Goal 1: All stakeholders satisfied with course outcome • OK, the final points will tell • Goal 2: Customer is satisfied with the product • OK, TMS to be used in Winter Assembly 2008 • Goal 3: Project organization works smoothly • OK, Everyone still happy • Goal 4: Everyone reaches their personal learning goals on this course • OK • Goal 5: Winning the quality award with superior quality product • OK, looks pretty good • Goal 6: Creating interest in the assembly organization among the group • OK, at least 1 developer going to WA 2008 as an organizer

  5. Status of the iteration’s deliverables • Project plan, QA-plan, Requirements document & Technical specification • OK, updated • Test cases, QA report and test logs • OK • Software and online user manual • OK • Known defects listed in customer’s Trac • Final report • OK • T-76.5158: SEPA diaries • OK

  6. Resource usage Original plan (in the beginning of the iteration) • DevDays helped to utilize • Ok, 5% error goal set for the iteration reached Realization and updated plan (realized hours)

  7. Results of the iteration I2 • New major features developed during I2 • Phase types • Double-elimination, Round-robin, Single-result • Clan management • Seeding • By rank • Online admin user’s manual • New user interface • Tested by peer group

  8. System overview

  9. PMS permissions

  10. TMS access control

  11. Sample tournament

  12. Demo • The actual software developed • You may use the demo script to follow the presentation

  13. Quality Assurance (1/3):Quality dashboard

  14. Quality Assurance (2/3):Quality goals

  15. Quality Assurance (3/3):CruiseControl & automated testing • Automated unit-tests (NUnit) • 45 test cases concentrating on the most important modules • Automated acceptance-tests (Selenium) • Thorough suite of 111 test cases • Automated performance-tests (JMeter) • Code metrics and analysis • Linking between failed acceptance-tests and defect reports • See http://pyppe.iki.fi:8880/ccnet/

  16. Changes to the project • Moved to regular development days in I2 • Project not so distributed anymore • Requirement for new UI in sprint S2.2 • More important to customer than functionalities

  17. Agile methods- used work practices • Regular development days • Held 2 or 3 times a week • Weekly status meetings • Held every Tuesday • Customer present • Version control and documentation on customer server • Helps customer to find software and documentation • Demo environment for external stakeholders • Running 24/7 after I1 • Automated testing • Unit and acceptance-level • The Carrots of Agility

  18. Any Questions ? • Software Trickery would like to thank everyone!

More Related