Invariant not implemented in class TermMapping

Bug #609150 reported by Sergio Miranda Freire on 2010-07-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OSHIPpy
High
Wagner Mezaroba

Bug Description

The invariant
Purpose_valid: purpose /= Void implies terminology(Terminology_id_openehr).
has_code_for_group_id(Group_id_term_mapping_purpose, purpose.defining_code)

is not implemented and it must use the openehr terminology.

We must be establish a policy on how to implement invariants, for instance: declare the invariant in the interface and implement it in the class that implements that interface.

Related branches

Changed in oship:
importance: Undecided → High
milestone: none → 1.5
Changed in oship:
assignee: nobody → Wagner Mezaroba (wagnerfrancisco)
Changed in oship:
status: New → Fix Committed
affects: oship → oshippy
Changed in oshippy:
milestone: 1.5 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers