ECMS Phase 2 Presentation

1. ECMS Phase 2 Presentation Team S07

2. Agenda • Scope of project • Global use case diagram • Analysis use cases • High Level design (Software Architecture) • Prototype stage challenges • Technical risks and Mitigation • Transition strategy • Progress Tracking • Plans for implementation phase • Change Requests • Question and Answers

3. Scope of Project

4. Customer Profile Management (Marketing Staff) • Maintain customers’ profiles with their supplier information. • Agent Profile Management (Marketing Staff) • Maintain agents’ profiles with the branch details • Shipment Tracking Management (Customer Service Staff) • Track shipment by creating new shipment, updating shipment status with email notification feature • Sea & Air Import Document Processing(Operation Staff) • Maintain air & sea import jobs and generate all the necessary documents as required. • Business Reporting (Operation Staff) • User Administration

5. Global use case diagram

7. Analysis Use Case #1Maintain Air Freight Job Records (Add)

9. Analysis Use Case #2 Search Customer Profile

11. Software Architecture

12. Architectural changes and motivations behind the changes

13. High Level design - Software Architecture

14. Software Components

15. Dual layer MVC architecture

16. UI Layer Data Package

17. JSON Parsing 3 1 2 5 4

18. Following are key features of Spring framework, which ECMS application enjoys: • Annotation Driven Architecture. • IOC or Dependency Injection by its Component Scanning mechanism, which saves the time for instantiation of user objects. • Decoupling between Dispatcher and Mapping and View resolving mechanism. • Aspect Oriented Programming model • Spring in-built role based security.

19. Spring MVC Architectural View

20. Data Base Layer

21. Prototype Stage Challenges

22. Prototype challenges (1)

23. Prototype challenges (2)

24. Technical Risks and Mitigation

27. Transition StrategyUser Interface Layer

28. Static Structure (1)

29. Static Structure (2)

30. Dynamic Structure

31. Asynchronous calls to server

32. Communication Between UI and Service Layer

33. Transition StrategyService Layer

34. Static Structure

35. Dynamic Structure

36. Transition StrategyPersistence Layer

37. Static Structure

38. Dynamic Structure

39. Deployment Structure

40. Progress Tracking

42. Expended Effort Vs Budgeted Effort for Phase 2 Activities

43. Plan for Implementation Phase

45. 1 team member to handle data persistence layer and creation of common objects ~ to complete by 7th Oct • 5 team member to handle detailed design spec (sequence diagram for 40+ use cases) in parellel ~ to complete by 7th Oct • 1 team member (identified from above 5) to start working on system test plan by mid Sept, the rest continue with design spec • Upon completion of design spec, 1 team member released from development to work on user guide and acceptance test plan • Remaining 3 plus the database team member to start coding by 7th Oct, task allocation by use case basis. • Target to complete coding, unit testing, code reviews and system integration by 25th Nov • System testing preparation starts as early as 19th Nov, estimate to complete testing and test results logging by end Dec • Kick-start documenting end-of-project report by 22th Oct, estimate to take place throughout till end of project phase

46. Change Request

47. Change Requests

48. We are getting stronger now… By overcoming obstacles encountered in phase 2: Obstacle 1: Small team, Big System Strategy: • Prototyping phase has produced a framework to help us in automating the dominating number of CRUD cases in the system Obstacle 2: Relaxing project tracking during early phase 2 Strategy: • Practiced close project tracking in meeting tighter deadlines nearer the end • Team power unleashed Obstacle 3: Manpower shortage closer to deadline Strategy : • Swapping of roles leading to discovery of better roles for team member Key to MovE forward

49. Questions and Answers