20概念階段產(chǎn)品設(shè)計需求模板_第1頁
20概念階段產(chǎn)品設(shè)計需求模板_第2頁
20概念階段產(chǎn)品設(shè)計需求模板_第3頁
20概念階段產(chǎn)品設(shè)計需求模板_第4頁
20概念階段產(chǎn)品設(shè)計需求模板_第5頁
已閱讀5頁,還剩7頁未讀, 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報或認(rèn)領(lǐng)

文檔簡介

1、Fpg套用端到端產(chǎn)品包需求模板模板:設(shè)計需求開發(fā) 指導(dǎo)書(正式模板見上面嵌入文件) Project Manager 項目經(jīng)理: _ Project項目: _ Project Phase / Decision Checkpoint: 項目階段/決策評審點 Concept概念 _ Develop開發(fā) _ Launch發(fā)布 _ Interim臨時 _ Plan計劃 _ Qualify驗證 _ Life Cycle生命周期1 將產(chǎn)品包需求分解為設(shè)計需求 Decompose offering requirements into Design requirements:1.1. 確定操作方式 對于每一個產(chǎn)

2、品包需求,根據(jù)下面內(nèi)容對操作方式進(jìn)行概括,寫入表1中: 操作環(huán)境及顧客/用戶眼中操作顧客/用戶期望操作在成本、尺寸、重量、電源、冷卻、環(huán)境、制造、服務(wù)等方面操作限制。限制范圍內(nèi)實際操作以下方面所帶來影響:成本、質(zhì)量、上市時間、顧客滿意度、兼容性等等客戶/用戶對操作表示出來任何吃驚(包括正面和負(fù)面) For each offering requirement, summarize the Operational Scenario by noting in the Table below: the operational environment and the operation from the

3、 customer/user viewthe customer/user expectations for the operationthe constraints on the operation in terms of cost, size, weight, power, cooling, environment, manufacturing, servicing, etc.the actual operation within the constraintsthe consequences in terms of cost, quality, time to market, custom

4、er satisfaction, compatibility, etc.any surprises for the customer/user (both positive and negative) for the operation. 對操作方式進(jìn)行概括一個例子: Another example: Operation 產(chǎn)品包需求:從中國偏遠(yuǎn)地區(qū)進(jìn)行緊急呼叫。用戶希望在旁邊有其他人呼叫時能在中國偏遠(yuǎn)地區(qū)進(jìn)行緊急呼叫而又不掉線。Place urgent calls from remote areas of PRC. Caller (user) wants to place urgent cal

5、l from remote areas of PRC in the presence of other callers, without call dropping, etc.1.1.1對操作方式進(jìn)行概括過程如下 Operational Profile:1)操作環(huán)境或上下文,從顧客/用戶角度考慮操作。 Context or operational environment and the operation from the customer/user view. 呼叫人可能在偏遠(yuǎn)山區(qū)快速移動,可能在大客車上,車上還有很多人也在打電話;電池可能不足,等等。 Caller may be movin

6、g at high speed in remote hilly areas, may be in a bus with numerous other callers; battery may be weak, etc.2) 顧客/用戶對操作期望。 Customer/user expectations for the operation. Classify the expectations as mandatory, competitive or nice to have. Example: Mandatory:Caller places call and is connected within

7、 five rings Competitive:Caller connected within three rings Nice to have:Caller connected within one ring將期望劃分為強制性、具有競爭力或者最好。比如:強制性:呼叫人呼叫,在振鈴五次內(nèi)接通具有競爭力: 在振鈴三次內(nèi)接通最好: 一次振鈴便接通3) 操作在以下方面受到限制:成本、體積、重量、功率、冷卻、環(huán)境、制造、服務(wù)等。 Constraints on the operation in terms of cost, size, weight, power, cooling, environmen

8、t, manufacturing, servicing, etc. 呼叫人不愿為被提供緊急呼叫便利而另外付費,也不愿為支持緊急呼叫功能手機而額外付費,并且希望電池使用時間越長越好。因此,也許必須使基站具有支持緊急呼叫額外功能。內(nèi)部限制是,原有基站已經(jīng)占用所有可用功率,因此在基站上補充新功能要求進(jìn)行重新設(shè)計。 Caller is not willing to pay a premium for the convenience of placing urgent calls. Caller is not willing to pay more for the handset and want th

9、e power to last as long as possible. Therefore, additional functionality to support urgent calling may have to be implemented in the base station. Internal constraints are that the base stations are already using all the power available, so implementing additional functionality in the base stations

10、requires redesign.4) 在實際系統(tǒng)操作時盡量考慮這些限制因素。要注意考慮對成本、質(zhì)量、上市時間、客戶滿意度、兼容性等方面影響。 Actual system operation that is possible taking the constraints into account. Make note of the consequences in terms of cost, quality, time to market, customer satisfaction, compatibility, etc.例如:必須對基站重新進(jìn)行設(shè)計來支持增加功能,這樣一來便會增加成本,要

11、求運營商們(顧客)對現(xiàn)有基站進(jìn)行升級會增加成本負(fù)擔(dān),而他們必須將這些負(fù)擔(dān)轉(zhuǎn)移到呼叫人那里。 Example: The base stations have to be redesigned to support additional functionality, increasing costs and requiring providers (customers) to upgrade existing base stations, imposing a cost burden which they have to pass on to callers.5). 顧客/用戶對操作任何吃驚反應(yīng)(

12、正面以及負(fù)面)都要重視。. Make note of any surprises for the customer/user (both positive and negative) for the operation.例如:如果需要為此項服務(wù)而額外付費(因為運營商產(chǎn)生了追加成本)話,呼叫人會很不愉快。如果呼叫人在邊遠(yuǎn)地區(qū)能夠很穩(wěn)定地進(jìn)行緊急呼叫話,他們便會很高興。而運營商對于必須升級他們基站則會很不愉快。 Example: Callers will be unhappy if they have to pay more for the service (because of the addi

13、tional costs to providers). Callers will be happy if they can place urgent calls reliably from remote areas reliably. Providers will be unhappy about having to upgrade the base stations.1.2.確定設(shè)計需求 在完成對操作方式概括后,在表1幫助下,依據(jù)操作方式把產(chǎn)品包需求分解為設(shè)計需求,并詳細(xì)列出每個設(shè)計需求可接受參數(shù)范圍。應(yīng)當(dāng)將產(chǎn)品包需求分解為不同種類設(shè)計需求,包括如下各部分:w 功能w 環(huán)境w 性能w 強健性

14、(魯棒性)w 可靠性w 可維護(hù)性w 可用性w 安全性w 重量w 電源w 尺寸大小w 可運輸性/可移動性w 靈活性w 其它Decompose the offering requirements into design requirements based on the operational scenarios and specify the acceptable parameter ranges for each design requirement using the following Table as an aid. Offering requirements should be dec

15、omposed into Design requirements of different types including: Functional Environmental Performance Robustness Reliability Maintainability Usability Security Weight Power Size Transportability/Mobility Flexibility etc.為了實現(xiàn)可追溯性,已經(jīng)分解描述設(shè)計需求應(yīng)當(dāng)與特定產(chǎn)品包需求建立明確聯(lián)系。 Design requirements that are already stated a

16、t the decomposed level should be clearly associated with specific offering requirements for traceability purposes. ±í1 產(chǎn)品包需求到設(shè)計需求映射產(chǎn)品包需求設(shè)計需求產(chǎn)品包需求操作方式需求分解為設(shè)計需求參數(shù)范圍(規(guī)格)從顧客/用戶/內(nèi)部角度描述產(chǎn)品包需求明確描述期望操作方式、期望結(jié)果、上下文關(guān)系、環(huán)境和限制把產(chǎn)品包需求分解為設(shè)計需求并進(jìn)行合理分類,類別可參照下面例子詳細(xì)說明產(chǎn)品包需求參數(shù)和可接受范圍此項應(yīng)出自已確定下來、按優(yōu)先程度分級產(chǎn)品包需求功能環(huán)境性能強健性

17、(魯棒性)可靠性安全性重量電源其它Offering RequirementsDesign RequirementsOffering RequirementOperational Scenario Requirements Decomposition into Design RequirementsParameter Ranges (Specification)State the offering requirement from the customer / user / internal viewDescribe and clarify the desired operational sce

18、nario, desired outcomes, context, environment and constraintsDecompose the offering requirements into design requirements and place in the appropriate categories such as those given below.Specify the parameters and acceptable ranges for the offering requirementsThis should come from the consolidated

19、 and prioritized offering requirementsFunctionalEnvironmentalPerformanceRobustnessReliabilitySecurityWeightPoweretc.舉例:EXAMPLE:產(chǎn)品包需求設(shè)計需求產(chǎn)品包需求操作方式需求分解為設(shè)計需求參數(shù)范圍(規(guī)格)1.1 將批量機密數(shù)據(jù)實時傳輸至200英里外遠(yuǎn)端局?jǐn)?shù)據(jù)必須能傳輸?shù)?或從遠(yuǎn)距離地點,中間可能有小山阻擋。數(shù)據(jù)包括大包和小包,最大包容量達(dá)10Gb。數(shù)據(jù)可晝夜隨時傳輸。功能.:1. 1.1 帶有用戶提示傳輸功能 I. 選擇要傳輸數(shù)據(jù)II. 確定目地III. 開始傳輸IV. 終止

20、V. 取消傳輸環(huán)境:1.1.2 在極端環(huán)境下操作溫度: -20C 到 50C 濕度:較潮濕 灰塵:振動:震動: 3g其他 性能:1.1.3 在電源沖足支持條件下 可連續(xù)進(jìn)行大量包傳輸。1.1.3 在20-25W有效發(fā)射功率條件下,提供10-15MHz鏈路,可最高達(dá)20分鐘不斷鏈強健性(魯棒性):1.1.4 I. 傳輸異常中斷 II. 錯誤檢測及恢復(fù)III. 傳輸確認(rèn)等1.1.4不許一個字節(jié)錯誤發(fā)生可靠性:1.1.5 連續(xù)地操作就緒1.1.5 不折不扣24 小時 / 365 天連續(xù)操作安全性:1.1.6 支持傳輸機密數(shù)據(jù)1.1.6 使用 PRC-XXX協(xié)議等重量1.1.7 在路況不好地區(qū)迅速移動

21、時,重量較輕易于攜帶1.1.7 總重(包括電池)不到2公斤電源1.1.8 電池供電和太陽能供電 等等Offering RequirementsDesign RequirementsOffering RequirementOperational Scenario Requirements Decomposition into Design RequirementsParameter Ranges (Specification)1.1 Transmit confidential bulk data in real time to remote station upto 200 miles away

22、Data has to be transmitted from/to remote sites which may be obstructed by hilly terrain. Data consists of both small and large packets upto 10Gb.Data may be transmitted at any time of day or night.etc.Functional:1.1.1 Transmit function with user prompts a.Select data for transmissionb.Specify desti

23、nationc.Initiate transmissiond.Terminatee.Abort transmissionEnvironmental:1.1.2 Operate in extreme environmentsTemperature: -20C to 50C Humidity: wet Dust/dirt:Vibration:Shock: up to 3getc.Performance:1.1.3 Operate with sufficient power continuously enough to transmit large packets1.1.3 Provide 10-1

24、5 Mhz link with 20-25 W effective radiated power for upto 20 minutes continuouslyRobustness:1.1.4 a.Transmit Abort b.Error Detect & Recoveryc.Confirm Transmission etc.1.1.4No single byte errors allowedReliability:1.1.5 Continuously operation-ready1.1.5 24 hours / 365 days operation; no compromis

25、eSecurity:1.1.6 Support transmission of confidential data1.1.6 Use PRC-XXX protocol etc.Weight1.1.7 Light weight to be carried while moving quickly through rough terrain1.1.7 Less than 2kg total including batteryPower:1.1.8 Battery power and solar power operationetc.1 設(shè)計需求合理化 Rationalize the design

26、requirements對上面表格中設(shè)計需求進(jìn)行如下合理化工作:1) 按照下表將設(shè)計需求進(jìn)行分類2)把相互支持需求合并為一項需求3)處理互相沖突需求 - 分析它們優(yōu)、劣勢,重新進(jìn)行優(yōu)先排序或者采取折衷方案4)對含混不清需求進(jìn)行澄清 - 由外部和內(nèi)部人員進(jìn)行5)整合冗余需求6) 將不需要需求轉(zhuǎn)入點子庫7) 修正產(chǎn)品包需求和設(shè)計需求表Rationalize the design requirements from the above table as follows:1) Categorize the design requirements into the categories in the T

27、able below2) Combine mutually supportive requirements into a single requirement3) Resolve conflicting requirements - look at pros and cons, reprioritize or compromise4) Clarify the confusing requirements - ask external and internal parties for clarification5) Consolidate redundant requirements6) Tra

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論