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

Noboru Fujimaki

dblp:76/543 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1998
—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
Software maintenance and evolution · 77% Requirements engineering and software design · 23%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software reuse
0.011998
A Systematic Approach to Domain-Oriented Software Development · ICSE 1998
Requirements engineering and software design › requirements analysis
domain analysis
0.011998
A Systematic Approach to Domain-Oriented Software Development · ICSE 1998

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

domain framework · 0.0CASE tools · 0.0
YearPublicationVenuePosition
1998 A Systematic Approach to Domain-Oriented Software Development
abstract
We describe our experience with domain-oriented software development in the domain of automatic teller machine applications. We systematically proceeded with development in four phases: domain analysis, domain formalization, domain facility building, and product development. In this development, we built domain facilities consisting of a domain framework and domain CASE (Computer Aided Software Engineering) tools, then employed them for application development. The framework shared about 4% of the application, and the remaining 96% was generated by the CASE tools automatically. Our approach was found to realize effective reuse of design and implementation and to enable domain-oriented development in large domains.
Yoko Shimizu, Noboru Fujimaki, Masayuki Hirayama
ICSE2