ECMS Phase 2 Presentation

ECMS Phase 2 PresentationTeam S07AgendaScope of projectGlobal use case diagram Analysis use cases High Level design (Software Architecture)Prototype challenges faced and remaining Technical risks mitigatedTransition strategy Management Issues / Change RequestsManagement Progress and TrackingPlans for implementation phase

Scope of projectGlobal use case diagram Analysis Use Case # 1Architectural changes and motivations behind the changesSNoChangeMotivation1Traditional user interface approach left and adopted Rich User InterfaceCustomer requirement of having enhanced UI with less number of steps to perform an operations.Intuitive UI.Non-Blocking UI experience.

2EJB centric approach has dropped, and Web centric approach adopted.

Support to Rich UI framework, which does most of the processing by using client resources such as browser cache and client machine processor which doesnt need the container to manage heavy EJBInstead an efficient and light weight container required to service Rich UI componentsSoftware ArchitectureHigh Level design - Software Architecture

Software ComponentsThird party Software Component and librariesVendorLicenseJDK/ JREOracleSun License (most of it also under GPL)Spring Framework 3.0Spring SourceSpring libraries are licensed under the terms of the Apache License, Version 2.0.Ext JS 4.0SenchaExtJs 4.0 is available in dual licensing scheme; however, we have used it under the licensing terms of GNU GPL license v3.Hibernate CoreJBOSS CommunityThe GNU Lesser General Public License version 2.1 (LGPLv2.1)Tomcat 7.0ApacheApache Tomcat is developed under the Apache License version 2Dual layer MVC architecture

UI Layer Data Package

JSON Parsing

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 modelSpring in-built role based security.

Spring MVC Architectural View

Data Base Layer

Prototype Stage ChallengesPrototype challenges (1)SnoChallengesAction Performed /Solutions1To reduce the number of steps taken to complete a user operationRequirement of having many CRUD operation with less number of steps, this is challenging to achieve if we proceed with a traditional approach of UI using HTML forms and pagesUsed Rich UI components from third party open source libraries with AJAX to provide enhanced user interface, which capable of operations without leaving a page2To reduce the latency time for a User actionFor non-blocking user experience of ECMS UI, it requires to reduce the latency time, which is time taken between data packets leaves and receive, from and by the client browser for given user commandAjax communication between UI and Service layer to meet this challengePrototype challenges (2)SnoChallengesAction Performed /Solutions

3Technological evolution (UI layer framework)Ext JS framework was revised in April 2011 from 3.x to 4.x which includes the MVC architecture. This change has required us to move to ExtJS 4.x and refactor the design at Client Tier to exhibit MVC architecture introduced in ExtJS 4.x.ExtJS 4.x documentation followed and revised the UI layer structure, integrated ExtJS 4.x together with ExtJS 3.x, to not to disturb existing modules.New features development with carry on using ExtJS 4.x and Ext3.x features shall be interchange with ExtJS4.x4Novelty of Technology Ext JS 4.x and Spring framework 3.x are new technologies which have recently released in 2011.An important use case prototyped. Technical Risks and MitigationTechnical Risks Mitigated (1)SnoRiskRisk Mitigation1Integration of two new frameworks at different layers (ExtJS (UI) and Spring framework (Service)), where team has no prior experience.Integrating two frame works performed in steps, as two unknown frameworks required good time of study and analysis.UI layer integrated to the system with ExtJS framework, which communicates to the server using Servlet technology.Spring Controller accessed by JSP at front end.JSP interchanged with Java Script and Servlet interchanged with Spring MVC Controller to finally integrate both layer MVCs2Exchanging Objects between layersPrototyped by sending JSON from UI Layer to Server and transform to JAVA object at Service Layer and vice versa.Technical Risks Mitigated (2)SnoRiskRisk Mitigation3Managing large number of records at UI Layer on general user queries (Risk realized proactively)Pagination Feature prototyped to mitigate the risk.Pagination send Ajax request to get the limited number of records on Java Script load.HibernateCallback implemented to get the limited number of records.4Analysis boundary objects realization using Java Script ComponentsMain Job use case implemented using ExtJS and Spring MVC.Transition StrategyUser Interface LayerStatic Structure (1)

Static Structure (2)

Dynamic Structure

Asynchronous calls to server

Communication Between UI and Service LayerTransition StrategyService LayerStatic Structure

Dynamic Structure

Transition StrategyPersistence LayerStatic Structure

Dynamic Structure

Deployment Structure

Management IssuesChange RequestsManagement Progress and TrackingPlans for implementation phaseExpected implementation issuesQuestions and AnswersSystem Administrator