Stem should$ (all stems)

87 papers:

DATE-2015-PozoSKM #question

Side-channel attacks from static power: when should we care? (SMDP, FXS, DK, AM), pp. 145–150.

ICSME-2015-XiaLWY #analysis #bibliography #recommendation

Who should review this change?: Putting text and file location analyses together for more accurate recommendations (XX, DL, XW, XY), pp. 261–270.

SANER-2015-ThongtanunamTKY #approach #bibliography #code review #perspective #recommendation

Who should review my code? A file location-based code-reviewer recommendation approach for Modern Code Review (PT, CT, RGK, NY, HI, KiM), pp. 141–150.

ICALP-v1-2015-AzarC

Serving in the Dark should be done Non-Uniformly (YA, IRC), pp. 91–102.

HIMI-IKC-2015-BrunsVGZS #personalisation #recommendation #visual notation #what

What Should I Read Next? A Personalized Visual Publication Recommender System (SB, ACV, CG, MZ, US), pp. 89–100.

KDD-2015-Dhar #question #trust

Should You Trust Your Money to a Robot? (VD), p. 1625.

RecSys-2015-Abel #recommendation

We Know Where You Should Work Next Summer: Job Recommendations (FA), p. 230.

SAC-2015-SakuraiM #debugging #object-oriented #source code

The omission finder for debugging what-should-have-happened bugs in object-oriented programs (KS, HM), pp. 1962–1969.

ESEC-FSE-2015-SaraivaBZ #developer #how #n-gram

Products, developers, and milestones: how should I build my N-Gram language model (JS, CB, TZ), pp. 998–1001.

ICSE-v1-2015-GaoLCMW #interactive #question #testing #what

Making System User Interactive Tests Repeatable: When and What Should We Control? (ZG, YL, MBC, AMM, ZW), pp. 55–65.

ICSE-v2-2015-Squire #developer #social #social media #stack overflow

“Should We Move to Stack Overflow?” Measuring the Utility of Social Media for Developer Support (MS), pp. 219–228.

SIGMOD-2014-HoweFFFKR #database #education #question

Should we all be teaching “intro to data science” instead of “intro to databases”? (BH, MJF, JF, JF, TK, RR), pp. 917–918.

ICALP-v1-2014-DemaineHLS

Canadians Should Travel Randomly (EDD, YH, CSL, KS), pp. 380–391.

CSCW-2014-CoetzeeFHH #question

Should your MOOC forum use a reputation system? (DC, AF, MAH, BH), pp. 1176–1187.

KMIS-2014-SaoutalMC #communication

Should I Be Aware of the Information of Other Actors — Transversal Communication in Crisis Management (AS, NM, JPC), pp. 212–219.

SEKE-2014-CostaFM #collaboration #development #distributed #question

Collaborative Merge in Distributed Software Development: Who Should Participate? (CC, JJCF, LM), pp. 268–273.

FSE-2014-HigoK #case study #functional #how #java #source code

How should we measure functional sameness from program source code? an exploratory study on Java methods (YH, SK), pp. 294–305.

ICSE-2014-ZhangE #configuration management #question

Which configuration option should I change? (SZ, MDE), pp. 152–163.

ASPLOS-2014-Wood #architecture #named

Resolved: specialized architectures, languages, and system software should supplant general-purpose alternatives within a decade (DAW), pp. 653–654.

RTA-TLCA-2014-Schmidt-SchaussS #call-by #λ-calculus

Applicative May- and Should-Simulation in the Call-by-Value λ Calculus with AMB (MSS, DS), pp. 379–394.

HT-2013-KumarMZL #identification

Whom should I follow?: identifying relevant users during crises (SK, FM, RZ, HL), pp. 139–147.

ICDAR-2013-Newell #identification #question #what

What Should We Be Comparing for Writer Identification? (AJN), pp. 418–422.

CSEET-2013-Vallino #question #re-engineering #student #what

What should students learn in their first (and often only) software engineering course? (JV), pp. 335–337.

ASPLOS-2013-OliveiraFDHS #why

Why you should care about quantile regression (ABdO, SF, AD, MH, PFS), pp. 207–218.

PLOS-2013-Kell #operating system #question

The operating system: should there be one? (SK), p. 7.

CHI-2012-Gaver #design #question #research #what

What should we expect from research through design? (WWG), pp. 937–946.

CIKM-2012-BlancoCLPS #exclamation #recommendation #why

You should read this! let me explain you why: explaining news recommendations to users (RB, DC, CL, RP, FS), pp. 1995–1999.

ICSE-2012-LemosFSG #agile #assessment #development #empirical #programming

Development of auxiliary functions: Should you be agile? An empirical assessment of pair programming and test-first programming (OALL, FCF, FFS, AG), pp. 529–539.

ICSE-2012-ZhouZL #debugging #information retrieval #locality

Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports (JZ, HZ, DL), pp. 14–24.

ICST-2012-ChenLYS #question #testing #user interface #what

When a GUI Regression Test Failed, What Should be Blamed? (JC, ML, KY, BS), pp. 467–470.

FASE-2011-GharaibehRC #framework #question

Analyzing Software Updates: Should You Build a Dynamic Updating Infrastructure? (BG, HR, JMC), pp. 371–385.

CHI-2011-WainerDK #email

Should I open this email?: inbox-level cues, curiosity and attention to email (JW, LD, RK), pp. 3439–3448.

ECIR-2011-MagdyJ #black box #question

Should MT Systems Be Used as Black Boxes in CLIR? (WM, GJFJ), pp. 683–686.

SIGIR-2011-CuiWLOYS #predict #ranking #social #what

Who should share what?: item-level social influence prediction for users and posts ranking (PC, FW, SL, MO, SY, LS), pp. 185–194.

ICSE-2011-MeneelyW #developer #metric #network #question #trust

Socio-technical developer networks: should we trust our measurements? (AM, LW), pp. 281–290.

CSEET-2010-Broman #education #question #re-engineering

Should Software Engineering Projects Be the Backbone or the Tail of Computing Curricula? (DB), pp. 153–156.

MSR-2010-IbrahimBSAH #question

Should I contribute to this discussion? (WMI, NB, ES, BA, AEH), pp. 181–190.

PEPM-2010-Siek #metalanguage

General purpose languages should be metalanguages (JGS), pp. 3–4.

CHI-2010-ForlizziBS #collaboration #design #interactive #navigation

Where should i turn: moving from individual to collaborative navigation strategies to inform the interaction design of future navigation systems (JF, WCB, TS), pp. 1261–1270.

CIKM-2010-BethardJ #behaviour #learning #modelling

Who should I cite: learning literature search models from citation behavior (SB, DJ), pp. 609–618.

ICML-2010-Scherrer #difference #fixpoint #perspective

Should one compute the Temporal Difference fix point or minimize the Bellman Residual? The unified oblique projection view (BS), pp. 959–966.

DAC-2009-HaritanKJERRG #question

EDA in flux: should I stay or should I go? (EH, AK, TJ, JE, JMR, RR, NG), pp. 91–92.

DAC-2008-Haensch #3d #integration #question #why

Why should we do 3D integration? (WH), pp. 674–675.

SAC-2008-VictorCTC #recommendation #trust

Whom should I trust?: the impact of key figures on cold start recommendations (PV, CC, AT, MDC), pp. 2014–2018.

ASE-2007-Selic #automation #what

The embarrassing truth about software automation and what should be done about it (BS), p. 3.

DATE-2007-Casale-RossiSADGMPS #named #product line #question #trust

DFM/DFY: should you trust the surgeon or the family doctor? (MCR, AJS, RCA, AD, CG, PM, DP, JS), pp. 439–442.

VLDB-2007-PossNW #analysis #why

Why You Should Run TPC-DS: A Workload Analysis (MP, RON, DW), pp. 1138–1149.

ITiCSE-2007-PecinovskyP #interface #order

Order of explanation should be interface: abstract classes — overriding (RP, JP), p. 338.

ITiCSE-2007-SloanNS #design #education #how #question

How should inclusivity influence teaching of ict design? (DS, BN, MS), pp. 307–308.

ESEC-FSE-2007-KimE #question

Which warnings should I fix first? (SK, MDE), pp. 45–54.

CSEET-2006-Budgen #nondeterminism #why

Why should they believe us? Determinism, non-determinism and evidence (DB), p. 4.

ICSM-2006-XingS #case study #eclipse #how #refactoring

Refactoring Practice: How it is and How it Should be Supported — An Eclipse Case Study (ZX, ES), pp. 458–468.

SIGAda-2006-Taft #ada #exclamation #using #why

Why you should be using Ada 2005 now! (STT), p. 75.

ICSE-2006-AnvikHM #debugging #question

Who should fix this bug? (JA, LH, GCM), pp. 361–370.

HPDC-2006-ChouhanDCV #how #question

How should you structure your hierarchical scheduler? (PKC, HD, EC, FV), pp. 339–340.

WICSA-2005-Koschke #architecture #reverse engineering #what

What Architects Should Know About Reverse Engineering and Rengineering (RK), pp. 4–10.

DAC-2005-FoxCMHHJKYZ #approach #question

Should our power approach be current? (TF, LC, SM, DH, EPH, VJ, AK, AY, PSZ), p. 611.

DAC-2005-NandraDMDHLSA

Interconnects are moving from MHz→GHz should you be afraid?: or... “my giga hertz, does yours?” (NN, PD, RM, JFD, AH, BL, JS, JA), pp. 289–290.

ICDAR-2005-AblameykoBP #what

. What Should the User Do? Inference Structures and Line Drawing Interpretation (SA, VB, TPP), pp. 760–764.

STOC-2004-Wigderson #question #why

Depth through breadth, or why should we attend talks in other areas? (AW), p. 579.

KR-2004-Patel-Schneider #owl #question #what #why

What Is OWL (and Why Should I Care)? (PFPS), pp. 735–737.

ASE-2003-MemonBN #effectiveness #question #testing #user interface #what

What Test Oracle Should I Use for Effective GUI Testing? (AMM, IB, AN), pp. 164–173.

CSEET-2003-Cowling #question #what

What Should Graduating Software Engineers Be Able To Do? (AJC), pp. 88–98.

ITiCSE-2003-Christensen #education #exclamation #testing #topic

Systematic testing should not be a topic in the computer science curriculum! (HBC), pp. 7–10.

CHI-2002-Bayles #design #online #question

Designing online banner advertisements: should we animate? (MEB), pp. 363–366.

PPDP-2001-Schmidt #declarative #programming #question #uml

Should UML Be Used for Declarative Programming? (DAS), pp. 1–3.

RE-2001-Gonzales #question #what

Systems or Software: What Should the “S” in SRE Stand for? (RG), p. 281.

ISSTA-2000-HindP #analysis #pointer #question

Which pointer analysis should I use? (MH, AP), pp. 113–123.

CSEET-1999-McMillanR #re-engineering #student #what

What Leading Practitioners Say Should be Emphasized in Students’ Software Engineering Projects (WWM, SR), pp. 177–185.

ITiCSE-1999-KopecCA #algorithm #data type #how

How should data structures and algorithms be taught (DK, RC, JA), pp. 175–176.

CHI-1999-BruckmanE #analysis #fault #programming language

Should we Leverage Natural-Language Knowledge? An Analysis of User Errors in a Natural-Language-Style Programming Language (AB, EE), pp. 207–214.

LCTES-1999-Engblom #benchmark #embedded #metric #tool support #why

Why SpecInt95 Should Not Be Used to Benchmark Embedded Systems Tools (JE), pp. 96–103.

HT-1997-NurnbergLS

As We Should Have Thought (PJN, JJL, ERS), pp. 96–101.

CSEE-1996-Ryan #education #industrial #question #re-engineering

Meeting Industry’s Needs — Should We Teach the Software Engineering of the Past? (KR), pp. 218–220.

ICML-1996-RaviseS #evolution #fault

An Advanced Evolution Should Not Repeat its Past Errors (CR, MS), pp. 400–408.

SIGMOD-1995-Golding #replication

Things Every Update Replication Customer Should Know (RG), pp. 439–440.

AdaEurope-1994-Gray #ada #how #question

How Should Military Ada Software be Documented? (LG), pp. 162–169.

ECOOP-1994-Hursch #question

Should Superclasses be Abstract? (WLH), pp. 12–31.

HT-1993-NanardN #empirical

Should Anchors be Typed Too? An Experiment with MacWeb (JN, MN), pp. 51–62.

RE-1993-PartridgeGBK #question

Should we specify systems or domain? (DP, DG, DRB, JK), pp. 77–80.

CHI-1991-BrennanDLMSF #interface #question

Should we or shouldn’t we use spoken commands in voice interfaces? (PB, GD, DL, MM, ECS, MF), pp. 369–372.

CLP-1990-Reiter90 #database #question #what

What Should a Database Know? (RR), p. 765.

DAC-1988-Savir #design #verification #why

Why Partial Design Verification Works Better Than It Should (JS), pp. 704–707.

PODS-1988-Reiter #database #question #what

What Should A Database Know? (RR), pp. 302–304.

HCI-CE-1987-Salvendy #development #human-computer #interactive #research #what

What We Know and What We Should Know About Human-Computer Interaction: Strategies for Research and Development (GS), pp. 13–19.

ICSE-1979-Dijkstra #re-engineering

Software Engineering : As It Should Be (EWD), pp. 442–448.

ICALP-1976-FriedmanW

CONS Should Not Evaluate its Arguments (DPF, DSW), pp. 257–284.