emphasizes developers’ issues over users‘ needs and may result in poor requirements. Requirements in the form of high-level design run the risk of being un-verifiable by the user， as user might not understand the design language. There are at least three broad contexts concerned to RE：
捕獲專注于需求而不是設(shè)計(jì)，這是為了充分了解用戶的關(guān)注點(diǎn)。專注于設(shè)計(jì)會(huì)不適當(dāng)?shù)膹?qiáng)調(diào)開發(fā)問題而忽略用戶的需要，導(dǎo)致失敗的需求。需求中摻雜了設(shè)計(jì)，會(huì)使用戶無法驗(yàn)證需求，同時(shí)用戶可能無法理解設(shè)計(jì)方面的語言。在需求獲取中有三個(gè)較大的領(lǐng)域需要特別注意：
Organization o Submitters of the input to the target system o Users of the output of target system o Ways in which target system will change the organization’s means of doing business
組織機(jī)構(gòu)目標(biāo)系統(tǒng)輸入信息的提供人員使用目標(biāo)系統(tǒng)輸出信息的用戶目標(biāo)系統(tǒng)可能改變組織機(jī)構(gòu)的業(yè)務(wù)流程。
Environment o Hardware and software constraints imposed on the target system o Maturity of target system‘s domain o Certainty of the target system’s interfaces to the larger system o The target system‘s role within a larger system
環(huán)境目標(biāo)系統(tǒng)的軟，硬件限制。
目標(biāo)系統(tǒng)問題域的成熟程度。
目標(biāo)系統(tǒng)的界面與組織現(xiàn)有大部分系統(tǒng)界面風(fēng)格一致。
目標(biāo)系統(tǒng)與組織現(xiàn)有其他系統(tǒng)的關(guān)系。
Project o Attributes of different stakeholders e.g. management style， domain/computer experience o Constraints imposed e.g. cost， quality， timelines， etc.
項(xiàng)目不同風(fēng)險(xiǎn)承擔(dān)人的特點(diǎn)，如管理風(fēng)格，問題域/計(jì)算機(jī)經(jīng)驗(yàn)。
其他約束條件，如資金，質(zhì)量，時(shí)間期限。
5 Requirements Elicitation Process
5、需求捕獲過程。
Following process graph shows the “should-be” RE process， which was created during a sample requirements elicitation process study. This gives a bird‘s eye view of the proposed business process model， which is a refined RE process.
下面的過程圖顯示了“應(yīng)該”的需求捕獲過程，它來源于實(shí)際的一個(gè)簡(jiǎn)單的需求捕獲任務(wù)。它給出了建議的過程模型，也是一個(gè)精確的需求捕獲過程。從這幅圖上，你可以對(duì)需求捕獲過程有個(gè)全面的認(rèn)識(shí)
下一章將介紹需求捕獲的階段組成（待續(xù)）