MétaCan
Menu
Back to cohort
Record W82013199

On verifying the use of a pattern language in model driven design

2009· dissertation· en· W82013199 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueSpectrum Research Repository (Concordia University) · 2009
Typedissertation
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsConcordia University
FundersDalhousie UniversityConcordia University
KeywordsComputer scienceRotation formalisms in three dimensionsProgramming languageSoftware design patternUnified Modeling LanguageCompilerPattern language (formal languages)SublanguageNatural language processingModeling languageArtificial intelligenceSoftware
DOInot available

Abstract

fetched live from OpenAlex

This thesis addresses the problem of verifying the application of a Pattern Language in a design that is built based upon the patterns of the language in a Model-Driven approach. Exploiting the ideas of compilers, we propose a process named Pattern Language Verifier (PLV). We argue that building a PLV for a given Pattern Language, requires the Structural, Syntactic, and Semantic rules of the language to be precisely defined. We present three formalisms for defining these three groups of rules. PLV is a profile-driven process and assumes that a UML Profile is already defined for the underlying Pattern Language. PLV consists of four phases: Pattern Structural Verifier (PSV), Pattern Language Syntactic Verifier (PTV), Pattern Language Semantic Verifier (PMV), and Pattern Language Advisor (PLA). PSV verifies the structure of every single pattern used in the design model. PTV verifies the relationships between the detected patterns. PMV verifies the semantic aspects of the patterns. PLA reports the problems to the designer and guides him/her in fixing the errors. For the case study, a group of enterprise architectural patterns is selected as the Pattern Language. The Structural, Syntactic, and Semantic rules of the language are defined using the proposed formalism, and a UML Profile is defined for the language. A PLV is designed and implemented as an integration into an open source modeling tool. The tool is then utilized in designing a sample web application: Online Student Registration System. The usefulness of the tool is represented by walkthrough scenarios that show finding the mistakes in the model and helping the designer repair the detected problems

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.832
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.059
GPT teacher head0.287
Teacher spread0.229 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it