Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Anand Raghavendran

dblp:40/2936 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1995
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 33% Requirements engineering and software design · 33% Software maintenance and evolution · 33%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › requirements analysis
domain analysis
0.011995
An Organizational Learning Approach to Domain Analysis · ICSE 1995
Empirical software engineering
mining software repositories
0.011995
An Organizational Learning Approach to Domain Analysis · ICSE 1995
Software maintenance and evolution
software reuse
0.011995
An Organizational Learning Approach to Domain Analysis · ICSE 1995

Methods — techniques the papers use, named apart from their topics

organizational learning · 0.0case-based reasoning · 0.0
YearPublicationVenuePosition
1995 An Organizational Learning Approach to Domain Analysis
abstract
As the application of computer technology continues to proliferate and diversify, the identification and understanding of application domains is becoming increasingly important to software development methodologies.Domain analysis techniques have been developed to accumulate and formalize the knowledge necessary for successful software reuse.These techniques have been shown to be useful, but suffer from defining the domain too restrictively, burying important relationships deep in domain taxonomies, and prohibiting flexible identification of domains with common issues.Techniques are needed that dynamically detect recurring patterns of activities in development projects, This paper presents a method for developing and refining the knowledge and experience accumulated by a development organization so it can learn from previous efforts.A case-based repository of project experiences supports the re-use and refinement of domain knowledge to reduce duplicate effort, build on successful efforts, and avoid repeating mistakes in the process of building quality software systems.
Scott Henninger, Kris Lappala, Anand Raghavendran
ICSE3