Requirements verification is a set of procedures used to detect errors in requirement specifications. This paper discusses various types of requirement errors and illustrates each error with an example. It also examines several techniques used for requirements verification and the capability of each technique to identify various requirement errors. In addition, it reviews the use of each technique in various requirements analysis approaches and indicates the drawbacks of these techniques. This paper can help systems analysts to be aware of possible errors in requirement specifications and the limitations in requirements verification while using a requirements analysis approach.
Get full access to this article
View all access options for this article.
References
1.
Abdel-HamidT.K. (1988). The economics of software quality: a simulation based case study. MIS Quarterly, 12, 395–411.
2.
AdlerM. (1988). An algebra for data flow diagram process decomposition, IEEE Transactions on Software Engineering, 14, 169–183.
3.
AdrionW.R., BranstadM.A., and CherniavskyJ.C. (1982). Validation, verification, and testing of computer software. Computing Surveys, 14, 159–192.
4.
AlfordM.W. (1977). A requirements engineering methodology for real-time processing requirements. IEEE Transactions on Software Engineering, SE-3, 60–69.
5.
An Introduction to SADT™ (1976). Document 9022–78, Waltham, MA, USA.
6.
AschimF., and MostueB.M. (1982). IFIP WG 8.1 case solved using SYSDOC and SYSTEMATOR, in Information Systems Design Methodologies: A Comparative Review, OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds.). (North-Holland, New York, NY) 15–40.
7.
BellT.E., BixlerD.C., and DyerM.E. (1977). An extendable approach to computer-aided software requirements engineering. IEEE Transactions on Software Engineering, SE-3, 49–59.
8.
BellT.E., and ThayerT.A. (1976). Software requirements: are they really a problem?, in Proceedings of the 2nd International Conference on Software Engineering. (IEEE Computer Society Press, Los Alamitos, CA, USA).
9.
BenyonD., and SkidmoreS. (1987). (eds.). Automating Systems Development. (Plenum, New York, NY).
10.
BlackburnM.R. (1989). Using expert systems to construct formal specifications. IEEE Expert, 4, 62–74.
11.
BluementhalS.C. (1969). Management Information Systems – A Framework for Planning and Development. (Prentice-Hall, Englewood Cliffs, NJ).
12.
BodartF., and PigneurY. (1979). A model and a language for functional specifications and evaluation of information systems dynamics, in Formal Models and Practical Tools for Information Systems Design, SchneiderH.J. (ed) North-Holland, (New York, NY), pp. 257–279.
13.
BodartF., HennebertA.M., LeheureuxJ.M., and PigneurY. (1985). Computer-aided specification, evaluation, and monitoring of information systems, in Proceedings of 1985 International Conference on Information Systems, 27–44.
14.
BoehmB.W. (1977). Software Engineering Techniques, seven basic principles of software engineering, in Infotech state of the art report, Infotech, London.
15.
BoehmB.W. (1984). Validating and verifying software requirements and design specifications. IEEE Software, 1, 75–88.
BorgidaA., GreenspanS., and MylopoulosJ. (1985). Knowledge representation as the basis for requirements specifications. Computer, 18, 82–91.
18.
BriggsR.B. (1966). A mathlematical model for the design of information management systems, MS thesis, Division of Natural Science, University of Pittsburgh, Pittsburg, PA, USA.
19.
BrodieM.L., and SilvaE. (1982). Active and passive component modelling: ACM/PCM in Information Systems Design Methodologies: A Comparative ReviewOlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY). pp. 41–92.
20.
BubenkoJ.A.Jr. (1980). Information modeling in the context of system development, in Information Processing 80, Proceedings of the IFIP Congress, (North-Holland, Amsterdam), pp. 395–411.
21.
BuckleyF.J., and PostonR. (1984). Software quality assurance. IEEE Transactions on Software Engineering, SE-10, 36–41.
22.
CaseA.F.Jr. (1985). Computer-Aided Software Engineering (CASE): technology for improving productivity. Data base, 17, 35–43.
23.
DearnleyP.A., and MayhewP.J. (1983). In favor of system prototypes and their integration into the systems development cycle. The Computer Journal, 26, 36–42.
24.
DeMarcoT. (1979). Structured Analysis and System Specification. (Yourdon Engledwood Cliffs, NJ).
25.
DijkstraE.W. (1972). Notes on structured programming, in Structured Programming, DahlO.J. (eds) (Academic, New York, NY).
26.
DownsE., ClareP., and CoeI. (1988). Structured Systems Analysis and Design Method, (Prentice-Hall, Hertfordshire, UK).
27.
EstrinG., FenchelR.S., RazoukR.R., and VernonM.K. (1986). SARA (System Architects Apprentice): modeling analysis, and simulation support for design of concurrent systems. IEEE Transactions on Software Engineering, SE-12, 293–311.
28.
Ewusi-MensahK. (1984). Identifying subsystems in information systems analysis. Information Systems, 9, 181–190.
29.
FaganM.E. (1976). Design and code inspections to reduce errors in program development. IBM Systems Journal, 15, 182–211.
30.
Federal Information Processing Standard 101. (1983). Guidelines for Life Cycle Validation, Verification, and Testing of Computer Software.National Bureau of Standards, Washington, D.C.
31.
FreedmanD.P., and WeinbergG.M. (1982). Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products. (Little, Brown and Company, Boston, MA).
32.
GaneC., and SarsonT. (1979). Structured Systems Analysis: Tools and Techniques.Prentice-Hall, Englewood Cliffs, NJ.
33.
GustafssonM.R., KarlssonT., and BubenkoJ.A. (1982). A declarative approach to conceptual in information modeling, in Information Systems Design Methodologies: A Comparative Review, OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY) pp. 93–141.
34.
HansenJ.V., McKellL.J., and MeitzerL.E. (1979). ISMS: computer-aided analysis for design of decision support systems. Management Science, 25, 1069–1081.
IBM (1978). Business Systems Planning-Information Systems Planning Guide. Manual GE20-0527-2.
37.
IEEE International Workshop on Timed Petri Nets. (1985). Torino, Italy. IEEE Catalog No. 85CH2 187-3, IEEE Computer Society Press.
38.
IEEE Standard Glossary of Software Engineering Terminology. (1983). IEEE Std. 729–1983, IEEE-CS order No. 729, Los Alamitos, CA: IEEE Computer Society.
39.
JacksonM.A. (1983). System Development, (Prentice-Hall International, London).
40.
JansonM.A., and SmithL.D. (1985). Prototyping for systems development: a critical appraisal. MIS Quarterly, 9, 305–316.
41.
KingW.R., and ClelandD.J. (1975). The design of management information systems, an information analysis approach. Management Science, 22, 286–297.
42.
KnuthE., HalazF., and RadoP. (1982). SDLA: system descriptor and logical analyzer, in Information Systems Design Methodologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY) pp. 143–171.
43.
LangeforsB. (1963). Some approaches to the theory of information systems. BIT, 3, 229–254.
44.
LawD. (1985). Prototyping: a state-of-the-art report, in Proceedings of the 1985 National Computer Conference.
45.
LoucopoulosP., and ChampionR. (1988). Knowledge-based approach to requirements engineering using method and domain knowledge. Knowledge Based Systems, 1, 179–187.
46.
LundebergM. (1982). The ISAC approach to specification of information systems and its application to the organization of an IFIP working conference, in Information Systems Design Methodologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY) pp. 173–234.
47.
MacDonaldI.G., and PalmerL.R. (1982). System development in a shared data environment, in Information Systems Design Methdologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY) pp. 235–283.
48.
MarimontR.B. (1959). A new method of checking the consistency of precedence matrices. Journal of the ACM, 6, 164–171.
49.
MartinJ. (1985). Program Design Which is Provably Correct. (Prentice-Hall, Englewood Cliffs, NJ).
50.
MartinJ., and FinkelsteinC. (1981). Information Engineering. (Savant Research Studies, Lancashire, England).
51.
MayhewP.J., and DearnleyP.A. (1987). An alternative prototyping classification. The Computer Journal, 30, 481–484.
52.
McClureC. (1989). A CASE workshop. BYTE, 14, 246.
53.
MillerE., and HowdenW.E. (eds) (1981). Tutorial: Software Testing and Validation Techniques. IEEE-CS order No. 365, Los Alamitos, CA: IEEE Computer Society.
54.
MiyamotoL, and YehR.T. (1981). A Software Requirements Analysis and Definition Methodology for Business Data Processing, in Proceedings of the 1981 National Computer Conference, pp. 571–581.
55.
NaumannJ.D., and JenkinsA.M. (1982). Prototyping: the new paradigm for systems development. MIS Quarterly, 6, 29–44.
56.
NunamakerJ.F. (1971). A methodology for the design and optimization of information systems, in AFIPS Conference Proceedings, 38, pp. 283–293.
57.
OliveA.R. (1982). DADES: A methodology for specification and design of information systems, in Information Systems Design Methdologies: A Comparative ReviewOlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, New York, NY) pp. 285–333.
58.
OliveA.R. (1983). Information derivability analysis in local information systems. Communications of the ACM, 26, pp. 933–938.
59.
OrrK.T. (1981). Structured Requirements Definition.Ken Orr and Associates, Topeka, KS).
60.
PetersL. (1987). Advanced Structured Analysis and Design. (Prentice-Hall, Englewood Cliffs, NJ). PRIDE, M. Bryce and Associates, Cincinatti, OH.
61.
RamamoorthyC.V., HoS.F., and SoH.H. (1978). The role of software tools in a methodology for the development and validation of critical software for nuclear plants, in Tutorial: Software Methdology.RamamoorthyC.V., and YehR.T. (eds) IEEE Catalog No. EHO 142–0, CA: IEEE Computer Society, pp. 397–415.
62.
RichterG., and DurchholzR. (1982). IML-inscribed high-level Petri Nets, in Information Systems Design Methdologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Holland, New York, NY) pp. 335–368.
63.
RockartJ.F. (1979). Chief executives define their own data needs. Harvard Business Review, 57, 81–93.
64.
RochfieldA., and TardieuH. (1983). MERISE: An information system design and development methodology. Information and Management, 6, 143–159.
65.
RollandC., and RichardC. (1982). The REMORA methodology for information systems design and management, in Information Systems Design Methodologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Hoi land, New York, NY) pp. 369–426.
66.
RomanG-C (1985). A taxonomy of current issues in requirement engineering. Computer, 18, 14–24.
67.
RossD.T. (1977). Structured analysis (SA): a language for communicating ideas. IEEE Transactions on Software Engineering.SE-3, 16–34.
68.
RossD.T. (1985). Applications and extensions of SADT. Computer, 18, 25–34.
69.
RzevskiG., TraffordD.B., and WellsM. (1982). The evolutionary design methodology applied to information systems, in Information Systems Design Methodologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Holland, New York, NY) pp. 427–473.
70.
SakthivelS., and AgarwalR. (1987). Verifying the correctness of information systems using PROLOG interpreted Petri nets, in Proceedings of the 1987 Decision Science Institute Conference, 369–371, Decision Sciences Institute, Atlanta, GA, USA.
71.
SakthivelS., and TanniruM.R. (1988–89). Information system verification and validation during requirements analysis using Petri Nets. Journal of MIS, 33–52.
72.
SalwinA.E. (1977). A Test Case Comparison of URU URA and RSL/REVS. Tech. Report FS-77-161, Fleet Systems Department, The John Hopkins University, Laurel, MD.
73.
SchefferP.A., StoneA.H., and RzepkaW.E. (1985). A case study of SREM. Computer, 18, 47–54.
74.
SchneiderH.J., and WassermanA.I. (1982). (eds). Automated Tools for Information Systems Design. (North-Holland, New York, NY).
75.
ShannonR.E. (1975). Systems Simulation, The Art of Science, (Prentice-Hall, Englewood Cliffs, NJ).
76.
SirbuM., SchoichetS., KuninJ., and HammerM. (1981). OAM: an office analysis methodology. Memo OAM-106, MIT.
77.
SievertG.E., and MizellT.A. (1985). Specification-based software engineering with TAGS. Computer, 18, 56–65.
78.
SolvbergA. (1982). A draft proposal for integrating system specification models, in Information Systems Design Methdologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Holland, New York, NY) pp. 475–535.
79.
StainerH.M. (1976). An Evaluation of PSL/PSA and RSL/REVS, Two Computer Assisted Software Requirements/Specification/Description Tools. Tech. Report FS-76–205, Fleet Systems department, The John Hopkins University, Laurel, MD.
80.
StephensS.A., and TrippL.L. (1978). Requirements expression and verification aid, in Proceedings of the 2rd International Conference on Software Engineering, IEEE Computer Society Press, Los Alamitos, CA, USA, 101–108.
TeichroewD., and HersheyE.A. (1977). PSL/PSA: A computer-aided technique for structured documentation and analysis of information processing systems. IEEE Transactions on Software Engineering, SE-3, 41–48.
VerheijenG.M.A., and VanBekkumJ. (1982). NIAM: an information analysis method, in Information Systems Design Methodologies: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Holland, New York, NY) pp. 537–589.
86.
WallaceD.R. (1985). The validation, verification and testing of software: an enhancement to software maintainability, in 1985 Conference on Software Engineering Proceedings, pp. 69–77. IEEE Computer Society Press, Los Alamitos, CA, USA.
87.
WassermanAT. (1982). The user software engineering methodology: an overview, in Information Systems Design Methdology: A Comparative Review.OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds). (North-Holland, New York, NY) pp. 591–628.
88.
YourdonE. (1977). Structured Walkthroughs. (Yourdon, New York, NY).
89.
YourdonY., and ConstantineL.L. (1979). Structured Design, (Prentice-Hall, Englewood Cliffs, NJ).
90.
ZaveP. (1982). An operational approach to requirements specification for embedded systems, IEEE Transactions on Software Engineering, SE-8, 250–269.
