Recording the reasons for design decisions
ICSE '88 Proceedings of the 10th international conference on Software engineering
gIBIS: a hypertext tool for exploratory policy discussion
ACM Transactions on Information Systems (TOIS)
Design rationale: the argument behind the artifact
CHI '89 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Design Rationale Systems: Understanding the Issues
IEEE Expert: Intelligent Systems and Their Applications
ScenIC: A Strategy for Inquiry-Driven Requirements Determination
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Computer
IEEE Software
Building up and Exploiting Architectural Knowledge
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Researching Information Systems and Computing
Researching Information Systems and Computing
A survey of architecture design rationale
Journal of Systems and Software
Problem Oriented Software Engineering: A design-theoretic framework for software engineering
SEFM '07 Proceedings of the Fifth IEEE International Conference on Software Engineering and Formal Methods
Arguing safety with Problem Oriented Software Engineering
HASE '07 Proceedings of the 10th IEEE High Assurance Systems Engineering Symposium
Problem Oriented Software Engineering: Solving the Package Router Control Problem
IEEE Transactions on Software Engineering
Designing an Online Part-Time Master of Philosophy with Problem Oriented Engineering
ICIW '09 Proceedings of the 2009 Fourth International Conference on Internet and Web Applications and Services
Safety process improvement with POSE and alloy
SAFECOMP'07 Proceedings of the 26th international conference on Computer Safety, Reliability, and Security
Hi-index | 0.00 |
Design rationale fills in the gaps between the original requirements of a system and the finished product encompassing decisions, constraints and other information that influenced the outcome. Existing research in Software Engineering corroborates the importance of design rationale to capture knowledge assets, particularly in the context of the global enterprise, with its increased reliance on IT systems, and risk of knowledge loss through staff movement and attrition. Despite this, the practice of design rationale capture is not as extensive as could be expected due to reasons which include time and budget constraints, the lack of standards and tools, and some uncertainty as to its actual added value. In this paper, we address the viability and benefits of capturing design rationale as a by-product of design in the context of a real-world global organisational setting. This was achieved through a study in which an emerging design approach--Problem Oriented Engineering--was applied in the context of a global financial institution to address a critical IT problem as part of its software supplier's client resolution process. The study provides some positive evidence that the approach-guided knowledge capture of key design rationale elements and that it combined well with existing practices within the organisation and even led to improvement to one of their key processes.