T-76.115%20Project%20Review

1
T-76.115 Project Review

• RoadRunners
• IM1 Iteration02.12.2003

2
Agenda

• Project status (15 min)
• Planned goals
• Planned deliveries
• Project metrics
• Risks
• Used work practices (5 min)
• Completed work (20 min)
• Test report
• User interface design
• Architecture design
• Plans for the next iteration (5 min)

3
Status of project

• Project is in time
• All planned tasks are started
• No major changes in project group or in
  requirements

4
Status of planned goals of the iteration

• 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

5
Status of planned deliverables of the iteration

• Deliverables
• Updated project plan
• Updated requirements document
• Architecture design
• User interface specifications
• Test case specifications
• Test report
• Test plan
• Progress report (slideshow)

6
Realization of the tasks

• Meetings -18,5
• Only 4 project group meeting
• Everyone didnt participate the customer meetings
• Personal SE practise 10
• Exercise was more extensive than expected.
• Use case User Interface 13,5
• Design and implementation are reported both into
  this task. Part of these hours should be under
  User Interface design -task
• Prepare testing -9, Execute and report tests -9
• This task is also for unit testing. Some modules
  have not been started yet
• Inspection -5
• Project manager was only one who inspeceted
  documents
• User interface design -6,5
• Some of this tasks hours were reported in Use
  case User Interface
• Write/update tech. specs -35
• Hours for this task is reported to the
  Architectural design

7
Working hours by person
Realized hours in this iteration
Plan in the beginning of this iteration

• jkatajal couldnt continue implementation because
  of other module depencies.
• pnoponen was sick long term during phase
• rraisane took some of pnoponens tasks.

Latest plan
8
Software size in Lines of Code (LOC)

• All modules are not needed yet and the
  implementation of these modules is started in
  next phase.

9
Risks

• The current situation regarding the risks
• Timetable risk has been realized
• One of the project member has been sick during
  this phase.
• Risk effect was not high, since task were divided
  to the others group members
• Identified risks
• Customer requirements are too vague and do not
  stabilize enough before I1
• Distributed development
• Java -competence is distributed unevenly
• New tools
• Timetable
• Juha will be away 4 weeks during phase IM3
• Juha has to do those hours in next and last phase
  and the work load will be heavy

10
Work practices

• In this phase following practices are used
• Time reporting
• Version control
• Personal SE assignments
• Test driven development
•  Communication practices
•  Meeting practices
•  Design patterns
•  Documentation practices
•  Configuration management
•  Architectural design
• Iteration planning
• Documenting and document delivery
• Project review
• Use cases
• Risk management
• Coding convention

11
Results of the iteration

• Updated project plan
• Next phase tasks and risks
• Use cases
• Updated requirements document
• Use cases updated
• Architecture design
• User interface specifications
• Test report
• Unit tests done in this phase
• Test plan
• What, when, who and how

12
Test report

• All modules have not been implemented yet. They
  will be implemented and tested in next phase

13
User interface (1/8)

• There have been two customer meetings during
  I1-phase about user interface
• Design aspects
• Tool is easy to use
• Windows -like
• At the moment UI has menus but no functionality

14
User interface (2/8)

• Main view

15
User interface (3/8)

• File-menu

16
User interface (4/8)

• Edit-menu

17
User interface (5/8)

• View-menu

18
User interface (6/8)

• Insert-menu

19
User interface (7/8)

• Tools-menu

20
User interface (8/8)

• Help-menu

21
Software Architecture (1 /13)

• Logical Architecture

22
Sofware Architecture (2/13)

• Package GUI
• MainView
• PresentationView

23
Software Architecture (3/13)

• GUI - MainView

24
Software Architecture (4/13)

• GUI PresentationView

25
Software Architecture (4/13)

• GUI - Menu Structure

26
Software Architecture (5/13)

• Package Controller
• CommandFactory

27
Software Architecture (6/13)

• Controller - Layer and Layers Controllers

28
Software Architecture (7/13)

• Package LayerManager
• RMTLayerManager

29
Software Architecture (8/13)

• Package GraphicLibrary

30
Software Architecture (9/13)

• Package Help
• Written in HTML
• External Browser

31
Software Architecture (10/13)

• Package ExternalDocumentHandler
• Supplementary implementations
• External documents saving and launching
• Copying Roadmap to clipboard
• Exporting Roadmap

32
Software Architecture (11/13)

• Package Storage
• non-volatile storage for a Roadmap
• Stored in XML

33
Software Architecture (12/13)

• Package Engine

34
Software Architecture (13/13)

• Basic sequence diagram - Adding Activity

35
Plan for the next iteration (1/2)

• Goals
• mandatory use cases are implemented
• User manual draft is written
• Peer testing arrangements is done
• Deliverables
• Updated project plan
• Updated requirements document
• Updated technical specification
• Updated test cases
• Test report and test log
• User's manual
• Progress report

36
Plan for the next iteration (2/2)

• Task schedule and dependencies