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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Oyindamola Olajubu

dblp:167/7859 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2015
—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 · 67% Programming languages and type systems · 33%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
domain-specific languages		 0.212015
A textual domain specific language for requirement modelling · ESEC/SIGSOFT FSE 2015
Requirements engineering and software design
requirements modeling		 0.212015
A textual domain specific language for requirement modelling · ESEC/SIGSOFT FSE 2015
Requirements engineering and software design
requirements specification		 0.212015
A textual domain specific language for requirement modelling · ESEC/SIGSOFT FSE 2015

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

domain-specific language · 0.2
YearPublicationVenuePosition
2015 A textual domain specific language for requirement modelling
abstract
Requirement specification is usually done with a combination of Natural Language (NL) and informal diagrams. Modeling approaches to support requirement engineering activities have involved a combination of text and graphical models. In this work, a textual domain specific modelling notation for requirement specification is presented. How certain requirement quality attributes are addressed using this notation is also demonstrated.
Oyindamola Olajubu
 ESEC/SIGSOFT FSE1