Functional Requirements - Sxm

Only available on StudyMode
  • Download(s) : 330
  • Published : January 26, 2013
Open Document
Text Preview
Functional Requirements
1. Catering Service Order
2.1 The system will allow customers to avail of the catering service via online. 2.2 The system will allow customers to place a catering service request or order, while also choosing among the established menu, prices, payment options, packages and other specifications, via online. 2.3

2. Receiving of Catering Orders
3.4 The system will allow the employees receiving orders for catering to check the orders via online. 3.5 The system will allow the catering segment manager to automate the processing of orders. 3.6 The system will enable the manager to determine the number of pending orders by schedule. 3.7 The system will enable the employee tasked with record keeping to track the number of orders placed. 3.8 They system will notify the manager of the payment option selected by the customer and process it as necessary. 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| 1.1.1| Staging database design| Mary Joy| 3| Wed 02/06/13| Fri 02/08/13| | | | | Open| 1.1.2| Suspense database design| Mary Joy| 3| Wed 02/06/13| Fri 02/08/13| | | | | Open| 1.2| Develop rejects-handling design document| Mary Joy| 3| Mon 02/11/13| Wed 02/13/13| | | | 1.1.1, 1.1.2| Open| 1.2.1| Rejects-handling engine design| Mary Joy| 3| Mon 02/11/13| Wed 02/13/13| | | | | Open| 1.3| Develop OLAP design document| Mary Joy| 3| Mon 02/11/13| Wed 02/13/13| | | | 1.1.1, 1.1.2| Open| 1.3.1| Universe design| Mary Joy| 3| Mon 02/11/13| Wed 02/13/13| | | | | Open| 1.4| Develop OLAP design part 1| Joni| 5| Thu 02/07/13| Wed 02/13/13| | | | | Open| 1.4.1| High-priority reports design| Joni| 5| Thu 02/07/13| Wed 02/13/13| | | | | Open| 1.5| Develop application design document| Kirt| 8| Mon 02/4/13| Wed 02/13/13 | | | | | Open| 1.5.1| Group consolidation and corporate reporting (GCCR) maintenance application design| Kirt| 8| Mon 02/4/13| Wed 02/13/13| | | | | Open| 1.6| Extract, transform, load (ETL) design document| Kirt| 2| Wed 02/13/13| Thu 02/14/13| | | | | Open| 1.6.1| Data export utility design| Kirt| 2| Wed 02/13/13| Thu 02/14/13| | | | | Open| 1.7| Application design document| Joni| 12| Mon 01/28/13| Tue 02/12/13| | | | | Open| 1.7.1| Web entry application UI application| Joni| 12| Mon 01/28/13| Tue 02/12/13| | | | | Open| 1.7.2| Web entry application UI design sigh-off| Joni| 1| Mon 02/04/13| Mon 02/04/13| | | | | Open| 1.7.3| Web entry forms and database model validation| Joni| 7| Mon 02/04/13| Tue 02/12/13| | | | | Open| 1.8| Functional requirements document| Kirt| 6| Tue 02/05/13| Tue 02/12/13| | | | | Open| 1.8.1| Application design| Kirt| 6| Tue 02/05/13| Tue 02/12/13| | | | | Open|...
tracking img