Integrated Electronic Message Board ( iEMB) Phase 2 Presentation Team S02PT

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  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  Title : Electronic Message Board  Stakeholders  Stakeholders : Staff, Students and Parents  Objective  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 #1 Maintain Message (Compose)

Analysis Use case #1 Maintain Message (Display)

Analysis Use case #1 Maintain Message (Response Message)

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

Software Architecture Language 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 Architecture Why ◦ 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 Architecture Layers ◦ 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

Transition Strategy Static Structure

Transition Strategy Dynamic Structure

Demo of Increment 1

Project Status

Schedule Variance

Project Plan - Schedule

Management Problem Project Slippage

Plan for Incremental 2  Incremental 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 unleashed  Swapping of roles leading to discovery of better roles for team member

Q & A