1. Enterprise Cargo Management System (ECMS) SE18S07

2. Team Members and Roles Metric NoNameRole A0006361U AYE THET MON A0065958L NG SIWE LENG PRAGATI A0019692X TIN LAI WAI VARUN TAK ZHANG SHUDONG

3. Agenda Introduction Project Overview Project Scope Project Features Project Plan Team Organization Structure Gantt Chart Effort Estimate Vs Coastar Function Point Count Project Risks Quality Plan Technical Strategies Q&A

4. Introduction private company offering a one-stop total logistics package It provides freight forwarding operations, customs brokerage, transportation & third party warehousing/distribution needs The company management feels the urgency to bring the company operational efficiency to a next high level relying on enterprise IT system SE18 Team 07 have taken up the opportunity to propose and implement the ECMS for WWW Cargo Pte Ltd to assist and automate its daily business operations.

5. Objectives To develop the Enterprise Cargo Management System (ECMS) which will automate the end-to-end business process for WWW Cargo Pte Ltd, a logistic service provider The new system is expected to ease their daily operations which is currently very much manual in nature, to a large extent. ECMS will span across the following business functions in WWW Cargo for work automation: Marketing Customer Service Operation

6. Project Overview

7. Business Flow Local Suppliers Overseas Singapore Agent (Forwarder) WWW (Forwarder) Suppliers (Shipper) Customer (Consignee) Goods shipped to consignee By overseas agent Consignee orders the goods and Makes payment to the shippers

8. Project Scope ECMS will include the following core software modules:

9. Project Features

10. Project Plan Team Organization Structure Gantt Chart Effort Estimate Vs Coastar Function Point Count

11. Team Organization Structure TeamTeam Members Management Team Project Manager (team leader) Business Analyst Development Team Technical Lead (sub-team leader) Developer System Analyst Quality Team Quality Manager (sub-team leader) Tester NameRole Shudong Project Manager (main functional role) Business Analyst System Analyst Developer Varun Technical Lead (main functional role) System Analyst Developer Pragati Quality Manager (main functional role) Technical Lead System Analyst Developer Tester Lai Wai System Analyst (main functional role) Business Analyst Developer Amy Developer (main functional role) System Analyst Developer Tester Siew Leng Business Analyst (main functional role) Project Manager System Analyst Developer Role Assignment Matrix Sub-team classification Organization Chart

12. Gantt Chart

14. Effort Estimates Costar Vs Bottom-up Estimation Estimated Costar effort = 27.0 man-months Duration = 11.9 months Translating to man-day per team member: Estimated Costar effort = 27.0 x 152hrs (Costar pre-defined) = 4104 man-hours = 4104 / 8 hr per man-day / 6 team members = 86 man-day per team member Estimated Effort = 528.5 man-days / 6 team members = 88 man-day per team member Total (man-day) Activity 1Initial Planning 30 Activity 2Project Monitoring, Controlling, Administration 102.5 Activity 3Requirements Identification32 Activity 4Prototyping36.5 Activity 5Analysis Modelling69 Activity 6Design Modelling74 Activity 7Database Design5 Activity 8Programming116.5 Activity 9System Integration Testing35.5 Activity 10User Acceptance 27.5 Total 528.5

15. Function Point Count ITEMLOWAVERAGEHIGHTOTAL External Input 5x3 = 1513x4 = 520x6 = 067 External Output 0x4 = 02x5 = 100x7 = 010 Internal File15x7 = 1052x10 = 200x15 = 0125 External file0x5 = 00x7 = 00x10 = 00 External Inquiry 15x3 = 459x4 = 360x6 = 081 UnadjustedFunction Points 283 CHARACTERISTICDI Data Communications4 Distributed Functions4 Performance1 Heavily Used configuration0 Transaction Rate1 On-line Data Entry5 End User efficiency3 On-line Update3 Complex Processing0 Re-usability1 Installation Ease1 Operational Ease0 Multiple Sites2 Facilitate Change0 Total Degree of Influence24 Adjustment Factor = 0.65 + (0.01 x Total Degree of Influence) = 0.65 + 0.24 = 0.89 Adjusted FPC = Unadjusted FPC* Adjustment Factor = 283 x 0.89 = 251.87

16. Project Risks

17. Quality Plan Filing System location – Google Project - ISS2011S7 Location - https://iss2011s7.googlecode.com/svn/trunk/Documentshttps://iss2011s7.googlecode.com/svn/trunk/Documents Documents MGMTCommunicationPlansQualityReportsTechSpecificationUserWorkSCM

18. Quality – Issue Tracker Issues raised in the project will be traced using Issue Tracker, online tool from Google Code Project.

19. Technical Strategies

20. System Overview

21. Architectural View of the Application – ECMS requirements shall map on a logical multitier architecture. Division between the logical tiers

22. Technological Approach Model View Controller architecture (MVC)- We are adopting the well known and proven MVC architecture for the application design and development. MVC architecture shall be achieved using Struts 2 as a Web Tier base line framework. Together with the above mentioned approach following are the applicable J2EE design patterns identified – Business Delegate Service Locator Front Controller Data Access Object Value Object Interceptors. Session Facade View  Renders the Model.  Send user requests to controller. View  Renders the Model.  Send user requests to controller. Model  Encapsulate application states.  Maintained by Controller and refer by View. Model  Encapsulate application states.  Maintained by Controller and refer by View. Controller  Selects view for response.  Updates Model with user actions. Controller  Selects view for response.  Updates Model with user actions. Changes the State Query the state Select the view

23. Design Aspects WEB – centric design (Web tier to communicate with Database) EJB – centric design (EJB tier to communicate with Database) Both of mentioned design approaches have their own benefits and down sides, however, for ECMS requirements point of view we have decided to go with EJB- centric design by keeping following things in mind Robustness. Secure access to the software components. Reusability. Managed transactions. Focus development on application domain. Proven container provided Transaction Management. More manageable large scale data intensive systems.

24. Platform and Software Components The development platform shall be Java EE 6, which has many APIs. However, for the requirement of ECMS, we are going to explore mainly followings Java Platform, Enterprise Edition 6 (Java EE 6) Enterprise JavaBeans 3.1 Java Servlet 3.0 JavaServer Pages 2.2/Expression Language 2.2 Standard Tag Library for JavaServer Pages (JSTL) 1.2 Followings are the Third Party Open Source Components to be integrate Apache log4j 1.2 APIs (For logging purpose) Hibernate (For Object Relational Mapping) Struts 2 (Web Tier framework to stick with MVC) Jasper Reports (For Reporting)

25. Q & A