1

Integrated ElectronicMessage Board

(iEMB)

Increment 2 Presentation, 27-Jan-2014

Team SE02S2

2

Team MembersName Matrix Number

Gu Hong Xiang A0093803

Raveendran Vineeth A0092690

Balasundaram Selvakumar

A0092673

Sujatha Somasundaram A0092602

Viswalingam Arivazhagan

A0092649

Kow Huey Ping A0092706

Win Kyi Tin A0005686

Yin Ni Tun A0006414

3

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

4

Project Introduction

Title : Integrated Electronic Message Board

Project Sponsor: Hwa Chong Institution

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

5

Global Use Case Diagram

6

Incremental Development Strategy

Iteration 1 Message Board Event Calendar

integrated with Outlook

System Administration

Iteration 2 Survey Module Accessibility via

Portable Device Basic Reports

7

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

8

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)

9

Open Source EvaluationLime Survey DotNetNuke Survey

Free, 100% Open Source CMS Software Free, 100% Open Source CMS Software

Low total cost of ownership Low total cost of ownership

Last Release: 16 January 2014 Last Release : Sun Jul 3, 2011 at 4:00 PM

Total Users: 19647 in community forum Website : http://dnnsurvey.codeplex.com/

Website : http://www.limesurvey.org/en/  

Production Criteria Lime Survey DotNetNuke Survey

1 Age  Very Mature Mature

- OSS efforts that are just getting underway are risky for enterprises  

2 Multiple Supported Platforms  Very Mature Less Mature

- products that work on both Windows & UNIX are more desirable Only support in Windows platform

3 Momentum  Very Mature Less Mature

- this is key to helping separate vital products from ones that are withering  

4 Popularity  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  

5 Design Quality  Very Mature Less Mature

- this is key to determining the effort required to extend & adapt the product for enterprise use

No proper CSS or UI design

10

Technical Challenges Integration between open source solution

which is in PHP and the main system in .NET platform.

Pipe line between 2 systemAPI Callback communicationSSO Login

11

Project Status

At the end of development stage The development period has extended

beyond the planned completion date Project slippage Development Status :

Now…

Modules Development StatusAuthenticate Users CompletedMaintain Access Control CompletedMaintain Event Calendar Completed

Maintain Group CompletedMaintain Message (web version) CompletedMaintain Message (mobile version) In-ProgressMaintain Message Board CompletedMaintain Organization IncompleteMaintain Parent Account IncompleteMaintain Parent Rating CompletedMaintain Survey In-ProgressMaintain System Configuration CompletedSendMail CompletedSendSMS Completed

12

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

13

Project Deliverables ScheduleNo. Activity Targeted Completed Date Actual/Revised Completed Date

1 Initial Planning

Produce Project Plan 11 Apr 2013 NC

Produce Quality Plan 14 Apr 2013 NC

2 Project Monitoring, Controlling and Administration

First Quality Audit and Presentation 15 Apr 2013 NC

Second Quality Audit 15 Aug 2013 NC

Third Quality Audit 15 Jan 2014 NC

End of Year Report 26 Dec 2013 8 Feb 2014

3 Requirement Identification

Produce User Requirement Spec. 17 Mar 2013 NC

Sign-Off User Requirement Spec. 18 Mar 2013 NC

Produce Use Case Model Survey 27 Mar 2013 NC

4 Prototyping

Produce Prototyping Study Report 4 Apr 2013 NC

Incremental Phase 1

5 Requirement Modeling

5.1 Produce Use Case Realization Report

(Requirement)

29 Apr 2013 30 Jun 2013

6 Analysis Modelling

6.1 Produce Use Case Realization Report (Analysis) 6 May 2013 15 Jul 2013

14

Project Deliverables Schedule

No. Activity Targeted Completed Date Actual/Revised Completed Date

Incremental Phase 1

7 Design Modelling

7.1 Produce Details Design Specification 12 May 2013 01 Aug 2013

7.2 Produce ERD 15 May 2013 NC

8 Database Design

8.1 Produce DB Logical Design 17 May 2013 NC

8.2 Produce DB Physical Design 22 May 2013 NC

9 Code Development

9.1 Produce Code 30 May 2013 1 Feb 2014

9.2 Complete Unit Testing 23 Jun 2013 1 Feb 2014

10 System Integration Test

10.1 Produce System Testing Plan and Script 19 May 2013 NC

10.2 Perform System Testing 26 Jun 2013 Ref. Incremental Phase 2

11 User Acceptance Testing

11.1 Produce UAT Plan and Script 21 May 2013 15 Sep 2013

11.2 Produce User Guide 28 Jun 2013 Ref. Incremental Phase 2

11.3 Produce UAT Ref. Incremental Phase 2 Ref. Incremental Phase 2

11.4 Produce UAT Testing Document Ref. Incremental Phase 2 Ref. Incremental Phase 2

15

Project Deliverables Schedule

No. Activity Targeted Completed Date Actual/Revised Completed Date

Incremental Phase 2

12 Requirement Modelling

12.1 Produce Use Case Realization Report

(Requirement)

15 Oct 2013 NC

13 Analysis Modeling

13.1 Produce Use Case Realization Report (Analysis) 20 Oct 2013 NC

14 Design Modeling

14.1 Produce Details Design Specification 25 Oct 2013 NC

14.2 Produce ERD 28 Oct 2013 NC

15 Database Design

15.1 Produce DB Logical Design 5 Oct 2013 NC

15.2 Produce DB Physical Design 8 Oct 2013 NC

16 Code Development

16.1 Produce Code 10 Dec 2013 1 Feb 2014

16.2 Complete Unit Testing 13 Dec 2013 1 Feb 2014

17 System Integration Test

17.1 Produce System Testing Plan and Script 10 Dec 2013 NC

17.2 Perform System Testing 23 Dec 2013 4 Feb 2014

17.3 Produce System Testing Document 27 Dec 2013 4 Feb 2014

18 User Acceptance Testing

18.1 Produce UAT Plan and Script 16 Dec 2013 NC

18.2 Produce User Guide 28 Dec 2013 8 Feb 2014

18.3 Produce UAT 10 Jan 2014 10 Feb 2013

18.4 Produce UAT Testing Document 13 Jan 2014 10 Feb 2014

16

Project Effort

Metrics Total Man days

Planned Effort 514.5

Actual Effort 476 

Variance 38.5

17

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

18

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.

19

Q & A