FINAL DEMO 4 3 2009 Apollo Crew group

FINAL DEMO 4. 3. 2009 Apollo Crew, group 3 T-76. 4115 SW Development Project

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

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. 3. 2009 Apollo Crew - Final Demo 3

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! 4. 3. 2009 Apollo Crew - Final Demo 4

Technical solution 4. 3. 2009 Apollo Crew - Final Demo 5

Apollo Crew proudly presents Version 1. 0 4. 3. 2009 Apollo Crew - Final Demo 6

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 4. 3. 2009 Apollo Crew - Final Demo 7

Project evaluation • This part includes – – – – Goals Deliverables Challenges Lessons Learned Risk Management Quality Assurance Metrics Practices 4. 3. 2009 Apollo Crew - Final Demo 8

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. 4. 3. 2009 Apollo Crew - Final Demo 9

Goals in detail • Customer's goals – – – The project outcome is a working system - Ok The project solution includes agreed-upon parts and features – Evaluation pending 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 – – – – – 4. 3. 2009 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 – Evaluation pending Apollo Crew - Final Demo 10

Deliverables • All deliverables have been submitted in time. • We have created comprehensive documentation including User manual, Quick user guide, Glossary, 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. 4. 3. 2009 Apollo Crew - Final Demo 11

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 4. 3. 2009 Apollo Crew - Final Demo 12

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. 4. 3. 2009 Apollo Crew - Final Demo 13

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. 4. 3. 2009 Apollo Crew - Final Demo 14

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) => reorganizations – Effort estimation problems => reorganizations – New technology caused some issues to solve => assigned more resources – Development infrastructure problems (server delivery was late) => changed supplier 4. 3. 2009 Apollo Crew - Final Demo 15

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. 4. 3. 2009 Apollo Crew - Final Demo 16

Quality Dashboard 4. 3. 2009 Apollo Crew - Final Demo 17

Quality Assurance Practices • Most important QA practices were – – – – 4. 3. 2009 Test cases and manual unit testing Explorative testing & bugfests Code reviews Refactoring Peer programming Static analysis methods Automated unit and acceptance testing Continuous feedback from the customer Apollo Crew - Final Demo 18

Quality Assurance Tools Target Tool Enterprise Java Bean testing EJB 3 Unit Basic unit testing JUnit + Emma Used UI and acceptance testing Selenium + Cubic. Test Statistical code analyzer PMD Metrics Eclipse metrics + Semmle. Code Continuous Integration Server Continuum Defect tracking Trac 4. 3. 2009 Apollo Crew - Final Demo 19

Metrics: Defects Apollo Crew - Final Demo 20

Metrics: Lines of Code 4. 3. 2009 Apollo Crew - Final Demo 21

Metrics: Time Usage 4. 3. 2009 Apollo Crew - Final Demo 22

Metrics: Time Usage by Sprint 4. 3. 2009 Apollo Crew - Final Demo 23

Metrics: Time Usage 2 This is a rough estimate. 4. 3. 2009 Apollo Crew - Final Demo 24

Practices: Visualizing

Practices: Visualizing 2

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/System. Architecture 4. 3. 2009 Apollo Crew - Final Demo 27

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! • Glorious group members: Tuomo Aura, Mikael Nousiainen, Juhana Yrjölä, Esa Tanskanen, Toni Sallanmaa, Anton Zvonkov, Antero Juntunen, Mira Maksimainen and Keijo Palmunen. 4. 3. 2009 Apollo Crew - Final Demo 28

Questions? • Any questions?