Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Concept acquisition and analysis for requirements specification

Concept acquisition and analysis for requirements specification

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Add to cart
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)
Add to cart

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
Software Engineering Journal — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

© The Institution of Electrical Engineers
Published

Arguably the most critical of all software development activities is that of requirements specification. Contemporary system development methods address this task in the context of a prescriptive approach, which recognises the need for well identified steps within which a developer builds models on the basis of the method's requirements specification language. This paper proposes that this approach needs to be augmented by the use of informal models which assist in the very early steps of the requirements specification process, i.e. during elicitation and analysis of concepts about the application domain. To this end, the paper discusses the use of a knowledge representation formalism, which provides the necessary foundation for capturing and analysing concepts about an application domain, and a prototype system which assists in this process.

Inspec keywords: knowledge representation; software engineering

Other keywords: concept acquisition; concept analysis; informal models; application domain; software development; system development methods; requirements specification; knowledge representation formalism

Subjects: Software engineering techniques; Expert systems and other AI software and techniques

References

    1. 1)
      • Rich, C., Waters, R.C., Reubenstein, H.B.: `Toward a requirements apprentice', 4th int workshop on software specification and design, 1987, Monterey, USA, p. 79–86.
    2. 2)
      • M. Jarke , M. Jeusfeld , T. Rose . Modelling software processes in a knowledge base: the case of information systems. Knowl. Based Syst. , 4 , 197 - 210
    3. 3)
      • Olle, T.W., Sol, H.G., Verrijn-Stuart, A.A.: Proc. ifip wg 8.1 working conf. on comparative review of information systems design methodologies: improving the practice, 5–7 May 1986.
    4. 4)
      • C. Fillmore , E. Bachs , R. Harms . (1968) The case for case, Universals in linguistic theory.
    5. 5)
      • T. Demarco . (1978) , Structured analysis and system specification.
    6. 6)
      • Inference Corporation, Los Angeles, USA, : `ART: Inference ART reference manual', 1987, version 3.0.
    7. 7)
      • Olle, T.W., Sol, H.G., Tully, C.J.: `Information systems design methodologies: a feature analysis', Ifip wg 8.1 cris II, 1983.
    8. 8)
      • Loucopoulos, P., Layzell, P.J., Champion, R.E.M., Gibson, M.: `A Knowledge-based requirements engineering environment', Proc. Conf. on Knowledge Based Software Assistance, 2nd-4th August 1988, Utica, USA, p. 139–154.
    9. 9)
      • Pietri, F.: `ASPIS: a knowledge-based environment for software development', Esprit '87: achievements and impact, 1987, North Holland, p. 375–391.
    10. 10)
      • P. Loucopoulos , R. Champion . A knowledge based approach to requirements engineering using method and domain knowledge. J. Knowl. Based Syst , 179 - 188
    11. 11)
      • Lubars, M.D., Harandi, M.T.: `Knowledge-based software design using design schemas', 9th int conf. on software engineering, 30th March–2nd April 1987, Monterey, USA, p. 253–262.
    12. 12)
      • MacDonald, I.: `Information engineering — an improved automatable methodology for designing data sharing systems', Proc. IFIP wg 8.1 Working Conf. on Comparative Review of Information Systems Design Methodologies: Improving the practice, 5–7 May 1986, The Netherlands, Noordwijkerhout, p. 173–224.
    13. 13)
      • R.C. Waters . The programmer's apprentice: a session with KBEmacs. IEEE Trans. Softw. Eng. , 11 , 1296 - 1320
    14. 14)
      • R. Balzer , T.E. Cheatham , C. Green . Software technology in the 1990s: using a new paradigm. Comput. , 39 - 45
    15. 15)
      • P.J. Layzell , P. Loucopoulos . (1989) , Systems analysis and development.
    16. 16)
      • van Assche, F., Layzell, P.J., Loucopoulos, P., Speltincx, G.: `RUBRIC: A rule based representtion of information system constructs', Proc. 5th annual esprit conf., 14–17 November 1988, Brussels, Belgium, p. 438–452, (North Holland).
    17. 17)
      • B. Adelson , E. Soloway . The role of domain experience in software design. IEEE Trans. Soft. Eng. , 11
    18. 18)
      • J.F. Sowa . (1984) , Conceptual structures: information processing in mind and machine.
    19. 19)
      • Kaiser, G.E., Feiler, P.H.: `An architecture for intelligent assistance in software development', 9th int. conf. on software engineering, 30th March–2nd April 1987, Monterey, USA.
    20. 20)
      • P. Loucopoulos , R.E.M. Champion . Knowledge based support for requirements engineering. J. Inf. Soft. Technol , 3 , 123 - 135
    21. 21)
      • G. Verheijen , J. van Bekkum , T.W. Olle , H.G. Sol , C.J. Tully . (1982) NIAM: an information analysis method, Information systems design methodologies: a comparative review.
    22. 22)
      • R.N. Maddison . (1983) , Information system methodologies.
    23. 23)
      • M. Jackson . (1983) , System development.
    24. 24)
      • Greenspan, S.J.: `Requirements modelling: a knowledge representation approach to software requirements definition', CSRG-155, Technical Report, 1984.
    25. 25)
      • N.P. Vitalari , G.W. Dickson . Problem-solving for effective systems analysis: an experimental exploration. Commun. ACM , 11
    26. 26)
      • Gibson, M., Harthoorn, C.: `The use of JSD', AA-U0010, Analyst Assist internal Report, 1987, UMIST, UK.
    27. 27)
      • Olle, T.W., Sol, H.G., Verrijn-Stuart, A.A.: Ifip wg 8.1 cris 1, 1982.
    28. 28)
      • Fickas, S.: `Automating the analysis process: an example', 4th int. workshop on software specification and design, 1987, Monterey, USA, p. 58–67.
    29. 29)
      • D.T. Ross . Structured analyis: a language for communicating ideas. IEEE Trans. Soft. Eng. , 1 , 16 - 39
    30. 30)
      • Chapin, N.: `Software lifecycle', Infotec conf. on Structured Software Development, 1979.
    31. 31)
      • C. Gane , T. Sarson . (1979) , Structured systems analysis: tools and techniques.
    32. 32)
      • W. Rzepka , Y. Ohno . Requirements engineering environments: software tools for modelling user needs. IEEE Computer , 9 - 12
http://iet.metastore.ingenta.com/content/journals/10.1049/sej.1990.0014
Loading

Related content

content/journals/10.1049/sej.1990.0014
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
Print this page
This is a required field
Please enter a valid email address