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

Kevin W. Jameson

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

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

Software engineering, systems software and programming languages · 1 · 1 first-author

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
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software design
design reuse
0.011989
A Model for the Reuse of Software Design Information · ICSE 1989
Requirements engineering and software design
software architecture
0.011989
A Model for the Reuse of Software Design Information · ICSE 1989

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

tagged design templates · 0.0reversible transformation · 0.0
YearPublicationVenuePosition
1989 A Model for the Reuse of Software Design Information
abstract
This paper presents a general model for the representation and manipulation of module level software design information, leading to the effective reuse of software design information across different programming languages.Language independent design documents are represented as ASCII files containing tagged design information sufficient for the construction of a compilable program architecture.The resulting architecture is composed of documented module stubs which describe calling relationships, parameters, functional descriptions, and algorithms characteristic of the architecture.No executable code is included in the compilable modules.Frameworks of tagged locations in Zanguage dependent standard module templates are matched against corresponding tags in the ASCII design files, effectively blending language dependent and independent information into a compilable stub architecture.The process is reversible in that a language independent design file can be generated from an architecture in the standard tagged format, thus supporting the movement of design information across different programming languages.
Kevin W. Jameson
ICSE1