A client oriented requirements baseline

Traceability, a major issue in software engineering, is seldom present at the initial requirements engineering process. The paper reports a proposal for organizing requirements statements as a model, where change and evolution are taken into consideration. The model uses natural language statements as its basic representation, which helps the communication between clients and software engineers. The model is supported by a customized software system for which a prototype was built and used in an industrial setting.

[1]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[2]  S. M. Deen Fundamentals of Data Base Systems , 1977, Macmillan Computer Science Series.

[3]  M. A Jackson,et al.  System development (Prentice-Hall International series in computer science) , 1983 .

[4]  Stephen M. McMenamin,et al.  Essential systems analysis , 1984 .

[5]  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[6]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[7]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[8]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.