「{iThome 書評} 從需求到設計—Exploring Requirements」的迴響

由：Kenming Wang

Kenming Wang — Wed, 16 Jul 2008 22:50:47 +0000

Hi Patrick:
耶！先前不是回應過？
————————————
"Change" 一直是軟體開發最大的議題。軟工會致力於如何 "控制改變"；而我倒是有另個想法，如何讓系統具備 "應變" 的彈性，也是另外一個方向的。 ^^

由：Patrick

Patrick — Mon, 14 Jul 2008 20:03:56 +0000

I agree. The requirements are always changing and sometimes it contradicted each other. That's why there is a process called change management. After business owner has signed off the "agreed" requirements, any change request will go on change management process and it is very expensive to raise a change request after signed off.

由：Kenming Wang

Kenming Wang — Mon, 02 Jun 2008 17:41:42 +0000

Hello sda:
軟體的重心在於人的調和與對系統的應變，此兩者一直是最重要的課題。

由：sda

sda — Mon, 02 Jun 2008 15:17:10 +0000

由：Kenming Wang

Kenming Wang — Mon, 25 Feb 2008 00:48:55 +0000

Hi Partick:
您所提貴單位的環境，比較像是傳統 2-tier 的模式，一般而言，那會比較重視功能的實作，而比較不具備應變的彈性。那麼，什麼又是 "應變的彈性" 呢？重視系統結構性元素的分析與設計，那是應變系統的根本所在！但是，諸多軟體公司，並不重視此，只重視現實需求的功能面實作，那是屬於短線式的作法。

另您所提預算等問題，這與軟體人員素質亦有關係，兩者互為正因子。但以國內台灣，兩者都比較偏向負因子，而負+負越往負面循環之路走了。

由：Patrick

Patrick — Sun, 24 Feb 2008 03:21:29 +0000

I read about both books you've mentioned. They are great and I believe I did learn a lot from them. Some of ideas in these books I've never thought about. The credit card company I work for is now using PEGA. The UI is written by JS, applet and certain parts that I am not too sure but it is linked to main frame (I think is Unix). We used to use main frame + sql database + a UI written from VB6 but it is kind of unstable.

Back to your comment above, "讓系統具備 "應變" 的彈性". I would say, unless business can offer unlimited budget, it is almost impossible to build a system has such flexibility for future change. I mean, it is less challenge to build a system that business can add extra to existing functions. It is quite impossible to build a system that can be flexible to accept new functions especially a system is shared and used by different regions (eg. Asia Pacific, Australia and Europe). Am I understand it right in 具備 "應變" 的彈性? Please excuse if any misunderstanding as I am not good in mandarin.

由：Kenming Wang

Kenming Wang — Tue, 15 Jan 2008 16:13:55 +0000

Hi Partick:
"Change" 一直是軟體開發最大的議題。軟工會致力於如何 "控制改變"；而我倒是有另個想法，如何讓系統具備 "應變" 的彈性，也是另外一個方向的。 ^^

由：Patrick

Patrick — Tue, 15 Jan 2008 09:58:58 +0000

The writing is great. It pin points real time problems the project team and the business owner. It is important for project team to understand how to manage the change requests even though during SIT and UAT stages.

Just to add, the common failure in understanding the business requirements is due to the person who has been apointed as "Subject Matter Expert" not really a subject matter expert. This often leads to UAT test case limitation and lack of coverage in critical areas.