Marc Behrens : criteria

MariellePetitDoche commented 11 years ago

from https://github.com/openETCS/toolchain/issues/158

Please add, if not already inside, the following criteria:

Requirements Handling

[x] Editing of Textual Requirements
[x] Represent Relations between Req (Textual-Based)
[x] Represent Relations between Req (Modelling-Based)
[x] Glossary and Abriviation handeling (Linked to Req))
[x] Traceability of Textual Requirements to Modelling
System Modelling
[x] User Scenario Modelling
[x] Test Case Modelling
[x] Test Sequence Modelling
System Model Verification
[x] Input/ Output checking
[x] System Behavior Simulation (Mathematical)
[x] System Behavior Simulation (Animated)
Software Model Verification
[x] Static Modell Verification
[x] Property Proofing
[x] Dynamic Testing
[x] Automatic Test Generation
[x] Input/ Output checking
[x] Software Behavior Simulation (Mathematical)
[x] Software Behavior Simulation (Animated)
Source Code
[x] Traceability to Modell
Code Verification
[x] Formal Proof
[x] Programming by contract
[x] Static Analysis
[x] Dynamic Analysis
[x] Dynamic Testing
[x] Automatic Test Generation
[x] Performance Testing
[x] Interface Testing
Validation System/Software/Code/ Validation
[x] Test Coverage
[x] Use Case Validation of Model
[x] Functional/ Black-box Testing
[x] User Scenario Testing
[x] Traceability
[x] Schedulability Analyzer / UseCase Check all
[x] Schedulability Analyzer / UseCase Check single mode
Toolchain Integration
[x] Eclipse platform
[x] Maintainability Concept
[x] Configuration Management
[ ] UseCase Validate Process

srieger commented 11 years ago

Some remarks:

I believe, we also need some descriptions for some of the items as their meaning is not always clear (at least not to me). E.g., "Schedulability Analyzer / UseCase Check all/single mode", "Use Case Validation of Model", etc.
The testing-related items should be only filled if testing activities are actually performed.
What does a number, e.g., 3, in "Test Coverage" mean? The actual coverage criteria would be more suited.

BerndHekele commented 11 years ago

With Focus on SSRS use case of the toolchain I want to add some criteria

Requirements Handling

[x] Import/Export of Industrial Standard Data (e.g., REQIF)
[x] Import/Export of Data in common formats like xml or csv (export to spreadsheet for further analysis and processing) Note: with this function we have a workaround to implement other comfort functions.
[ ] Reqtify needs to be able to build links
[x] Generation of Documents (e.g., .pdf, .doc)
[x] Data Search and Data Filtering Functions
[ ] Alternatively "Print" Function for selected data
[x] Data Sharing between users, Commiting of data by individual users in common data pool
[ ] Atomicity: Changes in the data shall be limited to an minimal entity (allows for parallel working on data)
[x] Multi-User Access on data
[ ] "Access Rights according to role" to data on GithubRepository
[ ] Undo/Redo Functions when editing
[ ] Database "Fallback" and "Recovery" functions

MariellePetitDoche commented 11 years ago

@MarcBehrens: I added or checked criteria in Management in 07.2.1_Management

@BerndHekele: Could you clarify some of your propositions:

[ ] Reqtify needs to be able to build links: Why a criteria on Reqtify for OS tools ?
[ ] Alternatively "Print" Function for selected data What do you mean by print function, is it a criterai on requirement management or on the toolchain ?
[ ] Atomicity: Changes in the data shall be limited to an minimal entity (allows for parallel working on data) Why we need such a criteria if we have configuration and version management ?
[ ] Access Rights according to role to data on GithubRepository Is this necessary with the role on github ?
[ ] Undo/Redo Functions when editing I suppose is a primitive function of lot of tools, is it necessary to add a criteria explicitely for requirement management ?
[ ] Database "Fallback" and "Recovery" functions Is it necessary with a version management as github ?

BerndHekele commented 11 years ago

[ ] REQTIFY is not an open source tool. But it is part of the Scade toolset and will be used in this context with modelling. We would like to use the tool to get an nice overview on requirements in different databases. I see 2 use-cases:
1. searching for keywords in ProR - needs some sort of "adapter" in ProR to interface with reqtify
2. import of results of reqtify into ProR when we transfer from closed source toolchain to open soure toolchain.
  - [ ] Print Function: here I mean functions to make prints out of ProR, e.g., when you make use of requirments with people not familiar with ProR.
  - [ ] Atomicity: I'm lacking a vision how a team can collect and docuement requirements in parallel on a common database without this feature. Each requirement should be seen as an individual atom.
  - [ ] Access Rights - we probably get it for free. Reason to put it here is: the requirements tool must not destroy the access rights concept.
  - [ ] Undo/Redo is not mandatory but nice to have. I like this functions whenever I use an editor. I would like to see it as a part of the requirements tool as well.
  - [ ] Fallback / Recovery: the functiions are essential. Maybe it is suffucient to document what to do to do a proper fallback/Recovery based on github. I'm not sure what the data security of Github promisses. What happens if the Github Server fails.

I hope this helps?

cu Bernd

MariellePetitDoche commented 11 years ago

In my opinion, Atomicity, Access Rights, Undo/Redo and Fallback/ Recovery are covered by the general requirements of §2.3.1 as version management, concurrent development, multi-users capabilities,...

Print function is covered by §2.5.1 "Documentation production" and §2.5.3 on the output artifacts.

in https://github.com/openETCS/toolchain/commit/17dc22b91d02f4a541249dd25fbdbac83994102b

For my point of view ReqTify is a close source tool independant from Scade and shall not be taken as reference as discussed in https://github.com/openETCS/requirements/issues/35

openETCS / toolchain