ohernan/test

test's Issues

Enable RDC-level parameter configuration

Test Issue 2

Lets see if it is useable

my issue test 3

Issue Git Hub

Issue Git Hub

Change the exposure information in the results page

Changing Exposure number by a sentence. We can use fixed sentences for some value ranges (the number could be added at the end of the sentence in brackets). We need to identify the different situations, something like:

• When the tendency (arrow) is negative: There are evidences that indicate a high/moderate/low possibility of having “Maintenance Risk”
• When the tendency is positive: There are strong/moderate/low evidences that indicate that the “Maintenance Risk” is not going to arise… (I don’t know how to say when the exposure is positive)
• When we have positive and negative equally (arrow pointing up): According to the evidences, the possibility of having “Maintenance Risk” cannot be assessed

documenting rest services

Get some order to the results page

When there are goal models, I should put first goals and then Risks, separated some way (a line or something). In order to show our 3-layer approach

Documenting models

The user need to have a more friendly way to see the models.

• #45 Some information in the platform
• #10 Uploading pdfs
• #52 Creating documentation from the model content

my issue test 4

my issue test 4

Just a test issue

Concrete problem to solve

The second test

this is not so critical

If model changes, it needs to be re-assigned in the risk configuration

Models are not referenced by name internally. Thus, changing a model, the risk configuration points to a non existing one.
Put a check and possibly an error message

Changing Risk Configuration form

The form to change a risk configuration should:

• Show the current models checked
• Having a Cancel button

Preliminary integration of the mitigation algorithm

As a initial step of having mitigation activities integrated in the risk analysis workflow.

Subtask of #34

[rdc] some indicators in the github model are not available on the github api

try to retrieve in other way,
or change the models

Adding mitigation activities

Sub tasks:

• #43 preliminary inclusion

Make database location configurable

the platform should identify the type of model (not asking to the user)

When a model is loaded, the platform should identify the type of model (not asking to the user)

A loaded risk model is not shown in the list of Models

When you loaded a new model, it does not appears in the list of Models, but it is in the platform because you can use it in the risk configurations

Models with same name can be loaded but not stored in the database

If model has same name than an existing one, print an error message.
Also we need to handle the reloading of models, possibly just by giving the same error message, thus forcing to delete the old one first.

create/edit/modify date/time entities data

The user should be able to create fields for date/time

Issue related to #38

Domain data management

User access asking for the domain:

• The RDR is shared for all the domains
• The rest of information is private per domain (layers, entities, risk configuration, risk analysis, models)

Related to:

• #47 User role management
• #48 User management
• #53 Domain management

OSS Component comparison

In option "One-layer Analysis" or a new option "Compare", the user can choose more than one Entity and 1 risk configuration.

The results for each entity are shown like in columns

If we have the Clone button (issue #102) and some kind of comparison, we are answering to the test cases SC-CEN7 and SC-CEN-8.

Informing about the last data collection date time

In the entity form, add a new field at the top of the RDCs showing the last date when the RDCs where run, I don't know if only one or one per each data collector

Using contextual indicators for the multi-layer analysis

The contextual indicators should be marked in some way to differentiate them from the data inputs gathered.

One model associated to one layer (e.g. OSS Component) can use contextual indicators from higher layers in the hierarchy.

Download of models

• nice to have low priority -
  downlaod button for a model.

For now: copy the raw model content to a file.

Problem with the frame on the right

Using Explorer and Firefox, the frame on the right uses only a small part of the frame. Showing a scroll

My Issue Test 2

My Issue Test 2

No IDs in the results page

The results are shown the ID model elements, if there is name, the name should be shown instead of the ID. The IDs should be last option in all cases

Making easier the RDC management

Entities data management

The platform should allow the create/edit/modify customized data at level of layer. This customized data will be used for the contextual indicators

The user will define which data is associated to a layer, and then these fields will be filled for the entities belonging to this layer. Each entity data will have at least:

• ID
• Name
• Description
• Default value
• Specific field depending on the type of the data (e.g. number minimun and maximun value)

This requirement is refined by issues related to create the customized data for each layer:

• #39 Integers
• #40 Boolean
• #41 Lists
• #42 Date/time

and, the issue related to:

• use this customized data in the Entity form: #51
• customize the fields to be shown in the results page #59

Get some order for goals in the results page

We should sort the goals according to the hierarchy, the roots first, the leafs after.

I don't know if risks have the same hierarchical view. In the future we could try to show the hierarchy in the results

Exporting Results

A button to export the results including the risks and the data inputs

Integrating LimeSurvey?

Using contextual data (current LimeSurvey Questionnaire). Integrating the LimeSurvey data collector (that includes the integration with the survey) or developing a new Questionnaire manager.

create/edit/modify list entities data

The user should be able to create fields for choosing 1 value from a list (dropdown or radio buttons, to be decided).

Each element of the list should be associated to a number (real), when a user selects an element from the list, the value stored in the database is the number associated to the element of the list

Issue related to #38

Improving the data input/sliders

For example fixing the minimum and maximum values.

Give the possibility to upload a document with a description for each model

Will be done in the model's properties tab
Alternatives:

1. txt, displaxed in the properties tab
2. image, displaxed in the properties tab
3. pdf - retrievable by a "download" button

No "last execution data"

I always see: 01-01-70 01.00.00 000 in the results page of Risk Analysis Session

New Risk Analysis Session automatically run

When the user arribes to the last step creating a new risk session, consider running the analysis instead of wait for the user clicking the button. Only for risk sessions that are no run yet

Forbid invalid characters in layer/entity/model/risk configuration names

Adding the version visible in the UI

Make database compatible for future versions

The database should be compatible for any platform version. 2 options:

• Having an import/export functionality for trespassing data
• Making compatible the database from the inside the platform.

One option to making the database compatible with existing versions:

1.- having a table in the database to know the database version

2.- having accumulative scripts for the database creatation

3.- each time the database structure needs to change, we do not create the script to create the database from the scratch, we create an accumulative script
inlcuding the changes to be done in an existing database (version -1)

3.1.- each script included one row in the version table including the version and the current time

3.2.- when the program is deployed, now the database is created automatically from the scratch, the new methodology would be

3.2.1.- If there is no database in the database path: run all the scripts

3.2.2.- If there is a database in the database path:

3.2.3.1.- Check for the database version (looking in the version table)

3.2.3.2.- Run all the necessary scripts, all the scripts after the current version

create/edit/modify integer entities data

The user should be able to create fields for Integer values. We need some data checkings, the user can define:

• minimun value
• maximun value

For displaying this kind of fields in the entity form, it should be nice using an edit box+arrows, the user could use the arrows in tactil devices.

Issue related to #38

My Issue test 2

My Issue Test 2

No goal models in what-if

Only risk models should be shown in the list to be selected.

Problem with the frame on the right

Using Explorer and Firefox, the frame on the right uses only a small part of the frame. Showing a scroll

my issue test

bad problem

create/edit/modify boolean entities data

The user should be able to create fields for boolean values, using a checkbox??

Issue related to #38

Risk Analysis session history

New menu option Browse/Risk Analysis: Form with 3 lists:

• List of the left: The list of all the entities that already have some risk analysis (see Figure 2. Risk Analysis History). When an entity is selected the list on the middle is filled (see next bullet) and a summary for this entity is shown at the bottom of the page (to be designed).
• List on the middle: When an entity is selected in the Entity list, all the different risk configurations used for analyzing the selected entity appear. When the risk configuration is selected the list on the right is filled (see next bullet) and a summary for this entity and risk configuration is shown at the bottom of the page (to be designed). See Figure 3. Risk Analysis History (Entity selected)
• List on the right: When an entity and a risk configuration is selected, all the risk analysis performed for this entity with this risk configuration appear. When the date is selected the results for this risk analysis are shown at the bottom of the page (in the exactly way are shown when a single risk analysis is performed). See Figure 4. Risk Analysis History (Entity and Risk configuation selected).

"One-layer analysis" vs. "Risk Analysis Sessions"

Why do we have 2 options?
Consider havin only one Risk Analysis Sessions:

• The same form that appears in one-layer analysys".
• The form has 2 buttons: "Run Analysis" and "Analysis Sessions".
• If we consider the comparison (issue #26), if more than one entity is selected the "Analysis Sessions" button is disabled
• If the user "Run Analysis", the results are shown, in the same form a button "Save as Analysis Session"
• If the user "Analysis Sessions", the form of the list of analysis sessions as now
  Maybe we can consider having a "Risk Analysis Sessions" in the Browse menu, which opens directly the list of analysis sessions in some way (see issue #19)