13 papers:
ESEC-FSE-2015-ErnstBONG #technical debt- Measure it? Manage it? Ignore it? software practitioners and technical debt (NAE, SB, IO, RLN, IG), pp. 50–60.
RE-2013-NiknafsB #case study #effectiveness #elicitation #generative #idea #industrial #requirements- An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation (AN, DMB), pp. 279–283.
MSR-2011-ParninBM #how #java- Java generics adoption: how new features are introduced, championed, or ignored (CP, CB, ERMH), pp. 3–12.
KR-2010-LarbiKM- A Characterization of Optimality Criteria for Decision Making under Complete Ignorance (RBL, SK, PM).
SEKE-2010-PimentelSC #requirements- Conditions for ignoring failures based on a requirements model (JP, ES, JC), pp. 48–53.
HCI-IDU-2007-HongX #experience #user interface- An Ignored Factor of User Experience: FEEDBACK-QUALITY (JH, JX), pp. 127–132.
HT-2002-HughesC #question- Microsoft smart tags: support, ignore or condemn them? (GVH, LC), pp. 80–81.
CHI-2001-GrayF- Ignoring perfect knowledge in-the-world for imperfect knowledge in-the-head (WDG, WTF), pp. 112–119.
- SEKE-2001-Davis #re-engineering #requirements
- Requirements Triage: The Most Important Part of Software Engineering… and the Most Ignored (AD), p. 275.
SAC-2000-ChenAZ #network- Broadcasting Under Network Ignorance Scenario (XC, HA, SZ), pp. 615–619.
- KR-1994-Woods
- Beyond Ignorance-Based Systems (Abstract) (WAW), p. 646.
PODS-1991-KrishnakumarB #bound- Bounded Ignorance in Replicated Systems (NK, AJB), pp. 63–74.
ICALP-1972-Bohm #question #syntax- Can Syntax Be Ignored during Translation? (CB, MDC), pp. 197–207.
