T Project Review Final Demo

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 2 Agenda  Sales pitch (20 min)  Project idea and customer needs  SW demo  Technologies  Project evaluation (15 min)  Summary

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 3 Product presentation In collaboration with

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 4 Imagine Unhappy Oy We are not efficient!!!! Consultants & C + ? Happy Oy

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 5 Project idea  Tool for modeling business processes  Diagrams modeled with UML notations  Digrams can be converted to XPDL format and saved on the server

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 6 What is business processes modeling for?  expressing business processes in terms of business activities.  To make communication easier  Allow different stakeholders to view system from different angles and communicate their perspectives with each other  Complex systems and processes need visual modeling  Makes clear what value system brings.

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 7 Why UML and XPDL?  UML  Widely adopted standard  Same notation from business to business  Understandable for both business analysts and system analysts  XPDL  Mechanism for the process for the process definition interchange  Different users can share source of diagrams even if they created them with different modeling tools.

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 8 Develop concept further (some suggestions for the next year project course)  Integrate tool with ERP systems:  connect the visually shown process parts to the IPSS CRM database. As an example the user can in the future use the diagram as a link to launch other functions of the product  Use tool to activate activities needed to perform task.  Implement more UML diagrams (use case diagrams, class diagrams)

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 9 SW demo 

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 10 Software structure

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 11 Backed by Strong Technologies  Java  Applet  Swing GUI  Apache XML-RPC  Client  Server  XML-Parser  XPDL  UML  UML Activity diagram

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 12 Part 2 Project evaluation

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 13 Structure of work performed

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 14 Working hours by person

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 15 Software size PackageClassesMethodsNCSSLOCJavadocs client.engine client.gui common server Total NCSS = Non commented source statements (all executable source code statements) LOC = Lines of code (with comments and blank lines)

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 16 Quality assessment Bug metrics  During last iteration acceptance testing was done  10 bugs identified by customer  2 new bugs reported by team members  7 of them closed  Improvements were suggested by customer and by team members  Out of 9 customer’s suggestions for improvement 6 were implemented and delivered for testing before the final release I1I2I3DETotal Reported Closed To be fixed

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 17 Suggestions for improvement

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 18 Used practices  Iteration planning  Risk management  Defect tracking  Requirement management  Version control  Testing

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 19 Personal practices  Requirements elicitation and analysis  Usability tests  Architectural design  Pair programming  Configuration management  Project progress tracking and control

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 20 Risks  Risk management  risks evaluation forms  Risks analysis (Red, Yellow, Green)  New risks reported  Risks are not reported  Risk actions are wrong  Person responsible for risks quits.  SoberIT is down  Birdflue will affect people and will come to Finland I1 I2 I3 Risk IDRisk Test plan fails 1.4Wrong architectural design 2.1Lack of experience 2.2Underestimated resources for project task 2.7Project is late 3.1Requirements changed

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 21 Summary of the project

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 22 Thank you! Have fun on your vocations!