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.

Nozomi Ikeya

dblp:68/1249 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2006
0000-0002-0241-7470ORCID · reported

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 · 44% Requirements engineering and software design · 44% Software maintenance and evolution · 13%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
design knowledge
0.112006
The problem of knowledge decoupling in software development projects · ICSE 2006
Empirical software engineering
developer studies
0.112006
The problem of knowledge decoupling in software development projects · ICSE 2006
Software maintenance and evolution
software integration
0.012006
The problem of knowledge decoupling in software development projects · ICSE 2006

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

ethnographic investigation · 0.1
YearPublicationVenuePosition
2006 The problem of knowledge decoupling in software development projects
abstract
In our ethnographic investigation of software integration projects a recurrent pattern emerges. The detailed understanding leaders have of the design and development decreases over time as they become busier and busier attending meetings, creating documents, and resolving issues and thus cannot spend much time on design or development work. As a result, their leadership becomes increasingly decoupled from the work of the project. We discuss various dimensions of this problem.
Yutaka Yamauchi, Jack Whalen, Nozomi Ikeya, Erik Vinkhuyzen
ICSE3