4.1.2 Functional Requirements
 Clarity of Functional Requirements

With our functional requirements we tried to cover every aspect of the business goals and cover every stakeholder involved. This meant that our requirements are very specific and serve a specific purpose. This is also a downfall as being too specific in the product and domain levels violates the definition and jeopardises further expansion on the requirement. While a generic naming system is used we feel that we are sometimes too specific in the requirements.

 Traceability of Requirements

Our requirements feature a hierarchical ordering system that follows the number system. This allows requirements to be easily traced to its origin as it is numbered.

 Conformity to Product Scope

All of our requirements try to conform to a business goal they are very relevant in regards to the product scope. Because of this the majority of the requirements conform to the product scope both directly and indirectly.