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.

Kanth Miriyala

dblp:92/858 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1997
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 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
2 papers
Requirements engineering and software design · 50% Empirical software engineering · 35% Program synthesis and code generation · 15%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › specification
specification generation
0.011991
Automatic Derivation of Formal Software Specifications From Informal Descriptions · IEEE Trans. Software Eng. 1991
Empirical software engineering
developer studies
0.011997
Panel on Collaborative Software Engineering · ICSE 1997
Program synthesis and code generation › knowledge-based program synthesis
program synthesis by analogy
0.011991
Automatic Derivation of Formal Software Specifications From Informal Descriptions · IEEE Trans. Software Eng. 1991

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

schema instantiation · 0.0difference-based reasoning · 0.0analogy mapping · 0.0
YearPublicationVenuePosition
1997 Panel on Collaborative Software Engineering
abstract
No abstract available.
Prasun Dewan, Kanth Miriyala, Remo Pareschi
ICSE3
1994 An architecture-driven, business-specific, and component-based approach to software engineering
abstract
The paper describes an approach to software reuse which is under development and evaluation at Andersen Consulting. Instead of restricting reuse to just code, we are exploring reuse of architectures that include component interfaces, interconnections between components, and platform configuration. The approach assumes that first a desired architecture is chosen and tailored according to the constraints at hand. Then, appropriate components are retrieved from a repository, subjected to restricted modifications if necessary and "glued" together following the architectural guidelines. Finally, a version of a system is automatically packaged from the selected components and the architectural specifications. The paper presents the approach and some initial experiments in the design of an interface specification language and an environment in which modules can be interconnected and their interface specifications used to determining the integrity of the connections.>
Jim Q. Ning, Kanth Miriyala, Wojtek Kozaczynski
ICSR2
1991 Automatic Derivation of Formal Software Specifications From Informal Descriptions
abstract
SPECIFIER, an interactive system which derives formal specifications of data types and programs from their informal descriptions, is described. The process of deriving formal specifications is viewed as a problem-solving process. The system uses common problem-solving techniques such as schemas, analogy, and difference-based reasoning to derive formal specifications. If an informal description is a commonly occurring operation for which the system has a schema, then the formal specification is derived by instantiating the schema. If there is a no such schema, SPECIFIER tries to find a previously solved problem which is analogous to the current problem. If the problem found is directly analogous to the current problem, it applies an analogy mapping to obtain a formal specification. On the other hand, if the analogy found is only approximate, it solves the directly analogous part of the problem by analogy and performs difference-based reasoning using the remaining (unmatched) parts to transform the formal specification obtained by analogy to a formal specification for the entire original problem.>
Kanth Miriyala, Mehdi T. Harandi
IEEE Trans. Software Eng.1