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

Requirements engineering with viewpoints

Requirements engineering with viewpoints

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

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

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 requirements engineering process involves a clear understanding of the requirements of the intended system. This includes the services required of the system, the system users, its environment and associated constraints. This process involves the capture, analysis and resolution of many ideas, perspectives and relationships at varying levels of detail. Requirements methods based on global reasoning appear to lack the expressive framework to adequately articulate this distributed requirementsknowledge structure. The paper describes the problems in trying to establish an adequate and stable set of requirements and proposes a viewpoint-oriented requirements definition (VORD) method as a means of tackling some of these problems. This method structures the requirements engineering process using viewpoints associated with sources of requirements. The paper describes VORD in the light of current viewpoint-oriented requirements approaches and shows how it improves on them. A simple example of a bank auto-teller system is used to demonstrate the method.

References

    1. 1)
      • S.M. Easterbrook . Resolving conflicts between domain descriptions with computer-supported negotiation. Knowl. Acquisition , 3 , 255 - 289
    2. 2)
      • Finkelstein, A., Kramer, J., Goedicke, M.: `Viewpoints oriented software specification', 3rd Int. IEEE Computer Society Workshop on Software Engineering and its Applications, 1990, Toulouse, France, p. 337–351.
    3. 3)
      • Mullery, G.P.: `A method for controlled requirements specifications', 4th IEEE Computer Society Int. Conf. on Software Engineering, 1979, Munich, Germany, p. 126–135.
    4. 4)
      • Hagsen, H.L.: `A notion of rule-based software quality engineering', Symp. on Applied Computing, April 1991, Kansas City, USA.
    5. 5)
      • B. Boehm . Industrial software metrics top 10 list. IEEE Softw. , 5 , 84 - 85
    6. 6)
      • D. Ross , K.E. Schoman . Structured analysis for requirements definition. IEEE Trans. , 1 , 6 - 15
    7. 7)
      • G. Kotonya , I. Sommerville . (1993) Framework for integrating functional and non-functional requirements, IEE Int. Workshop on Systems Engineering for Real-Time Applications.
    8. 8)
      • G.C.R. Roman . A taxonomy of current issues in requirements engineering. IEEE Computer , 4 , 14 - 21
    9. 9)
      • D. Hartley , I. Pirbhai . (1987) , Strategies for real-time systems specifications.
    10. 10)
      • A.W. Brown , N.A. Earl , J. McDermid . (1992) , Software engineering environments: automated support for software engineering.
    11. 11)
      • A.M. Davis . (1990) , Software requirements analysis and specification.
    12. 12)
      • Harel, D., Lachover, D., Naamad, A., Pngeli, A., Pouti, M., Sherman, R., Shtultrauring, A.: `STATEMATE: a working environment for development of complex reactive systems', Tenth IEEE Int. IEEE Computer Society Press Conf. on Software Engineering, 1988, Washington, DC, p. 396–406.
    13. 13)
      • Fickas, S., van Lamsweerde, A., Dardenne, : `Goal-directed concept acquisition in requirements elicitation', 6th Int. IEEE Computer Society Press Workshop on Software Specification and Design, 1991, Como Italy, p. 14–21.
    14. 14)
      • J. Rumbaugh , M. Blaha , W. Premerlani , F. Eddy , W. Lorensen . (1991) , Object-oriented modelling and design.
    15. 15)
      • Kotonya, G.: `A viewpoint-oriented method for requirements definition', 1994, PhD Thesis, Lancaster University, UK.
    16. 16)
      • B. Boehm . (1984) , Model and metrics for software management and engineering.
    17. 17)
      • S. Shlaer , S.J. Mellor . (1988) , Object-oriented systems analysis: modelling the world in data.
    18. 18)
      • P. Ward , S. Mellor . (1985) , Structured development for real-time systems.
    19. 19)
      • NORMAN, and DRAPER,: 1986.
    20. 20)
      • Greenspan, S., Feblowitz, M.: `Requirements engineering using the SOS paradigm', RE '93 IEEE Int. IEEE Society Press Requirements Symp. on Requirements Engineering, 1993, San Diego, California, p. 260–263.
    21. 21)
      • : `Serious problems require management attention to avoid wasting additional millions', Report FGMSD-80-4, 1979.
    22. 22)
      • A. Finkelstein , J. Kramer , B. Nuseibeh , M. Goedicke . Viewpoints: a framework for integrating multiple perspectives in system development. Int. J. Softw. Eng. Knowl. Eng. , 10 , 31 - 58
    23. 23)
      • J.C.P. Leite . Viewpoints analysis: a case study. ACM Softw. Eng. Notes , 3 , 111 - 119
    24. 24)
      • I. Sommerville . (1992) , Software engineering.
    25. 25)
      • M. Dorfman , R.H. Thayer . (1991) , Requirements definition guidelines, and examples on system and software requirements engineering.
    26. 26)
      • W. Rzepka . Requirements engineering environment: software tools for modelling user needs. IEEE Computer , 4 , 9 - 12
    27. 27)
      • A. Borglda , S. Greenspan , J. Mylopoulos . Knowledge representation as a basis for requirements specifications. IEEE Comput. , 4 , 71 - 85
http://iet.metastore.ingenta.com/content/journals/10.1049/sej.1996.0002
Loading

Related content

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