BibSLEIGH — Barry_W

Travelled to:

1 × Argentina
1 × Belgium
1 × China
1 × Germany
1 × Singapore
1 × South Africa
1 × Spain
1 × Switzerland
19 × USA
2 × Austria
2 × Canada
2 × India
2 × Japan
2 × United Kingdom
3 × Ireland
3 × Italy

Collaborated with:

∅ D.Port S.Koolmanojwong A.Egyed P.Grünbacher S.K.Mobasser P.K.Bose R.Turner H.In K.J.Sullivan D.Klappholz Q.Li R.Valerdi J.A.Lane N.Medvidović A.Jain E.Horowitz M.J.Lee R.Ross V.R.Lamb R.L.Mobley J.E.Rieber M.Abi-Antoun J.Kwan C.Chen Q.W.0001 T.Menzies J.Hihn R.J.Madachy A.B.Pyster P.Aroonvatanaporn C.Sinthop D.N.Port Y.Yang B.Clark A.W.Brown R.O.Briggs G.E.Kaiser B.Clark S.Devnani-Chulani T.E.Gray T.Seewaldt J.R.Brown M.Lipow N.Kukreja S.S.Payyavula S.Padmanabhuni S.Williams J.Bhuta C.Mattmann T.L.Rodgers M.Deutsch Y.Sun M.H.Erdogmus W.Harrison D.J.Reifer A.Lynch J.F.Elwell E.D.Stuckle R.D.Williams L.Shi S.Li O.El-Rawas M.S.Feather L.Huang H.Hu J.Ge J.Lü C.Qian L.J.Osterweil M.Evangelist V.Gruhn J.Kramer E.F.Miller P.Bourque D.Gelosh T.B.Hilburn M.M.Shaw J.B.Thompson

Talks about:

softwar (38) engin (23) requir (12) system (9) educ (9) win (9) project (8) model (7) cours (7) base (7)

Person: Barry W. Boehm

DBLP: Boehm:Barry_W=

Facilitated 2 volumes:

Contributed to:

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1989

1988

1987

1984

1982

1979

1976

1969

2017

Wrote 60 papers:

CSEET-2015-BoehmM: System Thinking: Educating T-Shaped Software Engineers (BWB, SKM), pp. 13–16.
ICSE-v2-2015-BoehmM: System Thinking: Educating T-Shaped Software Engineers (BWB, SKM), pp. 333–342.
CSEET-2014-BoehmK #education #empirical #re-engineering #research: Combining software engineering education and empirical research via instrumented real-client team project courses (BWB, SK), pp. 209–211.
CSEET-2013-KoolmanojwongB #re-engineering #risk management: A look at software engineering risks in a team project course (SK, BWB), pp. 21–30.
RE-2012-KukrejaBPP #framework #requirements: Selecting an appropriate framework for value-based requirements prioritization (NK, BWB, SSP, SP), pp. 303–308.
CSEET-2011-BoehmBGHPST #education #re-engineering: Panel on the role of graduate software and systems engineering bodies of knowledge in formulating graduate software engineering curricula (BWB, PB, DG, TBH, ABP, MMS, JBT), pp. 535–536.
CSEET-2011-KoolmanojwongB: Educating software engineers to become systems engineers (SK, BWB), pp. 209–218.
CSEET-2011-LiB #education #process #re-engineering #research #validation #verification: Making winners for both education and research: Verification and validation process improvement practice in a software engineering course (QL, BWB), pp. 304–313.
ICSE-2011-BoehmV #challenge #estimation #research: Impact of software resource estimation research on practice: a preliminary report on achievements, synergies, and challenges (BWB, RV), pp. 1057–1065.
ASE-2010-AroonvatanapornSB #assessment #estimation #nondeterminism: Reducing estimation uncertainty with continuous assessment: tracking the “cone of uncertainty” (PA, CS, BWB), pp. 337–340.
ICSE-2010-BoehmL #incremental #process: New processes for new horizons: the incremental commitment model (BWB, JAL), pp. 501–502.
CSEET-2009-KoolmanojwongB #case study #education #experience #research #using: Using Software Project Courses to Integrate Education and Research: An Experience Report (SK, BWB), pp. 26–33.
ICSE-2009-MenziesWBH #how #probability #process #using: How to avoid drastic software process change (using stochastic stability) (TM, SW, BWB, JH), pp. 540–550.
CSEET-2008-PortBK #requirements: Nancy R. Mead: Making Requirements Prioritization a Priority (DNP, BWB, DK), pp. 250–261.
ASE-2007-MenziesEHFMB #automation #re-engineering: The business case for automated software engineering (TM, OER, JH, MSF, RJM, BWB), pp. 303–312.
WICSA-2007-BhutaMMB #architecture #assessment #component #framework: A Framework for the Assessment and Selection of Software Components and Connectors in COTS-Based Architectures (JB, CM, NM, BWB), p. 6.
CSEET-2006-Boehm #design #student: Educating Students in Value-Based Design and Deve (BWB), p. 3.
CSEET-2006-JainB #game studies #named #re-engineering: SimVBSE: Developing a Game for Value-Based Software Engineering (AJ, BWB), pp. 103–114.
ICSE-2006-Boehm #re-engineering: A view of 20th and 21st century software engineering (BWB), pp. 12–29.
ICSE-2006-HuangBHGLQ #development #enterprise #process: Applying the Value/Petri process to ERP software development in China (LH, BWB, HH, JG, JL, CQ), pp. 502–511.
ICSE-2006-YangBC #estimation #integration #off the shelf #using: Assessing COTS integration risk using cost estimation inputs (YY, BWB, BC), pp. 431–438.
ICSE-2005-BoehmBT #development: Spiral development of software-intensive systems of systems (BWB, AWB, RT), pp. 706–707.
ICSE-2004-BoehmT #agile: Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods (BWB, RT), pp. 718–719.
CSEET-2003-BoehmPK04: Tailoring a Successful Project-Based Course (BWB, DP, DK), p. 329–?.
CSEET-2002-PortB #tutorial: Tutorial 1: Introducing Software Economics within SWE Project Courses (DP, BWB), p. 266.
ICSE-2002-ErdogmusBHRS #re-engineering: Software engineering economics: background, current practices, and future directions (MHE, BWB, WH, DJR, KJS), pp. 683–684.
CSEET-2001-PortB #framework #product line #re-engineering #using: Using a Model Framework in Developing and Delivering a Family of Software Engineering Project Courses (DP, BWB), pp. 44–55.
ESEC-FSE-2001-GrunbacherB #named #requirements: EasyWinWin: a groupware-supported methodology for requirements negotiation (PG, BWB), pp. 320–321.
ICSE-2001-BoehmGB #named #requirements: EasyWinWin: A Groupware-Supported Nethodology for Requirements Negotiation (BWB, PG, ROB), pp. 720–721.
ICSE-2001-BoehmP #re-engineering #student: Educating Software Engineering Students to Manage Risk (BWB, DP), pp. 591–600.
ICSE-2001-InBRD #case study #quality #requirements: Applying WinWin to Quality Requirements: A Case Study (HI, BWB, TLR, MD), pp. 555–564.
SEKE-2001-MedvidovicGEB #lifecycle #modelling: Software Model Connectors: Bridging Models across the Software Lifecycle (NM, PG, AE, BWB), pp. 387–396.
CSEET-2000-BoehmKP #approach #development #education #re-engineering #research: A Combined Curriculum Research and Curriculum Development Approach to Software Engineering Education (BWB, GEK, DP), p. 310–?.
FoSE-2000-BoehmS #roadmap: Software economics: a roadmap (BWB, KJS), pp. 319–343.
ICSE-2000-OsterweilBEGKM #re-engineering #research #why: Why don’t we get more (self?) respect: the positive impact of software engineering research upon practice (LJO, BWB, ME, VG, JK, EFM), p. 660.
RE-1999-BoehmAPKL #requirements: Requirements Engineering, Expectations Management, and the Two Cultures (BWB, MAA, DP, JK, AL), pp. 14–22.
SIGAda-1999-Boehm #future of #predict #re-engineering: Predicting the future of computer systems and software engineering (BWB), p. 227.
WICSA-1999-BoehmPEA #architecture #lifecycle: The MBASE Life Cycle Architecture Milestone Package (BWB, DP, AE, MAA), pp. 511–528.
ICSE-1998-BoehmE #lessons learnt #requirements: Software Requirements Negotiation: Some Lessons Learned (BWB, AE), pp. 503–506.
ICSE-1998-ClarkDB #architecture: Calibrating the COCOMO II Post-Architecture Model (BC, SDC, BWB), pp. 477–480.
ESEC-FSE-1997-BoehmEKM #multi: Developing Multimedia Applications with the WinWin Spiral Model (BWB, AE, JK, RJM), pp. 20–39.
CSEE-1996-Boehm #requirements #student: Helping Students Learn Requirements Engineering (BWB), pp. 96–99.
ICRE-1996-Boehm #requirements #roadmap: Requirements Engineering at Age 20: Looking Back, Looking Ahead (BWB), p. 255.
ICRE-1996-BoehmI #identification: Identifying Quality-Requirement Conflicts (BWB, HI), p. 218.
ICSE-1995-BoehmBHL #approach #requirements: Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach (BWB, PKB, EH, MJL), pp. 243–253.
ICRE-1994-BoehmBHL #requirements: Software requirements as negotiated win conditions (BWB, PKB, EH, MJL), pp. 74–83.
ICSE-1994-Boehm #architecture: Software Architectures: Critical Success Factors and Cost Drivers (BWB), p. 365.
KBSE-1994-BoehmB #knowledge-based #re-engineering: Critical Success Factors for Knowledge-Based Software Engineering Applications (BWB, PKB), pp. 166–171.
ESEC-1989-Boehm #risk management: Software Risk Management (BWB), pp. 1–19.
ICSE-1989-Boehm #generative #process #what: What We Really Need Are Process Model Generators (BWB), p. 397.
ICSE-1988-BoehmR #case study #project management: Theory-W Software Project Management: A Case Study (BWB, RR), pp. 30–40.
ICSE-1987-Boehm #lessons learnt #process: Software Process Management: Lessons Learned from History (BWB), pp. 296–298.
ICSE-1984-BoehmGS #empirical #multi #prototype #specification: Prototyping vs. Specifying: A Multi-Project Experiment (BWB, TEG, TS), pp. 473–485.
ICSE-1982-BoehmEPSW: The TRW Software Productivity System (BWB, JFE, ABP, EDS, RDW), pp. 148–156.
ICSE-1979-BoehmB #re-engineering: Software Engineering: As it is (BWB), pp. 11–21.
ICSE-1976-BoehmBL #evaluation #quality: Quantitative Evaluation of Software Quality (BWB, JRB, ML), pp. 592–605.
DAC-1969-BoehmLMR #analysis #interactive: Interactive trajectory analysis: the graphic rocket system (BWB, VRL, RLM, JER), pp. 205–232.
DAC-1969-RieberBLM #named: POGO: Programmer-oriented graphics operation (JER, BWB, VRL, RLM), pp. 233–255.
ASE-2017-ShiCWLB #analysis #comprehension #feature model #fuzzy: Understanding feature requests by leveraging fuzzy method and linguistic analysis (LS, CC, QW0, SL, BWB), pp. 440–450.
ASE-2017-SunCWB #using: Improving missing issue-commit link recovery using positive and unlabeled data (YS, CC, QW0, BWB), pp. 147–152.