1 / 12

Drop ship Automation Phase II

Drop ship Automation Phase II. Presented By : AMIT SHUKLA (amit.shukla@utdallas.edu) EMSE, Fall 2013 Under Guidance of Professor Lawrence Chung. Agenda. Overview “As Is” vs. “To Be” Issues (FR/NFR) Resolution Outcome Questionnaire. Overview.

chase-dyer
Download Presentation

Drop ship Automation Phase II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Drop ship AutomationPhase II Presented By: AMIT SHUKLA (amit.shukla@utdallas.edu) EMSE, Fall 2013 Under Guidance of Professor Lawrence Chung

  2. Agenda • Overview • “As Is” vs. “To Be” • Issues (FR/NFR) • Resolution • Outcome • Questionnaire

  3. Overview • Quick overview: In term phase-I we discussed about Drop-ship automation project, where a manual process was consider to-be automated. • Development cost was already decided as 500 sp. • Team “Yoda” was having above as their FY11R1’s deliverable. • Client’s expectation was completely different with estimated scope. • Re-budgeting was not possible as budget was already approved by its stake holders.

  4. “As-Is” vs. “To-Be” Create/update Order Ordering System Create Order Ordering System Submit Order Submit Order Answer Questionnaire Customer Care Call CC Valid Valid Answer Questionnaire Vendor Questionnaire Vendor Questionnaire Get confirmation Submit DS Order Valid Place DS Order

  5. Issues Functional Issues • Questionnaire behavior was not well defined. • Same Questionnaire may behave differently w.r.t different Vendor. • Future Questionnaire should be supported. Non Functional Issues • Limited time. • No full proof solution. • Restricted technology.

  6. Resolution: Realizing Domain behavior • Possible order Event: Even for infinite possible questionnaire, there were limited possibilities with order- • Accept Order • Cancel Order • Delete Item: (Item Level) • Questionnaire Type: Two type of questions- • Informative • Decisive(Trigger one of the possible event, as per questionnaire response)

  7. Continued… • Questionnaire Condition: Questionnaire condition are applied on respective Question- • Logical Operator ‘OR’ or ‘AND’ • Conditional operator ‘>’, ‘<‘ and ‘==‘ used with String, numeric, date literals • Arithmetic operator ‘*’,’+’,’%’ and ‘-’ used with string literal • Questionnaire Constants: Two type of questions- • Global Constants • Vendor Specific Constants (in hidden variable) • Item Specific Constants(in hidden variable)

  8. Translation of questionnaire into framework… • Java script based validation event • Questionnaire Records Framework: Two type of questions- • Questionnaire Record • Vendor Specific Constant Record

  9. Questionnaire Structure • Overnight Delivery • Currenttime -cutofftime < 30 • Action True= Cancel q1 bean1 . Bean.. qn beann V1 Ques Map V2 Ques Map Questions Map . Ques Map Question Bean Attrb . Ques Map . Ques Map Vn Ques Map Mater Map

  10. Outcome

  11. Questionnaire… ?

  12. Thank You

More Related