skip to main content
10.5555/2821445.2821450acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

Traceability recovery for innovation processes

Published: 16 May 2015 Publication History

Abstract

Nowadays, innovation is a competitive business advantage. In practice, innovation and engineering are two distinct process steps with an information handover in between. Often only design prototypes are handed over that present the overall concept, but justify design decisions only partially. However, engineers require thorough knowledge about design rationales when getting the innovation ready for the market. Therefore, innovation processes need to support traceability to enable the retrieval of design rationales. But, existing approaches for documenting innovation processes rather focus on capturing artifacts than enabling the retrieval of traceability information. Furthermore, existing traceability approaches often cannot be employed, because they rely on structured artifacts.
In this paper, we present a traceability recovery approach for innovation processes that enables traceability for unstructured artifacts as often used in innovation processes by employing recovery modules, which jointly recover traceability information. We demonstrate and evaluate our approach using the innovation methodology of Design Thinking.

References

[1]
T. Brown, Change By Design. HarperCollins Publishers, 2009.
[2]
T. Beyhl and H. Giese, "Connecting Designing and Engineering Activities II," in Design Thinking Research - Building Innovators. Springer, 2015, pp. 211--239.
[3]
T. Beyhl, G. Berg, and H. Giese, "Why Innovation Processes Need to Support Traceability," in Proceedings of 7th International Workshop on Traceability in Emerging Forms of Software Engineering. IEEE, 2013, pp. 1--4.
[4]
O. Gotel and S. Morris, "Out of the Labyrinth: Leveraging Other Disciplines for Requirements Traceability," in Proceedings of 19th International Requirements Engineering Conference. IEEE, 2011, pp. 121--130.
[5]
H. Plattner, C. Meinel, and L. Leifer, Eds., Design Thinking Research - Building Innovators, ser. Understanding Innovation. Springer, 2015.
[6]
C. Meinel and L. Leifer, "Design Thinking Research," in Design Thinking Understand - Improve - Apply, 2011, pp. xiii--xxi.
[7]
J. A. Edelman and L. Leifer, "Qualitative Methods and Metrics for Assessing Wayfinding and Navigation in Engineering Design," in Design Thinking Research - Measuring Performance in Context. Springer, 2012, pp. 151--181.
[8]
K. Pohl, "The Three Dimensions of Requirements Engineering," in Seminal Contributions to Information Systems Engineering. Springer, 2013, pp. 63--80.
[9]
B. Ramesh and M. Jarke, "Toward Reference Models for Requirements Traceability," IEEE Transactions on Software Engineering, vol. 27, no. 1, pp. 58--93, 2001.
[10]
T. Fischer, J. Niere, L. Torunski, and A. Zündorf, "Story Diagrams: A New Graph Rewrite Language Based on the Unified Modeling Language and Java," in Theory and Application of Graph Transformations. Springer, 2000, pp. 296--309.
[11]
M. Wenzel, L. Gericke, R. Gumienny, and C. Meinel, "Creative Collaboration in Real World Settings," in Design Thinking Research - Building Innovation Eco-Systems. Springer, 2014, pp. 115--134.
[12]
W. Ju, A. Ionescu, L. Neeley, and T. Winograd, "Where the wild things work: capturing shared physical design workspaces," in Proceedings of ACM Conference on Computer Supported Cooperative Work 2004. ACM, 2004, pp. 533--541.
[13]
S. Winkler and J. von Pilgrim, "A survey of traceability in requirements engineering and model-driven development," Software & Systems Modeling, vol. 9, no. 4, pp. 529--565, 2009.
[14]
G. Spanoudakis, A. Zisman, E. Pérez-Miñana, and P. Krause, "Rule-based generation of requirements traceability relations," Journal of Systems and Software, vol. 72, no. 2, pp. 105--127, 2003.
[15]
W. Jirapanthong and A. Zisman, "XTraQue: traceability for product line systems," Software & Systems Modeling, vol. 8, no. 1, pp. 117--144, 2009.
[16]
W. Kunz and H. Rittel, Issues as Elements of Information Systems. Institute of Urban and Regional Development, University of California Berkeley, 1970.
[17]
B. Ramesh and V. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering," IEEE Transactions on Software Engineering, vol. 18, no. 6, pp. 498--510, 1992.
[18]
A. Tang, Y. Jin, and J. Han, "A rationale-based architecture model for design traceability and reasoning," Journal of Systems and Software, vol. 80, no. 6, pp. 918--934, 2006.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
SST '15: Proceedings of the 8th International Symposium on Software and Systems Traceability
May 2015
78 pages

Sponsors

Publisher

IEEE Press

Publication History

Published: 16 May 2015

Check for updates

Qualifiers

  • Research-article

Conference

ICSE '15
Sponsor:

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 07 Nov 2024

Other Metrics

Citations

Cited By

View all

View Options

Get Access

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media