Object-oriented software engineering
Object-oriented software engineering
“Open” software design: a case study
Educational Technology
Challenging Universal Truths of Requirements Engineering
IEEE Software
Scenario-based design: envisioning work and technology in system development
Scenario-based design: envisioning work and technology in system development
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Proceedings of the IFIP TC8/WG8.1 Working Conference on Information System Concepts: Improving the Understanding
Requirements Models in Context
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Comicboarding: using comics as proxies for participatory design with children
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Interactive Storyboard: Animated Story Creation on Touch Interfaces
AMT '09 Proceedings of the 5th International Conference on Active Media Technology
Teaching Requirements Engineering to the Baháí Students in Iran who are Denied of Higher Education
REET '09 Proceedings of the 2009 Fourth International Workshop on Requirements Engineering Education and Training
Hi-index | 0.00 |
Tools and techniques for requirements elicitation are generally unsuitable for use with children and for innovative and futuristic developments. Using case studies, this paper explores practical methods to get requirements for future technologies from children. Techniques such as scenurio building, roleplaying and storyboarding proved successful in involving children in the requirements process and stimulating innovation. The paper looks at how these methods can be adopted to take a more fundamental approach to requirements elicitation for adults.These techniques help requirements engineers face the difficult task of getting system requirements from users of whatever age, ability or background. They also enable requirements engineers to anticipate some of the future changes that might occur before or as a consequence of the installation of a new system. The lack of specialist notation was found to promote communication throughout the analysis and design process and gives the designers a context in which to design.