Deriving Software Services and Goals they Achieve from Business Process Models
Bibliographic record
Abstract
Modern organizations implement information systems (IS) to support their business processes. Service-Oriented Architecture (SOA) has become a well-established architectural style for designing modular, flexible, and scalable IS solutions. Centred on the concept of “service”, SOA promotes alignment between business process models and IS models through welldefined design principles. However, designing SOA services remains a complex task that requires significant technical expertise in both IS architecture and business processes. A key challenge when designing SOA-based ISs is identifying services that both automate process activities and align with business collaboration goals. This article introduces a new method called Business Process Models to SOA Services and Goals (BPM2SOAG) to design SOA-based ISs from collaborative process models. BPM2SOAG generates a Service-Goal architecture model that links identified software services to (i) the process activities they automate and (ii) the objectives of the collaboration they satisfy. BPM2SOAG uses business objectives and quality attributes derived from business patterns and a business transaction ontology to build ServiceGoal architecture models. Moreover, BPM2SOAG allows the architecture practitioners (such as business and solution architects) to automatically compute a score that evaluates the effectiveness of the software services in automating the process activities and satisfying the objectives of the business collaboration.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.014 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.007 | 0.004 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.005 | 0.006 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.002 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".