Proceedings of 1993 15th International Conference on Software Engineering
DOI: 10.1109/icse.1993.346041
|View full text |Cite
|
Sign up to set email alerts
|

Prototyping in industrial software projects-bridging the gap between theory and practice

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0
2

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(15 citation statements)
references
References 9 publications
0
13
0
2
Order By: Relevance
“…This review has found that it is not possible for some potential users to contribute adequately in development and evaluation of specific medical device technologies, particularly the more complex technologies (57), because they might not possess sufficient technological knowledge and understanding about products based on such technologies (46). This point should act as a warning to manufacturers that they should not expect solutions to complex technical problems from such users concerning medical device technologies, particularly those of a novel nature.…”
Section: Resourcesmentioning
confidence: 99%
See 1 more Smart Citation
“…This review has found that it is not possible for some potential users to contribute adequately in development and evaluation of specific medical device technologies, particularly the more complex technologies (57), because they might not possess sufficient technological knowledge and understanding about products based on such technologies (46). This point should act as a warning to manufacturers that they should not expect solutions to complex technical problems from such users concerning medical device technologies, particularly those of a novel nature.…”
Section: Resourcesmentioning
confidence: 99%
“…This point should act as a warning to manufacturers that they should not expect solutions to complex technical problems from such users concerning medical device technologies, particularly those of a novel nature. However, engagement with such users may be useful for the purpose of identification and clarification of user requirements and experiences, as well as in relation to vital features of the products (46). However, despite the general value of user involvement, it was found that such involvement does not provide any certainty that the products or technologies so developed will be always successful (5;10), or be perfect and function smoothly (18).…”
Section: Resourcesmentioning
confidence: 99%
“…Lichter et al (1994) call a prototype used to initiate a software project a `presentation prototype'. Generally, the purpose of early prototypes is to elicit or validate requirements.…”
Section: When To Prototypementioning
confidence: 99%
“…[OS94]. Evolutionary prototyping has been successfully employed in "real world" projects [LSZ93,NC98].…”
Section: Background and Related Workmentioning
confidence: 99%
“…• the clarification of management and user requirements [LSZ93]; • the ability to uncover missing or previously unknown requirements [Gra91,Dav92]; • the flexibility to meet changing constraints for software systems [NC98,FD89]; • the provision of a method whereby users, management, and developers can communicate about systems [Gra89,Gra91,LSZ93];…”
Section: Introductionmentioning
confidence: 99%