ࡱ> @ /*bjbjFF %,, e """8"#D<=X$$^8%8%<%p&T&&2222B)37Q<$(>Rz@u<'p&p&''u<<%<%4<^@*@*@*'<%<%2@*'2@*@*V`-U.<%L$ `"(=. .T<T<=I. Br)BU.&Tz6B m.$&'@*' '&&&u<u<"**"Deliverable Expectation Document (DED) For [Deliverable Title] [This template describes the required contents of a deliverable expectation document. Refer to the Request for Proposal and/or Statement of Work for more information on submitting the DED. Contractor format is acceptable, but the requested information must be readily identifiable, by using headings or other means. Work plans that support the activity summary can be attached, and may be referenced to support the methodology and schedule summary.] Introduction [A brief overview defining the purpose of the deliverable and how it fits within the overall completion of the project. Indicate if there are pre-requisite tasks and subsequent tasks.] Deliverable Description [Describe the deliverables objectives and scope. Discuss the level of detail to be provided such as will describe the rationale for design decisions, will provide a textual summary of the design with detailed design pseudocode in the appendices, will include database schema diagrams and database table relationships, field sizes and descriptions, and indices and keys. Discuss the intended audience. If the document assumes a specific knowledge level, list the key concepts that must be understood (e.g., understanding of backup rotation schedules, understanding of registry editing, etc.). Do not use vague terms such as basic knowledge of system administration.] Methodology for Creating the Deliverable [Provide a brief explanation of the tasks, activities and methods to be used to develop the deliverable. If appropriate, include a process flow diagram. Do not duplicate methodologies described elsewhere (e.g., if the design methodology was described in detail in the proposal and project management plan, reference the appropriate document section). Indicate if there are any assumptions or constraints on the development of the deliverable. In cases where the contractors methodologies differ significantly from the states, it may be appropriate to require the contractor to provide a mapping of their methodology to the states methodology (as an appendix to the DED and/or the deliverable).] Applicable Standards [List the specific industry and/or government standards which must be observed. Do not simply list industry standards or IEEE. Indicate if the format/order of the standard must be observed or if the contractor may provide a mapping of their format to the standard to show compliance.] Table of Contents [List the table of contents or outline of the document. Discuss the content of each major section. Where appropriate or as requested by the project, provide a sample of this document from other engagements/projects or sample content, level of detail and format of key sections.] Section 1 Introduction This section will provide a high-level overview of the deliverable, its scope and purpose. Section 2 Section 3 Section 4 Section 5 - Appendix A Appendix B Appendix C Deliverable Requirements [List the specific requirements for this deliverable from the Request for Proposal, Statement of Work, and/or contract. List the specific source of the requirement, including document name, document date/version, paragraph or page number, and requirement number (from the Requirements Traceability Matrix/Database).] Table  SEQ Table \* ARABIC 1. Deliverable Requirements Reqmt #Requirement DescriptionSource of the ReqmtComment Deliverable Format [List any required templates, diagrams, tables or specific content required for this deliverable. For instance in design and test deliverables, an updated requirements traceability matrix should be included in the final deliverable. Indicate the format of the document and any associated diagrams, spreadsheets (e.g., MS Word, MS Visio, MS Project, etc.). Estimate the length/size of the document, and number of copies to be delivered.] Deliverable Acceptance Criteria [List the specific acceptance criteria for the deliverable. The first criteria should always be were the requirements met. The criteria should be specific to the deliverable and indicate key needs of the project (e.g., must include detailed description of database sizing, growth considerations, performance considerations, and de-/normalization considerations). Other general review criteria (which are primarily the same for all deliverables) may be referenced or attached. The following are the minimum acceptance criteria.] Did the deliverable comply with the applicable standards from Section  REF _Ref81099952 \r \h  \* MERGEFORMAT 2.2 (above)? Were all requirements from Section  REF _Ref81099943 \r \h  \* MERGEFORMAT 2.4 (above) met? Did the deliverable comply with the stated format requirements from Section  REF _Ref81100004 \r \h  \* MERGEFORMAT 2.5 (above)? Is the deliverable consistent with other deliverables already approved? Did the deliverable meet the general review criteria (e.g., pages numbered, free of formatting and spelling errors, clearly written, no incomplete sections, etc.)? Deliverable Schedule Key Deliverable Dates [List the key activities and due dates in the preparation and review of this deliverable. If appropriate, list key meetings, walkthroughs, inspections and reviews. These tasks should be consistent with the activities and dates in the workplan and contractual timeframes regarding deliverable delivery, review and approval/rejection. Include time for state review of the deliverable and contractor incorporation of comments. Indicate if any activities/dates are on the critical path or have significant dependencies. The following is a sample.] Table  SEQ Table \* ARABIC 2. Key Deliverable Dates Key ActivityDue DateCommentDED Approval xx/xx/20xx*Internal Walkthrough with ProjectDraft Deliverable SubmittedState Review of DraftMinimum of 1 weekWalkthrough of Draft with StakeholdersDeadline for Comments on DraftContractor Incorporation of CommentsFinal Deliverable SubmittedState Review of FinalMinimum of 1 weekDeliverable ApprovalContractor Incorporation of Final Comments (if necessary)*Critical Date Schedule for Deliverable Updates [If the deliverable is expected to be updated on a periodic basis, list the proposed schedule of updates and tentative time frames. Dates may be either hard dates (e.g., May 5 2004) or soft dates (30 days prior to System Test). If appropriate, reference the appropriate RFP/SOW requirement for the update.] Table  SEQ Table \* ARABIC 3. Deliverables Update Schedule Reason for Deliverable UpdateSOW ReferenceDate DueCommentIncorporate any changes from Code/Unit Test phase[Reference, as used in SOW; i.e. paragraph #, or unique reference]Incorporate any changes from the Integration and System Test phaseSOW para 3.2Incorporate any changes from the Acceptance Test phaseIncorporate any changes from the Implementation phaseIncorporate updates related to the first (M&O) system release Resources Required [List the specific resources involved in the deliverable preparation and review. Estimate the amount of time required from each key resource, particularly for any sponsor, user, or stakeholder staff involved. If appropriate, list the specific skill or knowledge required, such as knowledge of case management policy or experience with current systems financial reports. It is not necessary to list all contractor staff involved in the preparation, only the key staff or required skills. This list is not intended to replace the workplan resources, but to identify specific individuals/skills needed to ensure successful completion of the deliverable. ] Table  SEQ Table \* ARABIC 4. Required Resources RoleName(s)ResponsibilitiesEstimated NeedDeliverable Lead2 monthsDeliverable Approver5 daysDeliverable Reviewers7 daysSubject Matter Experts10 daysPolicy Representative10 daysIV&V5 days Deliverable Payment [If applicable, indicate if this is a payment deliverable, if progress payments for this deliverable will be paid, and the estimated amount for developing this deliverable. If progress payments will be made, estimate the payment schedule. The payment schedule should be consistent with the contractors Task Accomplishment Plan (TAP) or cost/spending plan. This section is not applicable for fixed price contracts.]  DOCPROPERTY Subject \* MERGEFORMAT Office of System Integration < Date of Submission>< Contractor Name > < Deliverable Title > DED Last saved:  SAVEDATE \@ "M/d/yy h:mm am/pm" \* MERGEFORMAT 12/20/05 9:52 AM11/10/05 11:07 AM  FILENAME \p \* MERGEFORMAT C:\NrPortbl\SIDdocs\MVANDUZER\3353_3.DOCPage  PAGE 1 of  NUMPAGES 5 +?@    %&67:; #$%&f!g!|!̳̳̳̳̳̳̳̳̳̓̂q̳̳̳̳̳!jhkOJQJU^J!jhkOJQJU^J!jhkOJQJU^JhkOJQJ^JmHnHujhkOJQJU^Jhk>*OJQJ^JhkOJQJ^JhkCJOJQJ^J!hk5B*OJQJ\^Jphhk5OJQJ\^J,'?@A~   Y $$$$,$$$5$s$5$$CEƀˆF.CEƀˆF. (-*.* gf{$#$$w$#$CEƀˆF.CEƀˆF.:G$#$w$u$2$CEƀˆF..CEƀˆF..CEƀˆF.GTan$y$6$CEƀˆF..CEƀˆF..CEƀˆF..n|$y$6$4$CEƀˆF..CEƀˆF..CEƀˆF..*2J^f$#$$\M\M \M\Mh \M$IfCEƀˆF.fghijkke5e 5e5eh 5$Ifkd$$Ifl\Z8D%jb@ 0$64 laklmjki$&$#i$CEƀˆF.kd$$Ifl\Z8D%jb@ 0$64 laj7Wj$$5$$w$CEƀˆFCEƀˆF.I$Hy$6$HCEƀˆFCEƀˆFCEƀˆF4$(Y y$56$#4$4$CEƀˆF.CEƀˆF.CEƀˆF>KT\]kwx$\MT\M\Mh \MvpT5g5ph 5 $$Ifa$$Ifkd$$IflF:(#,@ 06    4 laz$Ifxy~xT5o5xh 5 $$Ifa$$Ifkd$$IflF:(#,@ 06    4 laz~xT5o5xh 5 $$Ifa$$Ifkd]$$IflF:(#,@ 06    4 laz~xT5o5xh 5 $$Ifa$$Ifkd $$IflF:(#,@ 06    4 laz~xT5o5xh 5 $$Ifa$$Ifkd$$IflF:(#,@ 06    4 laz012~xT5o5xh 5 $$Ifa$$Ifkdm$$IflF:(#,@ 06    4 laz23XYZ~xT5o5xh 5 $$Ifa$$Ifkd$$IflF:(#,@ 06    4 lazZ[wxy~xT5o5xh 5 $$Ifa$$Ifkd$$IflF:(#,@ 06    4 lazyz~xT5o5xh 5 $$Ifa$$Ifkd}$$IflF:(#,@ 06    4 laz~xT5o5xh 5 $$Ifa$$Ifkd- $$IflF:(#,@ 06    4 laz~xT5o5xh 5 $$Ifa$$Ifkd $$IflF:(#,@ 06    4 laz ) `!!~/x$55$#3$1$\MCEƀˆF.@^@kd $$IflF:(#,@ 06    4 laz|!}!~!!!S"T"""^#&&&&& &c&&&&&&&&&'''((((()))U)V)W)Y)e)Ʈwsm hk^Jhk!hk5B*OJQJ\^Jph%hk5B*CJOJQJ\^Jph%h`%5B*CJOJQJ\^Jph.jh`%5B*CJOJQJU\^Jphh`%hkB*OJQJ^JphhkOJQJ^JhkOJQJ^JmHnHujhkOJQJU^J(!!!!!!"Q"R"S": \M\MB\MZ\M^X: 5X5XB5XZ5$Ifkd= $$IfTl44\$5' 3 0"4 laf4T$If S"T"""""e _: 5_5_B5_Z5$Ifkd $$IfTl4\$5' 3 0"4 laf4T""""""e5_: 5_5_B5_Z5$Ifkd $$IfTl4\$5' 3 0"4 laf4T""####e5_: 5_5_B5_Z5$Ifkd $$IfTl4\$5' 3 0"4 laf4T##Z#[#\#]#e5_: 5_5_B5_Z5$Ifkdt$$IfTl4\$5' 3 0"4 laf4T]#^#_#r#e5c$ $5CEƀˆF.kdA$$IfTl4\$5' 3 0"4 laf4Tr#[%&5&:&B&S&b&$$$\M\M\M \M\M$IfDC$EƀÈFb&c&t&u&v&&ke5e5e 5e5$Ifkd$$Ifl\x#{ij064 la&&&&&&ke5e5e 5e5$Ifkd$$Ifl\x#{ij064 la&&&&&&k/e5e5e 5e5$Ifkd$$Ifl\x#{ij064 la&&&&&&k/e5e5e 5e5$IfkdQ$$Ifl\x#{ij064 la&&&&&'k/e5e5e 5e5$Ifkd$$Ifl\x#{ij064 la'''' ''k/e5e5e 5e5$Ifkd$$Ifl\x#{ij064 la'''&'(ki$&$5i$CEƀˆF.kd$$Ifl\x#{ij064 la((((()&):)T)$$t\Mt\M\M\M $<$Ifa$ $<$Ifa$ !DC$EƀÈFT)U)V)W)X)Y))*%*`$x#dw $$Ifa$$If$a$nkdU$$Ifl0D%Ld0%64 lae)f))))))))))**** *******!*"*#*$*%*&*(*,*.*/*﫛|x|h`%hkhkOJQJ^J!h`%CJOJQJ^JmHnHujhkCJOJQJU^JhkCJOJQJ^JhnH0^JmHnHu4hnH0h`%^JcHdhdhdhFmHnHu"HhFh`%^JmHnHu hk^JjhkU^J%*&*'*(*)***+*,*-*.*/*$hG$ !$a$Ekd$$Ifl0$n 4 la #0 P/ =!"#$%$$If!vh55j5b5@ #v#vj#vb#v@ :V l0$655j5b5@ 4a$$If!vh55j5b5@ #v#vj#vb#v@ :V l0$655j5b5@ 4a{DyK  _Ref81099952{DyK  _Ref81099943{DyK  _Ref81100004$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$Ifz!vh5,55@ #v,#v#v@ :V l065,55@ 4az$$If!vh5 5553 #v #v#v#v3 :V l440"5 5553 4af4T$$If!vh5 5553 #v #v#v#v3 :V l40"5 5553 4af4T$$If!vh5 5553 #v #v#v#v3 :V l40"5 5553 4af4T$$If!vh5 5553 #v #v#v#v3 :V l40"5 5553 4af4T$$If!vh5 5553 #v #v#v#v3 :V l40"5 5553 4af4T$$If!vh5 5553 #v #v#v#v3 :V l40"5 5553 4af4T$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5{5i5j5#v{#vi#vj#v:V l065{5i5j54$$If!vh5L5d#vL#vd:V l0%65L5d4k$$If!vh55n #v#vn :V l55n / 4 F@F Normal $xa$CJ_HmH sH tH L@L Heading 1$ & F@& 5CJKHH@H Heading 2$ & F@&CJD@D Heading 3$ & F<@&H@H Heading 4$ & F<@&5D@D Heading 5 & F<@&CJH@H Heading 6 & F<@&6CJ@@@ Heading 7 & F<@&D@D Heading 8 & F<@&6J @J Heading 9 & F<@& 56CJDAD Default Paragraph FontVi@V  Table Normal :V 44 la (k(No List 4@4 Header  !8 @8 Footer  !CJHOH TableTextLeft$((a$CJNO"N TableHeader$$a$ 5:CJB'1B Comment ReferenceCJaJ4OB4 TinyLineCJ2B@R2 Body TextB*H@bH k Balloon TextCJOJQJ^JaJ8@r8  Comment TextCJD"@D Caption$$x(a$5CJNON TableCaption$<a$ mHnHu<O< BulletIndent  & F@Y@  Document Map-D OJQJBOB FigureCaption $<8O8 Graphic$$a$LOL FileName $a$CJOJQJhtH u0>@0 Title$a$CJ /"/" z z z z zfm /"'?@A~Ygf{ : G T a n | * 2 J ^ f g h i j k l m j7WjI4>KT\]kwxy0123XYZ[wxyz)`QRSTZ[\]^_r[5:BSbctuv & !&!:!T!U!V!W!X!Y!!"%"&"'"(")"*"+","-"0"000000 00 000 000 00f 00 ( 0 0 ( 0 ( 0 ( 0 ( 0 ( 0 ( 0 ( 0 0  00 0 0  0  0  0  0  0  0  0  0  0  0  00m 0m  00707 07 07 07 07 07 0 00000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00_0_0_0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 0_ 00000000 00 0 000000 0 0 00000000`bdg|!e)/*/@ Gnfkjx2Zy!S"""#]#r#b&&&&&''(T)%*/* !"#$%&'()*+,-.0123456789:;<=>?A.*   6: #%f|~/" tttt t  t)F9@GINY[gUT!@  @H 0(  0( >l B S  ? _Ref81099952 _Ref81099943 _Ref81100004f m 0"z  0"m"u0"0"=*urn:schemas-microsoft-com:office:smarttags PlaceType 20045DayMonthYear* / X ]  ;<CDG !W!Y!e!!!""""""$"(","0"    jHI'`! !W!Y!e!!!""""""$"(","-"0":::::::   ; &f  !W!Y!e!!!""""$"(","0" -"0">7#` ueF*P^`P.@@^@`.0^`0..``^``... ^` .... ^` ..... ^` ...... `^``....... 00^0`........@D7#ue @h 8^8`OJQJo(P @h^`B*OJQJo( @ @`%nH0k?* 2 J ^ f g h i j k l >KT\]kwxy0123XYZ[wxyzQRSTZ[\]^5:BSbctuv  &!T!U!Y!"%"&"0"@\\projects_pq\12_EBT_HP5100Ne03:winspoolHP LaserJet 5100 PCL 6\\projects_pq\12_EBT_HP5100? odXXLette.HP LaserJet 5100 PCL 62ExeP.DQ=UszA!",0l%M"H/Y#a _!ڙ{_H✪s+UuO>?"buV!3>7?[X^Õ+h_n%ňZR%FGݠvx$aOxd~x:pH6 V[]`O4fB}'@@r+9{Y+F{A?a5i-CKSjђzکW)dԯSiByEs-1>"x,'~o~3/'J_$d? 1D2Ade" ZXZ}H0|u[.LB\\projects_pq\12_EBT_HP5100? odXXLette.HP LaserJet 5100 PCL 62ExeP.DQ=UszA!",0l%M"H/Y#a _!ڙ{_H✪s+UuO>?"buV!3>7?[X^Õ+h_n%ňZR%FGݠvx$aOxd~x:pH6 V[]`O4fB}'@@r+9{Y+F{A?a5i-CKSjђzکW)dԯSiByEs-1>"x,'~o~3/'J_$d? 1D2Ade" ZXZ}H0|u[.LBTy/"`@Unknown Tony Fong Laura Okawa AdministratorGz Times New Roman5Symbol3& z Arial5& zaTahoma"hFF,;;!4d 2QH?kSD:\Laura Okawa\Archive\Office\Tech. Services Division\TSD Monthly Status Report.dot)Deliverable Expectation Document TemplateOffice of System Integration Laura Okawa Administrator   Oh+'03$p      (*Deliverable Expectation Document TemplateWoOffice of System Integrationent Laura OkawaaurATypical format for a contractor deliverable expectation documenttatTSD Monthly Status Report.dotr Administratorat2miMicrosoft Word 10.0@@s/@2@2G1VT$m   ."System0T -@ Arial- 52 |X%` Office of System IntegrationA..37-..J3.3 .33 2 |%`  . ` %' +2 X%` < Date of Submission> 0<..3733J..330 2 %`  . ` %' %2 |Z < Contractor Namei0<33 ..3 <.J.2 |kZ  >0 2 |Z  . Z ' 12  Z < Deliverable Title > DEDi0<./. .3.4.0<7< 2 Z  . Z '- @ !;$%-- @ !$Z -- @ !$^ -@ Arial-  2 X 8 '@ Arial-2 X %) Last saved: %%""%!%%2 %) 12/20/05%%%%%% 2 %)  2 %) 9:52%%% 2 [%)  2 n%) AM-7 2 %)  $) %'2 X%) C:0 2 %) \2 %) NrPortbl0-%% 2 %) \2 %) SIDdocsl-0%%"" 2 %) \2  %) MVANDUZER7--000)-0 2 n%) \2  %) 3353_3.DOC%%%%%%040 2 %)  %) %'2 ># Page c-%%% 2 # 1%2 #  of % 2 p# 5% 2 #  %# '- @ ! Z+-- @ !Z& -- @ !Z* -@Times New Roman- 2 V  %'{@ Arial-D2 O&Deliverable Expectation Document (DED)`J%%GJ4JQ%J%YJQJJ,J,%QQ%`QJQvJQ,%,`Y`, 2 O J2 PFor QQ4% (2 K[Deliverable Title],`J%%GJ4JQ%J%Q%,%J, 2   J @ Arial- 2   6@ Arial-  2 3X - 2 XV[This template describes the required contents of a deliverable expectation document. >82&8T888&8822!882%88%!878!88%288882%8%8%8818!888%81882888%8828T88  2 XSRefer to the Request for Proposal and/or Statement of Work for more information on tH88!(8(88(H87882(8!(C!88828(8888!(C88T88(8(c8!2(8!(T8!8(88!T888'88  ,2 }Xsubmitting the DED. Co288T872882HCH2H8g2 }=ntractor format is acceptable, but the requested information 8!828!28!T8222822888882882882!8788288288!T888  k2 X@must be readily identifiable, by using headings or other means. T8288!888188888881828788888728!888!T8882 2 T  6  2 XTWork plans that support the activity summary can be attached, and may be referenced c8!2!8882!88!28888!!88!8211!28TT8!1!288!88!882888 888 T81 88 !88!88288  P2 X.to support the methodology and schedule summar828888!88T88888871888228888828TT8!2  y.]1 2 {  6 @ Arial- 2 $ X1.A!@ Arial- 2 $  R- 2 $  Introduction!G'.GGGA'!GG 2 $  A'- 2 X][A brief overview defining the purpose of the deliverable and how it fits within the overall DC8!8818!18G888878888!88288888818!88888888G2G8888818!8  Y2 @ X4completion of the project. Indicate if there are pre28T88888878878!8827882887788!878!878!8 2 @ -!:2 @ requisite tasks and subsequent !878287822278887288287888  2 Xtasks.]l8222 2 z 6 - 2 X2.A!- 2  R- .2 Deliverable DescriptionTA!!@A.AG!A!TAAA.!G'!GG 2  A'- 82 x X[Describe the deliverables obH822!8878878818!8882788\2 x 6jectives and scope. Discuss the level of detail to be 8218278887228887H22822788781868688868688  2 X[provided such as will describe the rationale for design decisions, will provide a textual l8!81888#2828#82#!G#8822!88#88#!88888#8!"88278"8822882"G"8!8188"8"8188  2 ^ XVsummary of the design with detailed design pseudocode in the appendices, will include 28TT8!1 8 88 88278 G8 88888 88278 8288882888 8 88888888282G82888  12 Xdatabase schema diagrams 8888828T2288T8T887!8T2TV2 2and database table relationships, field sizes and 888T8888828S888S!88882882S88S2182S888  D2 DX&descriptions, and indices and keys. 8822!8882888882828882812! 2 D 6  2 XSDiscuss the intended audience. If the document assumes a specific knowledge level, dH22822)88)888888)8888828))88(8828T88(8228T82(8(28822(288G8878(818  2 \XTlist the key concepts that must be understood (e.g., understanding of backup rotatio2(88(281(2882882(88'T82'88'8888!2888'!87'8888!288887'8'882288'!8882 \\n 8  2 XTschedules, understanding of registry editing, etc.). Do not use vague terms such as 22888882/8888!288887/8/!872!1/8887.82!.H8.88.828.18788.8!T2.2828.82  M2 BX,basic knowledge of system administration.]!8822288G887882128T88T82!888! 2 B  6 @ Arial- 2 BX2.1A!A@ Arial- 2 B M- G2 BH(Methodology for Creating the DeliverableaA!AAAAAA9!!A'!T'AA!AA!!AA!TA9A'AAA 2 B  ?'- 2 XT[Provide a brief explanation of the tasks, activities and methods to be used to deveC!8188$8$8!8$81888888$8$88#8222#82182#888#T88882#8#88#8288#8#88182 lop 88  2 wXRthe deliverable. If appropriate, include a process flow diagram. Do not duplicate 88?8818!888??888!88!88?82888?8?8!82822?8G?887!8T?H8?88>888288  2 XTmethodologies described elsewhere (e.g., if the design methodology was described in T888888782&8822!888&828G88!8&!87&&88&88278&T88888871&G82%8822!888%8  2 ]XNdetail in the proposal and project management plan, reference the appropriate 888G8G88G8!88828G888G8!882GT88878T88G888G!88!8828G88G888!88!88  2 Xdocument8828T88v2 G section). Indicate if there are any assumptions or constraints on the E28288!E88288ED88!8D8!8D881D8228T8882D8!D2882!882D88D88  :2 CXdevelopment of the deliverable.881888T888888818!888 2 C 6  2 XXIn cases where the contractors methodologies differ significantly from the states, it 80282820G88!8/88/288!828!2/T888888782/88!/2782881/!8T/88/2882/  m2 [XAmay be appropriate to require the contractor to provide a mappingnT8188888!88!888!878!888288!828!88!81888T88887,2 [  of their methodology 888!T88888871  2 XOto the states methodology (as an appendix to the DED and/or the deliverable).]8882882T88888871!82888888881888HCH8888!888818!888! 2  6 -                    ՜.+,0 hp  m#Office of System Integration (OSI)i; O *Deliverable Expectation Document Template IntroductionDeliverable Description- Methodology for Creating the Deliverable Applicable Standards Table of Contents! Section 1 Introduction Section 2  Section 3  Section 4  Section 5 -  Appendix A  Appendix B  Appendix C  Deliverable Requirements Deliverable Format Deliverable Acceptance CriteriaDeliverable Schedule Key Deliverable Dates% Schedule for Deliverable UpdatesResources RequiredDeliverable Payment Title Headings  !"#$%&'()*+,-./0123456789:;<=>?@ABDEFGHIJKLMNPQRSTUVWXYZ[\]^_`abcdefghijklmnoprstuvwxyz{|}~Root Entry FζData CW1TableOBWordDocument%SummaryInformation(q3DocumentSummaryInformation8CompObjj  FMicrosoft Word Document MSWordDocWord.Document.89q