Algorithm,€¦ · Alarm’ Manual’Input’ Scan’ Group ... 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 ’ ’ ’ ’ ’ ’ 06Jun 13Jun 20Jun 27Jun 04Jul 11Jul 18Jul 25Jul ’

SLIDE: 2 of 3 FYP Presentation

Scope / Demo

Scope / Demo Industry Knowledge Client requirement

Introduction

Schedule

UAT

metrics

Risks

LOMs

Sta$on Module Ques$on Score Category Weightage

Sta$on 3 Op#on-‐Based

1 30% Outlook 100%

2 20% Judgement 100%

3 30% Depth of thinking

100%

Sta$on 4 … … … … …

Algorithm


Scope / Demo


Introduction

Schedule

UAT

metrics

Risks

LOMs

Algorithm Outpu;ng

Category Sta$on Range (%) Output Depth of Thinking Sta#on 1 0 – 50 “Student is … “

51 – 70 Output A

71 – 100 Output B

Sta#on 2 … …

Category Sta$on Range (%) Output Outlook Sta#on 1 0 – 40 “Student is … “

41 – 60 Output X

61 – 100 Output Y

Sta#on 2 … …

Category Sta$on Range (%) Output Judgement Sta#on 1 0 – 40 “Student is … “

41 – 60 Output 1

61 – 100 Output 2

Sta#on 2 … …


Scope / Demo


Introduction

Schedule

UAT

metrics

Risks

LOMs

Algorithm Outpu;ng

Sta$on Category Score Output 1 Outlook 20% “Student is … He/

She should … To achieve…”

Depth of thinking 60% [Output A]

Judgement 70% [Output 2]


Scope / Demo


Introduction

Schedule

UAT

metrics

Risks

LOMs

Opera#on Tracking Applica#on

Money Calcula$on Comments Comments

Supermarket Scenario-‐based Decision-‐making

Batch 1 Batch 2 Batch 3


Scope / Demo


Introduction

Schedule

UAT

metrics

Risks

LOMs

Opera#on Tracking Applica#on

• Func$onali$es

• Speech to Text ü  Customized modules and personal touch through QR iden#fica#on

Alarm Manual Input Scan Group individuals


Scope / Demo


Introduction

Schedule

UAT

metrics

Risks

LOMs

X Factor •  Reports ü  Customized configura#on to tailor to exactly how YDC wants the progress tracking report to be ü Integrated with OTA customized modules to achieve that ü  Increases charges to school by est 20%.

•  Traffic Management ü  Integrated with instant messaging func#on to punch out messages to sta#ons

• Opera$on tracking Applica$on ü  Customized modules and personal touch through QR iden#fica#on


Schedule

Schedule Industry Knowledge Client requirement

Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐15 -‐14 -‐13 -‐12 -‐11 -‐10 -‐9 -‐8 -‐7 -‐6 -‐5 -‐4 -‐3 -‐2 -‐1 0

25-‐Apr

02-‐M

ay

09-‐M

ay

16-‐M

ay

23-‐M

ay

30-‐M

ay

06-‐Ju

n

13-‐Ju

n 20-‐Ju

n

27-‐Ju

n 04-‐Ju

l 11-‐Ju

l 18-‐Ju

l 25-‐Ju

l 01-‐Aug

08-‐Aug

Proposal Submission

PS (15 Jun)

Milestone A A (15 Jul)

Milestone B B

Acceptance Presenta#on

AP


Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

0 1 2 3 4 5 6 7 8 9 10 11 12

08-‐Aug

15-‐Aug

22-‐Aug

29-‐Aug

05-‐Sep

12-‐Sep

19-‐Sep

26-‐Sep

03-‐Oct

10-‐Oct

17-‐Oct

24-‐Oct

31-‐Oct

Milestone C C (21 Sept)

Mid-‐Terms Presenta#on

MT

Milestone D D (15 Oct)

Milestone E E (29 Oct)


Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

11 12 13 14 15 16

24-‐Oct

31-‐Oct

07-‐Nov

14-‐Nov

21-‐Nov

28-‐Nov

Commissioning Commission

Performance Guarantee Period (PGP, 1 month)

PGP end

Final Presenta#on FP


Schedule

Schedule

Industry Knowledge Client requirement

Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐10 -‐9 -‐8 -‐7 -‐6 -‐5 -‐4

30-‐M

ay

06-‐Ju

n

13-‐Ju

n

20-‐Ju

n

27-‐Ju

n

04-‐Ju

l

11-‐Ju

l

Requirements gathering (6 July)

User Interface Mock up (6 July)

Proposal Submission (15 Jun) Prototyping -‐ Android login, 3 modules, QR codes genera#on, Mgmt Portal (Access Control Matrix), Traffic Mgmt

(7 July)

User Acceptance Test Milestone A (8 July)

System Trial -‐ YCKSS

Assessment of risks, scope and feasibility

Project Management Monthly 1 (26 June)

Phase 2: Elabora#on


Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐15 -‐14 -‐13 -‐12 -‐11 -‐10

25-‐Apr-‐11

02-‐M

ay-‐11

09-‐M

ay-‐11

16-‐M

ay-‐11

23-‐M

ay-‐11

30-‐M

ay-‐11

Requirements gathering (14 May)

User Interface Mock up (14 May)

Prototyping -‐ web portal WP MP -‐ ACL

Assessment of risks, scope and feasibility

Phase 1: Incep#on


Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐4 -‐3 -‐2 -‐1 0 1 2 3 4 5 6 7 8 9

11-‐Ju

l

18-‐Ju

l

25-‐Ju

l 01-‐Aug

08-‐Aug

15-‐Aug

22-‐Aug

29-‐Aug

05-‐Sep

12-‐Sep

19-‐Sep

26-‐Sep

03-‐Oct

10-‐Oct

Smart FAQs (6 Aug)

Progress Tracking Report

(30 July)

OTA (Android) 6 modules

(30 July)

(19 Aug)

OTA (Android) func#ons (alarm, group users, notes)

(30 July) (1 Sept)

OTA Configura#ons (15 Sept)

OTA Integra#on

Phase 3: Construc#on


Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐4 -‐3 -‐2 -‐1 0 1 2 3 4 5 6 7 8 9

11-‐Ju

l

18-‐Ju

l 25-‐Ju

l 01-‐Aug

08-‐Aug

15-‐Aug

22-‐Aug

29-‐Aug

05-‐Sep

12-‐Sep

19-‐Sep

26-‐Sep

03-‐Oct

10-‐Oct

Personality Test (30 July)

(1 Sept)

Management Report

Instant Messaging func#on

Flash Based Game

Speech to text func#on

(4 Oct)



Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

-‐2 -‐1 0 1 2 3 4 5 6 7 8 9

25-‐Ju

l

01-‐Aug

08-‐Aug

15-‐Aug

22-‐Aug

29-‐Aug

05-‐Sep

12-‐Sep

19-‐Sep

26-‐Sep

03-‐Oct

10-‐Oct

Web Portal -‐ Video Plug-‐in

(4 Oct)

User Acceptance Test

B (1 Aug) C (21 Sept)

Acceptance/ Mid-‐term presenta#on

AP (11 Aug) MP

Project Management Monthly

2 (1 Sept) 3 (20 Sept)



Schedule


Scope / Demo

Introduction

UAT

metrics

Risks

LOMs

7 8 9 10 11 12 13 14 15 16

26-‐Sep

03-‐Oct

10-‐Oct

17-‐Oct

24-‐Oct

31-‐Oct

07-‐Nov

14-‐Nov

21-‐Nov

28-‐Nov

Deployment (11 Oct)

User Manual (14 Oct) (9 Nov)

Day in a life workshop (25 Oct)

Analysis and Report (25 Oct)

User Acceptance Test (SIT, Stress Test, Reliability Test)

D (15 Oct)

E (29 Oct)

Commissioning Acceptance Test

(11 Nov)

Final Presenta#on

Phase 4: Transi#on


UAT

UAT Industry Knowledge Client requirement

Scope / Demo

Schedule

Introduction

metrics

Risks

LOMs

Project Management

Report Traffic Management

Portal Opera$on Tracking Applica$on


Metrics

Metrics Industry Knowledge Client requirement

Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Schedule Metrics S/n Progress Project status

1 Tasks completed 3 days in advance / completed on #me

2 Tasks due in less than 3 days/ Task is completed + 3 days of original deadline

3 Task due/ s#ll not completed in + 3 days of original deadline


Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Schedule Metrics

PM Report Traffic Mgmt Portal OTA Owner (Ascension)

Ng Choon Teck Au Cheong Hing Chen Junfan Peh Wei Kiat Chee Jing Hui

Scope Schedule Requirements gathering Deliverable matrix Schedule matrix Bug matrix Smart FAQ

Individual progress tracking report Management tracking report

Traffic management QR codes generater Smart FAQs Instant messaging Integration

Front-end Management portal Flash based games Flash based personality test

OTA 6 modules QR codes reader Android functionalities except alarm Connection to database

Work-in-Progress

1.  Full requirement spec

2.  PMM 2 3.  Smart FAQ

1.  Logic on integration between BIRT report and config

1.  Smart FAQs 1.  Front-end – pending info from sponsor

2.  Personality test in progress

1.  Node dollars – pending refinements

2.  Comment and option based module not started

Testing As per milestone B deliverables

As per milestone B deliverables



As per milestone AB deliverables

Deliverables��Milestone B

1.  Schedule completed and submitted

2.  Processes completed

3.  Charter signed

1.  3 module completed for progress tracking module and algorithm for entire reporting module

1.  Traffic management done

1.  Mock up for personality test done up

2.  Web and management portal done up

1.  4 modules done up

2.  Functions except alarm is done up


Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Schedule Metrics


Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Schedule Metrics Score Ac$on

<0.8 Review why is there an underes#ma#on of the dura#on. Review bug metric to check on quality of codes.

>1.5 Assess impact on next milestone Assess cause of delay and come up with mi#ga#on to minimise future risk. Schedule for over#me work to catch up pace.

>2 Assess cause of delay. Consider discussion with sponsor and supervisor on cu;ng non-‐ major deliverables. Reshuffle schedule.


Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Itera$on Expected dura$on

Actual dura$on Score

1 11 11 1

2 11 11 1

3 14 14 1

4 24 24 1

5 15 24 1.6

Schedule Metrics

0

2

1 2 3 4 5

Score

Itera$on

Chart Title


Metrics

Metrics Bug Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Impact Level Score Descrip$on

Cosme#c/Trivial 1 Defect that is cosme#c and have low or no impact to system usage

Minor 3 Defect that results an impact on system usage of non cri#cal business functon, with alterna#ve workaround

Major 5

Defect that results in a system or cri#cal business func#on failure, with alterna#ve workaround

Show Stopper 10

Defect that results in a system or cri#cal business func#on failure, without alterna#ve workaround


Metrics

Metrics Bug Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Metrics score Ac$on >25 More #me to be scheduled for debugging

>50 The func#on responsible for the majority of the score will stop and perform debugging #ll score hits below 50

>100 All to stop and reschedule #me to debug


Metrics


Scope / Demo

Schedule

UAT

Introduction

Risks

LOMs

Bug Metrics

Milestone Number of

bugs Resolved Unresolved Score

A 18 14 4 10

B 35 15 20 48

10

48

0 0 0 0 0

20

40

60

A B C D E F

Bug Metrics


Risks

Risks Industry Knowledge Client requirement

Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Likelihood Poten$al Impact Insignificant Moderate Catastrophic

Almost Certain (a persistent issue) Likely (will probably recur, but not a persistent issue) Possible (may recur occassionally) Unlikely (do not expect it to happen again) Rare (Cannot believe that it can happen again)


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Business

Descrip$on Likelihood Impact Ra$ng

Sponsor is a new start-‐up. Much of the requirements remain unclear and the client do not know what they do not know. Hence requirements may change over #me.

Likely Catastrophic

Unclear & Evolving Business Requirement


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Business

1.Adopt Iterative Approach 2. Conduct detailed user requirements gathering 3. Ask questions relating to the problem they faced rather than the solution they think they want 4. Increase user participation and stake in the project 5. Highlight risk and tradeoffs discussion with sponsor

Unclear & Evolving Business Requirement


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Business


Sponsor has changed Project Manager twice, owners of the various tasks are not firmed up. High possibility that owner's agreement is over writen by higher management

Possible Moderate

Unclear ownership of tasks and issues


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Business

1. Agreement of owners of various tasks and decision makers. 2. Perform mocks up of user requirement for owners to bring back and discuss with higher management. 3. Conduct periodic User Acceptance Test and PMM to ensure higher management are updated and in agreement with work performed

Unclear ownership of tasks and issues


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical Integration Issues


Our project is developed on 2 different plavorms, WAMP and Tomcat. Hence, integra#on issues may occur.

Likely Moderate


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical

1.  Research to be done prior to integration.

2. Regular integrations to be done before end of each milestone if applicable. 3. Seek help from supervisor or online forums if problem persists.

Integration Issues


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical Learning of a new technology Descrip$on Likelihood Impact Ra$ng

Our project consists of several new technologies to us, for example, the use of Android SDK and BIRT Project, which requires #me for us to familiarize ourselves in order to carry on with development.

Likely Moderate


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical

1.  Allocate time for the familiarizing of technology.

2. Attend training workshops organized by external parties if relevant. 3. Have internal group technological training sessions where any member who are more familiar with the technology can coach the others.

Learning of a new technology


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical Connection via 3G SIM card


Heavy dependency on internet connec#on to establish connec#on and tracking to the management portal from Android App

unlikely Catastrophic


Risks


Scope / Demo

Schedule

UAT

metrics

Introduction

LOMs

Technical

1. Convert connection to wiFi using wireless router 2. Standby SIM card from different telcos. 3. Tracking information stored locally in Android

DB, traffic management module switch off

Connection via 3G SIM card


LOMs

LOMs

Business-IT linkage • Assess the key processes of YDC’s activity • Identify areas where IT solutions can replace processes or solve issues.


Scope / Demo

Schedule

UAT

metrics

Risks

Introduction


LOMs

LOMs

Technical skills + integration Industry Knowledge Client requirement

Scope / Demo

Schedule

UAT

metrics

Risks

Introduction

Documents

Algorithm,€¦ · Alarm’ Manual’Input’ Scan’ Group ... 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 ’ ’ ’ ’ ’ ’ 06Jun 13Jun 20Jun 27Jun 04Jul 11Jul 18Jul 25Jul ’