Non-functional Requirements 1. Operational 2.1 The system should run on the hardware used currently by the company. 2.2 The system should be integrated smoothly into the company’s existing website. 2.3 The system should be user-friendly for both the receiving staff and customers. 2. Performance 3.4 The system should be updated frequently for proper scheduling of orders placed. 3. Security 4.5 Customer payment option credentials or information should be kept confidential. 4.6 Only the segment manager can approve orders 4. Cultural and Political
No special cultural and political requirements are expected.
Task ID | Task Name | Assigned To | Estimated | Actual | Dependency | Status | | | | Duration (days) | Start Date | Finish Date | Start Date | Finish Date | DurationVariance | | | 1 | Design Phase | Mary Joy | 14 | Mon 01/28/13 | Mon 02/15/13 | | | | | Open | 1.1 | Develop database design document | Mary Joy | 3 | Wed 02/06/13 | Fri 02/08/13 | | | | | Open