ReqsManagement: Difference between revisions
From Event-B
Jump to navigationJump to search
imported>Jastram |
imported>Jastram No edit summary |
||
Line 8: | Line 8: | ||
* Multiple Requirement Specifications can be managed in a Requirements Project. | * Multiple Requirement Specifications can be managed in a Requirements Project. | ||
* A Requirements Project manages Links between individual requirements and the Event-B Specification. | |||
== Status == | == Status == |
Revision as of 12:16, 21 July 2008
Description
The Requirements Plugin...
- Manages Text-Based Requirements
- Requirements are managed and edited in an external Tool (currently Latex, Plain Text and OpenOffice)
- Multiple Requirement Specifications can be managed in a Requirements Project.
- A Requirements Project manages Links between individual requirements and the Event-B Specification.
Status
The Requirements-Plug-In is currently available through CVS only and not yet useable.
User Documentation
Currently, a new Requirements Project is created by manually creating a file, ending in .req, containing the following:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <root> </root>
Developer Documentation
The Requirements Plug-in has the plug-in ID fr.systerel.reqsmgr
Architecture
The "Connection" between a Requirements Document (managed and edited outside Rodin) and an Event-B Machine is a .req file. This file can manage any number of Requirements Documents.
Package Structure
The package name space is fr.systerel.reqsmgr
- The elemnts-Package contains the interfaces to the entities inside Rodin, which are Associations, Documents and Requirements. The elements.basis package provides implementations of those interfaces. This package is a good starting point for understanding the data structures.
- The exteranl_docs package contains the interfaces to entities outside Rodin, which are Document, ExternalRequirement, etc.