-
Notifications
You must be signed in to change notification settings - Fork 18
Add a new use case
eprocurementontology edited this page Apr 26, 2017
·
7 revisions
To create a new use case, please submit an issue by clicking here. And then click on "New issue".
Replace the text of the default template (first row and first column) by the text of the table below:
Element | Description |
---|---|
Title | A short phrase that can be used to refer to the use case |
Category | The type of use case; one of:
|
Description | Concise text that provides basic information about the actors, the goal and the intended results of the use case |
Actors | Further details on the agents (persons, organisations or software programs) involved in the use case |
Final recipients | The actors that receive the results or benefits from the use case |
Preconditions | Anything that can be said about the situation before the use case begins |
Flow | A step-by-step description of the actions taken and responses received by the user:
|
Comments | Any other observation related to the use case |
And then fill the table with your input by following the guidelines provided in the table above (second column).
Find a list of issues related to this topic by clicking here.
see more
-
Presentations
- IFLA-LRM-Volume Aggregation Serialisation
- Notice Types
- ePO-LEX Resource Versioning and Identification
- ePO-Roles
- Discussion Procurement Criteria
- Buyer and Organisation Examples
- Definitions of classes and attributes
- Roles Taxonomy and Procurement Events (Work in Progress)
- DCAT-EPO (Discussion 14/01/2021)
- Roles Group of lots (Discussion 11/05/2021)
see more
see more
- ePO Glossary (spread-sheet)
- ePO Glossary
- Glossary management
- Improve term and definition
- Add new term and definition
Online documentation
Information requirements
Conceptual Model (CM)
OWL
Proof of Concept
see more
Information requirements
Conceptual model
Mapping of the conceptual data entities to OWL