Goal and scenario based domain requirements analysis environment

Department of Computer Science, Sogang University, Shinsu-Dong, Mapo-Gu, Seoul, 121-742, Republic of Korea
Journal of Systems and Software (Impact Factor: 1.35). 07/2006; 79(7):926-938. DOI: 10.1016/j.jss.2005.06.046
Source: DBLP


Identifying and representing domain requirements among products in a product family are crucial activities for a successful software reuse. The domain requirements should be not only identified based on the business goal, which drives marketing plan, product plan, and differences among products, but also represented as familiar notations in order to support developing a particular product in the product family. Thus, our proposal is to identify the domain requirements through goals and scenarios, and represent them as variable use cases for a product family. Especially, for identification of the domain requirements, we propose four abstraction levels of requirements in a product family, and goal and scenario modeling. For representation of them, variable use case model is suggested, and also the use case transfer rules are proposed so as to bridge the gap between the identification and representation activity. The paper illustrates the application of the approach within a supporting tool using the HIS (Home Integration System) example.

Download full-text


Available from: Minseong Kim,
  • Source
    • "Even though there are other methods for producing a domain model, we decided to customize our own model and process because none of them directly applies to the meshing tool domain. Some of them are general and need tailoring [2] [20] [21], others are domain specific and need adapting [22], and yet others are product oriented and need to rely on having many products already developed [23]. In this paper, we propose and formalize a domain model definition specially suited for meshing tools, as well as a rigorous process for building this model with the purpose of serving as a basis for rapidly building particular meshing tools within the SPL. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Meshing tools are highly complex software for generating and managing geometrical discretizations. Due to their complexity, they have generally been developed by end users --physicists, forest engineers, mechanical engineers -- with ad hoc methodologies and not by applying well established software engineering practices. Different meshing tools have been developed over the years, making them a good application domain for Software Product Lines (SPL). This paper proposes building a domain model that captures the different domain characteristics such as features, goals, scenarios and a lexicon, and the relationships among them. The model is partly specified using a formal language. The domain model captures product commonalities and variabilities as well as the particular characteristics of different SPL products. The paper presents a rigorous process for building the domain model, where specific roles, activities and artifacts are identified. This process also clearly establishes consistency and completeness conditions. The usefulness of the model and the process are validated by using them to generate a software product line of Tree Stem Deformation (TSD) meshing tools. We also present Meshing Tool Generator, a software that follows the SPL approach for generating meshing tools belonging to the TSD SPL. We show how an end user can easily generate three different TSD meshing tools using Meshing Tool Generator.
    Advances in Engineering Software 04/2014; 70:77-89. DOI:10.1016/j.advengsoft.2014.01.011 · 1.40 Impact Factor
  • Source
    • "Context-aware application design is actually scenario-based in many researches. Scenarios are stories about the system work, in particular the interaction between system and the user[19] [20] [21] [22] [23]. Scenario-based methods are usually used in system design and system evaluation. "
    [Show abstract] [Hide abstract]
    ABSTRACT: With the remarkable increase of mobile worker, it is important to provide support for them to work more efficiently and conveniently in mobile environment. Compared with stationary office workers, the requirements of support for mobile workers are quite different. Mobile work support should be proactive and pervasive. This requires that the support system should be inherently context-aware. However, despite of technological possibility, context-aware support for mobile-worker is still in its infancy. Lack of unified and systematic method for the logic design of the context-aware support model is one of the problems. This paper proposes a scenario-based approach to construct context-aware support model. We firstly define a formal context-aware support model based on colored petri net, and then propose a scenario-based method which can be used in logic design phase. The method focuses on dealing with different scenarios, in particular consistency checking and model synthesis. A support model in hull painting and deck maintenance, which are two activities in ship repair, are designed according to this method.
    International Journal of Advancements in Computing Technology 01/2012; 4(1). DOI:10.4156/ijact.vol4.issue1.60
  • Source
    • ") No No No Yes No Software Hadad et al., (2009) No No Yes Yes No Software Santos et al., (2010) No No Yes Yes No Software Martinez and Cechich (2005 and 2007) No No Yes Yes No Software Park et al., (2004) and Kim et al., (2004, 2006a and 2006b) No No No Yes No Software Kavakli and Loucopoulos (1999, 2002 and 2003) No No No Yes No Software Giorgini et al., (2003) No No No Yes Yes Software Cooper et al., (2005 and 2006) No No No Yes No Software Estrada et al., (2003) and Martinez et al., (2006) No No No Yes No Software "
    [Show abstract] [Hide abstract]
    ABSTRACT: One of the first items which should be identified in resolving a problem or need is an objective in the various fields of knowledge as it enables determining which results must be achieved. Objectives are the starting point in identifying goals, processes, tasks and the people in charge; moreover, activities defined to fulfil their follow-up are based on a set of proposed objectives and enable evaluating results. This article shows how objectives can be defined and used in various fields, especially in software engineering, and depicts the flaws found.
    Ingenieria e Investigación 01/2012; 32(2):63-67. · 0.19 Impact Factor
Show more