Comments for Patterns-Based Engineering

Comment on Patterns, ABD and Styles of Reuse by Asset Customization and Reuse – Balancing Flexility and Complexity « Patterns-Based Engineering

Fri, 12 Aug 2011 21:30:18 +0000

[...] – and assumes that all types of reusable assets are the same. We’ve already talked about different reuse styles – and as expected, this also has an impact on our investment [...]

Comment on Modeling Patterns, Part 2: Modeling Pattern Definitions by Pattern Instance Notation – Another Approach for Modeling Patterns « Patterns-Based Engineering

Fri, 10 Jun 2011 23:29:23 +0000

[...] talked about modeling pattern definitions and instantiations via the use of UML (Part 1, Part 2 and Part 3). These approaches provide information about how we’ve used patterns in creating [...]

Comment on Modeling Patterns, Part 1: What should we model? by Pattern Instance Notation – Another Approach for Modeling Patterns « Patterns-Based Engineering

Fri, 10 Jun 2011 23:29:20 +0000

[...] talked about modeling pattern definitions and instantiations via the use of UML (Part 1, Part 2 and Part 3). These approaches provide information about how we’ve used patterns in [...]

Comment on Modeling Patterns, Part 3: Pattern Instantiations by Pattern Instance Notation – Another Approach for Modeling Patterns « Patterns-Based Engineering

Fri, 10 Jun 2011 23:29:12 +0000

Comment on Pattern Specification vs. Pattern Implementation, which do I choose? by Rui Curado

Rui Curado — Wed, 02 Feb 2011 22:47:05 +0000

I am also a supporter of pattern-based software engineering approaches.

My research on this subject has resulted on the design of ABSE (Atom-Based Software Engineering), a generative model-driven development approach. ABSE uses reusable patterns (a.k.a. “Atoms”) as the basis of its model-driven approach.

ABSE patterns are coupled with metadata, giving them the necessary variability to deal with real-world applications. ABSE Atoms have borrowed concepts from OOP like inheritance and composition, allowing you to create pattern families, and build “patterns of patterns”. Atoms are glued together like Lego to form a model that has a tree-like structure. A code generator “executes” the model to obtain the desired generated artifacts.

ABSE features and benefits to software engineering are explained at http://www.abse.info. A free IDE-like tool that implements ABSE is available too. It’s named AtomWeaver, and you can download and try it at http://www.atomweaver.com .

AtomWeaver is in itself ABSE’s proof of concept: AtomWeaver is developed through an ABSE model.

ABSE is a very simple model-driven methodology and it could be a great way for developers to introduce themselves to this new patterns-based development world with the help of the PBE book.

My personal opinion is that a “reusable pattern” is really an overloaded concept: Reusable patterns, reusable assets, metamodels, they are all similar in nature. All these concepts promote reuse of tried-and-tested code and architectures.

Comment on About by Buidling XML Solutions with Rational Software Architect (RSA) and Rational Application Developer (RDA) « Native XML Database

Sat, 09 Oct 2010 00:22:24 +0000

[...] using Rational Software Architect (RSA) and Rational Application Developer (RDA). The speakers are Lee Ackerman and Jean-Louis Marechaux, two high caliber experts in IBM’s Information Management and [...]

Comment on Pattern Specification vs. Pattern Implementation, which do I choose? by Types of Pattern Implementations « Patterns-Based Engineering

Types of Pattern Implementations « Patterns-Based Engineering — Wed, 22 Sep 2010 21:21:36 +0000

[...] Earlier we discussed the difference between pattern specifications and pattern implementations. In this posting we’ll take a brief look at three types of pattern implementations. In classifying the types of pattern implementations our focus is on the types of artifacts that serve as input and output for the pattern implementation. [...]