MétaCan
Menu
Back to cohort
Record W2144437058 · doi:10.1109/ccece.2005.1557447

How can i* complement uml for modeling organizations?

2006· article· en· W2144437058 on OpenAlexaff
Subhas Chandra Misra, Vinod Kumar, Uma Kumar

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsCarleton University
Fundersnot available
KeywordsUnified Modeling LanguageComputer scienceApplications of UMLModeling languageEnterprise modellingObject Constraint LanguageSoftware engineeringUML toolProcess modelingTable (database)Process (computing)Complement (music)Systems engineeringKnowledge managementProgramming languageDatabaseEnterprise integrationWork in processEngineeringSoftwareEnterprise software

Abstract

fetched live from OpenAlex

This paper presents a thorough investigation of the two popular enterprise modeling techniques: the UML-based, and the i*-based, and the research efforts undertaken using these modeling techniques. However, this paper does not provide a survey and/or explain these two enterprise-modeling techniques exhaustively. It aims at analyzing how these two techniques are complementary to each other and providing some guidance regarding selecting an appropriate modeling technique. Many interesting information that can help in deciding the modeling technique have been summarized in a comparison-table that we have developed. UML fails to address different challenges for modeling modern day enterprises, i* modeling language can address these issues by capturing the motivations, intents, and rationales behind the activities. However, i* cannot address "what" steps a process consists of, and "how" those steps are to be done as UML can address. Thus, i* complements UML in modeling a project

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.022
metaresearch head score (Gemma)0.040
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.022
Threshold uncertainty score0.116

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0220.040
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0020.003
Bibliometrics0.0040.004
Science and technology studies0.0010.006
Scholarly communication0.0100.033
Open science0.0040.007
Research integrity0.0020.005
Insufficient payload (model declined to judge)0.0040.003

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.013
GPT teacher head0.224
Teacher spread0.211 · 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

Citations0
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicService-Oriented Architecture and Web ServicesFrench-language works237,207