where are we?
DESCRIPTION
Where are we?. Milestones. Reqirements changed. Input systems must now have the same structure Module instances shall not be explicitly chosen for the new system Less dependencies between operations H istory tree different. Project model decided. More solutions available - PowerPoint PPT PresentationTRANSCRIPT
Where are we?Activity w45 w46 w47 w48 w49 w50 w51 w52 w1 w2 w3
Project preparations
Project Plan
Requirements analysis & definition
Eclipse preparation
Plugin
EMF
GEF
XSD
System design
Plugin
Model
GUI
Implementation
Plugin
Model
GUI
Editor
Acceptans Test Plan
Testing
Deployment
Delivery
Milestones
Finished week Forecast Id
Milestone Description
Responsible Dept./Initials Plan
Week +/- Actual
Metr.
M001 Project description (document) 46 46 0 46 0 M002 Requirements definition (document) 47 49 +2 50 +3 M003 Project design draft (document) 49 49 0 49 0 M004 Project design (document) 50 50 0 M005 Acceptance test plan (document) 51 51 0 M006 Final delivery (software) 3 3 0 M007 Final project report (document) 3 3 0
Reqirements changed
Input systems must now have the same structure
Module instances shall not be explicitly chosen for the new system
Less dependencies between operations
History tree different
Project model decided
More solutions available
The best solution was the merge
UML specification
Solution
SolutionUsing Merlin eclipse plugin
Generates code using EMF & GEF
Big job: adjusting genreated MCV architecture to fit our system
Half-automated build
XSD specification of the core system
Coding started
Merlin Generator• free Eclipse plugin• connection between EMF and GEF (models
and graphics)• code generation• advanced model transformation tools• why to use it: increased productivity, saved
time
ProblemsCode adjustment
Custom properties windows
History drawing
XSD representation of entire system is hard
Once generated code is hard to reshape for different model.