Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jean-Jacques Dubray on Jul 27, 2010
Hugo Bruneliere, Jordi Cabot, Frédéric Jouault from the AtlanMod Research Team and Frederic Madiot from MIA Software recently published a short introduction on the MoDisco project, a generic and extensible open source reverse engineering solution. They explain:
Almost all companies are facing the problematic of having to manage, maintain or even replace their legacy systems. Many times, the first problem they need to solve is to really understand what are the functionalities, architecture, data, etc of all these often huge legacy applications As a consequence, reverse engineering still remains a major challenge for software engineering today.
The major challenge is to be able to discover and understand the functionalities, architecture, data... of the legacy systems and reverse engineer them into a meaningful representation that can be later on manipulated and re-implemented.
MoDisco intensively uses MDE principles and techniques to improve existing approaches for reverse engineering.
They explain that one of the key issue in reverse engineering is the heterogeneity of legacy systems and one of the key goals of MoDisco is to:
Model Driven Reverse Engineering (MDRE) is about switching from the heterogeneous world of implementation technologies to the homogeneous world of models.
MoDisco is built around two phases: Model Discovery and Model Understanding.
[Model Discovery] consists in obtaining a model that represents a view on the legacy system (or at least parts of it) from its source code, raw data, available documentation, etc. This model provides a uniform representation of the system, which conforms to a given metamodel expressing the chosen viewpoint.
During [the Model Understanding] phase, the content of these models is analyzed and computed , in particular using model transformations, until we obtain the final desired representation/data (i.e. source code, documentation, structured data, etc) of/on the system
MoDisco is an Eclipse open source project which provides an extensible and customizable MDRE framework to develop model-driven tools supporting different reverse engineering scenarios such as legacy migration or modernization, quality assurance, retro-documentation, etc.
Today, MoDisco components include:
MoDisco also provides and uses concrete implementations of Knowledge Discovery Metamodel (KDM) and Software Metrics Metamodel (SMM). It also offers extended technology-specific support for Java reverse engineering (including a full Java metamodel and corresponding discoverer) and XML reverse engineering (for some JEE framework configuration files such as Struts or Hibernate ones).
Getting Started with Stratos - an Open Source Cloud Platform
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
A practical guide to choosing the right agile tools
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
You get better documentation on Modisco than this paper on the Eclipse/Mosdico website :
www.eclipse.org/MoDisco/
and wiki.eclipse.org/MoDisco#Documentation
Well, I wouldn't say better, I would say more complete :-)
As this news post says, the paper is a short introduction to Modisco that, we believe, helps people understand what MoDisco is about. Of course, once you realize that MoDisco can be helpful in your company, then you should go to the official documentation (many parts of it written by the same authors of the paper) to get the full information about the project.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
2 comments
Watch Thread Reply