Integrated Electronic Message Board

(iEMB)

Phase 2 Presentation

Team S02PT

Team MembersName Matrix Number

Gu Hong Xiang A0093803Raveendran Vineeth A0092690Balasundaram Selvakumar A0092673Sujatha Somasundaram A0092602Viswalingam Arivazhagan A0092649Kow Huey Ping A0092706Win Kyi Tin A0005686Yin Ni Tun A0006414

Agenda Introduction and Scope of project Global use case diagram Analysis use cases Incremental Development Strategy Software Architecture Transition Strategy Technical risks and mitigation Management Problems Progress Tracking Change Requests Demo for Maintain Message Plan for Incremental 2

Project Introduction Title : Electronic Message Board Stakeholders : Staff, Students and Parents Objective : To develop a future proof communication

system. It allows the users to Post, Reply and private messaging to

other users. To share ideas and knowledge. To Create and Manage Surveys. Accessible via mobile platforms, including smart phones

and tablets.

Global use case diagram

Analysis Use case #1Maintain Message (Compose)

Analysis Use case #1Maintain Message (Display)

Analysis Use case #1Maintain Message (Response Message)

Incremental Development StrategyIteration 1Message BoardEvent Calendar

integrated with Outlook

System Administration

Iteration 2Survey ModuleAccessibility via

Portable DeviceBasic Reports

Software ArchitectureLanguage Choose :

◦HTML + JS + C# + MSSQL Platform Choose:

◦Jquery + MVC 4 Plugin Choose:

◦Jquery UI, Jquery Template Programming Principle:

◦Open-Close (Open of extension and close for modification)

Software ArchitectureWhy

◦Easy to migrate◦80% developers are familiar with

those technical◦Experience and self-confidence for

architect◦Fast development ◦Easy to maintain◦Easy to collect information/tutorial for

beginner

Software ArchitectureLayers

◦ UI Layer Pure JavaScript mode Jquery support MVC4 Support

◦ Business Layer IEMB

Business Factory Business Implementer

Survey Service

◦ DB Layer Simple Entity Framework

ADO.NET

Software Architecture

Software Architecture

Software Architecture

Transition Strategy

Static Structure

Transition StrategyDynamic Structure

Demo of Increment 1http://imessageboard.cloudapp.n

et

Project Status

Schedule Variance

Project Plan - Schedule

Project Plan - Schedule

Project Plan - Schedule

Management ProblemProject Slippage

Plan for Incremental 2Incremental 1 phase has produced a

framework to help us in automating the dominating number of CRUD cases in the system

Practiced close project tracking in meeting tighter deadlines nearer the end

Team power unleashedSwapping of roles leading to discovery

of better roles for team member

Q & A