Software Product Line Engineering (SPLE) is a prominent paradigm for the assembly of a family of products using product line core assets. The modeling of software assets that together form the actual products is critical for achieving the strategic benefits of Software Product Lines (SPLs). We propose a feature-based approach to software asset modeling based on abstractions provided by Domain-Specific Kits (DSKs). This approach involves a software Asset Metamodel (AMM) used to derive Asset Modeling Languages (AMLs) that define reusable software assets in domain-specific terms. The approach also prescribes a roadmap for modeling these software assets in conjunction with the product line reference architecture. Asset capabilities can be modeled using feature diagrams as the external views of the software assets. Internal views can be expressed in terms of Domain-Specific Artifacts (DSAs) with Variability Points (VPs), where the domain-specific artifacts are created using Domain-Specific Kits. This approach produces loosely coupled and highly cohesive software assets that are reusable for multiple product lines. The approach is validated by assessing software asset reuse in two different product lines in the finance domain. We also evaluated the productivity gains in large-scale complex projects, and found that the approach yielded a significant reduction in the total project effort.

Although service-oriented computing holds great promises, it is still not clear when and how the existing systems will exploit this new computational model. The problem is particularly severe for the software having several years of use. This work provides a roadmap for the migration of legacy software to service-oriented computing by means of right levels of abstraction. The key idea is having integration even at the presentation layer, not only at backend layers such as application or data. This requires re-inventing the popular MASHUP technology of Web 2.0 at the enterprise level. Domain- specific-kits and choreography engine concepts that were originally introduced by the software factory automation approach have been reshaped as another enabling technology towards migrating to the service harmonization platform. The paper also exemplifies the proposed approach on a simple case problem.

Architectural modeling identifies several concerns in problem domain and associates them with design decisions in solution domain. There is, however, no commonsense on how to localize problem domain concerns and relate them to the solution domain. This paper proposes a modeling approach to address the architectural concerns in multiple concern spaces both for problem and solution domains, and align them "symmetrically". This approach identifies the problem domain in multiple concern spaces by correlating the "architectural aspects" and "quality attributes". The solution domain is likewise identified in other multiple concern spaces by correlating the "multi-views" and "multi-tiers" of architectures. Symmetric alignment is used here for the correlation between separate concern spaces instead of mapping individual concerns from problem to solution domain. The paper claims that this alignment helps identifying architectural components, connectors and properties in the solution domain.