Three-dimensional appearance models represent an essential outcome of industrial design practice, facilitating the origination, evaluation and specification of exterior form. As manufacturers face increasing pressure to reduce time scales for new product development, the production of such models using conventional fabrication techniques must be appraised. As a means of economically translating digital geometry into one-off components, rapid prototyping has the potential to contribute towards a reduction in lead times for the production of appearance models. The objective of this research is to propose a methodological approach for the effective integration of rapid prototyping within industrial design practice. The field and practice of industrial design is defined, the technology of rapid prototyping discussed, and their integration proposed through a draft computer-aided industrial design/rapid prototyping (CAID/RP) methodological approach. This is exposed to practitioner feedback, modified, and employed as a revised CAID/RP methodological approach during the industrial design of a nylon line trimmer. The product outcome is used to compare and contrast the production of an appearance model via rapid prototyping, an appearance prototype via rapid prototyping, and an appearance model via conventional fabrication techniques. Two issues arise from the use of the revised CAID/RP methodological approach: the production of stl files and the lack of physical interaction with product form. In addition, the emergence of rapid prototype sketch modelling systems following the line trimmer case study provides an opportunity for further enhancement. A strategy for the resolution of these issues is proposed, and their effectiveness evaluated through additional case studies. The resulting CAID/RP methodological approach is subject to validation through practitioner interviews and a normalised rating/weighting method. The positive feedback acknowledges the significance of the CAID/RP methodological approach through a reduction in product development lead times and enhancement of professional practice. The project makes a contribution to new knowledge and understanding in the area of professional practice through the definition and validation of operational paradigmatic change.

This dissertation focuses on how requirements for a new software development system are elicited and what pitfalls could cause a software development project to fail if the said requirements are not captured correctly. A number of existing requirements elicitation methods, namely: JAD (Joint Application Design), RAD (Rapid Application Development), a Formal Specifications Language (Z), Natural Language, UML (Unified Modelling Language) and Prototyping are covered. The aforementioned techniques are then integrated into existing software development life cycle models, such as the Waterfall model, Rapid Prototyping model, Build and Fix model, Spiral model, Incremental model and the V-Process model. Differences in the domains (knowledge and experience of an environment) of a client and that of the software development team are highlighted and this is done diagrammatically using the language of Venn diagrams. The dissertation also refers to a case study highlighting a number of problems during the requirements elicitation process, amongst other the problem of tacit knowledge not surfacing during elicitation. Two new requirements elicitation methodologies are proposed namely: the SRE (Solitary Requirements Elicitation) and the DDI (Developer Domain Interaction) methodology. These two methods could potentially be more time consuming than other existing requirements elicitation methods, but the benefits could outweigh the cost of their implementation, since the new proposed methods have the potential to further facilitate the successful completion of a software development project. Following the introduction of the new requirements elicitation methods, they are then applied to the aforementioned case study and highlight just how the hidden domain of the client may become more visible, because the software development team has gained a deeper understanding of the client’s working environment. They have therefore increased their understanding of how the final product needs to function in order to fulfil the set out requirements correctly. Towards the end of the dissertation a summary and a conclusion as well as future work that could be undertaken in this area are provided. / Computer Science / M. Sc. (Computer Science)

This dissertation focuses on how requirements for a new software development system are elicited and what pitfalls could cause a software development project to fail if the said requirements are not captured correctly. A number of existing requirements elicitation methods, namely: JAD (Joint Application Design), RAD (Rapid Application Development), a Formal Specifications Language (Z), Natural Language, UML (Unified Modelling Language) and Prototyping are covered. The aforementioned techniques are then integrated into existing software development life cycle models, such as the Waterfall model, Rapid Prototyping model, Build and Fix model, Spiral model, Incremental model and the V-Process model. Differences in the domains (knowledge and experience of an environment) of a client and that of the software development team are highlighted and this is done diagrammatically using the language of Venn diagrams. The dissertation also refers to a case study highlighting a number of problems during the requirements elicitation process, amongst other the problem of tacit knowledge not surfacing during elicitation. Two new requirements elicitation methodologies are proposed namely: the SRE (Solitary Requirements Elicitation) and the DDI (Developer Domain Interaction) methodology. These two methods could potentially be more time consuming than other existing requirements elicitation methods, but the benefits could outweigh the cost of their implementation, since the new proposed methods have the potential to further facilitate the successful completion of a software development project. Following the introduction of the new requirements elicitation methods, they are then applied to the aforementioned case study and highlight just how the hidden domain of the client may become more visible, because the software development team has gained a deeper understanding of the client’s working environment. They have therefore increased their understanding of how the final product needs to function in order to fulfil the set out requirements correctly. Towards the end of the dissertation a summary and a conclusion as well as future work that could be undertaken in this area are provided. / Computer Science / M. Sc. (Computer Science)