2009 | ||
---|---|---|
181 | EE | Supannika Koolmanojwong, Barry W. Boehm: Using Software Project Courses to Integrate Education and Research: An Experience Report. CSEE&T 2009: 26-33 |
180 | EE | Di Wu, Da Yang, Supannika Koolmanojwong, Barry W. Boehm: Experimental Evaluation of Wiki Technology and the Shaper Role in Rapid Interdisciplinary Requirements Negotiation. HICSS 2009: 1-9 |
179 | EE | Qi Li, Mingshu Li, Ye Yang, Qing Wang, Thomas Tan, Barry W. Boehm, Chenyong Hu: Bridge the Gap between Software Test Process and Business Value: A Case Study. ICSP 2009: 212-223 |
2008 | ||
178 | EE | Daniel Noah Port, Barry W. Boehm, David Klappholz: Nancy R. Mead: Making Requirements Prioritization a Priority. CSEE&T 2008: 250-261 |
177 | EE | Vu Nguyen, Bert Steece, Barry W. Boehm: A constrained regression technique for cocomo calibration. ESEM 2008: 213-222 |
176 | EE | Ye Yang, Mei He, Mingshu Li, Qing Wang, Barry W. Boehm: Phase distribution of software development effort. ESEM 2008: 61-69 |
175 | EE | Da Yang, Di Wu, Supannika Koolmanojwong, A. Winsor Brown, Barry W. Boehm: WikiWinWin: A Wiki Based System for Collaborative Requirements Negotiation. HICSS 2008: 24 |
174 | EE | Barry W. Boehm, Sunita Chulani, June M. Verner, Bernard Wong: Sixth workshop on software quality. ICSE Companion 2008: 1035-1036 |
173 | EE | Raymond J. Madachy, Barry W. Boehm: Assessing Quality Processes with ODC COQUALMO. ICSP 2008: 198-209 |
172 | EE | Tim Menzies, Oussama El-Rawas, Barry W. Boehm, Raymond J. Madachy, Jairus Hihn, Daniel Baker, Karen T. Lum: Accurate Estimates without Calibration?. ICSP 2008: 210-221 |
171 | EE | Barry W. Boehm: Making a Difference in the Software Century. IEEE Computer 41(3): 32-38 (2008) |
170 | EE | Barry W. Boehm, Ricardo Valerdi: Achievements and Challenges in Cocomo-Based Software Resource Estimation. IEEE Software 25(5): 74-83 (2008) |
169 | EE | Barry W. Boehm, Jesal Bhuta: Balancing Opportunities and Risks in Component-Based Software Development. IEEE Software 25(6): 56-63 (2008) |
2007 | ||
168 | EE | Tim Menzies, Oussama El-Rawas, Jairus Hihn, Martin S. Feather, Raymond J. Madachy, Barry W. Boehm: The business case for automated software engineering. ASE 2007: 303-312 |
167 | EE | Monvorath Phongpaibul, Barry W. Boehm: A Replicate Empirical Comparison between Pair Development and Software Development with Inspection. ESEM 2007: 265-274 |
166 | EE | Supannika Koolmanojwong, Barry W. Boehm: An Empirical Study on MBASE and LeanMBASE. ESEM 2007: 496 |
165 | EE | Yue Chen, Barry W. Boehm, Luke Sheppard: Value Driven Security Threat Modeling Based on Attack Path Analysis. HICSS 2007: 280 |
164 | EE | Hasan Kitapci, Barry W. Boehm: Formalizing Informal Stakeholder Decisions--A Hybrid Method Approach. HICSS 2007: 283 |
163 | EE | Barry W. Boehm, Sunita Chulani, June M. Verner, Bernard Wong: Fifth Workshop on Software Quality. ICSE Companion 2007: 131-132 |
162 | EE | Steven Fraser, Barry W. Boehm, Frederick P. Brooks Jr., Tom DeMarco, Tim Lister, Linda Rising, Edward Yourdon: Retrospectives on Peopleware. ICSE Companion 2007: 21-24 |
161 | EE | Da Yang, Barry W. Boehm, Ye Yang, Qing Wang, Mingshu Li: Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model. ICSP 2007: 37-48 |
160 | EE | Monvorath Phongpaibul, Supannika Koolmanojwong, Alexander Lam, Barry W. Boehm: Comparative Experiences with Electronic Process Guide Generator Tools. ICSP 2007: 61-72 |
159 | EE | Jesal Bhuta, Chris Mattmann, Nenad Medvidovic, Barry W. Boehm: A Framework for the Assessment and Selection of Software Components and Connectors in COTS-Based Architectures. WICSA 2007: 6 |
158 | EE | Barry W. Boehm, Apurva Jain: Developing a process framework using principles of value-based software engineering. Software Process: Improvement and Practice 12(5): 377-385 (2007) |
157 | EE | Ye Yang, Barry W. Boehm: Improving process decisions in COTS-based development via risk-based prioritization. Software Process: Improvement and Practice 12(5): 449-460 (2007) |
156 | EE | Raymond J. Madachy, Barry W. Boehm, Jo Ann Lane: Assessing hybrid incremental processes for SISOS development. Software Process: Improvement and Practice 12(5): 461-473 (2007) |
2006 | ||
155 | EE | Apurva Jain, Barry W. Boehm: SimVBSE: Developing a Game for Value-Based Software Engineering. CSEE&T 2006: 103-114 |
154 | EE | Barry W. Boehm: Educating Students in Value-Based Design and Deve. CSEE&T 2006: 3 |
153 | EE | Ye Yang, Barry W. Boehm, Dan Wu: COCOTS Risk Analyzer. ICCBSS 2006: 144-151 |
152 | EE | Sunita Chulani, Barry W. Boehm, June M. Verner, Bernard Wong: Workshop description of 4th workshop on software quality (WOSQ). ICSE 2006: 1019-1020 |
151 | EE | Barry W. Boehm: A view of 20th and 21st century software engineering. ICSE 2006: 12-29 |
150 | EE | Ye Yang, Barry W. Boehm, Betsy Clark: Assessing COTS integration risk using cost estimation inputs. ICSE 2006: 431-438 |
149 | EE | LiGuo Huang, Barry W. Boehm, Hao Hu, JiDong Ge, Jian Lü, Cheng Qian: Applying the Value/Petri process to ERP software development in China. ICSE 2006: 502-511 |
148 | EE | Monvorath Phongpaibul, Barry W. Boehm: An empirical comparison between pair development and software inspection in Thailand. ISESE 2006: 85-94 |
147 | EE | Barry W. Boehm, Apurva Jain: A Value-Based Software Process Framework. SPW/ProSim 2006: 1-10 |
146 | EE | Raymond J. Madachy, Barry W. Boehm, Jo Ann Lane: Spiral Lifecycle Increment Modeling for New Hybrid Processes. SPW/ProSim 2006: 167-177 |
145 | EE | LiGuo Huang, Hao Hu, JiDong Ge, Barry W. Boehm, Jian Lü: Tailor the Value-Based Software Quality Achievement Process to Project Business Cases. SPW/ProSim 2006: 56-63 |
144 | EE | Ye Yang, Barry W. Boehm: Optimizing Process Decision in COTS-Based Development Via Risk Based Prioritization. SPW/ProSim 2006: 64-71 |
143 | EE | Steven Fraser, Barry W. Boehm, Jack Järkvik, Erik Lundh, Kati Vilkki: How Do Agile/XP Development Methods Affect Companies?. XP 2006: 225-228 |
142 | EE | Hoh Peter In, Jongmoon Baik, Sangsoo Kim, Ye Yang, Barry W. Boehm: A quality-based cost estimation model for the product line life cycle. Commun. ACM 49(12): 85-88 (2006) |
141 | EE | LiGuo Huang, Barry W. Boehm: How Much Software Quality Investment Is Enough: A Value-Based Approach. IEEE Software 23(5): 88-95 (2006) |
2005 | ||
140 | Mingshu Li, Barry W. Boehm, Leon J. Osterweil: Unifying the Software Process Spectrum, International Software Process Workshop, SPW 2005, Beijing, China, May 25-27, 2005, Revised Selected Papers Springer 2005 | |
139 | EE | Jesal Bhuta, Barry W. Boehm: A Method for Compatible COTS Component Selection. ICCBSS 2005: 132-143 |
138 | EE | Barry W. Boehm, Ye Yang, Jesal Bhuta, Daniel Port: Composable Spiral Processes for COTS-Based Application Development. ICCBSS 2005: 6-7 |
137 | EE | Ye Yang, Barry W. Boehm: A Contextualized Study of COTS-Based E-Service Projects. ICCBSS 2005: 9 |
136 | EE | Bernard Wong, June M. Verner, Sunita Chulani, Barry W. Boehm: Third workshop on software quality. ICSE 2005: 688-689 |
135 | EE | Barry W. Boehm, A. Winsor Brown, Richard Turner: Spiral development of software-intensive systems of systems. ICSE 2005: 706-707 |
134 | EE | LiGuo Huang, Barry W. Boehm: Determining how much software assurance is enough? A value-based approach. ISESE 2005: 172-181 |
133 | EE | Keun Lee, Barry W. Boehm: Empirical results from an experiment on value-based review (VBR) processes. ISESE 2005: 3-12 |
132 | EE | Barry W. Boehm: The Future of Software Processes. ISPW 2005: 10-24 |
131 | EE | Jesal Bhuta, Barry W. Boehm, Steven Meyers: Process Elements: Components of Software Process Architectures. ISPW 2005: 332-346 |
130 | EE | Zhihao Chen, Daniel Port, Yue Chen, Barry W. Boehm: Evolving an Experience Base for Software Process Research. ISPW 2005: 433-448 |
129 | EE | Jewel Ward, Johan Bollen, Jeffrey Pearson, Shing-Cheung Chan, Hui-Hsien Chi, Marie Chi, Kristine Guevara, Hsiao-han Huang, Genesan Kim, Maks Krivokon, Bo H. Lee, Pei-Han Li, Fenny Muliawan, Vu Nguyen, Barry W. Boehm, A. Winsor Brown, Edward Colbert, Alexander Lam, Mayur K. Patel: Mining and analyzing digital archive usage data to support collection development decisions. JCDL 2005: 417 |
128 | EE | LiGuo Huang, Barry W. Boehm: Using iDAVE to determine availability requirements. ACM SIGSOFT Software Engineering Notes 30(4): 1-4 (2005) |
127 | EE | LiGuo Huang, Barry W. Boehm: Determining how much software assurance is enough?: a value-based approach. ACM SIGSOFT Software Engineering Notes 30(4): 1-5 (2005) |
126 | EE | Apurva Jain, Barry W. Boehm: Developing a theory of value-based software engineering. ACM SIGSOFT Software Engineering Notes 30(4): 1-5 (2005) |
125 | EE | Zhihao Chen, Tim Menzies, Daniel Port, Barry W. Boehm: Feature subset selection can improve software cost estimation accuracy. ACM SIGSOFT Software Engineering Notes 30(4): 1-6 (2005) |
124 | EE | Monvorath Phongpaibul, Barry W. Boehm: Improving quality through software process improvement in Thailand: initial analysis. ACM SIGSOFT Software Engineering Notes 30(4): 1-6 (2005) |
123 | EE | Barry W. Boehm: Value-based quality processes and results. ACM SIGSOFT Software Engineering Notes 30(4): 1-6 (2005) |
122 | EE | Ye Yang, Jesal Bhuta, Barry W. Boehm, Daniel Noah Port: Value-Based Processes for COTS-Based Applications. IEEE Software 22(4): 54-62 (2005) |
121 | EE | Barry W. Boehm, Richard Turner: Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software 22(5): 30-39 (2005) |
120 | EE | Zhihao Chen, Barry W. Boehm, Tim Menzies, Daniel Port: Finding the Right Data for Software Cost Modeling. IEEE Software 22(6): 38-46 (2005) |
2004 | ||
119 | EE | Donald J. Reifer, Victor R. Basili, Barry W. Boehm, Betsy Clark: COTS-Based Systems - Twelve Lessons Learned about Maintenance. ICCBSS 2004: 137-145 |
118 | EE | Barry W. Boehm, Richard Turner: Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods. ICSE 2004: 718-719 |
117 | EE | Bernard Wong, Sunita Chulani, June M. Verner, Barry W. Boehm: Second Workshop on Software Quality. ICSE 2004: 780-782 |
116 | EE | Barry W. Boehm, Jesal Bhuta, David Garlan, Eric Gradman, LiGuo Huang, Alexander Lam, Raymond J. Madachy, Nenad Medvidovic, Kenneth Meyer, Steven Meyers, Gustavo Pérez, Kirk Reinholtz, Roshanak Roshandel, Nicolas Rouquette: Using Empirical Testbeds to Accelerate Technology Maturity and Transition: The SCRover Experience. ISESE 2004: 117-126 |
115 | EE | Barry W. Boehm, A. Winsor Brown, Raymond J. Madachy, Ye Yang: A Software Product Line Life Cycle Cost Estimation Model. ISESE 2004: 156-164 |
114 | EE | Yue Chen, Barry W. Boehm, Raymond J. Madachy, Ricardo Valerdi: An Empirical Study of eServices Product UML Sizing Metrics. ISESE 2004: 199-206 |
113 | EE | Victor R. Basili, Barry W. Boehm, Al Davis, Watts S. Humphrey, Nancy G. Leveson, Nancy R. Mead, John D. Musa, David Lorge Parnas, Shari Lawrence Pfleeger, Elaine J. Weyuker: New Year's Resolutions for Software Quality. IEEE Software 21(1): 12-13 (2004) |
112 | EE | Barry W. Boehm, LiGuo Huang, Apurva Jain, Raymond J. Madachy: The ROI of Software Dependability: The iDAVE Model. IEEE Software 21(3): 54-61 (2004) |
2003 | ||
111 | EE | Barry W. Boehm, Richard Turner: Observations on Balancing Discipline and Agility. Agile Development Conference 2003: 32-39 |
110 | EE | Barry W. Boehm, Daniel Port, David Klappholz: Tailoring a Successful Project-Based Course. CSEE&T 2003: 329- |
109 | EE | Paul Grünbacher, Michael Halling, Stefan Biffl, Hasan Kitapci, Barry W. Boehm: Repeatable Quality Assurance Techniques for Requirements Negotiations. HICSS 2003: 23 |
108 | EE | Donald J. Reifer, Barry W. Boehm, Murali Gangadharan: Estimating the Cost of Security for COTS Software. ICCBSS 2003: 178-186 |
107 | EE | Barry W. Boehm, Daniel Port, Ye Yang, Jesal Bhuta: Not All CBS Are Created Equally: COTS-Intensive Project Types. ICCBSS 2003: 36-50 |
106 | EE | Barry W. Boehm, Daniel Port, Ye Yang, Jesal Bhuta, Chris Abts: Composable Process Elements for Developing COTS-Based Applications. ISESE 2003: 8-17 |
105 | EE | Steven Fraser, Ray Bareiss, Barry W. Boehm, Mark Hayes, Laura Hill, Gabby Silberman, Dave A. Thomas: Meeting the challenge of software engineering education for working professionals in the 21st century. OOPSLA Companion 2003: 262-264 |
104 | EE | Steven Fraser, Dave Astels, Kent Beck, Barry W. Boehm, John D. McGregor, James Newkirk, Charlie Poole: Discipline and practices of TDD: (test driven development). OOPSLA Companion 2003: 268-270 |
103 | EE | Barry W. Boehm, Richard Turner: Rebalancing Your Organization's Agility and Discipline. XP/Agile Universe 2003: 1-8 |
102 | EE | Barry W. Boehm: Value-based software engineering: reinventing. ACM SIGSOFT Software Engineering Notes 28(2): 3 (2003) |
101 | EE | Barry W. Boehm: Value-based software engineering. ACM SIGSOFT Software Engineering Notes 28(2): 4 (2003) |
100 | EE | Barry W. Boehm, LiGuo Huang: Value-Based Software Engineering: A Case Study. IEEE Computer 36(3): 33-41 (2003) |
99 | EE | Kent Beck, Barry W. Boehm: Agility through Discipline: A Debate. IEEE Computer 36(6): 44-46 (2003) |
98 | EE | Barry W. Boehm, Richard Turner: Using Risk to Balance Agile and Plan-Driven Methods. IEEE Computer 36(6): 57-66 (2003) |
97 | EE | Donald J. Reifer, Victor R. Basili, Barry W. Boehm, Betsy Clark: Eight Lessons Learned during COTS-Based Systems Maintenance. IEEE Software 20(5): 94-96 (2003) |
96 | EE | Nenad Medvidovic, Paul Grünbacher, Alexander Egyed, Barry W. Boehm: Bridging models across the software lifecycle. Journal of Systems and Software 68(3): 199-215 (2003) |
2002 | ||
95 | EE | Daniel Port, Barry W. Boehm: Tutorial 1: Introducing Software Economics within SWE Project Courses. CSEE&T 2002: 266 |
94 | EE | M. Hakan Erdogmus, Barry W. Boehm, Warren Harrison, Donald J. Reifer, Kevin J. Sullivan: Software engineering economics: background, current practices, and future directions. ICSE 2002: 683-684 |
93 | EE | Forrest Shull, Victor R. Basili, Barry W. Boehm, A. Winsor Brown, Patricia Costa, Mikael Lindvall, Daniel Port, Ioana Rus, Roseanne Tesoriero, Marvin V. Zelkowitz: What We Have Learned About Fighting Defects. IEEE METRICS 2002: 249- |
92 | EE | Mikael Lindvall, Victor R. Basili, Barry W. Boehm, Patricia Costa, Kathleen Dangle, Forrest Shull, Roseanne Tesoriero Tvedt, Laurie A. Williams, Marvin V. Zelkowitz: Empirical Findings in Agile Methods. XP/Agile Universe 2002: 197-207 |
91 | EE | Steven Fraser, Rachel Reinitz, Ken Auer, Barry W. Boehm, Ward Cunningham, Robert Mee: XP - Beyond Limitations? XP/Agile Universe 2002: 288 |
90 | EE | Barry W. Boehm: Get Ready for Agile Methods, with Care. IEEE Computer 35(1): 64-69 (2002) |
89 | EE | Tom DeMarco, Barry W. Boehm: The Agile Methods Fray. IEEE Computer 35(6): 90-92 (2002) |
88 | EE | Allen B. Tucker, Barry W. Boehm: Point/Counterpoint: On the Balance between Theory and Practice / Software Engineering Is a Value-Based Contact Sport. IEEE Software 19(5): 94-97 (2002) |
87 | EE | Jongmoon Baik, Barry W. Boehm, Bert Steece: Disaggregating and Calibrating the CASE Tool Variable in COCOMO II. IEEE Trans. Software Eng. 28(11): 1009-1022 (2002) |
2001 | ||
86 | EE | Daniel Port, Barry W. Boehm: Using a Model Framework in Developing and Delivering a Family of Software Engineering Project Courses. CSEE&T 2001: 44-55 |
85 | EE | Paul Grünbacher, Barry W. Boehm: EasyWinWin: a groupware-supported methodology for requirements negotiation. ESEC / SIGSOFT FSE 2001: 320-321 |
84 | Hoh In, Barry W. Boehm, Thomas Lee Rodgers, Michael Deutsch: Applying WinWin to Quality Requirements: A Case Study. ICSE 2001: 555-564 | |
83 | Barry W. Boehm, Daniel Port: Educating Software Engineering Students to Manage Risk. ICSE 2001: 591-600 | |
82 | Barry W. Boehm, Paul Grünbacher, Robert O. Briggs: EasyWinWin: A Groupware-Supported Nethodology for Requirements Negotiation. ICSE 2001: 720-721 | |
81 | Kevin J. Sullivan, Mary M. Shaw, Barry W. Boehm, David Notkin, Warren Harrison: Third International Workshop on Economics-Driven Software Engineering Research. ICSE 2001: 770-770 | |
80 | Nenad Medvidovic, Paul Grünbacher, Alexander Egyed, Barry W. Boehm: Software Model Connectors: Bridging Models across the Software Lifecycle. SEKE 2001: 387-396 | |
79 | Hoh In, Barry W. Boehm: Using WinWin Quality Requirements Management Tools: A Case Study. Ann. Software Eng. 11(1): 141-174 (2001) | |
78 | EE | Barry W. Boehm, Victor R. Basili: Software Defect Reduction Top 10 List. IEEE Computer 34(1): 135-137 (2001) |
77 | EE | Victor R. Basili, Barry W. Boehm: COTS-Based Systems Top 10 List. IEEE Computer 34(5): 91-93 (2001) |
76 | EE | Barry W. Boehm, Paul Grünbacher, Robert O. Briggs: Developing Groupware for Requirements Negotiation: Lessons Learned. IEEE Software 18(3): (2001) |
2000 | ||
75 | EE | Barry W. Boehm, Gail E. Kaiser, Daniel Port: A Combined Curriculum Research and Curriculum Development Approach to Software Engineering Education. CSEE&T 2000: 310- |
74 | EE | Leon J. Osterweil, Barry W. Boehm, Michael Evangelist, Volker Gruhn, Jeff Kramer, Edward F. Miller: Why don't we get more (self?) respect: the positive impact of software engineering research upon practice. ICSE 2000: 660 |
73 | EE | Barry W. Boehm, Kevin J. Sullivan: Software economics: a roadmap. ICSE - Future of SE Track 2000: 319-343 |
72 | Barry W. Boehm, Chris Abts, Sunita Chulani: Software development cost estimation approaches - A survey. Ann. Software Eng. 10: 177-205 (2000) | |
71 | EE | Barry W. Boehm: The Art of Expectations Management. IEEE Computer 33(1): 122-124 (2000) |
70 | Barry W. Boehm, Daniel Port, Mohammed Al-Said: Avoiding the Software Model-Clash Spiderweb. IEEE Computer 33(11): 120-122 (2000) | |
69 | Barry W. Boehm: Unifying Software Engineering and Systems Engineering. IEEE Computer 33(3): 114-116 (2000) | |
68 | EE | Barry W. Boehm, Victor R. Basili: Gaining Intellectual Control of Software Development. IEEE Computer 33(5): 27-33 (2000) |
67 | EE | Barry W. Boehm: Requirements that Handle IKIWISI, COTS, and Rapid Change. IEEE Computer 33(7): 99-102 (2000) |
66 | EE | Barry W. Boehm: Termination Doesn't Equal Project Failure. IEEE Computer 33(9): 94-96 (2000) |
65 | EE | Barry W. Boehm: Manager - Safe and Simple Software Cost Analysis. IEEE Software 17(5): (2000) |
64 | EE | Barry W. Boehm, Richard E. Fairley: Software Estimation Perspectives - Guest Editors' Introduction. IEEE Software 17(6): (2000) |
1999 | ||
63 | EE | Barry W. Boehm, Marwan Abi-Antoun, Daniel Port, Julie Kwan, Anne Lynch: Requirements Engineering, Expectations Management, and the Two Cultures. RE 1999: 14-22 |
62 | EE | Hal Hart, Barry W. Boehm, S. Tucker Taft, Tony Wasserman: What happened to integrated environments? (panel session). SIGAda 1999: 225-226 |
61 | EE | Barry W. Boehm: Predicting the future of computer systems and software engineering (keynote address). SIGAda 1999: 227 |
60 | Barry W. Boehm, Daniel Port, Alexander Egyed, Marwan Abi-Antoun: The MBASE Life Cycle Architecture Milestone Package. WICSA 1999: 511-528 | |
59 | Barry W. Boehm, Chris Abts: COTS Integration: Plug and Pray? IEEE Computer 32(1): 135-138 (1999) | |
58 | Barry W. Boehm: Making RAD Work for Your Project. IEEE Computer 32(3): 113-114 (1999) | |
57 | Barry W. Boehm: Managing Software Productivity and Reuse. IEEE Computer 32(9): 111-113 (1999) | |
56 | EE | Sunita Chulani, Barry W. Boehm, Bert Steece: Bayesian Analysis of Empirical Software Engineering Cost Models. IEEE Trans. Software Eng. 25(4): 573-583 (1999) |
55 | EE | Barry W. Boehm, Kevin J. Sullivan: Software economics: status and prospects. Information & Software Technology 41(14): 937-946 (1999) |
1998 | ||
54 | Bradford Clark, Sunita Devnani-Chulani, Barry W. Boehm: Calibrating the COCOMO II Post-Architecture Model. ICSE 1998: 477-480 | |
53 | Barry W. Boehm, Alexander Egyed: Software Requirements Negotiation: Some Lessons Learned. ICSE 1998: 503-506 | |
52 | Barry W. Boehm, Alexander Egyed, Daniel Port, Archita Shah, Julie Kwan, Raymond J. Madachy: A Stakeholder Win-Win Approach to Software Engineering Education. Ann. Software Eng. 6: 295-321 (1998) | |
51 | Barry W. Boehm, Alexander Egyed, Julie Kwan, Daniel Port, Archita Shah, Raymond J. Madachy: Using the WinWin Spiral Model: A Case Study. IEEE Computer 31(7): 33-44 (1998) | |
1997 | ||
50 | EE | Barry W. Boehm, Daniel Port: Conceptual Modeling Challenges for Model-Based Architecting and Software Engineering (MBASE). Conceptual Modeling 1997: 24-43 |
49 | EE | Barry W. Boehm, Alexander Egyed, Julie Kwan, Raymond J. Madachy: Developing Multimedia Applications with the WinWin Spiral Model. ESEC / SIGSOFT FSE 1997: 20-39 |
48 | Barry W. Boehm, Tom DeMarco: Guest Editors' Introduction: Software Risk Management. IEEE Software 14(3): 17-19 (1997) | |
1996 | ||
47 | EE | Barry W. Boehm, Hoh In: Software Cost Option Strategy Tool (S-COST). COMPSAC 1996: 15-20 |
46 | EE | Barry W. Boehm, Hoh In: Identifying Quality-Requirement Conflicts. ICRE 1996: 218 |
45 | EE | Barry W. Boehm: Requirements Engineering at Age 20: Looking Back, Looking Ahead. ICRE 1996: 255 |
44 | EE | Barry W. Boehm, Steven Wolf: An open architecture for software process asset reuse. ISPW 1996: 2-7 |
43 | EE | Barry W. Boehm: Industrial Priorities for Software Engineering Research (Panel). SIGSOFT FSE 1996: 2 |
42 | EE | Barry W. Boehm, Hoh In: Identifying Quality-Requirement Conflicts. IEEE Software 13(2): 25-35 (1996) |
41 | EE | Barry W. Boehm: Anchoring the Software Process. IEEE Software 13(4): 73-82 (1996) |
1995 | ||
40 | EE | Barry W. Boehm, Prasanta K. Bose, Ellis Horowitz, Ming June Lee: Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach. ICSE 1995: 243-253 |
39 | Barry W. Boehm, Bradford Clark, Ellis Horowitz, J. Christopher Westland, Raymond J. Madachy, Richard W. Selby: Cost Models for Future Software Life Cycle Processes: COCOMO 2.0. Ann. Software Eng. 1: 57-94 (1995) | |
38 | Barry W. Boehm, Prasanta K. Bose: Critical Success Factors for Knowledge-Based Software Engineering Applications. Autom. Softw. Eng. 2(3): 193-202 (1995) | |
1994 | ||
37 | EE | Barry W. Boehm: Megaprogramming (Abstract). ACM Conference on Computer Science 1994: 412 |
36 | EE | Barry W. Boehm: Software Architectures: Critical Success Factors and Cost Drivers. ICSE 1994: 365 |
35 | Barry W. Boehm, Prasanta K. Bose: Humans and process frameworks: some critical process elements. ISPW 1994: 82-84 | |
34 | Barry W. Boehm, Prasanta K. Bose: Critical Success Factors for Knowledge-Based Software Engineering Applications. KBSE 1994: 166-171 | |
1991 | ||
33 | Barry W. Boehm: Software Risk Management: Principles and Practices. IEEE Software 8(1): 32-41 (1991) | |
1989 | ||
32 | Barry W. Boehm: Software Risk Management. ESEC 1989: 1-19 | |
31 | Barry W. Boehm: What We Really Need Are Process Model Generators. ICSE 1989: 397 | |
30 | Barry W. Boehm: Software Factories in the USA. IFIP Congress 1989: 701-703 | |
29 | Barry W. Boehm, Frank C. Belz: Experiences with the spiral model as a process model generator. ISPW 1989: 43-45 | |
28 | EE | Barry W. Boehm, Rony Ross: Theory-W Software Project Management: Principles and Examples. IEEE Trans. Software Eng. 15(7): 902-916 (1989) |
1988 | ||
27 | Barry W. Boehm, Rony Ross: Theory-W Software Project Management: A Case Study. ICSE 1988: 30-40 | |
26 | Barry W. Boehm, Frank C. Belz: Applying process programming to the spiral model. ISPW 1988: 46-56 | |
25 | Barry W. Boehm: A Spiral Model of Software Development and Enhancement. IEEE Computer 21(5): 61-72 (1988) | |
24 | EE | Barry W. Boehm, Philip N. Papaccio: Understanding and Controlling Software Costs. IEEE Trans. Software Eng. 14(10): 1462-1477 (1988) |
1987 | ||
23 | Barry W. Boehm: Software Process Management: Lessons Learned from History. ICSE 1987: 296-298 | |
22 | Barry W. Boehm: Improving Software Productivity. IEEE Computer 20(9): 43-57 (1987) | |
1986 | ||
21 | Barry W. Boehm: Understanding and Controlling Software Costs (Invited Paper). IFIP Congress 1986: 703-714 | |
20 | Barry W. Boehm, Frank C. Belz: Reasoning about iteration: a cost-benefit approach. ISPW 1986: 40-44 | |
1985 | ||
19 | Barry W. Boehm: A spiral model of software development and enhancement. ISPW 1985: 22-42 | |
1984 | ||
18 | Barry W. Boehm, Terence E. Gray, Thomas Seewaldt: Prototyping vs. Specifying: A Multi-Project Experiment. ICSE 1984: 473-485 | |
17 | Barry W. Boehm, Terence E. Gray, Thomas Seewaldt: Prototyping versus specifying: A multiproject experiment. ISPW 1984: 133-145 | |
16 | EE | Barry W. Boehm, M. H. Penedo, E. Don Stuckle, Ronald D. Williams, Arthur B. Pyster: A Software Development Environment for Improving Productivity. IEEE Computer 17(6): 30-44 (1984) |
15 | Barry W. Boehm: Verifying and Validating Software Requirements and Design Specifications. IEEE Software 1(1): 75-88 (1984) | |
14 | Barry W. Boehm: Software Engineering Economics. IEEE Trans. Software Eng. 10(1): 4-21 (1984) | |
13 | Barry W. Boehm, Terence E. Gray, Thomas Seewaldt: Prototyping Versus Specifying: A Multiproject Experiment. IEEE Trans. Software Eng. 10(3): 290-303 (1984) | |
1983 | ||
12 | Barry W. Boehm, Thomas A. Standish: Software Technology in the 1990's: Using an Evolutionary Paradigm. IEEE Computer 16(11): 30-37 (1983) | |
11 | EE | Barry W. Boehm: Seven basic principles of software engineering. Journal of Systems and Software 3(1): 3-24 (1983) |
1982 | ||
10 | Barry W. Boehm, James F. Elwell, Arthur B. Pyster, E. Don Stuckle, Ronald D. Williams: The TRW Software Productivity System. ICSE 1982: 148-156 | |
1981 | ||
9 | Barry W. Boehm: An Experiment in Small-Scale Application Software Engineering. IEEE Trans. Software Eng. 7(5): 482-493 (1981) | |
1980 | ||
8 | EE | Barry W. Boehm: Software engineering education. AFIPS National Computer Conference 1980: 781 |
7 | Barry W. Boehm: Developing Small-Scale Application Software Products: Some Experiment Results. IFIP Congress 1980: 321-326 | |
6 | EE | Barry W. Boehm, Ray W. Wolverton: Software cost modeling: Some lessons learned. Journal of Systems and Software 1: 195-201 (1980) |
1979 | ||
5 | Barry W. Boehm: Software Engineering: As it is. ICSE 1979: 11-21 | |
1976 | ||
4 | Barry W. Boehm, J. R. Brown, M. Lipow: Quantitative Evaluation of Software Quality. ICSE 1976: 592-605 | |
3 | Barry W. Boehm: Software Engineering. IEEE Trans. Computers 25(12): 1226-1241 (1976) | |
1975 | ||
2 | Barry W. Boehm, Robert K. McClean, D. B. Urfrig: Some Experience with Automated Aids to the Design of Large-Scale Reliable Software. IEEE Trans. Software Eng. 1(1): 125-133 (1975) | |
1974 | ||
1 | Barry W. Boehm: Some Steps Toward Formal and Automated Aids to Software Requirements Analysis and Design. IFIP Congress 1974: 192-197 |