Status Report

Project: UCMNav Eclipse Plug-in

Iteration: MilestoneTwo

Implementation Status

In a sentence or two briefly describe what can currently be run to demonstrate the system. In other words, what is now available for feedback from the customer and testing within the development team? Attach or include a few sample screen shows to illustrate the progress.

In addition to the resizable rectangle of MilestoneOne which represent components in Use Case Maps, we have added the following elements which all act as nodes (movable, not resizable): start point, end point, empty point and responsibility. We have also started working on paths by creating connections between our nodes. These are simply straight arrows for the moment. Our use case map can be saved and loaded in XMI. We also have Hello World versions of most of our views.

Example data:
Editor Toolbox:

Property Page:

Model Used for the Hello World:

Highlights

List any items of note. Breakthroughs, accomplishments, major decisions, or changes in the project plan. Are you on schedule, ahead of schedule or behind schedule?
  • We have started using EMF for the model aspect of our MVC architecture. It works really well and saved us lots of time.
  • We realized that the initial editor framework was hard to realize but once it is done, it becomes easy to add features to the project.
  • The loading and saving according to the DTD has been downgraded in priority. We will be loading and saving in XMI, which is trivial in EMF. We are still awaiting an initial version of the DTD.
  • Our Hello World throwaway prototype is ahead of schedule. Development has been easier than expected.
  • Our requirements definition is on schedule. We have restrained the scope of our project but have discussed future requirements.
  • Some of our views are still at the mockup level as implementing them in Eclipse is not a priority right now. The main views are used in our prototype but some others are of no use until we have obtained our meta-model.

Risks or Issues List

In the following table, list any risk or issue that needs to be managed that is critical to the success of the project. This could be anything from we need to get good test data from our customer, to how do we ensure the system is usable, to performance is unacceptable. This should be a complete historical list that is kept from the beginning of the project until the end. Status should be one of New, Ongoing, Closed. The resolution column should be filled in if the issue or risk is closed. Normally, I would expect a project to have about 1-5 issues or risks they are managing that are New or Ongoing at any given time. If you have more than that then either you have a project in serious trouble or your criteria for what is 'critical to success' is to loose.
Date Entered Risk or Issue Description Resolution Status
05 Jan 2005 Eclipse is an evolving platform Eclipse/GEF is rapidly evolving and the current version (3.1) has not yet been released as stable. We have decided to settle on version 3.0.1 of all Eclipse tools that we will be using. Closed
05 Jan 2005 New Tools We are using various tools that we don't necessarily have experience with: Ant, BugZilla, CVS, DOORS, Eclipse+GEF+EMF, JUnit, Rational XDE, TWiki, UCMNav See below Closed
05 Jan 2005 Varying schedules Must find way so that all team members can contribute equally, regardless of schedule differences. - Ongoing
05 Jan 2005 Difficult deployment We may have to support different versions of Eclipse, testing different operating systems, distributing the plug-in with and without Eclipse We have decided on supporting only Eclipse/GEF version 3.0.1 and EMF v2.0.1, testing only on Windows XP SP2 and distributing the plug-in without Eclipse. Closed
23 Jan 2005 New version of the DTD We await the new version of the DTD that we will have to support (read/write). UCM Version 0.23 is already on the website Supporting the DTD is no longer in the scope of our project Closed
23 Jan 2005 Requirements We have defined the requirements definition process in which DanielAmyot will have an important role but they have yet to be drafted Requirements have been drafted. Closed
15 Feb 2005 Meta-model We await our meta-model draft for the notation's elements to be used by our tool - Ongoing
15 Feb 2005 Paths We're not sure how paths will be implemented in our system. Must experiment. - Ongoing
15 Feb 2005 Element behaviour We're not sure how we will determine our element's behaviour. We're not sure to what point our meta-model will define this. We want to avoid having to specify this for all elements. - Ongoing

New Tools

  • BugZilla/CVS/Rational tools: Already familiar.
  • TWiki: Passed the critical level, very easy to use.
  • Ant/JUnit: Tested on prototypes, learnt in SEG4511.
  • DOORS: Abandoned in favor of TWiki.
  • UCMNav: We have three experts to help us. We are only replicating the tool's basic functionality.
  • Eclipse+GEF+EMF: Developing Java in Eclipse is a breeze. Developing plug-ins with GEF and EMF requires lots of reading and experimenting. Our hello world prototype has allowed us to feel comfortable with GEF and EMF.

Tasks in Progress or Completed This Iteration:

List the tasks that each member of the project worked on last iteration.

Task Name Description Who Worked on it %complete
Investigate JUnit + Eclipse Write a 1-2 page report on the subject OlivierCliftNoel 100%
Build prototype EMF+GEF Build a simple prototype using EMF and GEF with components and links EtienneTremblay, JordanMcManus 100%
File Manipulation Investigate XML based file manipulations using UCM's DTD and EMF JasonKealey 100%
Build prototype views Define and prototype all the views in the system. Major UI work here. OlivierCliftNoel, JeanPhilippeDaigle 50%
Build prototype views Research standard plugin design for consistency laying out / accessing resources on disk JeanPhilippeDaigle 33%
Define requirements Work with DanielAmyot to define the draft requirements JasonKealey 100%
Define QA process Define QA process OlivierCliftNoel, JasonKealey 25%
MilestoneTwo Example data and scenarios OlivierCliftNoel, JordanMcManus 100%
MilestoneTwo Use case model + functional features JeanPhilippeDaigle 100%
MilestoneTwo Background, non functional features, database schemas and file formats JasonKealey 100%
MilestoneTwo Architecture for MilestoneTwo EtienneTremblay 100%
MilestoneTwo Algorithms JordanMcManus 100%
Ant Develop ant build scripts for existing projects JeanPhilippeDaigle 100%
Document network editor recreation So that others can benefit from the knowledge JordanMcManus 50%
Investigate Requirements We researched many requirements to verify the ease of creation All 100%

Tasks to be worked on next Iteration:

List the tasks that each member of the project is planning on working on this iteration.

Task Name Description Who Will Work on it
Build prototype views Define and prototype all the views in the system. Major UI work here. OlivierCliftNoel, JeanPhilippeDaigle
Define QA process Define QA process OlivierCliftNoel, JasonKealey
Test plan Write the test plan for our different requirements OlivierCliftNoel
Views Implement first version of all views JeanPhilippeDaigle
UI Implementation Define all hooks that must be made for relevant notifications JeanPhilippeDaigle
Define editpart hierarchy So that we can bind paths to components, etc. JordanMcManus
Investigate coding Attempt to code as many features as possible to understand what needs to be done and what can be done very quickly in our prototype. JordanMcManus
Redefine architecture Following lessons learned, redesign the system so that our architecture is sufficiently robust to continue development EtienneTremblay
Refine requirements According to feedback, go to a more granular level for requirements so that our team knows exactly what needs to be implemented. JasonKealey
Research Use Case Maps Need to define a way to express how elements can behave together but first, we need to know what these behaviours are. JasonKealey
Topic revision: r6 - 24 Aug 2005, JasonKealey
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback