Her primary areas of investigation include Software development, Technical debt, Software engineering, Software maintenance and Debt. When carried out as part of a general Software development research project, her work on Social software engineering and Software development process is frequently linked to work in Context, therefore connecting diverse disciplines of study. Carolyn Seaman has researched Technical debt in several fields, including Software quality and Code smell.
Her studies deal with areas such as Package development process, Personal software process, Software walkthrough and Empirical process as well as Software engineering. Her research integrates issues of User interface, Project management and Software analytics in her study of Software walkthrough. Her work in Debt addresses subjects such as Risk analysis, which are connected to disciplines such as Management science and Principal.
Carolyn Seaman focuses on Software development, Software engineering, Technical debt, Software and Knowledge management. Personal software process, Software peer review, Software construction, Social software engineering and Software development process are subfields of Software development in which her conducts study. Her work is dedicated to discovering how Software peer review, Software analytics are connected with Software sizing and other disciplines.
Carolyn Seaman merges Software engineering with Empirical research in her study. Her Technical debt study integrates concerns from other disciplines, such as Software maintenance, Management science, Risk analysis, Debt and Software quality. Her Software research is multidisciplinary, incorporating elements of Agile software development, Task and Data science.
Carolyn Seaman mainly investigates Technical debt, Software, Debt, Software development and Knowledge management. Her work carried out in the field of Technical debt brings together such families of science as Software maintenance, Engineering management, Risk analysis, Payment and Software quality. The various areas that Carolyn Seaman examines in her Software maintenance study include Management science and Identification.
Her study looks at the relationship between Software and topics such as Data science, which overlap with Source code and Concept map. Her Software development research integrates issues from Software system and Software engineering. Her Software peer review study combines topics in areas such as Software analytics and Social software engineering.
Technical debt, Debt, Risk analysis, Software maintenance and Software development are her primary areas of study. Her Technical debt study which covers Engineering management that intersects with Agile software development, Software analytics, Software peer review and Software sizing. The Risk analysis study combines topics in areas such as Quality, Maintainability and Scale.
Her biological study spans a wide range of topics, including Maturity, Software quality, Management science and Identification. Carolyn Seaman is interested in Software project management, which is a branch of Software development. Her Software project management study combines topics from a wide range of disciplines, such as Software verification and validation and Software engineering.
This overview was generated by a machine learning system which analysed the scientist’s body of work. If you have any feedback, you can contact us here.
Qualitative methods in empirical studies of software engineering
C.B. Seaman.
IEEE Transactions on Software Engineering (1999)
Managing technical debt in software-reliant systems
Nanette Brown;Yuanfang Cai;Yuepu Guo;Rick Kazman.
international conference on software engineering (2010)
Using the ISO/IEC 9126 product quality model to classify defects: A controlled experiment
Antonio Vetro;Nico Zazworka;Carolyn B. Seaman;Forrest Shull.
evaluation and assessment in software engineering (2012)
Practical Software Maintenance
Carolyn B. Seaman.
Journal of Software Maintenance: Research and Practice (2000)
Measuring and Monitoring Technical Debt
Carolyn B. Seaman;Yuepu Guo.
Advances in Computers (2011)
A Balancing Act: What Software Practitioners Have to Say about Technical Debt
E. Lim;N. Taksande;C. Seaman.
IEEE Software (2012)
Linking Software Development and Business Strategy Through Measurement
Victor R Basili;Mikael Lindvall;Myrna Regardie;Carolyn Seaman.
(2010)
Identification and management of technical debt
Nicolli S.R. Alves;Thiago S. Mendes;Manoel G. de Mendonça;Rodrigo O. Spínola.
Information & Software Technology (2016)
Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162)
Paris Avgeriou;Philippe Kruchten;Ipek Ozkaya;Carolyn B. Seaman.
(2016)
Investigating the impact of design debt on software quality
Nico Zazworka;Michele A. Shaw;Forrest Shull;Carolyn Seaman.
Proceedings of the 2nd Workshop on Managing Technical Debt (2011)
If you think any of the details on this page are incorrect, let us know.
We appreciate your kind effort to assist us to improve this page, it would be helpful providing us with as much detail as possible in the text box below:
University of Maryland, College Park
Carnegie Mellon University
University of British Columbia
Reutlingen University
University of Groningen
University of Maryland, College Park
University of Washington
Mayo Clinic
University of Ottawa
Karlsruhe Institute of Technology
University of Arkansas at Fayetteville
University of Warwick
Curtin University
Claude Bernard University Lyon 1
University of California, Berkeley
Tsinghua University
Yamaguchi University
Mayo Clinic
University of Delhi
Heidelberg University
RMIT University
Linköping University
University Hospital of Basel
Beth Israel Deaconess Medical Center
Media NeuroConsultants
Durham University