A Requirements Analyst ' s Apprentice : A Proposal
نویسنده
چکیده
The Requirements Analyst's APprentice (RAAP) partially automates the modeling process involved in creating a software requirement. It uses knowledge of the specific domain and general experience regarding software requirements to guide decisions made in the construction of a requirement. RAAP assists the analyst by maintaining consistency, detecting redundancy of description, and analyzing completeness relative to a known body of requirements experience. RAAP is a tool to be used by an analyst in his dealings with the customer. It helps him translate the customer's informal ideas into a requirements knowledge base. RAAP will have the ability to present its internal representation of the requirement in document form. Document-based requirements analysis is the state of the art. A computer-based, knowledge-based analysis system can provide improvement in quality, efficiency and maintainability over document-based requirements analysis and thus advance the state of the art towards automatic programming. RAAP takes a new approach to automating software development by concentrating on the modeling process involved in system construction (as opposed to the model translation process). By supporting the intelligent creation of perspicuous models, it is hoped that flaws will become self revealing and the quality of software can be improved. Assistance is proved for the creation of "correct" models and for the analysis of the implications of modeling decisions. Artificial Intelligence Laboratory Papers are produced for internal circulation, and may contain information that is, for example, too preliminary or too detailed for formal publication. It is not intended that they should be considered papers to which reference can be made in the literature. Copyright (c) 1986 Howard Reubenstein
منابع مشابه
Panel 4A: Apprentice - VTS edition: Season 3
The main objective of this active “panel” is to increase technical interaction among attendees. Team leaders listed below will recruit participants to their team. Each team will try to clearly articulate the problems and come up with ways to solve this problem in the form of new business proposal. The teams will present their findings and business proposals in front of judges later during the c...
متن کاملAnalysis of the Reliability of a Three-Component System with Two Repairmen
In this paper authors have considered a system having three units A, B1 and B2. A is controlled by a controller and B1 and B2 are independent. Two repairmen are involved in repair of the system. One of the repairmen (the first) is the foreman (boss) and the other an assistant (apprentice). Whenever any unit fails, repair is undertaken by boss. If the boss is busy in repairing and at the same ti...
متن کاملUnderstanding Analyst Effectiveness in Requirements Elicitation: A Gestalt Fit Perspective
Analyst effectiveness has been viewed as a critical success factor for information systems development (ISD) projects, especially for the requirements elicitation phase. Prior literature on “analyst effectiveness” has primarily focused on examining (and understanding) the specific set of capabilities an analyst needs to possess in order to be effective. We argue that such an assumption may not ...
متن کاملPanel 12C: Apprentice - VTS edition judging session
This is the judging session for the Panel 4A: Apprentice – VTS edition. The main objective of this active “panel” is to increase technical interaction among attendees. Team leaders listed below will recruit participants to their team. Each team will try to clearly articulate the problems and come up with ways to solve this problem in the form of new business proposal. The teams will present the...
متن کاملA Proposal to Elicit Usability Requirements within a Model-Driven Development Environment
Nowadays there are sound Model-Driven Development (MDD) methods that deal with functional requirements, but in general, usability is not considered from the early stages of the development. Analysts that work with MDD implement usability features manually once the code has been generated. This manual implementation contradicts the MDD paradigm and it may involve much rework. This paper proposes...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2008