VALIDATION, VERIFICATION, AND TESTING TECHNIQUES
THROUGHOUT THE LIFE CYCLE OF A SIMULATION STUDY
1994
\n\n
", "tags": [], "relations": {}, "dateAdded": "2011-07-07T20:46:37Z", "dateModified": "2011-07-07T20:46:37Z" } }, { "key": "236BJT69", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/236BJT69", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/236BJT69", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Balci", "parsedDate": "1994", "numChildren": 1 }, "data": { "key": "236BJT69", "version": 1, "itemType": "journalArticle", "title": "Validation, verification, and testing techniques throughout the life cycle of a simulation study", "creators": [ { "creatorType": "author", "firstName": "Osman", "lastName": "Balci" } ], "abstractNote": "", "publicationTitle": "Annals of Operations Research", "publisher": "", "place": "", "date": "12/1994", "volume": "53", "issue": "1", "section": "", "partNumber": "", "partTitle": "", "pages": "121-173", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Ann Oper Res", "DOI": "10.1007/BF02136828", "citationKey": "", "url": "http://www.springerlink.com/content/qg272j760109m330/", "accessDate": "2011-06-06T14:33:53Z", "PMID": "", "PMCID": "", "ISSN": "0254-5330", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "3D3ZF6NC" ], "relations": {}, "dateAdded": "2011-07-07T20:46:37Z", "dateModified": "2011-07-07T20:46:37Z" } }, { "key": "VC5C8N6T", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/VC5C8N6T", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/VC5C8N6T", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "parsedDate": "1997-06-16", "numChildren": 0 }, "data": { "key": "VC5C8N6T", "version": 1, "itemType": "journalArticle", "title": "Tools for formal specification, verification, and validation of\nrequirements", "creators": [], "abstractNote": "Although formal methods for developing computer systems have been available for more than a decade, few have had significant impact in practice. A major barrier to their use is that software developers find formal methods difficult to understand and apply. One exception is a formal method called SCR for specifying computer system requirements which, due to its easy to use tabular notation and its demonstrated scalability, has already achieved some success in industry. Recently a set of software tools, including a specification editor, a consistency checker, a simulator, and a verifier has been developed to support the SCR method. This paper describes recent enhancements to the SCR tools: a new dependency graph browser which displays the dependencies among the variables in the specification, an improved consistency checker which produces detailed feedback about detected errors, and an assertion checker which checks application properties during simulation. To illustrate the tool enhancements, a simple automobile cruise control system is presented and analyzed", "publicationTitle": "", "publisher": "", "place": "", "date": "16-19 Jun 1997", "volume": "", "issue": "", "section": "", "partNumber": "", "partTitle": "", "pages": "35-47", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "", "DOI": "10.1109/CMPASS.1997.613206", "citationKey": "", "url": "", "accessDate": "", "PMID": "", "PMCID": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Automobiles", "type": 1 }, { "tag": "Computational modeling", "type": 1 }, { "tag": "Computer industry", "type": 1 }, { "tag": "Control systems", "type": 1 }, { "tag": "Displays", "type": 1 }, { "tag": "Feedback", "type": 1 }, { "tag": "Formal specifications", "type": 1 }, { "tag": "SCR", "type": 1 }, { "tag": "SCR tools", "type": 1 }, { "tag": "Scalability", "type": 1 }, { "tag": "Thyristors", "type": 1 }, { "tag": "assertion checker", "type": 1 }, { "tag": "consistency checker", "type": 1 }, { "tag": "dependency graph browser", "type": 1 }, { "tag": "formal methods", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "program verification", "type": 1 }, { "tag": "software engineering", "type": 1 }, { "tag": "software tools", "type": 1 }, { "tag": "validation of requirements", "type": 1 }, { "tag": "verification", "type": 1 } ], "collections": [ "3D3ZF6NC" ], "relations": {}, "dateAdded": "2011-07-07T20:46:33Z", "dateModified": "2011-07-07T20:46:33Z" } }, { "key": "FG87DQTD", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/FG87DQTD", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/FG87DQTD", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Balci", "parsedDate": "1995", "numChildren": 0 }, "data": { "key": "FG87DQTD", "version": 1, "itemType": "conferencePaper", "title": "Principles and techniques of simulation validation, verification, and testing", "creators": [ { "creatorType": "author", "firstName": "Osman", "lastName": "Balci" } ], "abstractNote": "Sufficient experience has been gained over the last decade in simulation validation, verification, and testing (VV&T) to establish basic principles about its characteristics. This paper presents 15 principles of simulation VV&T. These principles help the researchers, practitioners and managers better understand what model VV&T is all about. They serve to provide the underpinnings for the VV&T techniques that can be used throughout the life cycle of a simulation study. This paper also surveys current software VV&T techniques and current simulation VV&T techniques. Understanding and applying these principles and employing proper testing techniques throughout the life cycle of a simulation study are key factors in increasing the probability of success in a simulation study.", "proceedingsTitle": "Proceedings of the 27th conference on Winter simulation", "conferenceName": "", "publisher": "IEEE Computer Society", "place": "Washington, DC, USA", "date": "1995", "eventPlace": "", "volume": "", "issue": "", "numberOfVolumes": "", "pages": "147–154", "series": "WSC '95", "seriesNumber": "", "DOI": "http://dx.doi.org/10.1145/224401.224456", "ISBN": "0-7803-3018-8", "citationKey": "", "url": "http://dx.doi.org/10.1145/224401.224456", "accessDate": "2011-06-07T15:25:28Z", "ISSN": "", "archive": "", "archiveLocation": "Arlington, Virginia, United States", "shortTitle": "", "language": "", "libraryCatalog": "ACM Digital Library", "callNumber": "", "rights": "", "extra": "ACM ID: 224456", "tags": [ { "tag": "design", "type": 1 }, { "tag": "design studies", "type": 1 }, { "tag": "life cycle", "type": 1 }, { "tag": "management", "type": 1 }, { "tag": "model validation and analysis", "type": 1 }, { "tag": "verification", "type": 1 } ], "collections": [ "3D3ZF6NC" ], "relations": {}, "dateAdded": "2011-07-07T20:46:22Z", "dateModified": "2011-07-07T20:46:22Z" } }, { "key": "8RZIF7BW", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/8RZIF7BW", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/8RZIF7BW", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "parsedDate": "2004-09-06", "numChildren": 0 }, "data": { "key": "8RZIF7BW", "version": 1, "itemType": "journalArticle", "title": "Goal-oriented requirements animation", "creators": [], "abstractNote": "Requirements engineers need to make sure that the requirements models and specifications they are building do accurately capture what stakeholders really want. Requirements animation has been recognized to be a promising approach to support this. The principle is to simulate an executable version of the requirements model and to visualize the simulation in some form appealing to stakeholders. Most animation tools available to date simulate operational models. Such models in general do not directly reflect the objectives, constraints and assumptions stated declaratively by stakeholders. It is also not possible to focus the animation on particular portions of a complex model relevant to some specific concern. The paper describes a tool aimed at overcoming such limitations by animating goal-oriented requirements models. The tool automatically generates parallel state machines from goal operationalizations, instantiates those machines to specific instances created by users at animation time, executes them from concurrent events input by multiple users, monitors property violations at animation time, and visualizes concurrent simulations in terms of animated scenes in the domain.", "publicationTitle": "", "publisher": "", "place": "", "date": "6-11 Sept. 2004", "volume": "", "issue": "", "section": "", "partNumber": "", "partTitle": "", "pages": "218- 228", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "", "DOI": "10.1109/ICRE.2004.1335679", "citationKey": "", "url": "", "accessDate": "", "PMID": "", "PMCID": "", "ISSN": "1090-705X", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Animation", "type": 1 }, { "tag": "animation tools", "type": 1 }, { "tag": "computer animation", "type": 1 }, { "tag": "concurrent simulations", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "goal operationalizations", "type": 1 }, { "tag": "goal-oriented requirements animation", "type": 1 }, { "tag": "parallel state machines", "type": 1 }, { "tag": "property violation monitoring", "type": 1 }, { "tag": "requirement engineers", "type": 1 }, { "tag": "requirement models", "type": 1 }, { "tag": "requirement specifications", "type": 1 }, { "tag": "simulation visualization", "type": 1 }, { "tag": "software tools", "type": 1 }, { "tag": "systems analysis", "type": 1 }, { "tag": "visual programming", "type": 1 } ], "collections": [ "3D3ZF6NC" ], "relations": {}, "dateAdded": "2011-07-07T20:46:07Z", "dateModified": "2011-07-07T20:46:07Z" } }, { "key": "HP39CTV6", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/HP39CTV6", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/HP39CTV6", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "parsedDate": "1996-06-17", "numChildren": 0 }, "data": { "key": "HP39CTV6", "version": 1, "itemType": "journalArticle", "title": "Feasibility of model checking software requirements: a case study", "creators": [], "abstractNote": "Model checking is an effective technique for verifying properties of a finite specification. A model checker accepts a specification and a property, and it searches the reachable states to determine if the property is a theorem of the specification. Because model checking examines every state of the specification, it is a more thorough validation technique than testing executable specifications. However, some researchers question the feasibility of model checking, because the size of a specifications state-space grows exponentially with respect to the number of variables in the specification. This paper demonstrates the feasibility of symbolically model checking a non-trivial specification: the software requirements of the A-7E aircraft. The A-7E requirements document lists five properties that the designers manually derived from the requirements. Using McMillan's (1992) Symbolic Model Verifier, we were able to verify or find a counterexample to each property in less than 10-15 CPU minutes. In particular, we found that an important safety property did not hold", "publicationTitle": "", "publisher": "", "place": "", "date": "17-21 Jun 1996", "volume": "", "issue": "", "section": "", "partNumber": "", "partTitle": "", "pages": "77-88", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "", "DOI": "10.1109/CMPASS.1996.507877", "citationKey": "", "url": "", "accessDate": "", "PMID": "", "PMCID": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "Feasibility of model checking software requirements", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "10 to 15 min", "type": 1 }, { "tag": "A-7E aircraft", "type": 1 }, { "tag": "Computer aided software engineering", "type": 1 }, { "tag": "Costs", "type": 1 }, { "tag": "Laboratories", "type": 1 }, { "tag": "Software systems", "type": 1 }, { "tag": "State-space methods", "type": 1 }, { "tag": "Switches", "type": 1 }, { "tag": "Symbolic Model Verifier", "type": 1 }, { "tag": "Temperature", "type": 1 }, { "tag": "Thermostats", "type": 1 }, { "tag": "Thyristors", "type": 1 }, { "tag": "Timing", "type": 1 }, { "tag": "aircraft computers", "type": 1 }, { "tag": "case study", "type": 1 }, { "tag": "finite specification properties verification", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "formal verification", "type": 1 }, { "tag": "model checking feasibility", "type": 1 }, { "tag": "reachable states", "type": 1 }, { "tag": "safety", "type": 1 }, { "tag": "safety property", "type": 1 }, { "tag": "software requirements", "type": 1 }, { "tag": "specifications state-space exponential growth", "type": 1 }, { "tag": "symbolically model checking", "type": 1 }, { "tag": "system documentation", "type": 1 }, { "tag": "theorem", "type": 1 }, { "tag": "variables", "type": 1 } ], "collections": [ "3D3ZF6NC" ], "relations": {}, "dateAdded": "2011-07-07T20:46:00Z", "dateModified": "2011-07-07T20:46:00Z" } }, { "key": "45HGG8DM", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/45HGG8DM", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/45HGG8DM", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Kanyaru and Phalp", "parsedDate": "2008", "numChildren": 0 }, "data": { "key": "45HGG8DM", "version": 1, "itemType": "journalArticle", "title": "Validating software requirements with enactable use case descriptions", "creators": [ { "creatorType": "author", "firstName": "John Mathenge", "lastName": "Kanyaru" }, { "creatorType": "author", "firstName": "Keith", "lastName": "Phalp" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "11/2008", "volume": "14", "issue": "1", "section": "", "partNumber": "", "partTitle": "", "pages": "1-14", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Eng", "DOI": "10.1007/s00766-008-0070-8", "citationKey": "", "url": "http://www.springerlink.com/content/y4844455u0660500/", "accessDate": "2011-06-23T15:31:12Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "44UVBRV4", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/44UVBRV4", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/44UVBRV4", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Leite and Freeman", "parsedDate": "1991-12", "numChildren": 0 }, "data": { "key": "44UVBRV4", "version": 1, "itemType": "journalArticle", "title": "Requirements validation through viewpoint resolution", "creators": [ { "creatorType": "author", "firstName": "J. C.S.P", "lastName": "Leite" }, { "creatorType": "author", "firstName": "P. A", "lastName": "Freeman" } ], "abstractNote": "A specific technique-viewpoint resolution-is proposed as a means of providing early validation of the requirements for a complex system, and some initial empirical evidence of the effectiveness of a semi-automated implementation of the technique is provided. The technique is based on the fact that software requirements can and should be elicited from different viewpoints, and that examination of the differences resulting from them can be used as a way of assisting in the early validation of requirements. A language for expressing views from different viewpoints and a set of analogy heuristics for performing a syntactically oriented analysis of views are proposed. This analysis of views is capable of differentiating between missing information and conflicting information, thus providing support for viewpoint resolution", "publicationTitle": "IEEE Transactions on Software Engineering", "publisher": "", "place": "", "date": "Dec 1991", "volume": "17", "issue": "12", "section": "", "partNumber": "", "partTitle": "", "pages": "1253-1269", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "", "DOI": "10.1109/32.106986", "citationKey": "", "url": "", "accessDate": "", "PMID": "", "PMCID": "", "ISSN": "0098-5589", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Airplanes", "type": 1 }, { "tag": "Biomedical engineering", "type": 1 }, { "tag": "Information analysis", "type": 1 }, { "tag": "Knowledge engineering", "type": 1 }, { "tag": "Packaging", "type": 1 }, { "tag": "Patient monitoring", "type": 1 }, { "tag": "Performance analysis", "type": 1 }, { "tag": "Software systems", "type": 1 }, { "tag": "Systems engineering and theory", "type": 1 }, { "tag": "Vacuum systems", "type": 1 }, { "tag": "analogy heuristics", "type": 1 }, { "tag": "software engineering", "type": 1 }, { "tag": "software requirements", "type": 1 }, { "tag": "syntactically oriented analysis of views", "type": 1 }, { "tag": "systems analysis", "type": 1 }, { "tag": "viewpoint resolution", "type": 1 } ], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "5FJSIVC3", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/5FJSIVC3", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/5FJSIVC3", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Melchisedech", "parsedDate": "1998", "numChildren": 0 }, "data": { "key": "5FJSIVC3", "version": 1, "itemType": "journalArticle", "title": "Investigation of requirements documents written in natural language", "creators": [ { "creatorType": "author", "firstName": "Ralf", "lastName": "Melchisedech" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "6/1998", "volume": "3", "issue": "2", "section": "", "partNumber": "", "partTitle": "", "pages": "91-97", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Eng", "DOI": "10.1007/BF02919968", "citationKey": "", "url": "http://www.springerlink.com/content/u6q5710438347647/", "accessDate": "2011-06-23T15:32:10Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "TUXZM9DI", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/TUXZM9DI", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/TUXZM9DI", "type": "text/html" }, "up": { "href": "https://api.zotero.org/groups/47036/items/GWHNXMT4", "type": "application/json" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } } }, "data": { "key": "TUXZM9DI", "version": 1, "parentItem": "GWHNXMT4", "itemType": "attachment", "linkMode": "linked_url", "title": "Amazon.com Link", "accessDate": "2011-06-25T00:04:05Z", "url": "http://www.amazon.com/dp/0471972088", "note": "", "contentType": "text/html", "charset": "", "tags": [], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "IJ2I5KBX", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/IJ2I5KBX", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/IJ2I5KBX", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Some", "parsedDate": "2005-09-29", "numChildren": 0 }, "data": { "key": "IJ2I5KBX", "version": 1, "itemType": "conferencePaper", "title": "Use cases based requirements validation with scenarios", "creators": [ { "creatorType": "author", "firstName": "S. S", "lastName": "Some" } ], "abstractNote": "Use cases are analytical descriptions of how a system should react in interaction with actors. Use cases are appropriate as specification of a system required behavior. A scenario is an example of execution of a system that may be defined with the intention that it should be supported or the intention that it should be avoided. As such, scenarios are appropriate for requirements validation. This paper presents an approach where use cases and scenarios are used to complement each other for requirements engineering. Use cases define what a system should do, and scenarios are used to validate use cases.", "proceedingsTitle": "13th IEEE International Conference on Requirements Engineering, 2005. Proceedings", "conferenceName": "13th IEEE International Conference on Requirements Engineering, 2005. Proceedings", "publisher": "IEEE", "place": "", "date": "29 Aug.-2 Sept. 2005", "eventPlace": "", "volume": "", "issue": "", "numberOfVolumes": "", "pages": "465- 466", "series": "", "seriesNumber": "", "DOI": "10.1109/RE.2005.75", "ISBN": "0-7695-2425-7", "citationKey": "", "url": "", "accessDate": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Computer aided software engineering", "type": 1 }, { "tag": "Data security", "type": 1 }, { "tag": "Delay systems", "type": 1 }, { "tag": "Displays", "type": 1 }, { "tag": "Information technology", "type": 1 }, { "tag": "Programming", "type": 1 }, { "tag": "Unified modeling language", "type": 1 }, { "tag": "Voting", "type": 1 }, { "tag": "Web pages", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "formal verification", "type": 1 }, { "tag": "requirements engineering", "type": 1 }, { "tag": "requirements validation", "type": 1 }, { "tag": "safety", "type": 1 }, { "tag": "system specification", "type": 1 }, { "tag": "use cases", "type": 1 } ], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "PX7FFIU2", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/PX7FFIU2", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/PX7FFIU2", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Heymans and Dubois", "parsedDate": "1998", "numChildren": 0 }, "data": { "key": "PX7FFIU2", "version": 1, "itemType": "journalArticle", "title": "Scenario-Based Techniques for Supporting the Elaboration and the Validation of Formal Requirements", "creators": [ { "creatorType": "author", "firstName": "Patrick", "lastName": "Heymans" }, { "creatorType": "author", "firstName": "Eric", "lastName": "Dubois" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "3/1998", "volume": "3", "issue": "3-4", "section": "", "partNumber": "", "partTitle": "", "pages": "202-218", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Engineering", "DOI": "10.1007/s007660050005", "citationKey": "", "url": "http://www.springerlink.com/content/r3k5xe7alqtt44ac/", "accessDate": "2011-06-23T15:31:06Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "U8WTIZ5U", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/U8WTIZ5U", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/U8WTIZ5U", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Nanduri and Rugaber", "parsedDate": "1995-01-03", "numChildren": 0 }, "data": { "key": "U8WTIZ5U", "version": 1, "itemType": "conferencePaper", "title": "Requirements validation via automated natural language parsing", "creators": [ { "creatorType": "author", "firstName": "S.", "lastName": "Nanduri" }, { "creatorType": "author", "firstName": "S.", "lastName": "Rugaber" } ], "abstractNote": "Object oriented analysis (OOA) has become a popular method for analyzing system requirements. Unfortunately however, none of the current versions of OOA have included a validation technique tailored to the object oriented approach. Most, instead, merely recommend document reviews without specifying what kinds of problems to look for. The paper explores the question by applying a natural language parser to a requirements document, extracting candidate objects, methods and associations, composing them into an object model diagram, and then comparing the results to those determined by manual OOA. To do this, we have adapted an automated natural language parser and used it to examine several high level specifications. The results indicate that with a modest amount of effort, our technique can give valuable feedback to the analyst", "proceedingsTitle": "Proceedings of the Twenty-Eighth Hawaii International Conference on System Sciences, 1995", "conferenceName": "Proceedings of the Twenty-Eighth Hawaii International Conference on System Sciences, 1995", "publisher": "IEEE", "place": "", "date": "3-6 Jan 1995", "eventPlace": "", "volume": "3", "issue": "", "numberOfVolumes": "", "pages": "362-368 vol.3", "series": "", "seriesNumber": "", "DOI": "10.1109/HICSS.1995.375617", "ISBN": "0-8186-6940-3", "citationKey": "", "url": "", "accessDate": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Automation", "type": 1 }, { "tag": "Design methodology", "type": 1 }, { "tag": "Documentation", "type": 1 }, { "tag": "Formal specifications", "type": 1 }, { "tag": "Guidelines", "type": 1 }, { "tag": "Natural languages", "type": 1 }, { "tag": "OOA", "type": 1 }, { "tag": "Object detection", "type": 1 }, { "tag": "Object oriented methods", "type": 1 }, { "tag": "Object oriented modeling", "type": 1 }, { "tag": "Robustness", "type": 1 }, { "tag": "automated natural language parser", "type": 1 }, { "tag": "automated natural language parsing", "type": 1 }, { "tag": "candidate objects", "type": 1 }, { "tag": "document reviews", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "formal verification", "type": 1 }, { "tag": "grammars", "type": 1 }, { "tag": "high level specifications", "type": 1 }, { "tag": "object model diagram", "type": 1 }, { "tag": "object oriented analysis", "type": 1 }, { "tag": "object-oriented methods", "type": 1 }, { "tag": "requirements document", "type": 1 }, { "tag": "requirements validation", "type": 1 }, { "tag": "system requirements", "type": 1 }, { "tag": "validation technique", "type": 1 } ], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "M6942BEA", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/M6942BEA", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/M6942BEA", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Yousuf et al.", "parsedDate": "2008-12-23", "numChildren": 0 }, "data": { "key": "M6942BEA", "version": 1, "itemType": "conferencePaper", "title": "Requirements validation techniques in GSD: A survey", "creators": [ { "creatorType": "author", "firstName": "F.", "lastName": "Yousuf" }, { "creatorType": "author", "firstName": "Z.", "lastName": "Zaman" }, { "creatorType": "author", "firstName": "N.", "lastName": "Ikram" } ], "abstractNote": "Global software development (GSD) is an emerging trend of software engineering. Seeking lower cost and accessing global resources pool are the main factors towards globalization of software development. GSD exhibits certain characteristics such as distance, time zone and cross-cultural differences that differentiate global software development from co-located software development. GSD makes many activities of software development difficult so as Requirements validation. Requirements validation can only be performed against the user's intention; thus the user's participation in the validation techniques is paramount. Traditional requirements validation techniques do not fit into issues imposed by GSD because of their inherent characteristics and shortcomings. In essence, they are designed for co-located development. This paper examines the existing requirements validation techniques, describes the issues in GSD, and evaluates them as well. The results show that some of the existing requirement validation techniques require extensive informal communication that is not convenient in GSD while other techniques which can be applied effectively in GSD are not very mature yet.", "proceedingsTitle": "Multitopic Conference, 2008. INMIC 2008. IEEE International", "conferenceName": "Multitopic Conference, 2008. INMIC 2008. IEEE International", "publisher": "IEEE", "place": "", "date": "23-24 Dec. 2008", "eventPlace": "", "volume": "", "issue": "", "numberOfVolumes": "", "pages": "553-557", "series": "", "seriesNumber": "", "DOI": "10.1109/INMIC.2008.4777800", "ISBN": "978-1-4244-2823-6", "citationKey": "", "url": "", "accessDate": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "Requirements validation techniques in GSD", "language": "English", "libraryCatalog": "IEEE Xplore", "callNumber": "", "rights": "", "extra": "", "tags": [ { "tag": "Animation", "type": 1 }, { "tag": "Computer science", "type": 1 }, { "tag": "Context", "type": 1 }, { "tag": "Costs", "type": 1 }, { "tag": "Cultural differences", "type": 1 }, { "tag": "DP industry", "type": 1 }, { "tag": "Global software development", "type": 1 }, { "tag": "Globalization", "type": 1 }, { "tag": "Programming", "type": 1 }, { "tag": "Prototypes", "type": 1 }, { "tag": "Requirements validation techniques", "type": 1 }, { "tag": "cross-cultural differences", "type": 1 }, { "tag": "formal specification", "type": 1 }, { "tag": "formal verification", "type": 1 }, { "tag": "global resources pool", "type": 1 }, { "tag": "globalisation", "type": 1 }, { "tag": "requirements validation", "type": 1 }, { "tag": "software development management", "type": 1 }, { "tag": "software engineering", "type": 1 }, { "tag": "software houses", "type": 1 }, { "tag": "software prototyping", "type": 1 }, { "tag": "systems analysis", "type": 1 }, { "tag": "time zone", "type": 1 } ], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "XUMZ448M", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/XUMZ448M", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/XUMZ448M", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Katasonov and Sakkinen", "parsedDate": "2005", "numChildren": 0 }, "data": { "key": "XUMZ448M", "version": 1, "itemType": "journalArticle", "title": "Requirements quality control: a unifying framework", "creators": [ { "creatorType": "author", "firstName": "Artem", "lastName": "Katasonov" }, { "creatorType": "author", "firstName": "Markku", "lastName": "Sakkinen" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "10/2005", "volume": "11", "issue": "1", "section": "", "partNumber": "", "partTitle": "", "pages": "42-57", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Eng", "DOI": "10.1007/s00766-005-0018-1", "citationKey": "", "url": "http://www.springerlink.com/content/yh0t524823548040/", "accessDate": "2011-06-25T00:01:41Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "Requirements quality control", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "GWHNXMT4", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/GWHNXMT4", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/GWHNXMT4", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Kotonya and Sommerville", "parsedDate": "1998-08-25", "numChildren": 1 }, "data": { "key": "GWHNXMT4", "version": 1, "itemType": "book", "title": "Requirements Engineering: Processes and Techniques", "creators": [ { "creatorType": "author", "firstName": "Gerald", "lastName": "Kotonya" }, { "creatorType": "author", "firstName": "Ian", "lastName": "Sommerville" } ], "abstractNote": "", "series": "", "seriesNumber": "", "volume": "", "numberOfVolumes": "", "edition": "1", "date": "1998-08-25", "publisher": "Wiley", "place": "", "originalDate": "", "originalPublisher": "", "originalPlace": "", "format": "", "numPages": "", "ISBN": "0471972088", "DOI": "", "citationKey": "", "url": "", "accessDate": "", "ISSN": "", "archive": "", "archiveLocation": "", "shortTitle": "Requirements Engineering", "language": "", "libraryCatalog": "Amazon.com", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "Z82GCP8P", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/Z82GCP8P", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/Z82GCP8P", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Uchitel et al.", "parsedDate": "2005", "numChildren": 0 }, "data": { "key": "Z82GCP8P", "version": 1, "itemType": "journalArticle", "title": "Goal and scenario validation: a fluent combination", "creators": [ { "creatorType": "author", "firstName": "Sebastian", "lastName": "Uchitel" }, { "creatorType": "author", "firstName": "Robert", "lastName": "Chatley" }, { "creatorType": "author", "firstName": "Jeff", "lastName": "Kramer" }, { "creatorType": "author", "firstName": "Jeff", "lastName": "Magee" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "12/2005", "volume": "11", "issue": "2", "section": "", "partNumber": "", "partTitle": "", "pages": "123-137", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Eng", "DOI": "10.1007/s00766-005-0024-3", "citationKey": "", "url": "http://www.springerlink.com/content/7w1lw56x38123041/", "accessDate": "2011-06-23T15:31:19Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "Goal and scenario validation", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "WC89N3RU", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/WC89N3RU", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/WC89N3RU", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Gemino", "parsedDate": "2003", "numChildren": 0 }, "data": { "key": "WC89N3RU", "version": 1, "itemType": "journalArticle", "title": "Empirical comparisons of animation and narration in requirements validation", "creators": [ { "creatorType": "author", "firstName": "Andrew", "lastName": "Gemino" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "11/2003", "volume": "9", "issue": "3", "section": "", "partNumber": "", "partTitle": "", "pages": "", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Eng", "DOI": "10.1007/s00766-003-0182-0", "citationKey": "", "url": "http://www.springerlink.com/content/0586a29wd7amr6vy/", "accessDate": "2011-06-23T15:31:15Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "RKSR328E", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/RKSR328E", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/RKSR328E", "type": "text/html" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "creatorSummary": "Halling et al.", "parsedDate": "2003", "numChildren": 0 }, "data": { "key": "RKSR328E", "version": 1, "itemType": "journalArticle", "title": "An economic approach for improving requirements negotiation models with inspection", "creators": [ { "creatorType": "author", "firstName": "Michael", "lastName": "Halling" }, { "creatorType": "author", "firstName": "Stefan", "lastName": "Biffl" }, { "creatorType": "author", "firstName": "Paul", "lastName": "Gr�nbacher" } ], "abstractNote": "", "publicationTitle": "Requirements Engineering", "publisher": "", "place": "", "date": "11/2003", "volume": "8", "issue": "4", "section": "", "partNumber": "", "partTitle": "", "pages": "236-247", "series": "", "seriesTitle": "", "seriesText": "", "journalAbbreviation": "Requirements Engineering", "DOI": "10.1007/s00766-002-0155-8", "citationKey": "", "url": "http://www.springerlink.com/content/cfch920klx387x05/", "accessDate": "2011-06-23T15:32:13Z", "PMID": "", "PMCID": "", "ISSN": "0947-3602", "archive": "", "archiveLocation": "", "shortTitle": "", "language": "", "libraryCatalog": "CrossRef", "callNumber": "", "rights": "", "extra": "", "tags": [], "collections": [ "XEJ55ITC" ], "relations": {}, "dateAdded": "2011-07-07T20:45:44Z", "dateModified": "2011-07-07T20:45:44Z" } }, { "key": "CZSBS9WE", "version": 1, "library": { "type": "group", "id": 47036, "name": "erss_rlagido", "links": { "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido", "type": "text/html" } } }, "links": { "self": { "href": "https://api.zotero.org/groups/47036/items/CZSBS9WE", "type": "application/json" }, "alternate": { "href": "https://www.zotero.org/groups/erss_rlagido/items/CZSBS9WE", "type": "text/html" }, "up": { "href": "https://api.zotero.org/groups/47036/items/FX2PJ8XV", "type": "application/json" } }, "meta": { "createdByUser": { "id": 528517, "username": "rbelchior", "name": "", "links": { "alternate": { "href": "https://www.zotero.org/rbelchior", "type": "text/html" } } }, "numChildren": 0 }, "data": { "key": "CZSBS9WE", "version": 1, "parentItem": "FX2PJ8XV", "itemType": "note", "note": "
Validation, Verification, and Testing of Computer Software , 1982
\n\n
Programming is an exercise in problem
solving. As with any problem-solving activ-
ity, determination of the validity of the
solution is part of the process.
Programs whose malfunction would have
severe consequences justify greater effort
in their validation.
For example, software
used in the control of airplane landings or
directing of substantial money transfers re-
quires higher confidence in its proper func-
tioning than does a car pool locator pro-
gram. For each software project, the vali-
dation requirements, as well as the product
requirements, should be determined and
specified at the initiation of the project.
Project size, uniqueness, criticalness, the
cost of malfunction, and project budget all
influence the validation needs. After the
validation requirements have been clearly
stated, specific techniques for validation,
verification, and testing (VV&T) can and
should be chosen.
Although good quality may be difficult to
define and measure, poor quality is glar-
ingly apparent. For example, software that
is filled with errors or does not work ob-
viously lacks quality. Program testing, by
executing the software using representative
data samples and comparing the actual re-
sults with the expected results, has been
the fundamental technique used to deter-
mine errors. However, testing is difficult,
time consuming, and often inadequate.
Consequently, increased emphasis has been
placed upon ensuring quality through-
out the entire development process, rather
than trying to do so after the process is
finished.
The traditional develop-
ment life cycle confines testing to a stage
immediately prior to operation and main-
tenance. All too often, testing is the only
verification technique used to determine
the adequacy of the software. When verifi-
cation is constrained to a single technique
and confined to the latter stages of devel-
opment, severe consequences can result,
since the later in the life cycle that an error
is found, the higher is the cost of its correc-
tion [INFO79]. Consequently, if lower cost
and higher quality are the goal, verification
should not be isolated to a single stage in
the development process but should be in-
corporated into each phase of development.
The primary reason for early investment in ver-
ification activity is to catch potentially ex-
pensive errors early before the cost of their
correction escalates.
Of the methods discussed, the most successful
have been the disciplined manual tech-
niques, such as walk-throughs, reviews, and
inspections, applied to all stages in the life
cycle. Discovery of errors within
the first stages of development {require-
ments and design) is particularly critical
since the cost of these errors escalates sig-
nificantly if they remain undiscovered until
construction or later. Until the develop-
ment products at the requirements and de-
sign stages become formalized, and hence
amenable to automated analysis, disci-
plined manual techniques will continue to
be the key verification techniques.
One of the reasons for the great success of disciplined
manual techniques is their uniform appli-
cability at requirements, design, and coding
phases. These techniques can be used with-
out massive capital expenditure. However,
to be most effective, they require a serious
commitment and a disciplined application.
Careful planning, clearly stated objectives,
precisely defined techniques, good manage-
ment, organized record keeping, and strong
commitment are critical to successful vali-
dation.
No single technique provides a magic solu-
tion. For this reason, the integration of tools
and techniques and the extension of these
to the entire life cycle is necessary before
adequate validation and verification be-
comes possible.
More-
over, given the increasing cost of software,
both absolutely and as a proportion of total
system cost, and the increasing need for
reliability, it is important that management
apply the needed resources and direction
so that verification and validation can be
effective.
The purpose of “requirements validation and
verification” is to ensure that the requirements are an
acceptable description of the system to be implemented.
Unlike the “requirements analysis task”, that check a
specification against objective well-formedness criteria,
validation is typically a subjective evaluation of the
specification with respect to informally described or
undocumented requirements. Presence of stakeholders
in this task and direct involvement of them to review
the requirements artifacts is highly recommended
\n
The purpose of
requirement validation and verification is to certify that
the elicited requirements are an acceptable description
of the system under development. Validation usually
requires stakeholders to be directly involved in
reviewing the requirements artifacts [19]. Verification
techniques used to prove that the software specification
meets validated requirements of stakeholder.
Techniques such as prototyping, scenario-based
approaches, state diagram, animations [24, 25, 26],
simulation [23], derived invariants [27], model
checking [28, 29, 30], and model satisfiability [31] can
be used for validation and verification task in EUC.
\n
generally end-users rarely have
knowledge about software engineering processes and
transferring such knowledge to end-users usually is
difficult to achieve because most of these techniques
require technical background. (Especially the
techniques related to the tasks such as modeling,
requirements analysis, and validation and verification).
Therefore more effort for improving the RE tasks and
techniques in this context is required.
\n
", "tags": [], "relations": {}, "dateAdded": "2011-07-07T20:45:13Z", "dateModified": "2011-07-07T20:45:13Z" } } ]