Vaadin - Everest

- Vaadin is a must - Please mention your experience, with sample previous deliverable This document describes the requirements needed for the project (codename Everest): General: - This is just the initial milestone for two main screens, and is meant to select a developer for further implementation. - Everest is a project which sells some hardware/software to the customers online - Look and Feel is not in the current scope - All data will be static (no database) at the moment. Later, even when the database is used, a Java API with DAO design pattern will be automatically generated by a tool. Technical requirements: - Code will be hosted in SVN - Vaadin 7 will be used Functional requirements: [login to view URL]: - Outer logo/labels/certified/logged area should be static with empty content - On the left side: Resource Owner contains the company hierarchy, groups/subgroups and employees - Group can be renamed - Main Corporate group is always the root - Employees of a given group are sorted alphabetically (first name, then last name) - User can add/delete/update group/employee - In each row (group or employee), it can has one or many 'resource lines' (RL) - The category is a list of items, the user selects from, [login to view URL] contains sample input. - In each RL: - Category 1 is a must to have per RL (not nullable), so its combobox will have all list and 'cancel' in case he has the item already - Category 2: null for "web"/"shared" Category1, 1 to 1 with category1 - Category 3: not nullable, 1 to 1 with category1 - Category 4: null for web/shared Category1 - Category 5: is completely independent of category 1, it can be 1-to-many to resource owner - Category 6: is completely independent of category 1, it can be 1-to-many to resource owner [login to view URL]: - In each row (group or employee), it can has one or many 'resource lines' (RL) - The category is a list of items, the user selects from, [login to view URL] contains sample input. - In each RL: - Category 11 is a must to have per RL (not nullable), so its combobox will have all list and 'cancel' in case he has the item already - Category 12: not nullable, 1 to 1 with category11 - Category 13: nullable, 1 to 1 with category11 - Category 14: nullable, 1 to 1 with category11 - Category 15: is completely independent of category 11, it can be 1-to-many to resource owner - Category 16: nullable, 1 to 1 with category14 (14 not 11) - Category 17: nullable, 1 to 1 with category14 (14 not 11) Others: - Click 'New' it will show "[login to view URL]" modal window (on top of existing window) - [login to view URL], will select either [login to view URL] or [login to view URL] - For now, 'Del' will show confirmation box before deleting the group/employee - Clicking existing group/employee will show [login to view URL] - Move/Copy/St Prm (Set Permission) are out of the current scope - On creation of group/employee, its Resource Lines can be empty or inherited for immediate parent group, 'configuration package' is out of scope