PapersFlow Research Brief
Software Engineering Techniques and Practices
Research Guide
What is Software Engineering Techniques and Practices?
Software Engineering Techniques and Practices is the cluster of methodologies, empirical studies, and processes in software engineering research that encompasses agile software development, requirements engineering, global software development, systematic literature reviews, project risk management, pair programming, software process improvement, user feedback, and continuous integration.
This field includes 88,787 works focused on improving software development processes through empirical methods and practical techniques. Key areas cover agile practices like Extreme Programming, usability engineering, object-oriented metrics, software architecture, and evidence-based approaches such as systematic literature reviews. Growth data over the past 5 years is not available.
Topic Hierarchy
Research Sub-Topics
Agile Software Development Practices
Researchers conduct empirical studies on Scrum, Kanban, and XP implementation challenges, team dynamics, and velocity metrics. Meta-analyses synthesize success factors across domains.
Requirements Engineering in Software Projects
This sub-topic examines elicitation techniques, traceability, volatility management, and user involvement strategies. Controlled experiments test RE method efficacy on project outcomes.
Global Software Development Coordination
Studies address temporal, geographical, and cultural distance mitigation through tools, processes, and trust-building. Case studies analyze offshore outsourcing team performance.
Systematic Literature Reviews in Software Engineering
Researchers develop protocols for SLRs, mapping studies, and evidence-based guidelines in SE. Meta-research evaluates SLR methodological quality and impact.
Software Process Improvement Frameworks
This area evaluates CMMI, ISO 15504, and SPIRE models through longitudinal organizational case studies. ROI analyses quantify maturity level advancement benefits.
Why It Matters
Software engineering techniques enable teams to deliver reliable software under constraints, as shown in Beck (2000) where Extreme Programming supports small teams in volatile environments to produce business value consistently. Nielsen (1993) provides methods for cost-effective usability improvements that developers apply immediately to enhance user interfaces in products. Chidamber and Kemerer (1994) introduced a metrics suite for object-oriented design that managers use to focus on process improvements in information technology delivery, with the work cited 5613 times for its role in software quality assessment. Kitchenham et al. (2008) established systematic literature reviews as the core method for evidence-based software engineering, aggregating findings from studies to guide practitioners in requirements engineering and risk management.
Reading Guide
Where to Start
"Extreme Programming Explained: Embrace Change" by Kent Beck (2000) is the beginner start because it introduces agile practices accessibly for small teams, explaining how to embrace change with concrete methods like pair programming.
Key Papers Explained
Beck (2000) "Extreme Programming Explained: Embrace Change" lays agile foundations, which Chidamber and Kemerer (1994) "A metrics suite for object oriented design" complements by providing measurable quality indicators for process improvement. Nielsen (1993) "Usability Engineering" extends these with user-centered techniques, while Kitchenham et al. (2008) "Systematic literature reviews in software engineering – A systematic literature review" offers evidence aggregation methods to validate them empirically. Bass et al. (1997) "Software Architecture in Practice" builds on all by structuring designs that incorporate metrics, usability, and agile principles.
Paper Timeline
Most-cited paper highlighted in red. Papers ordered chronologically.
Advanced Directions
Wohlin et al. (2012) "Experimentation in Software Engineering" advances empirical validation of techniques like those in Beck (2000) and Chidamber (1994). Benbasat et al. (1987) "The Case Research Strategy in Studies of Information Systems" supports qualitative depth for global development challenges.
Papers at a Glance
| # | Paper | Year | Venue | Citations | Open Access |
|---|---|---|---|---|---|
| 1 | Computers and Intractability: A Guide to the Theory of NP-Comp... | 1979 | — | 44.4K | ✕ |
| 2 | Usability Engineering | 1993 | — | 9.4K | ✕ |
| 3 | Software engineering: A practitioner's approach | 1983 | Advances in Engineerin... | 8.3K | ✕ |
| 4 | Quasi-experimentation: Design and analysis issues for field se... | 1980 | Evaluation and Program... | 6.1K | ✕ |
| 5 | Extreme Programming Explained: Embrace Change | 2000 | — | 5.9K | ✕ |
| 6 | A metrics suite for object oriented design | 1994 | IEEE Transactions on S... | 5.6K | ✕ |
| 7 | Software Architecture in Practice | 1997 | — | 5.1K | ✕ |
| 8 | The Case Research Strategy in Studies of Information Systems | 1987 | MIS Quarterly | 4.7K | ✕ |
| 9 | Systematic literature reviews in software engineering – A syst... | 2008 | Information and Softwa... | 4.2K | ✓ |
| 10 | Experimentation in Software Engineering | 2012 | — | 4.1K | ✕ |
Frequently Asked Questions
What is Extreme Programming in software engineering?
Extreme Programming (XP) is an agile methodology for small teams facing rapidly changing requirements. Kent Beck (2000) in "Extreme Programming Explained: Embrace Change" describes XP as enabling fun, productive projects that deliver business value under control through practices like pair programming and continuous integration.
How are systematic literature reviews conducted in software engineering?
Systematic literature reviews (SLRs) aggregate evidence using standardized protocols introduced in evidence-based software engineering. Kitchenham et al. (2008) in "Systematic literature reviews in software engineering – A systematic literature review" assessed SLRs' impact, finding them the recommended method with 4207 citations. The process involves defined search, selection, and synthesis steps for reproducible results.
What metrics evaluate object-oriented software design?
A metrics suite for object-oriented design measures aspects like coupling and cohesion to support process improvement. Chidamber and Kemerer (1994) in "A metrics suite for object oriented design" proposed these metrics, cited 5613 times, to help managers address software development quality in information technology applications.
Why use case research in information systems studies?
Case research provides in-depth qualitative insights into information systems phenomena. Benbasat et al. (1987) in "The Case Research Strategy in Studies of Information Systems" define the strategy, offer evaluation criteria, and categorize cases, with 4680 citations for guiding empirical software engineering investigations.
What is the role of software architecture in practice?
Software architecture structures systems to meet quality attributes like performance and maintainability. Bass et al. (1997) in "Software Architecture in Practice" introduce concepts from SEI's curriculum for engineers and managers, cited 5051 times, combining theory with pedagogical approaches for design and management.
How is experimentation designed in software engineering?
Experimentation in software engineering uses controlled and field studies to validate techniques empirically. Wohlin et al. (2012) in "Experimentation in Software Engineering" cover design and analysis, cited 4122 times, providing methods for quasi-experiments as in Shrout (1980).
Open Research Questions
- ? How can systematic literature reviews be adapted for rapidly evolving agile practices?
- ? What empirical evidence supports pair programming's impact on defect rates in global software development?
- ? Which object-oriented metrics best predict maintainability in continuous integration pipelines?
- ? How do usability engineering methods integrate with modern software architecture for user feedback loops?
- ? What risk management techniques from project studies scale to large-scale requirements engineering?
Recent Trends
The field maintains 88,787 works with no specified 5-year growth rate; established papers like Kitchenham et al. with 4207 citations continue dominating citations without recent preprints or news in the last 12 months.
2008Research Software Engineering Techniques and Practices with AI
PapersFlow provides specialized AI tools for Computer Science researchers. Here are the most relevant for this topic:
AI Literature Review
Automate paper discovery and synthesis across 474M+ papers
Code & Data Discovery
Find datasets, code repositories, and computational tools
Deep Research Reports
Multi-source evidence synthesis with counter-evidence
AI Academic Writing
Write research papers with AI assistance and LaTeX support
See how researchers in Computer Science & AI use PapersFlow
Field-specific workflows, example queries, and use cases.
Start Researching Software Engineering Techniques and Practices with AI
Search 474M+ papers, run AI-powered literature reviews, and write with integrated citations — all in one workspace.
See how PapersFlow works for Computer Science researchers