OBJECTIVE:
This section describes the various roles to be performed in the development life cycle of an ITS project. It provides guidance on “what the roles entail” and “who the potential candidates are to perform them”. A matrix shows what role is played by the system’s owner, the systems engineering technical assistant, and the development team during each stage of the development life cycle.
The role of the system’s owner, systems engineering technical assistant, and development team will vary in level of involvement and areas of responsibility throughout the project life cycle. This chapter provides guidance in each development step. It identifies the roles needed in each phase of the life cycle of an ITS project. A matrix of roles and responsibilities follows this discussion.
System’s Owner [Project Sponsor & Stakeholders]
The system’s owner [project sponsor & stakeholders] implementing an ITS will acquire a set of development services to develop the ITS project. The services can be either in-house or contracted. The system’s owner and operating organization will ultimately be responsible for the system and its operations & maintenance. The system’s owner needs to supply clear requirements and expected project outcomes to the development team. These outputs must be compatible with the long-term operations & maintenance goals of the system’s owner & stakeholders. The success of the project relies on the system’s owner’s working relationship with the systems engineering technical assistant and development team[s] who implement the system. This chapter will identify the roles and responsibilities of the system’s owner at each phase of the ITS life cycle [from the interface to the regional ITS architecture to retirement & replacement of the system or major system elements].
Systems Engineering Assistant [In-house staff, Independent Verification and Validation, System Manager ]
The systems engineering assistant provides the system’s owner with specialty support in systems engineering. This role can be undertaken by in-house staff, a system manager, or an Independent Verification and Validation consultant [IV&V] to a limited extent. Contract resources are particularly valuable for large, complex, or unusual projects. It is also valuable when the system’s owner’s organization is small and lacks systems engineering expertise. This may be the case with a small or medium size city or MPO. The systems engineering assistant:
§ defines requirements and the project architecture:
§ prepares the request for proposal or other system procurement documents,
§ assists in the review of proposals,
§ provides independent review services [Independent Verification & Validation]
§ Provides technical assistance to the system’s owner during the life cycle of the ITS system.
A consultant who neither offers products nor is affiliated with a development team or vendor can be un-biased in the selection and evaluation of developers and products. The consultant can assist the agency in Configuration Management, Risk Management, development team evaluations, and process improvement. It is important to find a consultant who has both systems engineering expertise and ITS knowledge and experience.
Development Team [In-house, Systems Integrator]
An ITS system development team normally develops or supplies hardware and software that integrate custom [project-specific] and COTS products. The system’s owner secures the the following services of a development team:
§ perform the detailed design
§ develop any necessary custom hardware or software
§ integrate COTS products
§ Verify the sub-systems and the system as a whole
The development team may be another department within the system owner’s organization [internal development team].
It be a contracted integration team. This is the normal case for most organizations.
The following tables identify the different roles and responsibilities during each phase of the project life-cycle.
Table 6‑1 Phases [-1] & 0 Roles and Responsibilities
|
Phase |
Phase [-1] Interfacing to the Regional ITS Architecture |
Phase 0 Concept Exploration and Feasibility Analysis
|
|
|---|---|---|---|
|
Tasks |
3.2.1 Interfacing with Planning and the Regional ITS Architecture |
3.3.1 Needs Assessment |
|
|
System Owner Project Sponsor & Stakeholders
|
Coordinate, identify, participate: R Coordinate with Planning R Identify applicable portion of the Regional Architecture R Ensure that project goals & objectives are sufficiently clear to support tasks |
Review & approve: R Statement of work R Current inventories R Supporting documentation R Identify & encourage Stakeholder participation R Actively participate in the elicitation of Needs
|
Review & approve: R Refined needs, vision, goals, objectives, and constraints R Overall measures of performance R Candidate concepts R Recommendations |
|
Systems Engineering Technical Assistance In-house, Independent Verification & Validation** Consultant, systems Manager |
Identify & document: R Applicable portion of the RA R Inventory R Stakeholders R Needs/Services R RA Requirements R Area of Coverage R Operational Concept R RA Interfaces R RA Information flows R ITS Standards R Project Sequencing R Agency agreements R Constraints R Goals & objective
|
Identify & document: R Validated & prioritized needs R Challenges & issues R Perform Gap Analysis R Refine & update stakeholder lists |
Identify, refine & document: R Vision, goals & objectives R Constraints R Alternatives, recommendations, and rationale Develop: R Evaluation criteria R Measures of performance R Concepts
Perform: R Cost/benefit analysis R Alternatives analysis |
|
Development Team In-house, System Integrator |
Review & comment* *subject to public comment e.g. Industry review of architecture
|
Review and comment* *subject to public comment e.g. Industry review of needs |
Review & comment* *subject to public comment e.g. Vision, goals & objectives |
** Independent Verification & Validation - role and responsibility are monitoring, reporting, supporting, and participating but not performing- applies to all phases and tasks
Table 6‑2 Phase 1 Roles and Responsibilities
|
Tasks |
3.4.1 Project Planning |
3.4.3 Concept of Operations |
|
|---|---|---|---|
|
System Owner Project Sponsor & Stakeholders
|
Review and approve: R Project Tasks, plans, budgets and schedules R Scope of Work R Supporting resources R Management plans (CM, QA, Risk) R RFP & Procurement type |
Review & approve: R SEMP Framework R Project products R Decision gate process R Project organization R Initial set of risks R Tailoring options R Supporting plans R Technical evaluation R Development strategy R Technical SOW R CM process & Organization |
Review & approve: R Refined needs, vision, goals, objectives, and constraints R Stakeholder lists R Validation strategy & plan
Participate in the development or refinement of: User needs, Concept of Operations, vision, goals & objectives, and operational scenarios Validation strategy & planning |
|
Systems Engineering Technical Assistance In-house, Independent Verification & Validation** Consultant, systems Manager |
Identify, prepare, and document R Scope of Work R Budgets & Schedules R Project Resources R Project Plans R Management Plans R RFP, RFQ, RFI R Procurement documents R Evaluation Criteria
|
Identify, prepare, participate and document: R SEMP Framework R Technical SOW R Development strategy R Technical evaluation R Supporting plans R Tailoring options R Reviews R Decision gate process R Initial set of risks
|
Identify, prepare and document R Vision, goals & objectives R Operational scenarios R Validation strategy & plan R Project specific stakeholder lists R Update project risks
Support, participate & report R Decision gates R Technical activities & products |
|
Development Team In-house, System Integrator |
Review & comment* All or in-part of the project management plan
*subject to a public comment |
Review & comment* All or in part of the technical products
*subject to a public comment |
Review & comment*** All phase products
***Internal Development Team |
** Independent Verification & Validation - role and responsibility are monitoring, reporting, supporting, and participating but not performing- applies to all phases and tasks
Table 6‑3 Phase 2 Roles and Responsibilities
|
Tasks |
3.5.1 Requirements Development |
3.5.2 High Level Design |
|
|---|---|---|---|
|
System Owner Project Sponsor & Stakeholders
|
Participate and facilitate: R Stakeholder participation R Elicitation process for requirements capture Monitor, review, and approve: R Requirements baseline R Requirements metrics and tracking R Project risks |
Participate and facilitate: R Stakeholder participation Review & approve: R Interface agreements R Project architecture Monitor: R Requirements baseline R Project risks
|
Participate and facilitate: R Stakeholder participation R Technical reviews R COTS product review Review & approve: R Detailed design R Contract for Development Team Monitor R Baseline requirements and design R Project risks |
|
Systems Engineering Technical Assistance In-house, Independent Verification & Validation** Consultant, systems Manager |
Identify, Prepare, and document or update: R Validated set of system level requirements R Requirements review R Verification plan R Interfaces R Risks and trend Perform: R Analysis R Decomposition R Requirements baseline R Completeness of requirements Perform/Support: R Feasibility analysis Support, participate and report R Decision gates |
Identify, prepare, and document (update) R System Development RFP R Validated set of sub-system requirements R Project architecture alternatives R Interfaces R Verification plans R Integration plan R Project risks R Configuration items Perform: R Analysis R Decomposition R Requirements baseline R Completeness of requirements Perform/Support R Feasibility analysis Support, participate and report R Decision gates |
Support, participate, review, and comment: R Development team evaluation R COTS evaluation R Detailed design R Technical reviews R Developmental CM R Development risks R Unit test procedures R Technical plans: - Deployment - Installation - Technology - Security - Development - O&M Support, participate, and report R Decision gates |
|
Development Team In-house, System Integrator |
Review & comment* R All or in-part all project management plans
*subject to availability to public comment |
Review and comment* R All or in-part all Definition & Architecture
*subject to availability to public comment |
Identify, prepare, and document: R Technical plans R Developmental plan R Developmental CM R Developmental risks Perform and document R Detailed design R Technical review |
** Independent Verification & Validation - role and responsibility are monitoring, reporting, supporting, and participating but not performing- applies to all phases and tasks
Table 6‑4 Phase 3 Roles and Responsibilities
|
3.6.2 Integration |
3.6.3 Verification |
|||
|---|---|---|---|---|
|
System Owner Project Sponsor & Stakeholders |
R Review, participate, and approve R Technical reviews R CM activities R Coordination between projects Monitor R Project risks
|
Review, participate, and approve R Integration plan R Integration support R Training staff Monitor R Integration activities
|
Review, participate, and approve R Verification master plan R Verification plans R Verification procedures R Verification of the system Monitor R Verification activities R Verification risks R Defects & resolution |
Review, participate, and approve R Deployment plans R Deployment support Monitor R Deployment activities R Deployment risks R Staff readiness
|
|
Systems Engineering Technical Assistance In-hours, Independent Verification and Validation**, Consultant, Systems Manager |
Support, participate & report R Technical reviews R Decision gate R Monitor & report R Development risks R COTS procurements Perform & report R Coordination between projects R Risk assessment R Risk mitigation
|
Support, participate , and report R Integration reviews R Training Monitor and report R Integration risks R CM activities Perform & report R Coordination between projects R Risk assessment R Risk mitigation
|
Support, participate , and report R Verification readiness reviews R Verification procedures R Verification of the system Monitor and report R Verification risk R CM activities R Defect & resolution activities Perform and report R Coordination between projects R Risk assessment R Risk mitigation |
