Constraints On Dates (feature)

From UG

Revision as of 15:49, 11 January 2010 (edit) Alex (Talk | contribs) (→Business Needs and Requirements) ← Older edit		Revision as of 17:16, 11 January 2010 (edit) (undo) Alex (Talk | contribs) (→Business Need) Newer edit →
Line 7:		Line 7:
	== Business Need ==		== Business Need ==
-	There is a natural "sequence of dates". For example date of departure of a vessel can not be later than date of arrival of this vessel.	+	We have a number of constraints / validation rules that we need to enforce.
	It is important to prevent operator from making error.		It is important to prevent operator from making error.
-
	== Requirements ==		== Requirements ==

---

Revision as of 17:16, 11 January 2010

Contents 1 Parent Mantis 2 Business Need 3 Requirements 4 Technical Specification 4.1 Summary 4.2 User Interface and Functionality 4.3 Entities and Attributes 4.4 Special Cases and Misc 4.5 Look And Feel 4.6 Figures 4.6.1 Figure: XXX 5 History 6 Non Critical Bugs and RFC 7 DB

Parent Mantis

tbd

Business Need

We have a number of constraints / validation rules that we need to enforce.

It is important to prevent operator from making error.

Requirements

All detailed requirements have been translated into specifications - see below.

Technical Specification

Summary

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure: XXX

History

Non Critical Bugs and RFC

DB