| Proposed re-phrasing of the proposal [message #561570] |
Wed, 28 November 2007 15:15 |
 Eric Dillon
Messages: 103
Registered: July 2009 |
Senior Member |
|
|
Hi all,
thanks much for all the feedback.
I have tried to digest all the comments and I think I need to re-phrase the
proposal in a number of areas to address some of your concerns and make it a
bit more "crisp". We are not trying to overlap with any existing project,
nor trying to re-invent the wheel. We certainly don't want to create
confusion in the community.
It seems the proposal was received as being a lot broader than it really is.
In particular, the truth is that our current user community is based in the
Telecom vertical, and that some of the technologies and implementation
choices were certainly driven by this fact (even if the same choices would
be different now based on the availability of some of the existing modeling
sub-projects).
So, as stated in some of the comments, I think it would make sense to
re-center the proposal on the Telecommunications Vertical, state that the
project uses technologies and techniques that are taylored to that industry,
yet that we intend to adopt more of the Modeling components over time and
feedback accordingly.
So I intend to rephrase the proposal as follows. I'm hoping this will clear
all concerns and provide a good base to start working together.
Regards,
Eric
------------------------
1. - in the "Background section",
1.1 - in the 3rd paragraph, rephrase
"...Moreover, generic-purpose UML modeling tools offer UML modeling
environment that is too broad.
With experience it becomes clear that constraining the model with tight
conventions and rules is necessary to control
the quality of the generated code or specification for a specific
industry, technology or domain."
by
"...Moreover, generic-purpose UML modeling tools offer too much flexibility
to non-experienced UML modelers. When working with large distributed teams,
it becomes clear that the modeling tool needs to guide and constrain the
users according to the target domain. This typically goes beyond UML
profiles and require tight naming conventions and validation rules accross a
model to ensure the quality of the generated code or specification, in
particular in the Telecommunications Industry".
1.2. - in the 4th paragraph, rephrase
"Tigerstripe was born two years ago to address this need of a single,
integrated environment dedicated to generic MDD."
by
"Tigerstripe was born two years ago to address this need of a single,
integrated environment dedicated to MDD in the Telecommunications Industry:
in particular, Tigerstripe was first adopted by Telecommunications standard
bodies for Operational and Business Support Systems management interfaces."
2. in the "Scope section", re-phrase the objectives as follows:
- contribute an extensible toolset for Model-Driven Development targeting
the Telecommunications Vertical, with extension points supporting the
generation of application code, APIs, specifications or documentation. The
initial version was built using a combination of existing Eclipse components
and proprietary technology to address the specific needs of this industry.
- integrate additional components of Eclipse projects into the existing
environment to enhance the existing MDD environment or replace proprietary
technologies as appropriate.
- provide an extensible framework, and solicit contributions so that
industry specific models can be developed, maintained and exchanged.
Tigerstripe's initial user community is expected to be in the Telecoms'
industry.
- provide additional tools, samples and ideas that allows integration of
Tigerstripe with other existing environments.
We intend to migrate existing parts of the software to the latest frameworks
supported by the Modeling top-level project. In particular, we intend to use
more of the EMF and UML2 frameworks where applicable to complement the
current technology in use, and allow easier model sharing between users. As
we proceed we will feedback requirements as experienced in our Telecom
industry vertical.
3. in the "Description Section", re-phrase the following:
"UML2 modeling capabilities through a graphical editor for Class Diagrams or
Instance Diagrams"
by
"A subset of UML2 features with Class Diagrams and Instance Diagrams"
|
|
|
Powered by
FUDForum. Page generated in 0.02130 seconds
] 
Search
Help
Register
Login
Home
