Re pository for Mo del D riven D evelopment (ReMoDD)

1. Repository for Model Driven Development (ReMoDD) Robert France, Jim Bieman (Colorado State University), Betty H.C. Cheng (Michigan State University)

2. What is ReMoDD? • ReMoDD will contain artifacts to support MDD research and education • 2006-2007: Prototype development funded by the National Science Foundation (NSF) • 2008: Proposal for full-blown system submitted to NSF in September 2008 • Proposed contents: • Documented MDD case studies. • Examples of “good” and “poor” models. • Modeling exercises suitable for classroom assignments and projects.

3. Perceived ReMoDD Benefits • Sharing of MDD-related research and teaching experiences • Community-based evolution of MDD knowledge • Documented “lessons learned” for stored artifacts • Support for empirical studies of modeling phenomena • Provide modeling experience for student

4. About the NSF CRI Program • CSU/MSU awarded a Computing Research Infrastructure (CRI) planning grant in 2006 to plan development of ReMoDD • CRI • The program funds development of infrastructure that accelerates research in a computing research domain

5. NSF Planning Grant Goals • Establishment of ReMoDD user community • Development of ReMoDD requirements • Prototype ReMoDD interface • Demonstration of ReMoDD use with sample artifacts

6. Planning Activities • Repository Development Workshops at ICSE and MODELS conferences • Collection of initial artifacts • Develop use cases and prototype ReMoDD interface • Identify means to obtain models from industry while protecting proprietary interests • Form and activate ReMoDD Advisory Board

7. Members from industy: Susan Wong, Microsoft. Brian Berenbach, Siemens. Alexander Egyed, Teknowledge. Frank Weil, Heng Software. Pascal Roques, Valtech. Richard Soley, OMG. Clay Williams, IBM. Bran Selic, Malina Software William Milam, Ford Academic Members: Joanne Atlee, U. Waterloo. Don Batory, U. Texas. Jean Bezivin, U. Nantes, France. Lionel Briand, Carleton U., Canada. Doris Carver, Louisiana State U. David Garlan, Carnegie Mellon U. Jeff Gray, U. Alabama Birmingham. Mark Harman, Kings College, UK. Jean-Marc Jezequel, IRISA/INRIA France. Kevin Lano, Kings College, UK. Robin Lutz, Iowa State U. Atif Memon, U. Maryland. Spencer Rugaber, Georgia Tech. Bernhard Rumpe, TU Braunschweig, Germany. Doug Schmodt, Vanderbilt Univ. Perdita Stevens, U. Edinburgh, UK. Steffen Strecker, U. Essen-Dusiberg, Germany Current ReMoDD Advisory Board

8. Advisory Board: Incentives & Expectations • Incentives • Help define vision for ReMODD • Influence and guide the construction of ReMODD • Expectations • Help populate ReMODD • Help attract/engage potential users/contributors • Help evaluate candidate artifacts • Use artifacts (classroom/research and in industry) • Provide feedback • Publicize and promote the use of ReMODD

9. Contributors: Incentives & Expectations • Incentives: • Gain access to ReMODD artifacts • Advance the MDD field • Gain users for their artifacts • Obtain validation for their work • Influence the direction of education/research • Widen the impact of their work • Expectations: • Provide useful artifacts • Serve as peer reviewers of ReMODD artifacts • Publicize and promote the use of ReMODD

10. ReMoDD Challenges • Populating ReMoDD • How can we encourage and obtain industrial artifacts for ReMoDD? • What artifacts should we prioritize in the 1st generation of ReMoDD? • Developing ReMoDD storage infrastructure • How will artifacts be stored? • Accessing artifacts • What user interfaces are needed to support easy access to ReMoDD artifacts? • How can we seamlessly interface with other related repositories? • Managing ReMoDD • What mechanisms are needed to evolve ReMoDD so that it continues to provide useful services to the MDD community?

11. Populating ReMoDD • First generation of ReMODD education-related artifacts/projects • Examples of end-to-end MDD products (business to requirements to design to implementation models) • Examples of good and poor modeling practices • Other educational resources: modeling projects, specialized lecture materials by experts • Sources • Industry: modeling exemplars • Academia: community developed reference models, classroom models, student projects • Industry organizations (e.g., OMG): models used in standards work

12. Population Issues • Legal sharing of artifacts from industry • Non-Disclosure Agreements (tiers of users) • Serve as a broker for a P2P (peer-to-peer exchange) • Broadcast industry needs • Sanitized data • What type of review (i.e., quality control) • Peer reviews • User rating system • How do we determine the providence of the data (e.g., source, metadata)?

13. Storage Infrastructure Issues • What formats should we use to store artifacts? • Free form vs. standard form • XMI/XML, Eclipse formats, pdf, postscript • How do we transform data in one form to another? • Use of Data interchange formats • (Data) Transformers should be published • Need ability to define metadata • Submitters should be allowed to maintain control over the versions available in the repository

14. Accessing ReMoDD • Key elements of interface • Should have a dialogue interface for entering the providence of data • Search/browse capability: • by lifecycle stage • by version history (look at same artifact over time) • by model types (e.g., class, state, sequence, etc.) • by domain-based models (e.g., telecomm., embedded systems, enterprise systems)

15. Managing ReMoDD • How do we create a sustainable resource? • Ensure that it evolves to changing needs of community • Enhance its role as an agent of change in the community • ReMoDD should be community-driven • Community should drive ReMoDD evolution • Provide mechanisms for extending ReMoDD capabilities in a controlled manner • Provide incentives to encourage use and evolution • ReMoDD should be self-regulating

16. Questions/Discussion • If you’re interested in becoming a participant/contributor contact send email with subject header “REMODD” to: • Betty Cheng (chengb@cse.msu.edu) • Robert France (france@cs.colostate.edu)