People, Organizations, and Process Improvement
IEEE Software
The role of knowledge in software development
Communications of the ACM
A Coding Scheme to Support Systematic Analysis of Software Comprehension
IEEE Transactions on Software Engineering
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Process-Based Software Engineering: Building the Infrastructures
Annals of Software Engineering
A quantitative and qualitative analysis of factors affecting software processes
Journal of Systems and Software
Integrated Requirements Engineering: A Tutorial
IEEE Software
Monitoring GSD projects via shared mental models: a suggested approach
Proceedings of the 2006 international workshop on Global software development for the practitioner
Towards software process patterns: An empirical analysis of the behavior of student teams
Information and Software Technology
A framework for understanding creativity in requirements engineering
Information and Software Technology
The learning component in social software engineering
Proceedings of the 4th international workshop on Social software engineering
| Hi-index | 0.00 |
Software development is a complex, mainly cognitive endeavor.What is specific about software engineering relative to other engineering disciplines, and how can we measure what can be improved?Many concepts, such as problem solving and opportunistic design, are common to all engineering disciplines. The author reviews these concepts from a software engineering perspective in order to highlight their links to software practices. Software engineering activities are composed of cognitive actions performed by human beings. For many years, researchers and developers have helped improve software engineering practice by suggesting various intuitive approaches, proposing modeling techniques, and presenting case studies of successful projects. Real and durable improvements are likely to emerge from a scientific approach based on observation and measurement of real human behaviors. Based on results from measuring cognitive actions, the author proposes synchronization meetings to improve practices with a high degree of opportunistic problem-solving content.