56 papers:
SEKE-2014-LiuCB #architecture- Software Architecture Rationale Capture through Intelligent Argumentation (XFL, NC, ECB), pp. 156–161.
QoSA-2013-DurdikR #design pattern #documentation #on the #using- On the appropriate rationale for using design patterns and pattern documentation (ZD, RHR), pp. 107–116.
CIKM-2012-DiriyeWBD #comprehension #predict #web- Leaving so soon?: understanding and predicting web search abandonment rationales (AD, RW, GB, STD), pp. 1025–1034.
SAC-2012-NetoA #analysis #process- Keeping decisions and rationale explicit in business process analysis (MSdSN, RMdA), pp. 1702–1708.
ICSE-2012-RogersGQB #documentation- Exploring techniques for rationale extraction from existing documents (BR, JG, YQ, JEB), pp. 1313–1316.
ECSA-2011-SilvaB #architecture #specification #using- A Model for Specifying Rationale Using an Architecture Description Language (LdS, DB), pp. 319–327.
HCD-2011-LieberF #design #integration #question- Human Systems Integration Design: Which Generalized Rationale? (RL, DF), pp. 101–109.
SIGIR-2011-GuoWZAD #comprehension #predict #why- Why searchers switch: understanding and predicting engine switching rationales (QG, RWW, YZ, BA, STD), pp. 335–344.
SAC-2010-ShahinLK #architecture #design #using #visualisation- Rationale visualization of software architectural design decision using compendium (MS, PL, MRK), pp. 2367–2368.
WICSA-ECSA-2009-Capilla #architecture #design #embedded- Embedded design rationale in software architecture (RC), pp. 305–308.
WICSA-ECSA-2009-CarignanoGL #architecture #design- A model to represent architectural design rationale (MCC, SG, HPL), pp. 301–304.
ICSM-2009-LuciaFGT #design #email #repository- Recovering design rationale from email repositories (ADL, FF, CG, GT), pp. 543–546.
CHI-2009-MentisBHRC #development- Development of decision rationale in complex group decision making (HMM, PMB, BH, MBR, JMC), pp. 1341–1350.
ICEIS-ISAS-2009-FerreiraCAB #modelling #requirements #using- Keeping the Rationale of IS Requirements using Organizational Business Models (JJF, VMC, RMdA, FAB), pp. 292–297.
ECSA-2008-NavarroC #approach #architecture #automation #design #using- Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach (EN, CEC), pp. 114–130.
WICSA-2008-CantoneK #design #documentation #empirical- Value-Based Design Decision Rationale Documentation: Principles and Empirical Feasibility Study (GC, PK), pp. 189–198.
WICSA-2008-CuiSM #architecture #automation #design #synthesis #towards- Towards Automated Solution Synthesis and Rationale Capture in Decision-Centric Architecture Design (XC, YS, HM), pp. 221–230.
ICSM-2008-MalikCTJH #comprehension- Understanding the rationale for updating a function’s comment (HM, IC, HMT, ZMJ, AEH), pp. 167–176.
ICSE-2008-BurgeB #named- SEURAT: integrated rationale management (JEB, DCB), pp. 835–838.
SPLC-2008-KumarBC #identification #variability- Identifying and Exploiting the Similarities between Rationale Management and Variability Management (AKT, BB, OC), pp. 99–108.
CASE-2007-JacksonCM- A Rationale for the use of Optical Mice Chips for Economic and Accurate Vehicle Tracking (JDJ, DWC, JM), pp. 939–944.
HCI-IDU-2007-AtwoodH #design- Redesigning the Rationale for Design Rationale (MEA, JH), pp. 11–19.
HIMI-MTT-2007-LeeL #design #navigation- Integrated Physically Based Manipulation and Decision-Making Tree for Navigation to Support Design Rationale (JHL, TCL), pp. 480–489.
SEKE-2007-MedeirosS #design #representation #reuse- Representing Design Rationale to support Reuse (APdM, DS), p. 332–?.
RE-2007-ThurimellaB #approach #evolution #product line #requirements- Evolution in Product Line Requirements Engineering: A Rationale Management Approach (AKT, BB), pp. 254–257.
CAiSE-2006-HaggmarkA #analysis #logic #principle #why- Why Software Engineers Do Not Keep to the Principle of Separating Business Logic from Display: A Method Rationale Analysis (MH, PJÅ), pp. 399–413.
SEKE-2006-PaivaFF #design #development #representation #requirements- Design Rationale in Academic Software Development: Requirements for a Representation Model (DMBP, APF, RPdMF), pp. 469–472.
WICSA-2005-Sotirovski #architecture- An Architecture and Its Rationale (DMS), pp. 287–288.
WICSA-2005-TangBGH #architecture #bibliography #design #documentation- A Survey of the Use and Documentation of Architecture Design Rationale (AT, MAB, IG, JH), pp. 89–98.
CSEET-2005-DutoitWPBR #education #re-engineering #using- Using Rationale for Software Engineering Education (AHD, TW, BP, LB, JR), pp. 129–136.
SEKE-2005-PaivaF #case study #design #re-engineering- Design Rationale in Software Engineering: A Case Study (DMBP, RPdMF), pp. 342–347.
CAiSE-2004-WistrandK #component- Method Components — Rationale Revealed (KW, FK), pp. 189–201.
ICEIS-v1-2004-KralZ #design #towards- Towards Design Rationales of Software Confederations (JK, MZ), pp. 105–112.
DATE-2003-VachouxGE #design #requirements- SystemC-AMS Requirements, Design Objectives and Rationale (AV, CG, KE), pp. 10388–10395.
ICEIS-v3-2003-AgerfalkW #analysis #concept #development #framework- Systems Development Method Rationale: A Conceptual Framework for Analysis (PJÅ, KW), pp. 185–190.
ICSE-2003-BaniassadMS #design pattern #graph- Design Pattern Rationale Graphs: Linking Design to Source (ELAB, GCM, CS), pp. 352–362.
WICSA-2002-SmolanderP #architecture- Practical Rationale for Describing Software Architecture (KS, TP), pp. 113–125.
CAiSE-2002-SmolanderP #architecture #communication- Describing and Communicating Software Architecture in Practice: Observations on Stakeholders and Rationale (KS, TP), pp. 117–133.
ASE-2001-BurgeB #design #maintenance- Design Rationale for Software Maintenance (JEB, DCB), p. 433.
ASE-1997-WilliamsonH #design #specification- Formally Specifying Engineering Design Rationale (KEW, MH), pp. 317–318.
CSEET-1997-LethbridgeIMG #analysis #re-engineering- An Undergraduate Option in Software Engineering: Analysis and Rationale (TCL, DI, AM, DG), pp. 120–131.
ICSM-2000-Sneed- The rationale for software wrapping (HMS), p. 303.
HPCA-1997-AugustCGH #architecture #branch #predict- Architectural Support for Compiler-Synthesized Dynamic Branch Prediction Strategies: Rationale and Initial Results (DIA, DAC, JCG, WmWH), pp. 84–93.
KBSE-1996-DellenKM #design #modelling #process- Integrating Software Process Models and Design Rationales (BD, KK, FM), p. 14.
CHI-1996-Karsenty #design #documentation #empirical #evaluation- An Empirical Evaluation of Design Rationale Documents (LK), pp. 150–156.
ESEC-1995-MonkSPD #design #evolution- Supporting Design Rationale for System Evolution (SRM, IS, JMP, BD), pp. 307–323.
CHI-1994-CarrollAKDR94b #design #multi- Raison d’Etre: capturing design history and rationale in multimedia narratives (JMC, SRA, JK, MSVD, MBR), pp. 192–197.
INTERCHI-1993-Bellotti #design- Integrating theoreticians’ and practitioners’ perspectives with design rationale (VB), pp. 101–106.
INTERCHI-1993-McKerlieM #design #using- QOC in action (abstract): using design rationale to support design (DM, AM), p. 519.
RE-1993-JohnsonGLFP #requirements- Recording requirements assumptions and rationale (LJ, SJG, JL, GF, CP), pp. 282–285.
TRI-Ada-C-1992-Lodge #ada #benchmark #metric- Benchmarking Ada: A Rationale (MJL), pp. 142–147.
CHI-1991-MacLeanBYM #design- Reaching through analogy: a Design Rationale perspective on roles of analogy (AM, VB, RMY, TPM), pp. 167–172.
ML-1991-GruberBBW #design #information management- Design Rationale Capture as Knowledge Acquisition (TRG, CB, JHB, JW), pp. 3–12.
ICSE-1991-Lee #design- Extending the Potts and Bruns Model for Recording Design Rationale (JL), pp. 114–125.
CSCW-1990-Lee #design #named- SIBYL: A Tool for Managing Group Design Rationale (JL), pp. 79–92.
CHI-1989-MacLeanYM #design- Design rationale: the argument behind the artifact (AM, RMY, TPM), pp. 247–252.