Commit 1231932d authored by Alexander Philipp Nowosad's avatar Alexander Philipp Nowosad
Browse files

Rename company model to composed model

parent 6af78a51
<ng-template #createModal let-d="dismiss">
<div class="modal-header">
<h4 class="modal-title" id="modal-basic-title">Create Company Model</h4>
<h4 class="modal-title" id="modal-basic-title">Create Composed Model</h4>
<button type="button" class="close" aria-label="Close" (click)="d()">
<span aria-hidden="true">&times;</span>
</button>
......@@ -18,7 +18,7 @@
class="btn btn-sm btn-dark btn-block"
[disabled]="!createForm.valid"
>
Create Company Model
Create Composed Model
</button>
</div>
</div>
......@@ -30,7 +30,7 @@
<ng-container [formGroup]="formGroup">
<div class="form-group form-row">
<label for="companyModelSelector" class="col-sm-6 col-form-label"
>Company Model</label
>Composed Model</label
>
<div class="col-sm-6 input-group">
<select
......@@ -66,7 +66,7 @@
class="btn btn-primary ml-auto"
(click)="openCreateCompanyModelModal()"
>
Create new Company Model
Create new Composed Model
</button>
</div>
</ng-container>
......@@ -26,7 +26,7 @@
</div>
<div class="my-3 p-3 bg-white rounded shadow-sm">
<h6 class="border-bottom border-gray pb-2 mb-0">Edit Company Model</h6>
<h6 class="border-bottom border-gray pb-2 mb-0">Edit Composed Model</h6>
<div class="text-muted pt-3">
<app-feature-model-form
[featureModel]="companyModel"
......
......@@ -3,21 +3,21 @@
(dismiss)="d()"
(delete)="deleteCompanyModel(modalCompanyModel._id); c()"
>
<div modalTitle>Delete Company Model {{ modalCompanyModel.name }}</div>
You are deleting the company model {{ modalCompanyModel.name }}. This can
<div modalTitle>Delete Composed Model {{ modalCompanyModel.name }}</div>
You are deleting the composed model {{ modalCompanyModel.name }}. This can
not be undone.
</app-delete-modal>
</ng-template>
<main role="main" class="container">
<div class="my-3 p-3 bg-white rounded shadow-sm">
<h6 class="border-bottom border-gray pb-2">Company Models</h6>
<h6 class="border-bottom border-gray pb-2">Composed Models</h6>
<p class="mt-1">
Company Models are used to represent merged canvas building blocks.
Composed Models are used to represent merged canvas building blocks.
</p>
<app-model-list
modelListTitle="List of Company Business Knowledge Models"
modelFormTitle="Add Company Business Knowledge Model"
modelListTitle="List of Composed Models"
modelFormTitle="Add Composed Model"
(viewModel)="viewCompanyModel($event)"
(editModel)="editCompanyModel($event)"
(deleteModel)="openDeleteCompanyModelModal($event)"
......
......@@ -16,7 +16,7 @@
{{
featureModel.hasOwnProperty('version')
? 'Canvas Building Block'
: 'Company Model'
: 'Composed Model'
}}
</td>
</tr>
......
......@@ -29,7 +29,7 @@
{{
featureModel.hasOwnProperty('version')
? 'Canvas Building Block'
: 'Company Model'
: 'Composed Model'
}}
</td>
</tr>
......
......@@ -100,7 +100,7 @@
<div class="alert alert-warning" role="alert">
<p>
This will add all subfeatures of
{{ modalFeature ? modalFeature.name : 'the model' }} to the company
{{ modalFeature ? modalFeature.name : 'the model' }} to the composed
model as new features if they are not merged yet.
</p>
</div>
......@@ -225,21 +225,20 @@
<div class="alert alert-info container" role="alert">
<p>
Merge all features from the canvas building block on the left into the
company knowledge model on the right. This can be done in three
different ways:
composed model on the right. This can be done in three different ways:
</p>
<ul>
<li>
Add all: Add all subfeatures that are not yet merged to the company
knowledge model.
Add all: Add all subfeatures that are not yet merged to the composed
model.
</li>
<li>
Add: Add the feature to the company knowledge model. Opens a pre
filled feature form to adjust the feature.
Add: Add the feature to the composed model. Opens a pre filled feature
form to adjust the feature.
</li>
<li>
Select: Select the corresponding feature in the company knowledge
model. This just creates a trace.
Select: Select the corresponding feature in the composed model. This
just creates a trace.
</li>
</ul>
</div>
......
......@@ -20,20 +20,20 @@
to create a canvas building block and can show errors if a canvas building
block does not allow the creation of consistent derived business models due
to too restrictive constraints. After creating or importing canvas building
blocks the user is able to merge these models into company knowledge models.
blocks the user is able to merge these blocks into composed models.
</p>
<p>
Canvas building blocks support the creation of patterns and example business
models. These patterns and examples can be used in company models later to
models. These patterns and examples can be used in composed models later to
compare derived business models with them or to give hints about possible
patterns to the user.
</p>
<p>
New business model decisions of single business models are synchronized with
the corresponding feature model to ensure consistency. Moreover, the
conformance of business models can be checked with the feature model and
the corresponding composed model to ensure consistency. Moreover, the
conformance of business models can be checked with the composed model and
occurring conformance errors are explained. Additionally the tool checks for
strengths and weaknesses of the business model and gives hints about
patterns and possible supportive features. It is also possible to compare
......@@ -67,12 +67,11 @@
<figure class="figure">
<img
src="assets/bmdl_company.png"
alt="Company knowledge model page"
alt="Composed Model page"
class="carousel-image figure-img"
/>
<figcaption class="figure-caption">
2. Create the company knowledge model by merging canvas building
blocks
2. Create the composed model by merging canvas building blocks
</figcaption>
</figure>
</ng-template>
......@@ -118,13 +117,13 @@
instances of the canvas building block.
</li>
<li>
<strong>Create Company knowledge Model:</strong> In the second step, a
method engineer can create a company knowledge model. While creating it
the developer selects canvas building blocks that should be merged into
the company knowledge model and later merge it manually into the company
model. After that the method engineer can edit the company model and adapt
it. In this step it is also possible to see conflicting requirements that
lead to the impossibility to create conform derived business models.
<strong>Create Composed Model:</strong> In the second step, a method
engineer can create a composed model. While creating it the developer
selects canvas building blocks that should be merged into the composed
model and later merge it manually into the composed model. After that the
method engineer can edit the composed model and adapt it. In this step it
is also possible to see conflicting requirements that lead to the
impossibility to create conform derived business models.
</li>
<li>
<strong>Derive Business Models:</strong> In the third step, the business
......@@ -132,16 +131,16 @@
Here, he can use the existing features from the feature model or add new
business model decisions. These new feature model decisions will be added
to the feature model to save consistency. Here it also possible to check
the conformance between the company knowledge model and the business
model. Conformance errors will be explained to support the resolution. It
is also possible to show weaknesses (due to hurts cross-tree relation) and
the conformance between the composed model and the business model.
Conformance errors will be explained to support the resolution. It is also
possible to show weaknesses (due to hurts cross-tree relation) and
strengths (due to supports cross-tree relation), hints about supportive
features, hints about patterns and used patterns. Moreover, it is possible
to compare with patterns of canvas building blocks. It is also possible to
compare the business model with other business models of the same company
knowledge model or with examples of the merged canvas building blocks (if
merged completely). The corresponding views are automatically accessed,
when the business developer enacts a method.
compare the business model with other business models of the same composed
model or with examples of the merged canvas building blocks (if merged
completely). The corresponding views are automatically accessed, when the
business developer enacts a method.
</li>
</ol>
</div>
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment