default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDIpek Ozkaya
Person information
- affiliation: Carnegie Mellon Software Engineering Institute, USA
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
showing all ?? records
2020 – today
- 2024
[c47]Rachel A. Brower-Sinning, Grace A. Lewis, Sebastián Echeverría, Ipek Ozkaya:
Using Quality Attribute Scenarios for ML Model Test Case Generation. ICSA-C 2024: 307-310- [c46]Kevin Pitstick, Marc Novakouski, Grace A. Lewis, Ipek Ozkaya:
Defining a Reference Architecture for Edge Systems in Highly-Uncertain Environments. ICSA-C 2024: 356-361 - [c45]Heli Järvenpää
, Patricia Lago, Justus Bogner, Grace A. Lewis, Henry Muccini, Ipek Ozkaya:
A Synthesis of Green Architectural Tactics for ML-Enabled Systems. ICSE (SEIS) 2024: 130-141 - [e7]Bram Adams, Thomas Zimmermann, Ipek Ozkaya, Dayi Lin, Jie M. Zhang:
Proceedings of the 1st ACM International Conference on AI-Powered Software, AIware 2024, Porto de Galinhas, Brazil, July 15-16, 2024. ACM 2024 [contents] - [i11]Paris Avgeriou, Ipek Ozkaya, Alexander Chatzigeorgiou, Marcus Ciolkowski, Neil A. Ernst, Ronald J. Koontz, Eltjo R. Poort, Forrest Shull:
Technical Debt Management: The Road Ahead for Successful Software Delivery. CoRR abs/2403.06484 (2024) - [i10]Rachel A. Brower-Sinning, Grace A. Lewis, Sebastián Echeverría, Ipek Ozkaya:
Using Quality Attribute Scenarios for ML Model Test Case Generation. CoRR abs/2406.08575 (2024) - [i9]Kevin Pitstick, Marc Novakouski, Grace A. Lewis, Ipek Ozkaya:
Defining a Reference Architecture for Edge Systems in Highly-Uncertain Environments. CoRR abs/2406.08583 (2024) - 2023
- [j54]Ipek Ozkaya:
Infrastructure as Code and Software Architecture Conformance Checking. IEEE Softw. 40(1): 4-8 (2023) - [j53]Ipek Ozkaya:
No Silver Bullets, Only Disciplined Reflections to Guide Course Corrections [From the Editor]. IEEE Softw. 40(2): 4-7 (2023) - [j52]Ipek Ozkaya:
Application of Large Language Models to Software Engineering Tasks: Opportunities, Risks, and Implications. IEEE Softw. 40(3): 4-8 (2023) - [j51]Ipek Ozkaya:
The Next Frontier in Software Development: AI-Augmented Software Development Processes. IEEE Softw. 40(4): 4-9 (2023) - [j50]Ipek Ozkaya:
Can Architecture Knowledge Guide Software Development With Generative AI? IEEE Softw. 40(5): 4-8 (2023) - [j49]Ipek Ozkaya:
Looking Back, Looking Forward: Reflections of an Editor in Chief. IEEE Softw. 40(6): 4-10 (2023) - [j48]Thiago do Nascimento Ferreira, James Ivers, Jeffrey J. Yackley, Marouane Kessentini, Ipek Ozkaya, Khouloud Gaaloul:
Dependent or Not: Detecting and Understanding Collections of Refactorings. IEEE Trans. Software Eng. 49(6): 3344-3358 (2023) - [c44]Paris Avgeriou, Ipek Ozkaya, Alexander Chatzigeorgiou, Marcus Ciolkowski, Neil A. Ernst, Ronald J. Koontz, Eltjo R. Poort, Forrest Shull:
Technical Debt Management: The Road Ahead for Successful Software Delivery. ICSE-FoSE 2023: 15-30 - [i8]Heli Järvenpää, Patricia Lago, Justus Bogner, Grace A. Lewis, Henry Muccini, Ipek Ozkaya:
A Synthesis of Green Architectural Tactics for ML-Enabled Systems. CoRR abs/2312.09610 (2023) - [i7]Grace A. Lewis, Henry Muccini, Ipek Ozkaya, Karthik Vaidhyanathan, Roland Weiss, Liming Zhu:
Software Architecture and Machine Learning (Dagstuhl Seminar 23302). Dagstuhl Reports 13(7): 166-188 (2023) - 2022
- [j47]Ivano Malavolta, Henry Muccini, Ipek Ozkaya:
Software Architecture and Artificial Intelligence. J. Syst. Softw. 193: 111436 (2022) - [j46]Roberto Verdecchia, Ivano Malavolta, Patricia Lago, Ipek Ozkaya:
Empirical evaluation of an architectural technical debt index in the context of the Apache and ONAP ecosystems. PeerJ Comput. Sci. 8: e833 (2022) - [j45]Ipek Ozkaya:
The Developer Nation. IEEE Softw. 39(1): 3-6 (2022) - [j44]Ipek Ozkaya:
Architectural Concerns of Digital Twins. IEEE Softw. 39(2): 3-6 (2022) - [j43]Ipek Ozkaya:
Understanding and Building Trust in Software Systems. IEEE Softw. 39(3): 3-6 (2022) - [j42]Ipek Ozkaya:
Crossing the Great Divide of Software Engineering. IEEE Softw. 39(4): 4-7 (2022) - [j41]Ipek Ozkaya:
A Paradigm Shift in Automating Software Engineering Tasks: Bots. IEEE Softw. 39(5): 4-8 (2022) - [j40]Ipek Ozkaya:
An AI Engineer Versus a Software Engineer. IEEE Softw. 39(6): 4-7 (2022) - [j39]Ipek Ozkaya:
Barry Boehm: 1935-2022. IEEE Softw. 39(6): 13-14 (2022) - [j38]Mashel Albarak, Rami Bahsoon, Ipek Ozkaya, Robert L. Nord:
Managing Technical Debt in Database Normalization. IEEE Trans. Software Eng. 48(3): 755-772 (2022) - [j37]Raghvinder S. Sangwan, Ashkan Negahban, Robert L. Nord, Ipek Ozkaya:
Optimization of Software Release Planning Considering Architectural Dependencies, Cost, and Value. IEEE Trans. Software Eng. 48(4): 1369-1384 (2022) - [c43]James Ivers, Chris Seifried, Ipek Ozkaya:
Untangling the Knot: Enabling Architecture Evolution with Search-Based Refactoring. ICSA 2022: 101-111 - [c42]James Ivers, Robert L. Nord, Ipek Ozkaya, Chris Seifried, Christopher Steven Timperley, Marouane Kessentini:
Industry's Cry for Tools that Support Large-Scale Refactoring. ICSE (SEIP) 2022: 163-164 - [c41]James Ivers, Robert L. Nord, Ipek Ozkaya, Chris Seifried, Christopher Steven Timperley, Marouane Kessentini:
Industry experiences with large-scale refactoring. ESEC/SIGSOFT FSE 2022: 1544-1554 - [i6]Ipek Ozkaya, Zachary Kurtz, Robert L. Nord, Raghvinder S. Sangwan, Satish Mahadevan Srinivasan:
Detecting Discussions of Technical Debt. CoRR abs/2201.12177 (2022) - [i5]James Ivers, Robert L. Nord, Ipek Ozkaya, Chris Seifried, Christopher Steven Timperley, Marouane Kessentini:
Industry Experiences with Large-Scale Refactoring. CoRR abs/2202.00173 (2022) - 2021
- [j36]Raghvinder S. Sangwan, Robert L. Nord, Ipek Ozkaya:
Architectural Dependency Analysis: Addressing the Elephant in the Room. Computer 54(3): 73-78 (2021) - [j35]Ipek Ozkaya:
Protecting the Health and Longevity of the Peer-Review Process in the Software Engineering Community. IEEE Softw. 38(1): 3-6 (2021) - [j34]Ipek Ozkaya:
Mom, Where Are the Girls? IEEE Softw. 38(2): 3-6 (2021) - [j33]Ipek Ozkaya:
Can We Really Achieve Software Quality? IEEE Softw. 38(3): 3-6 (2021) - [j32]Ipek Ozkaya:
A Watershed Moment for Search-Based Software Engineering. IEEE Softw. 38(4): 3-6 (2021) - [j31]Ipek Ozkaya:
The Future of Software Engineering Work. IEEE Softw. 38(5): 3-6 (2021) - [j30]Ipek Ozkaya:
A Plea to Tool Vendors: Do Not Mislead How Technical Debt Is Managed. IEEE Softw. 38(6): 3-6 (2021) - [c40]Grace A. Lewis, Stephany Bellomo, Ipek Ozkaya:
Characterizing and Detecting Mismatch in Machine-Learning-Enabled Systems. WAIN@ICSE 2021: 133-140 - [c39]Grace A. Lewis, Ipek Ozkaya, Xiwei Xu:
Software Architecture Challenges for ML Systems. ICSME 2021: 634-638 - [c38]Chaima Abid, James Ivers, Thiago do Nascimento Ferreira, Marouane Kessentini, Fares E. Kahla, Ipek Ozkaya:
Intelligent Change Operators for Multi-Objective Refactoring. ASE 2021: 768-780 - [i4]Grace A. Lewis, Stephany Bellomo, Ipek Ozkaya:
Characterizing and Detecting Mismatch in Machine-Learning-Enabled Systems. CoRR abs/2103.14101 (2021) - 2020
- [j29]Ipek Ozkaya:
What Should a Software Engineer Know? IEEE Softw. 37(1): 3-6 (2020) - [j28]Ipek Ozkaya:
Building Blocks of Software Design. IEEE Softw. 37(2): 3-5 (2020) - [j27]Ipek Ozkaya:
The Deployment View. IEEE Softw. 37(3): 3-5 (2020) - [j26]Ipek Ozkaya:
What Is Really Different in Engineering AI-Enabled Systems? IEEE Softw. 37(4): 3-6 (2020) - [j25]Ipek Ozkaya:
Unanticipated Scenarios. IEEE Softw. 37(4): 3-5 (2020) - [j24]Ipek Ozkaya:
The Behavioral Science of Software Engineering and Human-Machine Teaming. IEEE Softw. 37(6): 3-6 (2020) - [c37]Roberto Verdecchia, Patricia Lago, Ivano Malavolta, Ipek Ozkaya:
ATDx: Building an Architectural Technical Debt Index. ENASE 2020: 531-539 - [c36]James Ivers, Ipek Ozkaya, Robert L. Nord, Chris Seifried:
Next generation automated software evolution refactoring at scale. ESEC/SIGSOFT FSE 2020: 1521-1524 - [e6]Anton Jansen, Ivano Malavolta, Henry Muccini, Ipek Ozkaya, Olaf Zimmermann:
Software Architecture - 14th European Conference, ECSA 2020, L'Aquila, Italy, September 14-18, 2020, Proceedings. Lecture Notes in Computer Science 12292, Springer 2020, ISBN 978-3-030-58922-6 [contents]
2010 – 2019
- 2019
- [j23]Ipek Ozkaya:
The Golden Age of Software Engineering [From the Editor]. IEEE Softw. 36(1): 4-10 (2019) - [j22]Ipek Ozkaya:
If It Does Not Scale, It Does Not Work! IEEE Softw. 36(2): 4-7 (2019) - [j21]Ipek Ozkaya:
Ethics Is a Software Design Concern. IEEE Softw. 36(3): 4-8 (2019) - [j20]Ipek Ozkaya:
Are DevOps and Automation Our Next Silver Bullet? IEEE Softw. 36(4): 3-95 (2019) - [j19]Ipek Ozkaya:
The Voice of the Developer. IEEE Softw. 36(5): 3-5 (2019) - [j18]Ipek Ozkaya:
Interact, Collaborate, Debate. IEEE Softw. 36(6): 3-6 (2019) - [c35]James Ivers, Ipek Ozkaya, Robert L. Nord:
Can AI Close the Design-Code Abstraction Gap? ASE Workshops 2019: 122-125 - [i3]Lena Pons, Ipek Ozkaya:
Priority Quality Attributes for Engineering AI-enabled Systems. CoRR abs/1911.02912 (2019) - 2018
- [j17]Linda M. Northrop, Ipek Ozkaya, George Fairbanks, Michael Keeling:
Designing the Software Systems of the Future. ACM SIGSOFT Softw. Eng. Notes 43(4): 28-30 (2018) - [j16]Lina Northrop, Ipek Ozkaya, George Fairbanks, Michael Keeling:
Designing the Software Systems of the Future. ACM SIGSOFT Softw. Eng. Notes 43(4): 53 (2018) - [j15]Claire Le Goues, Ciera Jaspan, Ipek Ozkaya, Mary Shaw, Kathryn T. Stolee:
Bridging the Gap: From Research to Practical Advice. IEEE Softw. 35(5): 50-57 (2018) - [c34]Ipek Ozkaya, Liming Zhu:
New and Emerging Ideas Track 2018. ICSA Companion 2018: 47 - 2017
- [j14]Clemente Izurieta, Ipek Ozkaya, Carolyn B. Seaman, Will Snipes:
Technical Debt: A Research Roadmap Report on the Eighth Workshop on Managing Technical Debt (MTD 2016). ACM SIGSOFT Softw. Eng. Notes 42(1): 28-31 (2017) - [c33]Neil A. Ernst, Stephany Bellomo, Ipek Ozkaya, Robert L. Nord:
What to Fix? Distinguishing between Design and Non-design Rules in Automated Tools. ICSA 2017: 165-168 - [i2]Neil A. Ernst, Stephany Bellomo, Ipek Ozkaya, Robert L. Nord:
What to Fix? Distinguishing between design and non-design rules in automated tools. CoRR abs/1705.11087 (2017) - 2016
- [j13]Paris Avgeriou, Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Carolyn B. Seaman:
Reducing Friction in Software Development. IEEE Softw. 33(1): 66-73 (2016) - [j12]Gregor Hohpe, Ipek Ozkaya, Uwe Zdun, Olaf Zimmermann:
The Software Architect's Role in the Digital Age. IEEE Softw. 33(6): 30-39 (2016) - [c32]Clemente Izurieta, Ipek Ozkaya, Carolyn B. Seaman, Philippe Kruchten, Robert L. Nord, Will Snipes, Paris Avgeriou:
Perspectives on Managing Technical Debt: A Transition Point and Roadmap from Dagstuhl. QuASoQ/TDA@APSEC 2016: 84-87 - [c31]Stephany Bellomo, Robert L. Nord, Ipek Ozkaya, Mary Popeck:
Got technical debt?: surfacing elusive technical debt in issue trackers. MSR 2016: 327-338 - [c30]Robert L. Nord, Ipek Ozkaya:
Software Vulnerabilities, Defects, and Design Flaws: A Technical Debt Perspective. SecDev 2016: 165 - [c29]Robert L. Nord, Ipek Ozkaya, Edward J. Schwartz, Forrest Shull, Rick Kazman:
Can Knowledge of Technical Debt Help Identify Software Vulnerabilities? CSET @ USENIX Security Symposium 2016 - [c28]Robert L. Nord, Raghvinder S. Sangwan, Julien Delange, Peter H. Feiler, Luke Thomas, Ipek Ozkaya:
Missed Architectural Dependencies: The Elephant in the Room. WICSA 2016: 41-50 - [i1]Paris Avgeriou, Philippe Kruchten, Ipek Ozkaya, Carolyn B. Seaman:
Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162). Dagstuhl Reports 6(4): 110-138 (2016) - 2015
- [j11]Carolyn B. Seaman, Robert L. Nord, Philippe Kruchten, Ipek Ozkaya:
Technical Debt: Beyond Definition to Understanding Report on the Sixth International Workshop on Managing Technical Debt. ACM SIGSOFT Softw. Eng. Notes 40(2): 32-34 (2015) - [j10]Ipek Ozkaya, Robert L. Nord, Heiko Koziolek, Paris Avgeriou:
Toward Simpler, not Simplistic, Quantification of Software Architecture and Metrics: Report on the Second International Workshop on Software Architecture and Metrics. ACM SIGSOFT Softw. Eng. Notes 40(5): 43-46 (2015) - [c27]Ipek Ozkaya, Robert L. Nord, Heiko Koziolek, Paris Avgeriou:
Second International Workshop on Software Architecture and Metrics (SAM 2015). ICSE (2) 2015: 999-1000 - [c26]Neil A. Ernst, Stephany Bellomo, Ipek Ozkaya, Robert L. Nord, Ian Gorton:
Measure it? Manage it? Ignore it? software practitioners and technical debt. ESEC/SIGSOFT FSE 2015: 50-60 - [e5]Ipek Ozkaya, Robert L. Nord, Heiko Koziolek, Paris Avgeriou:
2nd IEEE/ACM International Workshop on Software Architecture and Metrics, SAM 2015, Florence, Italy, May 16, 2015. IEEE Computer Society 2015, ISBN 978-1-4673-7076-9 [contents] - [e4]Philippe Kruchten, Ipek Ozkaya, Heiko Koziolek:
Proceedings of the 11th International ACM SIGSOFT Conference on Quality of Software Architectures, QoSA'15 (part of CompArch 2015), Montreal, QC, Canada, May 4-8, 2015. ACM 2015, ISBN 978-1-4503-3470-9 [contents] - 2014
- [j9]Davide Falessi, Philippe Kruchten, Robert L. Nord, Ipek Ozkaya:
Technical debt at the crossroads of research and practice: report on the fifth international workshop on managing technical debt. ACM SIGSOFT Softw. Eng. Notes 39(2): 31-33 (2014) - [j8]Robert L. Nord, Ipek Ozkaya, Heiko Koziolek, Paris Avgeriou:
Quantifying software architecture quality report on the first international workshop on software architecture metrics. ACM SIGSOFT Softw. Eng. Notes 39(5): 4:32-4:34 (2014) - [c25]Ipek Ozkaya:
Is the glass half empty or half full? conducting empirical studies in industry (invited talk). CESI 2014: 3-4 - [c24]Robert L. Nord, Ipek Ozkaya, Raghvinder S. Sangwan, Ronald J. Koontz:
Architectural dependency analysis to understand rework costs for safety-critical systems. ICSE Companion 2014: 185-194 - [c23]Stephany Bellomo, Neil A. Ernst, Robert L. Nord, Ipek Ozkaya:
Evolutionary Improvements of Cross-Cutting Concerns: Performance in Practice. ICSME 2014: 545-548 - [c22]Robert L. Nord, Ipek Ozkaya, Philippe Kruchten:
Agile in Distress: Architecture to the Rescue. XP Workshops 2014: 43-57 - 2013
- [j7]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Davide Falessi:
Technical debt: towards a crisper definition report on the 4th international workshop on managing technical debt. ACM SIGSOFT Softw. Eng. Notes 38(5): 51-54 (2013) - [c21]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Davide Falessi:
Message from the MTD 2013 Workshop Chairs. ESEM 2013: 396 - [c20]Stephany Bellomo, Robert L. Nord, Ipek Ozkaya:
Elaboration on an integrated architecture and requirement practice: Prototyping with quality attribute focus. TwinPeaks@ICSE 2013: 8-13 - [c19]Steven Fraser, Judith Bishop, Barry W. Boehm, Pradeep Kathail, Philippe Kruchten, Ipek Ozkaya, Alexandra Szynkarski:
Technical debt: past, present, and future (panel). ICSE 2013: 861-862 - [c18]Stephany Bellomo, Robert L. Nord, Ipek Ozkaya:
A study of enabling factors for rapid fielding: combined practices to balance speed and stability. ICSE 2013: 982-991 - [c17]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya:
4th international workshop on managing technical debt (MTD 2013). ICSE 2013: 1535-1536 - [c16]Robert L. Nord, Ipek Ozkaya, Raghvinder S. Sangwan, Julien Delange, Marco A. Gonzalez, Philippe Kruchten:
Variations on Using Propagation Cost to Measure Architecture Modifiability Properties. ICSM 2013: 400-403 - [c15]Steven Fraser, Dennis Mancl, Bill Opdyke, Judith Bishop, Pradeep Kathail, Junilu Lacar, Ipek Ozkaya, Alexandra Szynkarski:
Technical debt: from source to mitigation. SPLASH (Companion Volume) 2013: 67-70 - [c14]Neil A. Ernst, Ipek Ozkaya, Robert L. Nord, Julien Delange, Stephany Bellomo, Ian Gorton:
Understanding the role of constraints on architecturally significant requirements. TwinPeaks@RE 2013: 9-14 - [e3]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya:
Proceedings of the 4th International Workshop on Managing Technical Debt, MTD 2013, San Francisco, CA, USA, May 20, 2013. IEEE Computer Society 2013, ISBN 978-1-4673-6443-0 [contents] - 2012
- [j6]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Joost Visser:
Technical debt in software development: from metaphor to theory report on the third international workshop on managing technical debt. ACM SIGSOFT Softw. Eng. Notes 37(5): 36-38 (2012) - [j5]Robert L. Nord, Ipek Ozkaya, Raghvinder S. Sangwan:
Making Architecture Visible to Improve Flow Management in Lean Software Development. IEEE Softw. 29(5): 33-39 (2012) - [j4]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya:
Technical Debt: From Metaphor to Theory and Practice. IEEE Softw. 29(6): 18-21 (2012) - [c13]Robert L. Nord, Ipek Ozkaya, Philippe Kruchten, Marco Gonzalez-Rojas:
In Search of a Metric for Managing Architectural Technical Debt. WICSA/ECSA 2012: 91-100 - [e2]Philippe Kruchten, Robert L. Nord, Ipek Ozkaya, Joost Visser:
Proceedings of the Third International Workshop on Managing Technical Debt, MTD 2012, Zurich, Switzerland, June 5, 2012. IEEE/ACM 2012, ISBN 978-1-4673-1749-8 [contents] - 2011
- [j3]Ipek Ozkaya, Philippe Kruchten, Robert L. Nord, Nanette Brown:
Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at ICSE 2011. ACM SIGSOFT Softw. Eng. Notes 36(5): 33-35 (2011) - [c12]Nanette Brown, Robert L. Nord, Ipek Ozkaya, Philippe Kruchten, Erin Lim:
Hard choice: A game for balancing strategy for agility. CSEE&T 2011: 553 - [c11]Robert L. Nord, Nanette Brown, Ipek Ozkaya:
Architecting with just enough information. SHARK@ICSE 2011: 9-12 - [c10]Ipek Ozkaya, Philippe Kruchten, Robert L. Nord, Nanette Brown:
Second international workshop on managing technical debt: (MTD 2011). ICSE 2011: 1212-1213 - [c9]Len Bass, Rick Kazman, Ipek Ozkaya:
Developing Architectural Documentation for the Hadoop Distributed File System. OSS 2011: 50-61 - [c8]Nanette Brown, Robert L. Nord, Ipek Ozkaya, Manuel Pais:
Analysis and Management of Architectural Dependencies in Iterative Release Planning. WICSA 2011: 103-112 - [e1]Ipek Ozkaya, Philippe Kruchten, Robert L. Nord, Nanette Brown:
Proceedings of the 2nd Workshop on Managing Technical Debt, MTD 2011, Waikiki, Honolulu, HI, USA, May 23, 2011. ACM 2011, ISBN 978-1-4503-0586-0 [contents] - 2010
- [c7]Ipek Ozkaya, J. Andrés Díaz Pace, Arie Gurfinkel, Sagar Chaki:
Using Architecturally Significant Requirements for Guiding System Evolution. CSMR 2010: 127-136 - [c6]Ipek Ozkaya, Peter Wallin, Jakob Axelsson:
Architecture knowledge management during system evolution: observations from practitioners. SHARK@ICSE 2010: 52-59 - [c5]S. Jeromy Carrière, Rick Kazman, Ipek Ozkaya:
A cost-benefit framework for making architectural decisions in a business context. ICSE (2) 2010: 149-157 - [c4]