T Project Review RoadRunners [PP] Iteration

T Project Review 2 Agenda  Project status (5 min)  achieving the goals of the iteration  project metrics  Used work practices (10 min)  Completed work (15 min)  presenting the iteration’s results  Plans for the next iteration (5 min)

T Project Review 3 Status of planned goals of the iteration  Goal 1: Specify the goals of the project from all perspectives  OK  Goal 2: Select and adapt work practices to be used in the project  NOT OK, because all work practices are not needed yet. They are selected but some will adapted during next iterations (for example practices considering coding and testing ).  Goal 3: Get to know the customer and project topic  OK  Goal 4: Make project plan and requirement specification  OK  Goal 5: Select Personal Software Engineering Assingment topics  OK

T Project Review 4 Status of planned deliverables of the iteration  Project Plan  OK, except chapter 6.3 – 6.6 because iteration for use cases to implement are not done yet. This is done during next iterations.  Requirements document  OK in general level. Use cases will be refined next iterations.

T Project Review 5 Realization of the tasks  Meeting (status/mentor)  All group members have not participated all meetings.  Project review and preparation  Hours are reported after project review

T Project Review 6 Working hours by person  Some group member haven’t done all tasks in this iteration yet or haven’t participated all meetings. Realized hours in this iterationPlan in the beginning of this iteration

T Project Review 7 Changes to the project  There is no major changes to the project

T Project Review 8 Risks  Risk management is done by Risk management team. Team members are:  Kirsi Männistö  Reetta Räisänen  Petri Noponen  Jussi Katajala  Identified risks:  Customer requirements are too vague and do not stabilize enough before I1  Distributed development  Java -competence is distributed unevenly  New tools  Timetable  The current situation regarding the risks:  None of risks have been realized yet

T Project Review 9 Work practices  In this phase following practices are used:  Time reporting  Version control  personal SE assignments  Topic selected and presented to the mentor.  Iteration planning  Documenting and document delivery  Project review  Requirements priorization  Requirements management  Use cases

T Project Review 10 Results of the iteration  Project plan  Requirement specification

T Project Review 11 Project plan (1/3)  Background of the project is to:  Develop Roadmapping tool for software development organizations. Project is part of customer's own CORE research project.CORE  Iterations:  Project planning phase  Implementation phase 1  Implementation phase 2  Implementation phase 3  Delivery phase  Project organization:

T Project Review 12  Customers project goals are: GoalVerification criteria 1. UsabilityUser without experience has no difficulties to use this program. 2. Easy to installCustomer can install and start work with the program by using manual. 3. Reliability95 % of all test cases are passed. 4. Functional programProgram fills its expectation and customer is able to demonstrate it further. 5. Program can be in drawing mode and in review mode User can use program for editing and also just for reviewing. 6. Different layers can be defined. User can add, edit and remove layers with Roadmapping tool. 7. Portability of program's outputUser can easily transfer output to the other program (for example to PowerPoint) 8. Analyzing and categorizing of information Items can be grouped together for better categorizing. 9. PerformanceUsing program does not require new equipment or hardware for customer. 10. Possibility to add links to the other documents Link to the other documents can be created and opened. Project plan (2/3)

T Project Review 13 Goals of the project group Deliver valuable tool for Roadmapping in schedule Passing the course with grade 3 or higher Learn more about SW projects Develop communicational skills Test driven implementation (Module testing for critical parts/components) Good design and architecture Easy to use software Learn more about Java  Project group’s goals are: Project plan (3/3)

T Project Review 14 Requirement specification (1/9)  Customer’s wide expectations were gathered during meetings  Documentation from customer and WWW were processed  Customer’s desires were interpreted and iterated to goals and activities  Activities and goals were refined and grouped  Limitation of reality defined the structure of activities and goals  Structure was divided smaller parts as use cases

T Project Review 15 Requirement specification (2/9)  Functional requirements  Categorized according to customer goals  mandatory (must have features)  optional (additional features)  supplementary (adds value)  Categories will be implemented in priority order to product  Functional requirements are modelled using Use cases  Mandatory features will result in a coherent product  Each requirement has a requirement ID

T Project Review 16 Requirement specification (3/9)  Mandatory requirements 1/3

T Project Review 17 Requirement specification (4/9)  Mandatory requirements 2/3

T Project Review 18 Requirement specification (5/9)  Mandatory requirements 3/3

T Project Review 19 Requirement specification (6/9)  Optional requirements

T Project Review 20 Requirement specification (7/9)  Supplementary requirements

T Project Review 21 Requirement specification (8/9)  Properties  Three categories that have significant value to customer  Usability  emphasis on low learning curve  familiar user-interface (windows-like)  Reliability  focus on test first programming  robust  Performance  short response time to user actions

T Project Review 22 Requirement specification (9/9)  Constraints  Standards  MS Windows development platform  Export to MS Powerpoint  Software constraints  Developed using Java  Platform independent solution  XML for persistency  HW constraints  usable with a 1 GHz desktop PC

T Project Review 23 Plan for the next iteration (1/3)  Goals in priority order:  Goal 1: Designing core architecture  Goal 2: Implementing core architecture  Goal 3: Testing core architecture  Goal 4: Implementing user interface  Goal 5: Testing user interface  Goal 6: Writing system test plan document  Deliverables  Updated project plan  Updated requirements document  Technical specification (core architecture)  Test case specifications  Test report  Progress report (slideshow)

T Project Review 24 Plan for the next iteration (2/3)  Risks / uncertainties  Distributed development  Java -competence is distributed unevenly  New tools  Timetable  Planned tasks for next iteration

T Project Review 25 Plan for the next iteration (3/3)  Schedule