T-76.115 Project Review RoadRunners [PP] Iteration 30.10.2003.

T-76.115 Project Review

RoadRunners[PP] Iteration

30.10.2003

2

T-76.115 Project ReviewT-76.115 Project Review

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)

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

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.

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

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 iteration Plan in the beginning of this iteration

Member Real Plan Diffjkatajal 37 50,5 -13,5jpvalima 45 45,5 -0,5kmannist 81 80,5 0,5pnoponen 56 57,5 -1,5rraisane 48,5 61,5 -13stanabe 39 48,5 -9,5tpkoski1 33 45,5 -12,5

Member PP IM1 IM2 IM3 DE Totaljkatajal 50,5 39 43 52 5,5 190jpvalima 45,5 42 42 54 6,5 190kmannist 80,5 31 27 29 22,5 190pnoponen 57,5 36 39 51 6,5 190rraisane 61,5 41 46 36 5,5 190stanabe 48,5 41 39 56 5,5 190tpkoski1 45,5 34 42 59 9,5 190

7


Changes to the project

There is no major changes to the project

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

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

10


Results of the iteration

Project plan

Requirement specification

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. Iterations:

Project planning phase Implementation phase 1 Implementation phase 2 Implementation phase 3 Delivery phase

Project organization:

C em o Tim u c inM en tor

Tero K o joC u s tom erS ob erIT

P etri N op on enA ccou n t M n g r

R eetta R ä isä n enU ser In te rface M n g r

Ju ss i K a ta ja laS ys tem A rch itec t

Ju h a V ä lim ä k iD ocu m en ta tion M n g r

Tom i K osk in enP rog ram m er M n g r

S a ik i Tan ab eP rocess M n g r

K irs i M ä n n is töP ro jec t M an ag er

Jou ko K osk iTech n ica l A d visor

S ob erIT

12


Customers project goals are:

Goal Verification criteria

1. Usability User without experience has no difficulties to use this program.

2. Easy to install Customer can install and start work with the program by using manual.

3. Reliability 95 % of all test cases are passed.

4. Functional program Program 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 output User 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. Performance Using 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)

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)

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

15



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

16



Mandatory requirements 1/3

Roadmapping tool

Viewer

Save roadmap

Open roadmap

Create new roadmap

Edit roadmap

Creator

17




Roadmapping tool

Viewer

Create layer

Remove layer

Edit layer

View layers

Creator

18




Roadmapping tool

Add artifact

Add activity

Remove artifact

Remove activity

Edit artifact

Edit activity

Creator

19



Optional requirements

Roadmapping tool

Change layer order

Creator Adjust timescale

Focus layer

Viewer

20



Supplementary requirements

Roadmapping tool

Add document

Remove document

Create link to documentCreator

Launch document

Export roadmap

Export document

Viewer

21



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

22



Constraints Standards

MS Windows development platform Export to MS Powerpoint

Software constraints Developed using Java 1.4.2 Platform independent solution XML for persistency

HW constraints usable with a 1 GHz desktop PC

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)

24



Risks / uncertainties Distributed development Java -competence is

distributed unevenly New tools Timetable

Planned tasks for next iteration

25



Schedule

T-76.115 Project Review RoadRunners [PP] Iteration 30.10.2003.

Documents

Transcript of T-76.115 Project Review RoadRunners [PP] Iteration 30.10.2003.