The project manager writes user requirements formulated in natural textual language in the Inspecto need environment.
The project manager writes software requirements using a dedicated language that can be understood by the project stakeholders.
Inspecto need detects in a few seconds ambiguities or inconsistencies that could lead to unforeseen problems in development.
The project manager corrects ambiguities with the client.
Iterations until Inspecto need validates the terms without ambiguity.
The developer selects the features to be tested.
Inspecto code automatically generates the appropriate tests.
From the specifications, Inspecto code knows exactly which cases to test and generates the relevant test scenarios.
The developer develops the expected features in his development environment without changing his habits.
In a single click, the developer launches the tests on Inspecto code.
Inspecto code verifies that the features developed are those specified in the specifications.
+ Validation, continuation of the development of the features
Inspecto code tells the developer where the errors are. New iteration.
The Inspecto code Offer
(requires Inspecto need)
|Acceptance and validation test generator|
|Acceptance and validation test generation||✔|
|Identification of test cases required and essential for validation||✔|
|Collaborative (connection to Inspecto need)||✔|
|Effortless traceability between requirements and code||✔|
|Monthly fee:||120€ / month / user|
|Annual fee:||1200€ / year / user
or 2 months free
You can find here some papers that served as a basis for SPILEn :