MétaCan
Menu
Back to cohort
Record W1491459646 · doi:10.1109/sefm.2004.18

Formal derivation of functional architectural design

2004· article· en· W1491459646 on OpenAlexaff
Ridha Khédri, Imen Bourguiba

Bibliographic record

VenueSoftware Engineering and Formal Methods · 2004
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsMcMaster University
Fundersnot available
KeywordsComputer scienceFunctional requirementArchitectural geometryComponent (thermodynamics)Architectural patternSoftware engineeringArchitectural designFormal specificationMainstreamSystems engineeringSoftware designProgramming languageSoftwareArchitectureSoftware developmentEngineeringSoftware construction

Abstract

fetched live from OpenAlex

One of the drawbacks of mainstream design methods is that their processes are based on crafty procedures rather than on rigorous mathematically founded procedures. Software designers spend a lot of time attempting to come up with an Architectural Design that is very often inefficient and not directly and systematically derived from the requirements. The lack of a systematic and a mathematical way to decompose the requirements into simpler pieces (components) leads to inconsistency of different parts of the designed system. This paper proposes a two stages architectural design as well as attempts to answer the following questions: (1) How can we derive the functional structure of the system (i.e., functional architectural design) from its functional requirements? (2) What are the mathematical properties of an architectural component? (3) What kind of connectors might we have between these components? We adopt a state-oriented relational approach to the specification of the requirements and to the specification and the derivation of the architectural design.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.008
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.004
Threshold uncertainty score0.021

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.008
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0010.004
Scholarly communication0.0020.002
Open science0.0010.002
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0040.001

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.044
GPT teacher head0.294
Teacher spread0.250 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2004
Admission routes1
Has abstractyes

Explore more

Same venueSoftware Engineering and Formal MethodsSame topicAdvanced Software Engineering MethodologiesFrench-language works237,207