Integrated Electronic Message Board ( iEMB) Increment 2 Presentation, 27-Jan-2014 Team SE02S2 1

Team Members NameMatrix Number Gu Hong XiangA Raveendran VineethA Balasundaram SelvakumarA Sujatha SomasundaramA Viswalingam ArivazhaganA Kow Huey PingA Win Kyi TinA Yin Ni TunA

Agenda  Project Introduction  Global Use Case Diagram  Incremental Development Strategy  Software Architecture  Open Source Evaluation  Technical Challenges  Project Status  Project Deliverables Schedule  Project Effort  Management Challenges  Future Enhancement & Lesson Learnt  Demo  Q & A 3

Project Introduction  Title  Title : Integrated Electronic Message Board  Project Sponsor  Project Sponsor: Hwa Chong Institution  Objective  Objective :  To develop a future proof communication system  It allows the users to post and reply message; To share ideas and knowledge among users  To create and response survey  To maintain event calendar that can be downloaded and uploaded to outlook  To have web version that accessible via mobile device, including smart phones and tablets 4

Global Use Case Diagram 5

Incremental Development Strategy Iteration 1  Message Board  Event Calendar integrated with Outlook  System Administration Iteration 2  Survey Module  Accessibility via Portable Device  Basic Reports 6

Software Architecture  Language Choose :  HTML + JS + C# + MSSQL  Platform Choose:  Jquery + MVC 4  Plugin Choose:  Jquery UI, Jquery Template  About programming:  Open-Close (Open of extension and close for modification) ◦ TDD 7

Software Architecture  Layers  UI Layer  Jquery support  Javascript template engine  MVC4 Mobile/Web auto switch  Business Layer  IEMB  Business Factory  Business Implementer  Service API  Scheduler Management  DB Layer  Clown Fish framework  Simple Entity Framework  Survey (Open source solution – lime Survey) 8

Open Source Evaluation Lime SurveyDotNetNuke Survey Free, 100% Open Source CMS Software Low total cost of ownership Last Release: 16 January 2014Last Release : Sun Jul 3, 2011 at 4:00 PM Total Users: in community forumWebsite : Website : Production CriteriaLime SurveyDotNetNuke Survey 1Age Very MatureMature - OSS efforts that are just getting underway are risky for enterprises 2Multiple Supported Platforms Very MatureLess Mature - products that work on both Windows & UNIX are more desirableOnly support in Windows platform 3Momentum Very MatureLess Mature - this is key to helping separate vital products from ones that are withering 4Popularity Reasonably Mature No many online active users - popular OSS products are well tested & therefore more mature - they are also likely to be interoperable with a large number of other products 5Design Quality Very MatureLess Mature - this is key to determining the effort required to extend & adapt the product for enterprise use No proper CSS or UI design 9

Technical Challenges  Integration between open source solution which is in PHP and the main system in.NET platform.  Pipe line between 2 system  API Callback communication  SSO Login 10

Project Status  At the end of development stage  The development period has extended beyond the planned completion date  Project slippage  Development Status : Now… ModulesDevelopment Status Authenticate UsersCompleted Maintain Access ControlCompleted Maintain Event CalendarCompleted Maintain GroupCompleted Maintain Message (web version)Completed Maintain Message (mobile version)In-Progress Maintain Message BoardCompleted Maintain OrganizationIncomplete Maintain Parent AccountIncomplete Maintain Parent RatingCompleted Maintain SurveyIn-Progress Maintain System ConfigurationCompleted SendMailCompleted SendSMSCompleted 11

 Requested for project extension from ISS, new completion is targeted on 11-Feb-2014  Completing the development work  Re-plan impacted activities after development phase  To start system test and UAT immediate after development complete  On-site deployment Next… Project Status 12

Project Deliverables Schedule No.ActivityTargeted Completed DateActual/Revised Completed Date 1Initial Planning Produce Project Plan11 Apr 2013NC Produce Quality Plan14 Apr 2013NC 2Project Monitoring, Controlling and Administration First Quality Audit and Presentation15 Apr 2013NC Second Quality Audit15 Aug 2013NC Third Quality Audit15 Jan 2014NC End of Year Report26 Dec Feb Requirement Identification Produce User Requirement Spec.17 Mar 2013NC Sign-Off User Requirement Spec.18 Mar 2013NC Produce Use Case Model Survey27 Mar 2013NC 4Prototyping Produce Prototyping Study Report4 Apr 2013NC Incremental Phase 1 5Requirement Modeling 5.1 Produce Use Case Realization Report (Requirement) 29 Apr Jun Analysis Modelling 6.1Produce Use Case Realization Report (Analysis)6 May Jul

Project Deliverables Schedule No.ActivityTargeted Completed DateActual/Revised Completed Date Incremental Phase 1 7Design Modelling 7.1Produce Details Design Specification12 May Aug Produce ERD15 May 2013NC 8Database Design 8.1Produce DB Logical Design17 May 2013NC 8.2Produce DB Physical Design22 May 2013NC 9Code Development 9.1Produce Code30 May Feb Complete Unit Testing23 Jun Feb System Integration Test 10.1Produce System Testing Plan and Script19 May 2013NC 10.2Perform System Testing26 Jun 2013Ref. Incremental Phase 2 11User Acceptance Testing 11.1Produce UAT Plan and Script21 May Sep Produce User Guide28 Jun 2013Ref. Incremental Phase Produce UATRef. Incremental Phase Produce UAT Testing DocumentRef. Incremental Phase 2 14

Project Deliverables Schedule No.ActivityTargeted Completed DateActual/Revised Completed Date Incremental Phase 2 12Requirement Modelling 12.1 Produce Use Case Realization Report (Requirement) 15 Oct 2013NC 13Analysis Modeling 13.1Produce Use Case Realization Report (Analysis)20 Oct 2013NC 14Design Modeling 14.1Produce Details Design Specification25 Oct 2013NC 14.2Produce ERD28 Oct 2013NC 15Database Design 15.1Produce DB Logical Design5 Oct 2013NC 15.2Produce DB Physical Design8 Oct 2013NC 16Code Development 16.1Produce Code10 Dec Feb Complete Unit Testing13 Dec Feb System Integration Test 17.1Produce System Testing Plan and Script10 Dec 2013NC 17.2Perform System Testing23 Dec Feb Produce System Testing Document27 Dec Feb User Acceptance Testing 18.1Produce UAT Plan and Script16 Dec 2013NC 18.2Produce User Guide28 Dec Feb Produce UAT10 Jan Feb Produce UAT Testing Document13 Jan Feb

Project Effort MetricsTotal Man days Planned Effort Actual Effort 476 Variance

Management Challenges  Taken longer time in technology familiarization and development, result slippage in later activities  Asset management  MOE has advised schools to restrict server access from outside campus, as the result the team have to use self paid Windows Azure cloud Services as test server 17

Future Enhancement Lesson Learnt  Team work is the key for project success  Project issues should be highlighted to mentor earlier  Enhance more functions that supported by mobile version  Review the code, add comments to make them readable. 18

Q & A 19