Upload
eric-woods
View
252
Download
1
Tags:
Embed Size (px)
Citation preview
SE18S07
Metric No Name Role
A0006361U AYE THET MON
A0065958L NG SIWE LENG
PRAGATI
A0019692X TIN LAI WAI
VARUN TAK
ZHANG SHUDONG
• 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
• 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.
• 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
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
ECMS will include the following core software modules:
Agent Profile Management
Customer Profile Management
Customer Service Shipment Tracking Management
Operation Sea Import Job Processing
User Administration
Air Import Job Processing
Marketing
Administration
Business Reporting
Account Management
• Team Organization Structure• Gantt Chart• Effort Estimate Vs Coastar• Function Point Count
Team Team Members
Management TeamProject Manager (team leader)Business Analyst
Development TeamTechnical Lead (sub-team leader)DeveloperSystem Analyst
Quality TeamQuality Manager (sub-team leader)Tester
Name Role
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
Estimated Costar effort = 27.0 man-monthsDuration = 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 1 Initial Planning 30Activity 2 Project Monitoring, Controlling,
Administration 102.5Activity 3 Requirements Identification 32Activity 4 Prototyping 36.5Activity 5 Analysis Modelling 69Activity 6 Design Modelling 74Activity 7 Database Design 5Activity 8 Programming 116.5Activity 9 System Integration Testing 35.5Activity 10 User Acceptance 27.5
Total 528.5
ITEM LOW AVERAGE HIGH TOTAL
External Input
5x3 = 15 13x4 = 52 0x6 = 0 67
External Output
0x4 = 0 2x5 = 10 0x7 = 0 10
Internal File 15x7 = 105 2x10 = 20 0x15 = 0 125
External file 0x5 = 0 0x7 = 0 0x10 = 0 0
External Inquiry
15x3 = 45 9x4 = 36 0x6 = 0 81
Unadjusted Function Points 283
CHARACTERISTIC DI
Data Communications 4
Distributed Functions 4
Performance 1
Heavily Used configuration 0
Transaction Rate 1
On-line Data Entry 5
End User efficiency 3
On-line Update 3
Complex Processing 0
Re-usability 1
Installation Ease 1
Operational Ease 0
Multiple Sites 2
Facilitate Change 0
Total Degree of Influence 24
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
Filing System location –
Google Project - ISS2011S7
Location - https://iss2011s7.googlecode.com/svn/trunk/Documents
Issues raised in the project will
be traced using Issue Tracker,
online tool from Google Code
Project.
Technical Strategies
System Overview
Architectural View of the Application – ECMS requirements shall map on a logical multitier architecture.
Division between the logical tiers
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. 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 StateQuery the state
Select the view
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.
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)
Q & A