Learn More
Software architecture is a core asset for any organization that develops software-intensive systems. Unsuitable architecture can precipitate disaster because the architecture determines the structure of the project. To prevent this, software architecture must be evaluated. The current evaluation methods, however, focus on single product architecture, and(More)
Feature models have been used to support requirements analysis and domain engineering in Software Product Line. By identifying the mapping between feature model and architecture model by capturing the relationships among elements in the models, we can establish the traceability between the two models. The identified traceability can be used to verify(More)
A business process maturity model provides standards and measures to organizations in assessing, defining and improving business processes, thereby guiding them to achieving business goals and values. In this paper, we present a business process maturity model called Value based Process Maturity Model (vPMM) that overcomes the limitations of the existing(More)
Current software engineering practice is focused on value-neutral processes. Value-based architecting, one of value-based software engineering agendas, involves the further consideration of the system objectives associated with different stakeholder values in selecting an optimal architectural alternative. There are several value-based architectural(More)
During the past decade a number of methods and techniques for software product line scoping have been developed. Although their basic goal is the same, when it comes to details it is often hard to see what they have in common, where they differ and what their strengths and weaknesses are. This makes it difficult for the user to decide when and how to use(More)
During software development process, software artifacts are produced. Consistency among these artifacts should be verified to ensure error-free product. In software product line development, consistency becomes more important because commonalities and variabilities increase the complexity of relationship among artifacts. In this paper, we present a formal(More)
Conjoint analysis has received considerable attention as a technique for measuring customer preferences through utility tradeoffs among products and services. This paper shows how the method can be applied to the area of software architecture to analyze architectural tradeoffs among quality attributes. By eliciting customers utilities through conjoint(More)