BibSLEIGH
BibSLEIGH corpus
BibSLEIGH tags
BibSLEIGH bundles
BibSLEIGH people
CC-BY
Open Knowledge
XHTML 1.0 W3C Rec
CSS 2.1 W3C CanRec
email twitter
Used together with:
good (14)
not (13)
softwar (8)
when (8)
much (6)

Stem enough$ (all stems)

61 papers:

SIGMODSIGMOD-2015-RablDFSJ #big data
Just can’t get enough: Synthesizing Big Data (TR, MD, MF, SS, HAJ), pp. 1457–1462.
CHICHI-2015-DeberJFW #how #latency #performance
How Much Faster is Fast Enough?: User Perception of Latency & Latency Improvements in Direct and Indirect Touch (JD, RJ, CF, DW), pp. 1827–1836.
CHICHI-2015-KnavingWFB #comprehension #design #motivation
Flow is Not Enough: Understanding the Needs of Advanced Amateur Runners to Design Motivation Technology (KK, PW, MF, SB), pp. 2013–2022.
ICFPICFP-2014-Winograd-CortH #first-order #how
Settable and non-interfering signal functions for FRP: how a first-order switch is more than enough (DWC, PH), pp. 213–225.
LISPILC-2014-Nunes-Harwitt14a #approach #code generation #evaluation #semantics
Eager Evaluation Isn’t Eager Enough A Transformation Based Approach to Semantics-Directed Code Generation (ANH), p. 79.
CHICHI-2014-HornbaekSBS #human-computer #interactive
Is once enough?: on the extent and content of replications in human-computer interaction (KH, SSS, JABA, JGS), pp. 3523–3532.
CHICHI-2014-PaterNMB #functional
Just awful enough: the functional dysfunction of the something awful forums (JAP, YN, EDM, ASB), pp. 2407–2410.
KDDKDD-2014-PapalexakisFSTMF #algorithm #challenge #multi
Good-enough brain model: challenges, algorithms and discoveries in multi-subject experiments (EEP, AF, NDS, PPT, TMM, CF), pp. 95–104.
ASEASE-2013-VeerappaH #approach #maturity #requirements
Assessing the maturity of requirements through argumentation: A good enough approach (VV, RH), pp. 670–675.
DACDAC-2013-ZhaiBS #parallel #realtime #streaming
Exploiting just-enough parallelism when mapping streaming applications in hard real-time systems (JTZ, MB, TS), p. 8.
DATEDATE-2013-Mitcheson #adaptation #energy #performance #question
Adaptable, high performance energy harvesters: can energy harvesting deliver enough power for automotive electronics? (PDM), p. 482.
CHICHI-2013-JotaNDW #case study #how #latency #performance
How fast is fast enough?: a study of the effects of latency in direct-touch pointing tasks (RJ, AN, PD, DW), pp. 2291–2300.
HCIDUXU-NTE-2013-VilarRNTDF #question
Are Emergency Egress Signs Strong Enough to Overlap the Influence of the Environmental Variables? (EV, FR, PN, LT, ED, EF), pp. 205–214.
WICSA-ECSAWICSA-ECSA-2012-KeulerKNR #architecture #framework #re-engineering #towards
Architecture Engagement Purposes: Towards a Framework for Planning “Just Enough”-Architecting in Software Engineering (TK, JK, MN, DR), pp. 234–238.
DACDAC-2012-Rinard #reasoning
Obtaining and reasoning about good enough software (MCR), pp. 930–935.
CSMRCSMR-2012-OlszakJ #composition #concept #how #legacy #question
Modularization of Legacy Features by Relocation and Reconceptualization: How Much is Enough? (AO, BNJ), pp. 171–180.
STOCSTOC-2012-ChakrabartiFW #multi #network #problem
When the cut condition is enough: a complete characterization for multiflow problems in series-parallel networks (AC, LF, CW), pp. 19–26.
ECIRECIR-2012-NeumayerBN12a #effectiveness #semantics
When Simple is (more than) Good Enough: Effective Semantic Search with (almost) no Semantics (RN, KB, KN), pp. 540–543.
QoSAQoSA-ISARCS-2011-Stal #architecture
Good is not good enough: evaluating and improving software architecture (MS), pp. 73–74.
CIKMCIKM-2011-ElsayedLM #approximate #performance #retrieval
When close enough is good enough: approximate positional indexes for efficient ranked retrieval (TE, JJL, DM), pp. 1993–1996.
CIKMCIKM-2011-KoloniariNPS #distributed
One is enough: distributed filtering for duplicate elimination (GK, NN, EP, DS), pp. 433–442.
RERE-2011-Waldmann #agile #constraints #development #requirements #what
There’s never enough time: Doing requirements under resource constraints, and what requirements engineering can learn from agile development (BW), pp. 301–305.
ICALPICALP-v2-2010-MarcinkowskiMK #decidability #logic
B and D Are Enough to Make the Halpern-Shoham Logic Undecidable (JM, JM, EK), pp. 357–368.
KRKR-2010-PichlerRSW #bound #constraints #programming
Tractable Answer-Set Programming with Weight Constraints: Bounded Treewidth Is not Enough (RP, SR, SS, SW).
RERE-2010-RachevaDSHW #agile #case study #requirements
Do We Know Enough about Requirements Prioritization in Agile Projects: Insights from a Case Study (ZR, MD, KS, AH, RW), pp. 147–156.
ASPLOSASPLOS-2010-Brewer
Technology for developing regions: Moore’s law is not enough (EAB), pp. 1–2.
ASEASE-2008-Eltaher #approach #testing #towards
Towards Good Enough Testing: A Cognitive-Oriented Approach Applied to Infotainment Systems (AE), pp. 525–528.
MSRMSR-2008-Bernstein #data mining #how #mining
How to learn enough data mining to be dangerous in 60 minutes (AB), pp. 77–78.
CAiSECAiSE-2008-MuehlenR #how #modelling #process
How Much Language Is Enough? Theoretical and Practical Use of the Business Process Modeling Notation (MzM, JR), pp. 465–479.
DACDAC-2007-BacchiniHFRLTPZ #question #verification
Verification Coverage: When is Enough, Enough? (FB, AJH, TF, RR, DL, MT, AP, AZ), pp. 744–745.
CSEETCSEET-2007-WilliamsL #question #why
Lab Partners: If They’re Good Enough for the Natural Sciences, Why Aren’t They Good Enough for Us? (LW, LL), pp. 72–82.
RERE-2007-Jacobson #process
Enough of RE Processes — Let’s Do Practices (IJ).
CSLCSL-2007-BucciarelliEM
Not Enough Points Is Enough (AB, TE, GM), pp. 298–312.
FATESTestCom-FATES-2007-EldhPHJ #case study #component #fault #middleware #testing
Component Testing Is Not Enough — A Study of Software Faults in Telecom Middleware (SE, SP, HH, PJ), pp. 74–89.
TLCATLCA-2007-JohannG #algebra #exclamation #semantics
Initial Algebra Semantics Is Enough! (PJ, NG), pp. 207–222.
WICSAWICSA-2005-Schwanke #architecture #named #process #requirements
GEAR: A Good Enough Architectural Requirements Process (RWS), pp. 57–66.
DACDAC-2005-WolfsthalG #question #verification
Formal verification: is it real enough? (YW, RMG), pp. 670–671.
VLDBVLDB-2005-GuoLR #consistency
Caching with “Good Enough” Currency, Consistency, and Completeness (HG, PÅL, RR), pp. 457–468.
SIGIRSIGIR-2005-AllanCL #information retrieval #question
When will information retrieval be “good enough”? (JA, BC, JL), pp. 433–440.
HTHT-2004-MartinTA
The end-point is not enough (DM, MT, HA), pp. 128–129.
SIGMODSIGMOD-2004-GuoLRG #consistency #how #sql
Relaxed Currency and Consistency: How to Say “Good Enough” in SQL (HG, PÅL, RR, JG), pp. 815–826.
SIGMODSIGMOD-2004-IpeirotisG #database #using
When one Sample is not Enough: Improving Text Database Selection Using Shrinkage (PGI, LG), pp. 767–778.
SIGMODSIGMOD-2004-JagadishLSSW #xml
Colorful XML: One Hierarchy Isn’t Enough (HVJ, LVSL, MS, DS, NW), pp. 251–262.
CHICHI-2004-TeevanAAK #behaviour #case study
The perfect search engine is not enough: a study of orienteering behavior in directed search (JT, CA, MSA, DRK), pp. 415–422.
PPDPPPDP-2004-SagonasS
Just enough tabling (KFS, PJS), pp. 78–89.
CSEETCSEET-2003-CrnkovicLS #question #re-engineering
Is Software Engineering Training Enough for Software Engineers? (IC, RL, AS), p. 140–?.
CSMRCSMR-2003-Briand #documentation #how #question
Software Documentation: How Much Is Enough? (LCB), p. 13–?.
EDOCEDOC-2003-GreenfieldFJK
Compensation is Not Enough (PG, AF, JJ, DK), pp. 232–239.
ECOOPECOOP-2003-ClarkeW
External Uniqueness Is Unique Enough (DC, TW), pp. 176–200.
ITiCSEITiCSE-2001-BruceDM #programming
Event-driven programming is simple enough for CS1 (KBB, APD, TPM), pp. 1–4.
FASEFASE-2000-Soley
Memex Is Not Enough (RMS), p. 21.
DACDAC-1999-FranzonBFMPSW #how #question
Parasitic Extraction Accuracy — How Much is Enough? (PDF, MB, AF, SM, RP, RCS, MW), p. 429.
DLTDLT-1999-FreundF
Test tube systems: when two tubes are enough (RF, FF), pp. 338–350.
ICSEICSE-1999-Fordham #maturity #process #question
Software Process Maturity: Is Level five Enough? (RGF), p. 611.
SIGMODSIGMOD-1998-ChaudhuriMN #how #question #random
Random Sampling for Histogram Construction: How much is enough? (SC, RM, VRN), pp. 436–447.
IWPCIWPC-1998-ErdosS #comprehension #maintenance #source code
Partial Comprehension of Complex Programs (enough to perform maintenance) (KE, HMS), pp. 98–105.
ICPRICPR-1998-NishikawaOM #3d #using
Selective acquisition of 3-D information enough for finding passable free spaces using an active stereo vision system (AN, AO, FM), pp. 857–861.
SIGMODSIGMOD-1997-CareyK #exclamation #on the #sql
On Saying “Enough Already!” in SQL (MJC, DK), pp. 219–230.
CHIINTERCHI-1993-GaverSHL #multi
One is not enough: multiple views in a media space (WWG, AS, CH, PL), pp. 335–341.
PODSPODS-1989-CohenW #knowledge base #parallel #why
Why a Single Parallelization Strategy in not Enough in Knowledge Bases (SRC, OW), pp. 200–216.
ASPLOSASPLOS-1987-ChowCHKW #how #question
How Many Addressing Modes are Enough? (FCC, SC, MIH, EK, LW), pp. 117–121.

Bibliography of Software Language Engineering in Generated Hypertext (BibSLEIGH) is created and maintained by Dr. Vadim Zaytsev.
Hosted as a part of SLEBOK on GitHub.