1) Telecom system sounds large, but it looks like a pure server app, no UI, no real users, therefore some clever math, a database and a few services = 60 points, 50 points for overall complexity +10 for 24x7x365. Would get more points for integrating with a MF, or being written in reduced set kanji.
2) Horse betting, now we're talking, people on the phones, call centre, lots of UI, lots of interaction, lots of filthy lucre. I'd give that a 70, you do get 4 hours/day for maintenance, but if it was down for 30 seconds I'd doubt if you'd live long enough to get to that support window.
3) Yawn, Ajax is kind of cool, but the main complexity of CRM has got to be long running transactions, backed by billing systems and name and address. I'd give it a 35.
发布评论
评论（1）
这是我的看法
1) 电信系统听起来很大，但它看起来像一个纯粹的服务器应用程序，没有 UI，没有真正的用户，因此一些聪明的数学，数据库和一些服务 = 60 分，整体复杂性 50 分 + 24x7x365 10 。 与 MF 集成或以简化的汉字书写会获得更多积分。
2) 赌马，现在我们正在谈论，人们打电话，呼叫中心，大量的用户界面，大量的互动，大量的不义之财。 我会给它 70 分，你每天确实有 4 小时的维护时间，但如果它宕机了 30 秒，我会怀疑你是否能活到足够长的时间到达那个支持窗口。
3) 哈欠，Ajax 有点酷，但是 CRM 的主要复杂性必须是长期运行的事务，并由计费系统以及名称和地址支持。 我会给它35分。
让火焰开始吧......
Here's my take
1) Telecom system sounds large, but it looks like a pure server app, no UI, no real users, therefore some clever math, a database and a few services = 60 points, 50 points for overall complexity +10 for 24x7x365. Would get more points for integrating with a MF, or being written in reduced set kanji.
2) Horse betting, now we're talking, people on the phones, call centre, lots of UI, lots of interaction, lots of filthy lucre. I'd give that a 70, you do get 4 hours/day for maintenance, but if it was down for 30 seconds I'd doubt if you'd live long enough to get to that support window.
3) Yawn, Ajax is kind of cool, but the main complexity of CRM has got to be long running transactions, backed by billing systems and name and address. I'd give it a 35.
Let the flames begin ...