A Graduate's Role in Technology Transfer: From Requirements to Design with UML.
S. Hallinan, J. Paul Gibson
Abstract
S. Hallinan, J. Paul Gibson
Abstract
It is a universal challenge to bridge the gap between academia and industry, and between theory and practice. This challenge is particularly critical in the discipline of software engineering and is often categorised under the umbrella of technology transfer. Experience suggests that one of the least well understood aspects of software development is in the move from requirements to design. We support the view that software designers fail to treat design as a process rather than a product and as a consequence become experts in representing the products using models/languages but fail to master the design process. In contrast, recent developments in academia have shown that design can be more effectively taught using problem based learning techniques. This appears to produce students who better understand design as a process; but how can we ensure that this academic advancement will have a positive impact when these students move out into the real world? In this paper we analyse the role of a recently qualified student1 in facilitating technology transfer in the form of introducing engineers to best practices in using UML to move from requirements to design.
OpenAlex reports 3 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
It is a universal challenge to bridge the gap between academia and industry, and between theory and practice. This challenge is particularly critical in the discipline of software engineering and is often categorised under the umbrella of technology transfer. Experience suggests that one of the least well understood aspects of software development is in the move from requirements to design. We support the view that software designers fail to treat design as a process rather than a product and as a consequence become experts in representing the products using models/languages but fail to master the design process. In contrast, recent developments in academia have shown that design can be more effectively taught using problem based learning techniques. This appears to produce students who better understand design as a process; but how can we ensure that this academic advancement will have a positive impact when these students move out into the real world? In this paper we analyse the role of a recently qualified student1 in facilitating technology transfer in the form of introducing engineers to best practices in using UML to move from requirements to design.
Key concepts: Unified Modeling Language, Computer science, Software engineering, Process (computing), Software requirements, Bridge (graph theory), Requirements engineering, Engineering design process