1 / 38

Enterprise Cargo Management System (ECMS)

Enterprise Cargo Management System (ECMS). SE18S07. Project Background Project Objective Project Requirements Project Risks Project Plan Technical Strategies Quality Plan Project Status Q&A. Agenda. Project Background.

zahina
Download Presentation

Enterprise Cargo Management System (ECMS)

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. Enterprise Cargo Management System(ECMS) SE18S07 ISS SE18T7S

  2. Project Background Project Objective Project Requirements Project Risks Project Plan Technical Strategies Quality Plan Project Status Q&A Agenda ISS SE18T7S

  3. Project Background • WWW Cargo Pte Ltd (Project Sponsor) is a privately owned company offering a one-stop total logistics package. • At the moment, the daily business operation of WWW Cargo Pte Ltd heavily relies on MS Excel, where company staff will operate on the same set of excel files at the shared network drives. This prevent staffs concurrently access the same set of files. Also staffs need to manually navigate inside the file folders and excel worksheets in order to find the data. • As a result, it is decided that a new system with web platform support is required to improve their productivity ISS SE18T7S

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

  5. ISS SE18T7S

  6. Project Objective • 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. • Due to project resource constraint, the project will focus on import operation while leaving export operation for future phase. ISS SE18T7S

  7. Project Requirements • The main system users are the Employees, Managers (or management) and System Administrators. • Relevant user documentation (e.g. user guides) shall be created for both training and system support/maintenance. • Open-source software shall be used for the development of the ECMS system. • ECMS system shall be built using object-oriented technologies and techniques. • Rational Unified Process (RUP) methodology shall be adopted as the development approach. • Any formal changes to the requirements shall follow the SE18S7 “Change Control” procedure in the quality plan. ISS SE18T7S

  8. Project Requirements • Customer Profile Management • The system is required to keep track of WWW Cargo customers’ profiles with their supplier information. • Agent Profile Management • The system is required to keep track of all the agents’ profiles with all branch details. • Shipment Tracking Management • The system is required to allow user to track shipment by creating new shipment, updating shipment status. On status update, notification email should be sent to customers automatically. ISS SE18T7S

  9. Project Requirements • Sea & Air Import Document Processing • For each import shipment, quite a few documents needs to be issued due to business requirements. The system should minimize the data entry performed by the staff and generate all the necessary documents as required. • The following documents are required for Sea Import Shipments • Sea Import costing sheet • Sea Import Notice of Arrival with charges or without charges • Sea Import delivery note • Sea Import trucking instruction • Sea Console manifest • Transhipment cover note • Shipping note • House Bill of Lading (HBL) • Master Bill of Lading (MBL) ISS SE18T7S

  10. Project Requirements • Sea & Air Import Document Processing (cont’d) • The following documents are required for Air Import Shipments • Air Import Costing Sheet • Air Import Delivery Notes • Business Reporting • The system should allow user to view the monthly business report which describes the summary of shipments in the month. • User Administration • The system should allow administrative user to create/remove users and configure user access rights. ISS SE18T7S

  11. Project Scope ECMS will include the following core software modules: ISS SE18T7S

  12. Project Risks • Management Risk • Team member commitment • Lack of Domain Knowledge of Team members • Change in requirement due to users lack of experience in IT systems. • Resource overload due to small team size of 6 member, who are committed for 88 man-day for the project. • Lack of customer commitment • Technological Risks • Lack in skills of team member for J2EE Technologies. • Non availability of suitable hardware for the release. • Stability of J2EE6 components, as it’s a new release. • Technology Limitation • Defects in open source software components ISS SE18T7S

  13. Project Plan ISS SE18T7S

  14. Project Plan • Team Organization Structure • Effort Estimate Vs Costar • Function Point Count • Gantt Chart- Baseline ISS SE18T7S

  15. Team Organization Structure Role Assignment Matrix Organization Chart Sub-team classification ISS SE18T7S

  16. Effort EstimatesCostar 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 ISS SE18T7S

  17. Function Point Count 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 ISS SE18T7S

  18. Gantt Chart – Baseline (1/3) ISS SE18T7S

  19. Gantt Chart – Baseline (2/3) ISS SE18T7S

  20. Gantt Chart – Baseline (3/3) ISS SE18T7S

  21. ISS SE18T7S

  22. Technical Strategies ISS SE18T7S

  23. System Overview ISS SE18T7S

  24. Architectural View of ECMS requirements solution – a logical multitier architecture Division between the logical tiers ISS SE18T7S

  25. Model • Encapsulate application states. • Maintained by Controller and refer by View. Changes the State Query the state • View • Renders the Model. • Send user requests to controller. • Controller • Selects view for response. • Updates Model with user actions. Select the view Technological ApproachModel 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. ISS SE18T7S

  26. 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 functional and non-functional requirements point of view we have decided to go with EJB- centric design by considering following • 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. ISS SE18T7S

  27. Platform and Software ComponentsThe 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) ISS SE18T7S

  28. Quality Plan ISS SE18T7S

  29. Quality Plan Filing System location – Google Project - ISS2011S7 Location - https://iss2011s7.googlecode.com/svn/trunk/Documents ISS SE18T7S

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

  31. Project Status ISS SE18T7S

  32. Project Progress – completed to date • Initial Planning • Set-up Project Filing System • Produce Quality Plan • Produce Project Plan • Review / Finalize Quality Plan • Review / Finalize Project Plan • Requirements Identification • Interview Users & Gather Requirements • Produce User Requirements Specification • Internal Review / Finalize User Requirements Specification • External Review / Finalize User Requirements Specification • User Requirements Specification Sign-off ISS SE18T7S

  33. Project Progress – Plan for next phase • Prototype • Produce UI Prototype • Review UI Prototype • Produce System Prototype • Review System Prototype • Produce Prototyping Study Report • Review / Finalize Prototyping Study Report • Functional Specification • Produce Use Case Model Survey • Review / Finalize Use Case Model Survey • Produce Use Case Realization Reports (Analysis) • Review / Finalize Use Case Realization Report (Analysis) ISS SE18T7S

  34. Project Progress – Plan for next phase • High-level Design Specification • Produce High Level Software Architecture • Review / Finalize High Level Software Architecture • Produce Transition Strategy from Analysis to Design • Review / Finalize Transition Strategy from Analysis to Design • Produce DB Logical Design • Review / Finalize DB Logical Design ISS SE18T7S

  35. Gantt Chart – Tracking (1/3) ISS SE18T7S

  36. Gantt Chart – Tracking (2/3) ISS SE18T7S

  37. Gantt Chart – Tracking (3/3) ISS SE18T7S

  38. Q & A ISS SE18T7S

More Related