Fraunhofer-Institut für Angewandte Informationstechnik FIT

Filters

5
5 3 3
4 1
Reset filters

Settings
Now showing 1 - 5 of 5
  • Publication
    Relating domain model based requirements management and situational method engineering
    ( 2010)
    Schmitz, D.
    ;
    Nissen, H.W.
    ;
    Jarke, M.
    ;
    Rose, T.
    In this paper we revisit our earlier proposed domain model based approach to requirements management from a situational method engineering perspective. The approach has originally been developed dedicatedly for a small- and medium-sized enterprise (SME) in the field of control system development. Broadening the perspective by considering situational method engineering helps to generalize the approach to support any kind of flexible and customer-oriented enterprise that works in highly innovative fields. The investigation has opened up our method for new strategies to make domain model choices and to tailor the requirements-based search for similar projects. Furthermore, the feedback loop that we provide to adapt domain models according to the concrete experiences of an SME within recent projects raises an issue that possibly applies to knowledge management in situational method engineering in general.
  • Publication
    Requirements engineering for control systems
    ( 2010)
    Schmitz, D.
    ;
    Nissen, H.W.
    ;
    Jarke, M.
    ;
    Rose, T.
  • Publication
    Evolution in domain model based requirements engineering for control systems development
    ( 2009)
    Nissen, H.W.
    ;
    Schmitz, D.
    ;
    Jarke, M.
    ;
    Rose, T.
    ;
    Drews, P.
    ;
    Heßeler, F.J.
    ;
    Reke, M.
  • Publication
    Requirements engineering for control systems development in small and medium-sized enterprises
    ( 2008)
    Schmitz, D.
    ;
    Nissen, H.W.
    ;
    Jarke, M.
    ;
    Rose, T.
    ;
    Drews, P.
    ;
    Hesseler, F.J.
    ;
    Reke, M.
    Since nowadays more and more control systems are realised within software on electronic control units, a conceptual integration of control systems engineering and software engineering must be aimed at. Within this work, we build on a recent proposal to use the software requirements formalism i* to enable a combined investigation of control systems' and software requirements. While i*'s modelling means have turned out to be sufficiently expressive, two characteristics of control systems still need to be addressed: firstly, how to incorporate domain knowledge especially about the system to be controlled in the requirements development process and secondly, how to specifically support small and medium-sized companies (SMEs) that are the main driver for innovations in this domain. Due to their innovativeness and flexibility, the SMEs usually follow a project-oriented customer-specific development approach. To be nonetheless cost-effective, especially during the offer development phase, we develop a mechanism and a tool to compare a current requirements model with requirements models of control systems from earlier projects. Altogether this reduces time and increases reliability in regard to the identification of reusable software artefacts.
  • Publication
    Telos: Representing knowledge about control systems?
    ( 2008)
    Schmitz, D.
    ;
    Nissen, H.W.
    ;
    Jarke, M.
    ;
    Rose, T.
    Telos is a formal knowledge representation language designed for the development of information systems. It has been successfully applied in many different software development projects. Although the development of control systems also includes software development, it constitutes a completely different application domain. An in-depth analysis of the development process results in a set of key characteristics of this domain. Based on this set we investigate in this paper whether the features of Telos and its implementation ConceptBase are also valuable to support the development of control systems. We first review the existing application of the Telos-based, agent- and goal-oriented language i* to requirements modelling for control systems. Then we examine carefully each single feature of Telos and ConceptBase regarding the support of the identified key characteristics. This investigation shows that nearly all characteristics are well supported and only very few require further enhancements of Telos and ConceptBase.