1. FINAL DEMO 4.3.2009 Apollo Crew, group 3 T-76.4115 SW Development Project

2. 4.3.2009 Apollo Crew - Final Demo2 Agenda Customer’s need and solution (5 min) Product demonstration (20 min) Project evaluation and metrics (15 min) –Quality assurance Questions

3. 4.3.2009 Apollo Crew - Final Demo3 Customer’s need Design Factory needed an information and reservation system that… –welcomes visitors –guides and assists visitors –manages events –acts as a space reservation system

4. 4.3.2009 Apollo Crew - Final Demo4 Solution Apollo Crew created software that… –welcomes and guides visitors –manages events and workspace reservations –manages all content and its structure –delivers information through big screens and workspace screens –interacts with touch screens –has a total number of 10 web admin sections –is called Lobby!

5. 4.3.2009 Apollo Crew - Final Demo5 Technical solution

6. 4.3.2009 Apollo Crew - Final Demo6 Apollo Crew proudly presents Version 1.0

7. 4.3.2009 Apollo Crew - Final Demo7 Demonstration Script Admin –General introduction –Views: Event, Reservation, Content, Channel Big screen –Viewing channel (Device) Touch screen –Viewing menu structure and content –Updating content in admin Views: Companies, Users, Menu

8. 4.3.2009 Apollo Crew - Final Demo8 Project evaluation This part includes –Goals –Deliverables –Challenges –Lessons Learned –Risk Management –Quality Assurance –Metrics –Practices

9. 4.3.2009 Apollo Crew - Final Demo9 Goals Our goals were divided into customer’s goals, group’s goals and personal goals. All measurable goals were achieved. Some goals are hard to measure and some goals cannot be verified at the moment, e.g. course grade.

10. 4.3.2009 Apollo Crew - Final Demo10 Goals in detail Customer's goals –The project outcome is a working system - Ok –The project solution includes agreed-upon parts and features – Partly ok –The system is maintainable and scalable - Ok –The system is usable (ease of use) - Ok –The system's UI is attractive and inviting and the UI can be changed – Ok Group’s goals –Use the course's process - Ok –Create working practices that are improved on during the course - Ok –Learn how to utilize the methods and tools that are used in the project - Ok –Fulfilling personal learning goals - Ok –All deadlines are kept - Ok –Development tools work as expected - Ok –Demos are prepared well and held professionally - Ok –The mentor and customer are informed well enough - Ok –A high overall quality is reached – Partly ok

11. 4.3.2009 Apollo Crew - Final Demo11 Deliverables All deliverables have been submitted in time. We have created comprehensive documentation including User manual, Quick user guide, Technical specification, Installation and maintenance manual and release notes. Some deliverables will be delivered in the handover session since those are reviewed in the session. We will have a handover and training session on Tuesday 10.3.2009 12:00-16:00.

12. 4.3.2009 Apollo Crew - Final Demo12 Deliverables in detail Project plan - OK Requirements document - OK Technical specification - OK Test cases, QA report and test log - OK Peer test session charters with exploration logs - OK Peer test summaries - OK User's manual - OK Final report - OK Iteration demo slides - OK Glossary - OK Will be delivered in the handover session –Installation and maintenance manual –UI and layout manual –Release notes –Source delivered as GPL

13. 4.3.2009 Apollo Crew - Final Demo13 Challenges, most important A very large and vague domain and the requirements were very hard to define. The scope was extremely hard to define. A completely new technology for the user interface. Our software was probably one of the biggest software systems built in this course. Testing has been challenging because of the scope and the use of cutting edge technologies.

14. 4.3.2009 Apollo Crew - Final Demo14 Lessons Learned It's really hard to plan resources ahead. Organize common learning events instead of individual assignments. Organize as many common development session as possible. The manager needs to have a clear vision and be able to guide the developers.

15. 4.3.2009 Apollo Crew - Final Demo15 Risk Management Risk meetings were held after sprints. –The goal was to identify the current situation and any changes in risks. Some risks materialized but issues were solved. –Members not able to do assigned tasks (e.g. illness) –Effort/scope estimation problems –Technology didn’t work as expected

16. 4.3.2009 Apollo Crew - Final Demo16 Quality Assurance Most important QA practices were –Test cases and manual unit testing –Explorative testing –Continuous feedback from the customer –Refactoring –Static analysis methods –Automated unit and acceptance testing –Peer programming

17. 4.3.2009 Apollo Crew - Final Demo17 Quality Goals Functionality –All major components are implemented. Usability –Design Factory made a UI usability review and also reviewed the user manuals. –The system has been improved based on the feedback. –The customer participated in the development process and therefore has contributed to it. Code correctness –A large amount of effort has been put into refactoring the code. –PMD error levels are low and lot of testing has been done. Maintainability –The code is commented and automated unit tests are handed out. –The architectural document and Javadocs describe technical details.

18. 4.3.2009 Apollo Crew - Final Demo18 Quality Dashboard

19. 4.3.2009 Apollo Crew - Final Demo19 Quality Assurance Tools TargetToolUsed Continuous Integration Server Continuum Enterprise Java Bean testing EJB3Unit Basic unit testingJUnit + Emma UI and acceptance testingSelenium + CubicTest Statistical code analyzerPMD MetricsEclipse metrics + SemmleCode Defect trackingTrac

20. Apollo Crew - Final Demo20 Metrics: Defects

21. 4.3.2009 Apollo Crew - Final Demo21 Metrics: Lines of Code

22. 4.3.2009 Apollo Crew - Final Demo22 Metrics: Time Usage

23. 4.3.2009 Apollo Crew - Final Demo23 Metrics: Time Usage by Sprint

24. 4.3.2009 Apollo Crew - Final Demo24 Metrics: Time Usage 2 This is a rough estimate.

25. Practices: Visualizing

26. Practices: Visualizing 2

27. 4.3.2009 Apollo Crew - Final Demo27 Additional information More detailed information and metrics can be found in https://wiki.tkk.fi/display/apollocrew/Final+report https://wiki.tkk.fi/display/apollocrew/Quality+Assurance+Report+for+Iteration+2 http://lobby-dev.aaltodesignfactory.fi/trac/wiki/SystemArchitecture

28. 4.3.2009 Apollo Crew - Final Demo28 Thank you! We would like to thank Design Factory and Jussi Hannula for this opportunity to create something totally unique and exciting, Mentor Pyry Lahti for invaluable advice during the course, and the course personnel for providing a great environment!

29. Questions? Any questions?