Ravid A (1999) A method for extracting and stating software requirements that a user interface prototype contains. Thesis, Faculty of Computer Science, Technion, Haifa, Israelftp:// www.cs.technion.ac.il/pub/misc/dberry/alon.ravid/Thesis.doc Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
User's Manual as a Requirements Specification - Berry, Daudjee, Dong, Nelson.. (2001) (Correct)
....is a good representation of CBS requirements. The user s manual describes more than the requirements, i.e. it captures the requirements of the CBS as well as providing the user with step by step instructions of how to use the features of the CBS. This description amounts to a statement of intent [28, 34]. Understanding this intent is critical for the implementers, who may not have access to the specifiers. When the implementers have a question about the meaning of the specification, in the absence of access to the specifiers, knowledge of the intent helps the implementers to figure out the ....
Ravid, A., "A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains," M.Sc. Thesis, Faculty of Computer Science, Technion, Haifa, Israel (March 1999), Available at ftp://www.cs.technion.ac.il/pub/misc/dberry/alon.ravid/Thesis.doc..
Resume - Berry Self-citation (Berry) (Correct)
No context found.
Ravid, A. and Berry, D.M., "A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains," Requirements Engineering, 5, 225--241, 2000 (Published Research Paper) Contributions to Refereed Journals (accepted, but not yet appeared)
A Method for Extracting and Stating Software Requirements that .. - Ravid, Berry (2000) (3 citations) Self-citation (Ravid) (Correct)
....TSG system are presented, both to lend some concreteness to the solution approach and to help convince the reader of the effectiveness of the approach. Space limitations preclude giving all the details of the case study. The reader is referred to the first author s thesis for the missing details [13]. One caveat is in order. We do not advise on what to prototype and what not to prototype. What is prototyped and what is not are the specifier s decisions. This decision is made based on his or her experience in specifying other systems in the same or similar application domains; it is based on ....
....process, especially those of the system users and software maintenance personnel. This portion should be enough for the reader to see how the approach works, to judge whether it is worth applying in other situations, and to carry out the approach on other problems. The first author s thesis [13] gives additional portions of the case study documents for the benefit of those who need more information. Some comments are necessary: 1. Some of the information appears more than once or is expressed in more than one way. Although this duplication appears redundant, it is necessary because it ....
Ravid, A. A method for extracting and stating software requirements that a user interface prototype contains. M.Sc. Thesis, Faculty of Computer Science, Technion, Haifa, Israel, March 1999, Available at ftp://www.cs.technion.ac.il/pub/misc/dberry/alon.ravid/Thesis.doc
Original Article - Berry Daudjee Dong (Correct)
No context found.
Ravid A (1999) A method for extracting and stating software requirements that a user interface prototype contains. Thesis, Faculty of Computer Science, Technion, Haifa, Israelftp:// www.cs.technion.ac.il/pub/misc/dberry/alon.ravid/Thesis.doc
Round-Trip Prototyping Based on Integrated Functional.. - Homrighausen, Six.. (2002) (Correct)
No context found.
Ravid A, Berry DM. A method for extracting and stating software requirements that a user interface prototype contains. Requirements Eng 2000;5(4):225--241
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC