This paper uses a descriptive approach to analyzing the problem specification process within requirement engineering. Two ATR (Automatic Target Recognition) experts are requested to produce problem specifications for two given problems. From the protocol data, it is clear that both experts developed their problem specifications by first developing solutions to the problems. Furthermore, incompleteness in the problem specification is manifested in an incomplete solution.


    Access

    Access via TIB

    Check availability in my library


    Export, share and cite



    Title :

    What software engineering can learn from practitioners


    Additional title:

    Was Software Engineering von Praktikern lernen kann?


    Contributors:
    Volovik, D. (author) / Mojdehbakhsh, R. (author) / Tsai, W.T. (author)


    Publication date :

    1990


    Size :

    6 Seiten, 5 Bilder, 13 Quellen


    Type of media :

    Conference paper


    Type of material :

    Print


    Language :

    English




    What System Safety Engineering Can Learn from the Columbia Accident

    Leveson, N.G. / Cutcher-Gershenfeld, J. / System Safety Society (U.S.) | British Library Conference Proceedings | 2006


    What we learn from ethology

    Mori, H. | British Library Online Contents | 1996


    What can we learn from Germany

    Smalley, B.C. | Engineering Index Backfile | 1930


    AUTOMOTIVATION: WHAT WE CAN LEARN FROM CARS

    Abou-Assaad, A. / Holmes, J. | British Library Conference Proceedings | 2020


    AUTOMOTIVATION: WHAT WE CAN LEARN FROM CARS

    Abou-Assaad, A. / Holmes, J. | TIBKAT | 2020