Use cases for POC

Theses use cases are to be used for new UI POC, documentation associated and selenium unit task test.

All these use cases should be done with existing entities and services, if it's necessary to develop one, simplify the use case, the goal is UI, not service or entity.

These use case description are done in a agile philosophy, only main point is present and during realization details choices will be discuss and done.

Preliminary remarks :

1. In this document, the term "application" corresponding to "specialpurpose/component" in the ofbiz terminology which is not same as a "applications/component" in ofbiz terminology.
   An application is dedicated for a business purpose for a user type, it's build by assembling piece of ofbiz components, sometimes without any specifics entities, services and screen (ex: CRM-B2C, CRM-B2B, SFA are 3 applications uses by sales men)

2. Each use case is on an "application" and is part of one of the menu of this application. Of course, this document describe only menu-option needed by the use-case. As it's difficult to do a clear definition of "web-page" because it's depending of theme/template, use case is for me at two level :

   1. screen, which can be well define
   2. page, which depend on default theme

   Of course, some of use case (screen or page) will be done by a previous one (ex : sometime edit is done by the same screen as add). It's even, one of the re-usable important point (UI, Doc and Selenium)

3. Each time a line (or point) start by a "?" the question is "is this point is needed ?"