T Iteration Demo METAXA PP Iteration 17 November November November 2015

T Iteration demo 2 Agenda Introduction (5 min) Introduction (5 min) Project status (10 min) Project status (10 min) achieving the goals of the iteration achieving the goals of the iteration project metrics project metrics Work results (10 min) Work results (10 min) presenting the iteration’s results presenting the iteration’s results Used work practices (15 min) Used work practices (15 min)

T Iteration demo 3 Introduction to the project Language skills testing shifting from manual to computer-based Language skills testing shifting from manual to computer-based Less time-consuming (eventually) Less time-consuming (eventually) Less human mistakes in grading Less human mistakes in grading Results ready-to-analyze Results ready-to-analyze A working prototype already exists A working prototype already exists Not easy-to-use Not easy-to-use Not maintainable and hard to develop further Not maintainable and hard to develop further Lacks functionality Lacks functionality  METAXA will develop a software for a computer-based English exam for the Language Centre of HUT.

T Iteration demo 4 English exam system (EES) Basic functionalities Basic functionalities Creating & taking exams Creating & taking exams Automatically checking and grading exams Automatically checking and grading exams Handling exam feedback Handling exam feedback Exam data analyzable and linked to student profiles Exam data analyzable and linked to student profiles Users Users Teachers Teachers Students Students

T Iteration demo 5 Status of the iteration’s goals Goal 1: Getting to know the group and the customer Goal 1: Getting to know the group and the customer OK, several meetings with the customer and the group OK, several meetings with the customer and the group Goal 2: Project planning Goal 2: Project planning OK, project plan written OK, project plan written Goal 3: Decisions on technology and studying the new technologies Goal 3: Decisions on technology and studying the new technologies Decisions: OK Decisions: OK Studying: Postponed Studying: Postponed Goal 4: Designing a draft of the architecture Goal 4: Designing a draft of the architecture OK OK Goal 5: Specifying requirements on general level (including the most important functional requirements and use cases) Goal 5: Specifying requirements on general level (including the most important functional requirements and use cases) OK, the requirement document published and updated a few times already OK, the requirement document published and updated a few times already Use cases found unnecessary for now, because a prototype exists Use cases found unnecessary for now, because a prototype exists Goal 6: Deciding on SEPA topics Goal 6: Deciding on SEPA topics OK OK Meeting practices Meeting practices Code re-factoring Code re-factoring Eclipse metrics plug-in & statistical analysis of code Eclipse metrics plug-in & statistical analysis of code

T Iteration demo 6 Status of the iteration’s deliverables Project plan (excluding quality assurance plan) Project plan (excluding quality assurance plan) OK OK Requirements document Requirements document OK, multiple reviews OK, multiple reviews Progress report (for the iteration demo) Progress report (for the iteration demo) OK OK

T Iteration demo 7 Realization of the tasks (1/2)

T Iteration demo 8 Realization of the tasks (2/2) Work types a bit overlapping Work types a bit overlapping Unclear definitions for work types within the group (time-tracking) Unclear definitions for work types within the group (time-tracking) Major differences Major differences See the table above (MAN, DES, STU) See the table above (MAN, DES, STU) Postponed tasks Postponed tasks Developing use cases Developing use cases Presenting a draft of the architecture to the customer Presenting a draft of the architecture to the customer Unplanned tasks Unplanned tasks QA planning & documenting QA planning & documenting

T Iteration demo 9 Resource usage The developers used less time than estimated The developers used less time than estimated Realized 13h on average (est. 23h) Realized 13h on average (est. 23h) SE-experts spent more time than estimated SE-experts spent more time than estimated Realized 50h on average (est. 44h) Realized 50h on average (est. 44h)

T Iteration demo 10Risks

T Iteration demo 11 Results of the iteration 1. Project plan 2. Requirements 3. System architecture

T Iteration demo 12 1.Project plan Customer goalsStakeholders Estimated resources

T Iteration demo Requirements

T Iteration demo System architecture (1/3) Java web application (version 1.4) Java web application (version 1.4) Struts framefork (version 1.0) Struts framefork (version 1.0)MVC-architecture For view layer many tab libraries are going to be used HTMLJSPJSTL Struts logic, Struts HTML... MySQL –database management (version 5.0) MySQL –database management (version 5.0)

T Iteration demo System architecture (2/3) Model-View-Controller Model-View-Controller

T Iteration demo System architecture (3/3) Locations... Locations...

T Iteration demo 17 Used work practices 1. Project management 2. Requirements engineering 3. Design

T Iteration demo Project management (1/2) Project planning Project planning Done  Presented in the project plan Done  Presented in the project plan Iteration planning Iteration planning Done for PP; I1 will be done weeks Done for PP; I1 will be done weeks Experience: Difficult, hard to foresee the actual progress, needs reviewing during the iteration Experience: Difficult, hard to foresee the actual progress, needs reviewing during the iteration Communication Communication Planned & implemented Planned & implemented TikiWiki, , messenger, telephone, meetings (SEPA) TikiWiki, , messenger, telephone, meetings (SEPA) Experience: difficult to get people to follow communication protocol Experience: difficult to get people to follow communication protocol Time tracking Time tracking Excel sheet for time-tracking Excel sheet for time-tracking Collected, summarized & published weekly by the project manager Collected, summarized & published weekly by the project manager Experience: Some difficulties with task-relatedness and categorization, needs updating Experience: Some difficulties with task-relatedness and categorization, needs updating

T Iteration demo 19 Documenting Documenting Written by team management Written by team management Reviews expected by all stakeholders; monitored within the group Reviews expected by all stakeholders; monitored within the group Experience: time-consuming Experience: time-consuming Risk management Risk management Initial risks derived from “common” risks Initial risks derived from “common” risks Risk-specific instructions Risk-specific instructions Risks reviewed and updated every 2 weeks Risks reviewed and updated every 2 weeks Iteration demo Iteration demo Process improvement Process improvement Reflection workshops held in the end or iteration Reflection workshops held in the end or iteration reviews all the used practices reviews all the used practices analyses them for improvements analyses them for improvements The processes are constantly monitored and improved (if needed) by the group. The processes are constantly monitored and improved (if needed) by the group. Iterative development Iterative development Planned Planned 1. Project management (1/2)

T Iteration demo Requirements engineering Elicitation and analysis Elicitation and analysis Studying existing prototype (all members) Studying existing prototype (all members) Experience: Effective & fast Experience: Effective & fast Customer meetings (3) and discussion Customer meetings (3) and discussion The entire management team performed on-site and post-meeting analysis The entire management team performed on-site and post-meeting analysis Experience: Effective, but time-consuming Experience: Effective, but time-consuming Validation Validation Done by ing the document to customer Done by ing the document to customer Unclear cases verified in customer meetings, one by one Unclear cases verified in customer meetings, one by one Approval requested by Approval requested by Experience: Tricky, the customer knows what they want, but don’t necessarily link it to the requirements Experience: Tricky, the customer knows what they want, but don’t necessarily link it to the requirements Change management Change management Practice designed, but not yet discussed with customer Practice designed, but not yet discussed with customer Status tracking Status tracking Practice planned Practice planned Plan  implement  test  approved: “Ready” status Plan  implement  test  approved: “Ready” status Regular reviews (once in 2 weeks) Regular reviews (once in 2 weeks)

T Iteration demo Design Non-functional requirements will be Non-functional requirements will be validated using proto types Use-cases will follow functional Use-cases will follow functionalrequirements Use-cases will describe functional view Use-cases will describe functional view and tasks for the developers Version control Version control Unix CVS software will be used Unix CVS software will be used in I1 & I2 Coding convention Coding convention SUN proposed Java coding SUN proposed Java codingconvention