Proceedings of the ACM 1980 Annual Conference on - ACM 80 1980
DOI: 10.1145/800176.809990
|View full text |Cite
|
Sign up to set email alerts
|

Structured requirements definition in the 80s

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0

Year Published

1985
1985
2022
2022

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 10 publications
(5 citation statements)
references
References 2 publications
0
3
0
Order By: Relevance
“…Boar's prototyping model [59] was utilized in this study to understand the users of a product in the shortest time. Through the constructed prototype, the users' responses were repeatedly evaluated, with their feedback serving as the basis for the designer to modify the product.…”
Section: Prototype Developmentmentioning
confidence: 99%
“…Boar's prototyping model [59] was utilized in this study to understand the users of a product in the shortest time. Through the constructed prototype, the users' responses were repeatedly evaluated, with their feedback serving as the basis for the designer to modify the product.…”
Section: Prototype Developmentmentioning
confidence: 99%
“…Developers then take the feedback and make corresponding changes in the design. This process is repeated until the users agree that the prototype is satisfactory (Arthur, 1992;Boar, 1984).…”
Section: Bps For the Systems Design Phasementioning
confidence: 99%
“…Many system design or programming methods, e.g., those of Jackson (Jackson, 1975), Parnas (Parnas, 1972), Booch (Booch, 1986), Myers (Myers, 1979), Orr (Orr, 1977;Orr, 1981), etc., start from an assumed clear statement of requirements and show how to arrive at a design of a program meeting those requirements. However, none of these methods really explain how these requirements are obtained in the first place.…”
Section: The Problemmentioning
confidence: 99%