|
|
First International Workshop on Software Factories
Over the past few years, significant progress has been made in a variety of disciplines that build on object orientation, such as component based and model driven development, software architecture, aspect oriented programming, and requirements, process and software product line engineering. While progress in each discipline has occurred relatively independently of progress in others, several initiatives focusing on various synergies between disciplines suggest that understanding how they interrelate is one of the keys to further progress. Despite these advances, however, many open issues remain to be solved. Pragmatic methods and tool support are needed to offer the benefits of cross discipline integration to practitioners, and to support theoretical and methodological efforts to bring them together.
Software Factories is an emerging paradigm for automating software development, integrating advances in multiple disciplines to increase agility, productivity, and predictability across the software life cycle. It differs from other model driven methods through its reliance on domain specific languages and software product line practices, and its emphasis on integrating modeling with patterns, frameworks, testing, refactoring, and other agile, code focused development practices. It differs from other software product line engineering methods through its use of model driven development as a basis for automation, and its emphasis on making software product lines practices more accessible.
As described by the book, Software Factories: Assembling Applications with Patterns, Models, Frameworks and Tools, a Software Factory defines a tailored methodology for a specific system family, defining its life cycle processes, architecture, implementation and deployment topology, using a graph of viewpoints. The factory associates reusable assets with each viewpoint, and delivers them in the context of the viewpoint, eliminating the need to search for applicable assets, and supporting manual and automatic guidance enactment and validation.
The graph of viewpoints, called a schema, relates work done at one level of abstraction, in one part of the system, or in one phase of the life cycle, to work done at other levels, or in other parts and phases. It may be used to fully or partially generate artifacts from others, to keep artifacts synchronized during development, to validate hand developed artifacts, to determine the impact of defects or changes in system requirements, to support progression from requirements to deployment, to organize and apply patterns and other best practices, to capture metadata during system development to support system operation and maintenance, and to provide other forms of guidance and governance.
Software Factories automate the packaging and delivery of artifacts, including models and model driven tools, other types of tools, such as wizards, templates and utilities, development processes, implementation components, such as class libraries, frameworks and services, and other types of assets, such as patterns, style sheets, help files, configuration files, and documentation. Because factories are themselves defined using models, their definitions can be manipulated using tools, for example to compose larger factories from smaller ones, or to customize generic factories to create specialized ones.
[workshop]
17.10.2005
 Download...
 Details...
 Abstract...
|
First International Workshop on Software Factories
|
together with
Jack Greenfield
,
Steve Cook
,
Krzysztof Czarnecki
,
Jeff Gray
,
Michael Stal
,
Gabor Karsai
,
Don Batory
,
Brian Henderson-Sellers
,
Cesar Gonzalez-Perez
Conference:
OOPSLA 2005
|
|
Conferences