BAA_Attachment_-_Three_Phase_Development_Sample.docx

Broad Agency Announcement

DTFH61R0000X

Attachment 1 Three Phase Development Sample

The purpose of this document is to assist the offerors with a sample development outline. The three phase approach is neither suitable for every project nor should every proposal be required to start from phase 1. Again, this is only provided as a suggested sample.

Project Management

The development of the proposed application will require a disciplined approach to manage the execution of the work and ensure the team delivers the highest quality products on time and within budget. Best practices and procedures to Project Management should be used to ensure quality, timeliness, and cost control. A Project Management Plan (PMP) should be developed by the team per current PMBOK guidance and should consider at a minimum the following elements: scope management plan, schedule management plan, communications management plan, cost management plan, quality management plan, configuration management plan, stakeholder management plan and risk management plan.

Project Management deliverables must include at a minimum:

· Kick-off Meeting

· Project Management Plan (PMP)

· Project Schedule

· Monthly Progress Reports

· Phase 1 Close-out meeting

· Phase 2 Kick-off meeting

· Phase 2 Close-out meeting

· Phase 3 Kick-off meeting

· Project Closeout meeting

PHASE 1: Concept of Operations and System Requirements

Phase 1 consists of developing a concept of operations and documenting systems requirements for the proposed application.

Effective development and implementation of a technology application that addresses the needs of ATTRI users defined through the ATTRI User Needs Assessment project[endnoteRef:1] will require rigorous application of established systems engineering best practices. To reduce the risk of schedule and cost overruns and increase the likelihood of a successful prototype and demonstration that will meet users’ needs, awardees shall provide evidence of following a systems engineering process when developing the chosen application. [1: Accessible Transportation Technologies Research Initiative (ATTRI), User Needs Assessment Report, U.S.DOT, Final Report — March XX, 2016, FHWA-JPO-16-354. Interim report available at: www.its.dot.gov/index.htm]

To document how the awardee plans to follow a systems engineering approach, the awardee shall develop a Systems Engineering Management Plan (SEMP). The SEMP shall describe what systems engineering process the awardee plans to follow during the execution of the project’s work and how they plan to manage the specific systems engineering activities that will be performed during the project.

Please note that the USDOT recognizes the benefits of following a systems engineering approach and supports innovative approaches that are tailored to fit the needs of their particular application development. The USDOT also recognizes that some applications may benefit from utilizing other incremental and iterative development concepts, such as agile software development. The proposal shall identify the type of systems engineering approach that will be used for their application development and should describe their proposed approach in detail to successfully develop a concept of operations and system requirements documentation.

System Engineering deliverables should follow the appropriate IEEE standards to support ATTRI application development and should include at a minimum:

1. Concept of Operations (ConOps) that serves as the foundational document that conveys an overall view of the application that is understandable to stakeholders and how operational practice should be altered on the introduction of this application into the transportation environment. The ConOps should follow the in IEEE Standard 1362-1998 and include a set of proposed high-priority “needs” through structured stakeholder interaction, a context diagram, discussion of enhancements to operational practices, and use cases or scenarios. The awardee may also utilize ATTRI’s user needs assessment report for user needs identification.

2. Systems Requirements Specification (SyRS). System requirements define what the system will do but not how the system will do it. Working closely with stakeholders, requirements should be elicited, analyzed, validated, documented, and baselined. Following the guidance in IEEE Standard 1233-1998 requirements should include at a minimum: Functional, Interface, Data and Performance Requirements. For potential software specific applications, another reference to consider is IEEE Standard 830-1998.

3. Evaluation Plan that includes performance metrics to be used in the evaluation of the application.

4. System Architecture and Standards Plan that documents the architecture for systems associated with the application and associated standards that will be used.

5. Other systems engineering documents identified by the proposer.

PHASE 2: Prototyping and Testing

Upon successful completion of Phase 1 and USDOT approval of the final deliverables for Phase 1, the awardee may move into Phase 2 that consists of developing a prototype and testing the proposed application. In this phase, the awardee will develop and test the proposed application prototype. The purpose of this phase is to design and build the application prototype and then test the success of the prototype in a controlled environment.

Proposals should describe their prototyping and testing approach for the particular application being proposed. In this phase, the awardee shall develop a prototype design for the proposed application corresponding to the requirements developed in the Phase 1 following IEEE or other recognized design best practices. The awardee shall deliver design documentation as appropriate to the systems engineering and development process used. The awardee shall identify at least one opportunity for the USDOT team to review and provide comments and feedback on the prototype system design prior to it being finalized.

The awardee will then provide a test plan and test procedure documents for a field test in a controlled environment to evaluate the success of the prototype application. Testing documentation and processes should follow industry best practices such as IEEE 829-1998. Results of the prototype testing shall also be delivered in this Phase.

PHASE 3: Demonstration and Evaluation

Upon successful completion of Phase 2 and USDOT approval of the final deliverables for Phase 2 including the test results document, the awardee may move into Phase 3 for a small scale demonstration, evaluation and guidance documentation.

The purpose of this phase is for the awardee to conduct a small-scale demonstration of the prototype application designed and tested in Phase 2.

Contractor shall perform the necessary planning to ensure that the small-scale demonstration of the prototype is successfully conducted including the development of a Demonstration Site Plan identifying the demonstration elements, and a Demonstration Experimental Plan that identifies the demonstration hypotheses, testing protocols, and data elements to be collected for evaluation.