INTEGRATED ELECTRONIC MESSAGE BOARDProject By : SE20 PT02
AGENDA
Project Background Project Introduction Requirements Overview Use Case Model Overview System Architecture Prototype Preview Project Plan Project Progress Risks and Risk Mitigation Management Issues Question and Answers
PROJECT BACKGROUND
After the merger of the Hwa Chong Junior College and the Chinese High School into Hwa Chong Institution, there have been many changes to the IT infrastructure
The maintenance of the current system is difficult due to legacy issues.
The proposed iEMB project is a priority project
iEMB will enhance the communication between Staff, Students and Parents
PROJECT INTRODUCTION
Project Objective To develop a future proof communication
system. Allow the organization to incorporate new
features. It will be more than a Message Board Incorporate useful features such as Discussion
Board and Survey, with a user-friendly and appealing interface.
With the workforce becoming more mobile, the communication system must be compatible with different mobile platforms, including smart phones and tablets.
PROJECT INTRODUCTION
Sponsor : Hwa Chong Institution
It is an Independent School with approximately 4000 students and 500 staff. It has High School and Junior College.
PROJECT TEAM & ROLES
Name Role
Selvakumar Project Manager
Win Kyi Tin Asst. Project Manager
Kow Huey Ping Business Analyst
Gu Hong Xiang Team Lead
Vineeth Ravindran System Analyst
Viswalingam Arivazhagan Developer
Yin Ni Tun Quality Manager
Sujatha Somasundaram Test Manager
PROJECT SCOPE (HIGH LEVEL)
Sno.
Function Priority
1. Topic Management High
2. File Attachment High
3. Survey Module High
4. System Configuration High
5. Manage Global Groups High
6. Message workflow for students Medium
7. Accessibility via Portable Device High
8. Maintain Events incorporate with Outlook Calendar
Medium
9. Notifications High
10. Reports Medium
IEMB REQUIREMENTS OVERVIEW
System Admin Functions
Message Board Administration SMS and Email Templates Global Group Administration Manage Roles and Access Rights
IEMB REQUIREMENTS OVERVIEW Stakeholders : Staff, Students and Parents
Staff, Students and Parents will be communicating via iEMB
Multiple Message Boards Staff Board Student Board Support Services Staff Suggestion Board Out of Campus Board
Messages like Announcements, Notices will be posted regularly via iEMB
Discussion Forum Staff can manage their own Private Groups Post Private Messages to Private Group
IEMB REQUIREMENTS OVERVIEW
Email alert when post a message Message creation workflow for students Facility to maintain events that
subsequently will be incorporated with Microsoft Outlook Calendar
Survey ModuleCreate Survey QuestionsRespond Survey Survey Results and Analysis Reports
Accessibility via Portable Devices with limited functionalities
IEMB USE CASE MODEL OVERVIEWINCREMENTAL 0
IEMB USE CASE MODEL OVERVIEW
Maintain User accounts
SystemAdmin
(f rom Actors)
Maintain Groups
(from Groups)
Staff
(f rom Actors)
Parents
(f rom Actors)
Maintain Messages
(from Messages)
Maintain Event
(from Events)
Student
(f rom Actors)
Maintain Survey
(from Survey)
SYSTEM ADMINISTRATION USE CASE – INCREMENTAL 1
User
(f rom Actors)
List all User accounts
(from Use Cases)
Search User accounts
(from Use Cases)
SystemAdmin
(f rom Actors)
Create User accounts
(from Use Cases)
Modify User accounts
(from Use Cases)
Maintain User accounts
(from Use Cases)
Remove User accounts
(from Use Cases)
Reset User Password
(from Use Cases)
SendMail
(from Use Cases)
MailSystem
(f rom Actors)
SendSMS
(from Use Cases)
SMS System
(f rom Actors)
<<extend>>
<<include>>
<<include>>
<<include>><<include>>
MAINTAIN GROUP USE CASE – INCREMENTAL 1
Create Groups
Modify Groups
Delete Groups
View Groups
Global Groups
SystemAdmin
(f rom Actors)
Private Groups
Staff
(f rom Actors)<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
MAINTAIN MESSAGE USE CASE (INCREMENTAL 1)
<<extend>>
Parents
(f rom Actors)
<<extend>>
<<include>><<include>>
<<include>>
<<include>>
Maintain Messages
(from Messages)
Staff
(f rom Actors)
Delete Message
(from Messages)
Modify Message
(from Messages)
SystemAdmin
(f rom Actors)
SendMail
SendSMS
<<include>>
<<include>>
Compose Message
(from Messages)
List All Messages
Search Message
Respond Message
(from Messages)
Message2mail
(from Messages)
Student
(f rom Actors)
<<extend>>
<<extend>>
SEND MAIL USE CASE (INCREMENTAL 1)
MailSystem
(f rom Actors)SendMail
MAINTAIN EVENT USE CASE – INCREMENTAL 1
Create Event
Modify Event
Delete Event
Staff
(f rom Actors) Maintain Event
<<include>>
<<include>>
<<include>>
<<extend>>
Parents
(f rom Actors)
Student
(f rom Actors)
List Event
MAINTAIN SURVEY USE CASE – INCREMENTAL 2
Parents
(f rom Actors)
Create Survey
Modify Survey
Delete Survey
Maintain Survey
Staff
(f rom Actors)
<<extend>><<include>>
<<include>>
<<include>>
Participate Survey
Student
(f rom Actors)
(from Use Cases)
<<extend>>
REPORTING USE CASE (INCREMENTAL 2)
SystemAdmin
(f rom Actors)
Generate Report
PROJECT APPROACH
Incremental and Iterative Approach
Requirements Analysis Design ImplementationIntegration
TestingUAT Release 1
Analysis Design ImplementationIntegration
TestingUAT Release 2
PROJECT APPROACH
Increment 1 Message Board Event Calendar integrated with Outlook System Administration
Increment 2 Survey Module Accessibility via Portable Device Basic Reports
PROJECT PLAN – WBS & EFFORT SEL (PM)
WKT (APM) HP (BA) VIN (SA) HX (TL) AZ (Dev) YNT (QA) Suj (TestMgr) Total
Activity 1 - Initial PlanningStructure Project Team 1 1Setup Filing System 1 1Produce Project Plan 6 5 11Produce Quality Plan 8 8Review and Finalize Project Plan 1.5 1.5 0.5 0.5 0.5 0.5 0.5 0.5 6Review and Finalize Quality Plan 0.5 0.5 0.5 0.5 0.5 0.5 1.5 0.5 5 Activity 2- Project Monitoring, Controlling, AdministrationProduce Monthly Progress Report 1 1 0.5 0.5 0.5 0.5 1 0.5 5.5
Conduct Weekly Internal Progress Meeting 9 9 9 9 9 9 9 9 72
Prepare First Quality Audit and Presentation 1 1 2Preform Corrective Actions 1 1 1 1 1 1 1 1 8
Prepare Second Quality Audit and Presentation 1 1 0 2Perform Corrective Actions 1 1 1 1 1 1 1 1 8
Prepare Third Quality Audit and Presentation 1 1 2Preform Corrective Actions 1 1 1 1 1 1 1 1 8Produce End of Project Report 3 3
Review and Finalize End of Project Report 1.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 5 Activity 3 – Requirements Identification
Kick-off Meeting and Interview Users 3 1 1 5
Produce User Requirement Spec Draft 5 5
Review User Requirement Spec Draft 0.5 0.5 1.5 0.5 0.5 0.5 0.5 0.5 5Second Meeting with Users 1 1 1 1 1 5Revise User Requirement Spec 2 2
Review and Finalize User Requirement Spec 0.5 0.5 1.5 0.5 0.5 0.5 0.5 0.5 5
Sign-off User Requirement Specification 0.5 0.5 1Produce Use Case Global View 3 3Produce Use Case Model Survey 3 3
Review and Finalize Use Case Model Survey 0.5 0.5 1.5 0.5 0.5 0.5 0.5 0.5 5
Sign Off Production System by User 0.5 0.5TOAL 64 65 65 63.5 65 64 65 64.5 516
PROJECT PLAN – FUNCTION POINT ESTIMATION
Adjustment factor = 0.65 + 0.01 * Total Degree of Influence
1.0
Adjusted Function Point Count= Unadjusted FPC * Adjustment Factor= 385 * 1.0
385
PROJECT PLAN – SCHEDULE & PROGRESS
SCHEDULE & PROGRESS Overall Progress : % Project Status : On track
PROJECT RISKSSno Risk Factors Impact on the
BusinessOwner to Monitor the Risk
When to Activate Mitigation Strategies
1 Support Multiple Browsers Less user friendly QM Initial Phase Prototype to test the compatibility/portability against the browsers, to ensure maximum compatibility, at least support IE, Chrome, Firefox and Safari
2 Lack of Technical Skill sets Development slow
TL Initial Phase Knowledge sharing among team members Additional Team Training.
3 Volatile User Requirements during development
Delay in delivery PM Project Progress Regular meet up with the customer Effective communications between the team
and customer via email
4 Security concerns when upload files
System threats TL Initial Phase Prototype 3rd Party Tools Check the file extensions and file size.
5 No Domain Expert Development Slow
SA Project Progress Assign team members to gain domain knowledge by attending briefing by customer
6 Loss of Resources (e.g. Manpower)
Activities affected PM Main person not available
Redistribute the work among team members, based on the backup plan.
MANAGEMENT ISSUES
Slow user response e.g. Sign off issues Volatile User Requirements We try to work closely with the client
TECHNICAL – HIGH LEVEL DESIGN
Introduction of the design Software Architecture Prototype Q & A
INTRODUCTION
Design scope High performance Stability Security User friendly Configurability Easy to maintain Cross Platform, Cross Browser
SOFTWARE ARCHITECTURE
Provided Hardware Windows Server 2008 Microsoft AD Gateway
System to be migrated Written by ASP.NET Host by IIS 7.5 Persistent by MSSQL 2008
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
SOFTWARE ARCHITECTURE
SOFTWARE ARCHITECTURE
SOFTWARE ARCHITECTURE Why MVC4 not MVC3?
Latest technology Higher performance Mobile Support
Views can be view for desktop version, view for iphone version and view for Android version
Auto detect screen side Auto adjust css/images
SOFTWARE ARCHITECTURE
SOFTWARE ARCHITECTURE Factory + Singleton
System support multiple roles Each role have same business rule but different
implementation Those may implement frequency.
SOFTWARE ARCHITECTURE
Q & A Any Question ?
Thank You!
Top Related