TWiki> SEOC Web>SEOCProject (revision 4)EditAttach

SEOC Group Project

Please add any relevant comments about the SEOC Group Project.

  • Question: does the number of students in each team affect the workload expected?
Small teams (of 2/3 people) require less coordination effort than Large teams (up to 5 people). Note that the SEOC deliverables are assessed not on quantity, but on quality criteria - Check the marking scheme http://www.inf.ed.ac.uk/teaching/courses/seoc/2010_2011/coursework/

Questions on the P&G Requirements

  • Questions: "Ensures that the status of deliveries is up-to-date and visible at all times" - What should the "Status of Deliveries" include? Should it be visible to both P&G and customers
The first question is concerned with the "Status of Deliveries". The "status of deliveries" implies that deliveries (as well as orders) could be in a different state, which should me monitored throughout the process supported by the system. For instance, deliveries could be "ongoing" (meaning that deliveries are currently being despatched) or "completed" (meaning that the the goods have been delivered to the Customer delivery Points. Note that these are just sample states, the states depend on the way you interpret the requirements. Moreover, there could be some states that concern not just the deliveries, but the orders too.
The second question concerns who can view the deliveries' states, hence, what Actors can access particular system functionalities (use cases). It could be the case that Customers are able to view the states of the deliveries for their orders. However, this functionality should be further specified for P&G. For instance, P&G is able to view more information (e.g., track, exact position, etc.) than the customer. Therefore, the same functionality can be available to both Customers and P&G employees, but with different outcomes (that is, showing different set of information concerning the deliveries). Another difference i s that P&G employees should be able to access information about all deliveries.
  • Questions: What if the delivery plan created by users is not a good one? Should it be cancelled?
It depends on the interpretation of the delivery planning process. It is possible to assume that the customers select a specific delivery plan (e.g., a specific order, for a specific date and a specific delivery point), which then needs to be "approved/accepted" by P&G by providing an order number. If the specific order/delivery plan is not feasible by P&G for any reason, P&G could just refuse the order/delivery plan, or propose an alternative one (which then needs to be accepted by the customer).
  • Question: "Can accept orders and plan from a minimum of 24hrs and a maximum of 7 days before delivery" - What does this requirement mean? Does it mean that from order to end of delivery can only take the time from 24hours to 7days?
Yes, it means that any order can be delivered not before 24hrs (a similar, but different requirement, is next day delivery) and not later than in 7 days. In other words, if the order has been accepted on a specific date D, the delivery can append or be requested in the period [D+1;D+7]. It is not possible to plan any delivery outside this time window.

-- Main.mfelici - 24 Sep 2010

Topic attachments
I Attachment Action Size Date Who Comment
docdoc srs_template-1-2.doc manage 54.5 K 05 Oct 2010 - 12:29 Main.s1056938 IEEE System Requirements Specifications template
Edit | Attach | Print version | History: r8 | r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 07 Oct 2010 - 21:46:45 - Main.mfelici
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies