城 大 電 腦 工 程 及 資 訊 科 技 系 副
授 鄭 利 明 相 信 問 題 是 出 於 程 式 誤 差 ， 令 易 辦 事 與 八 達 通 系 統 未 能 同 步 處 理 交 易 ， 建 議 八 達 通 可 向 卡 主 發 電 話 短 訊 ， 以 確 認 完 成 交 易 。 八 達 通 去 年 12 月 更 新 系 統 後 ， 今 年 1 月 初 有 兩 名 市 民 發 現 以 易 辦 事 增 值 被 扣 錯 數 才 揭 發 事 件 。 look at the test case, the test script ......the test result....? Has the test plan been reviewed?
6 comments:
八達通多扣數早有前科 EPS增值05年已出錯 ... there are 'incidents' occured before ... did people notice back in year 2005? let's get this e-transactions resolved ASAP ...
Basically, network upgrade would not affect the system, and network team did not have enough technical skills to handle the application details, the trouble came easily!
I'll get the same trouble after CNY......
'network upgrade' may/may not affect the system. i think it depends on what type of work is done, and what your vendor told you on the detail; such as hardware/software impact? is old configuration in the network remain the same? even the network team is not technical, it's project manager who handle the project to ensure that the application user, or "END USER" be there to verify/validate the application is still performing the "same level" as it was before and after upgrade. simply put - we just don't do a hardware/software upgrade, after the device is upgraded (or new code is loaded) then the network team just walk away, or call it done? man! team work again ... thorough planning and execution step. you always want to fall back to the previous settings if your users said the upgrade has adversely impacted the application. Just my 2 cents ...
Hey, this is IT lor.....
and this is what disappointed me in my workplace lor....
Now, I focus on process and improvement, I don't touch on production environment. I hope I can step back and relax.....
Anyway, by statistics, INCIDENTS(in ITIL) or PRODUCTION PROBLEMS are usually caused by CHANGES.
Really that useful for ITIL? I dunno......
BTW, 情人節快樂
Post a Comment