MétaCan
Menu
Back to cohort
Record W4399793788 · doi:10.32920/26052496.v1

Engineering Stakeholders' Viewpoint-concerns for Architecting a Modern Enterprise

2024· preprint· en· W4399793788 on OpenAlexaff
Mujahid Sultan

Bibliographic record

Venuenot available
Typepreprint
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsToronto Metropolitan UniversityUniversity of Toronto
Fundersnot available
KeywordsBusinessProcess managementEngineering managementComputer scienceSystems engineeringEngineering

Abstract

fetched live from OpenAlex

Stakeholders in an enterprise have diverse concerns from a variety of viewpoints. Designers of the enterprise and its systems elicit, analyze, and engineer stakeholders' viewpoint concerns. Most, if not all, of the stakeholders' concerns, are written in natural language. Ambiguity is omnipresent when it comes to describing viewpoint concerns in natural language. This ambiguity may lead to sub-par requirements for systems design and documenting enterprise blueprints. Many requirements elicitation methods and enterprise architecture frameworks emerged in past decades and gained popularity. None of these linked the viewpoint concerns to natural language lexical and semantic constructs. In this dissertation, we describe English language interrogative investigations and their semantic and lexical relationships to formulate better viewpoint concerns for stakeholders. We included two publications, primarily for waterfall software development lifecycles and monolith applications, one on requirements engineering and the other on enterprise architecture. In the past decade, widespread adoption of agile project management, independent delivery with microservices, and automated deployment with DevOps has tremendously sped up systems development. Microservices are provisioned and accessed via application programming interfaces (APIs). APIs carry business value and have created an API economy for enterprises. The link between stakeholders’ concerns and microservices/APIs is not well captured nor adequately defined. We included a third publication in this dissertation that addresses these issues.Based on the publications included in the dissertation, we created a tool that uses a natural language generation system to auto formulate stakeholder viewpoint concerns for a system.

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 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.001
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: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.698
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.000
Open science0.0010.003
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.072
GPT teacher head0.304
Teacher spread0.232 · 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 teacher head, not a consensus.

Study designSimulation or modeling
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

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207