您的回應，老實講，非常令人意外

如果2167A不是標準的SOW(其經裁適後變成履約用的SOW)，或說2167A中的requirements(含shall的條文)不能成為SOW，實在不知道要怎麼講下去了？

2167A是不是標準的SOW不是您我用自己解讀的結果說的算，也不是任何人可以隨意解讀的！

大家都知道2167A需要經過Tailoring，那就看看美軍出的，專門針對2167A的 Tailoring Guide (HDBK-287)上面怎麼說好了？

MIL-HDBK-287 A Tailoring Guide for DOD-STD-2167A

4.3
4.3.1What is tailoring?
Definition. Tailoring is the process of
o Evaluating each requirement in a selected standard or DID to determine whether it is necessary for a given project.

0 Deleting those requirements that are not needed. Tailoring ia intended to eliminate unnecessary and duplicaye requirements. For standards, a modified version of the requirement may be included in the SOW. For DIDs, requirements may be deleted or partially deleted, but not modfied.

上面對2167A 的 Tailoring其定義再清楚不過了。就是決定將要納入合約SOW的2167A requirement(刪掉不要的或重覆的，留下要的)！

2167A中的每一條requirement，只要(經裁適後)被採用，都可以納入SOW！(例如前面提到的軟體需求分析)

4.3.5 where are tailoring decisitions specified?
Statement of Work. Tailoring decisions for standards are specified in the contrat SOW. A typical tailoring statement is

The contractor shall comply with all requirements of DOD-STD-2167A with the following exceptions “ -
4.1.2 Delete entire paragraph
4.2.9 Delete reference to software development files.
etc.

易言之，軟體發展合約SOW拿2167A中的requirements裁適後即可得

2167A的Tailoring結果(2167中合用的requirements)就成為SOW(的一部份)，當2167A引用到其它標準時，例如1521B，便要到各該標準1521B找適用的requirements(SOW條文)。事實上，對1521B的裁適結果(1521中合用的requirements)，也會被納到SOW中

以下結錄自1521B的Appendix J ApplicationtGuide for Tailoring MIL-STD-1521

When MIL-STD-1521 is used, then a task containing the applicable requirements will be specified in the SOW. Review factors not set forth in MIL-STD-1521 but considered necessary because of the nature of the particular Program should be added in the SOW. ......


同理，2167A中之CM需求引用480~483，當軟體發展合約中有對承商的CM要求時，這部份的SOW便得自480~483條文中去挑(裁適)出合用的requirement(s).


小弟之前的留言就是這個意思

單純使用2167A/498/016，加上適當的Tailoring，其實可以不用WBS就能與我國政府主計/審計制度結合；而承包者亦可在這個標準的SOW上依己的"內帳"計算履約所需投入的efforts和風險


498用途較2167A為廣，但並不影響其得為標準軟體發展SOW之目的，以下節自是一篇來自STSC的論文

Adopting MIL-STD-498:The Steppingstone to the U.S. Commercial Standard
Reed Sorensen, Software Technology Support Center
http://www.stsc.hill.af.mil/crosstalk/1996/03/Stepping.asp

其中提到關於裁適498的部份如下

Record Tailoring in the Statement of Work

The statement of work is to include two types of tailoring: the tailoring of MIL-STD-498 and the tailoring of the DIDs. Specific examples of each are found in paragraph 5.4.9 of [3]......

這裡所指的[3]就是498的裁適指導書(相當於2167A的HDBK-286)

MIL-STD-498 Overview & Tailoring Guidebook

5.4.9 Step 9: Recording tailoring decisions in the Statement of Work.

Step 9 in tailoring and applying MIL-STD-498 is recording the tailoring decisions of Steps 7 and 8 in the Statement of Work. The following guidelines apply.

a. Tailoring by exception. One method of recording the tailoring decisions in the Statement of Work is tailoring by exception. This method consists of requiring the fulfillment of all requirements of the standard and DIDs with certain, itemized exceptions. Figure 48 provides an example. Note that the DID paragraphs should have "10.2" appended to the front of the numbers given in the tailoring worksheets.

b. Tailoring by inclusion. An alternative method is tailoring by inclusion. This method consists of listing the paragraph numbers of the requirements in the standard and DIDs that must be fulfilled, with any special considerations noted.

其實，在該指導書的頁23講得更明白

b. Agreements. MIL-STD-498 is written in terms of the following agreements:
1) Contract: the agreement between the acquirer and developer. Between government agencies, the contract may take the form of a Memorandum of Agreement or other form of tasking.
2) Statement of Work (SOW): that portion of the contract that lays out the tasks to be performed by the developer.
3) Contract Line Item Number (CLIN): that portion of the contract that identifies deliverable products.
4) Contract Data Requirements List (CDRL): that portion of the contract that identifies deliverable software products.

498就是以合約/SOW/CLIN/CDRL(等各種協議)之用語方式撰寫(498用agreements來集合合約、SOW、CLIN、CDRL)

民間版的498→J-STD-016乾脆直接將Agreement下在標題上

Software Development - Acquirer-Supplier Agreement

至於承商要用何種方法，本來就與2167a/498是不是標準SOW無關，

2167A條文中要求承商採用well defined的方法，這個要求本質上就是一條work statement，由承商在SDP(或對等的交付事項中)交待