Level 1 – Performed:

The implemented process achieves its process purpose.

Although the process is not thoroughly planned and monitored the required output work products
will be achieved.
Customer requirement  System requirement  Software requirements  Derived requirement.

PA1.1 Process performance

BP.1 Specify software requirements:

a. We need to check the software requirements is at completed state.

b. We need to check Asil is assigned for completed software requirements.
c. Also we need to check the system requirements from which the software requirements are
derived should be at completed state.
d. Ensure the change request ID is allocated writing the software requirement.

BP.2 Structure software requirements

a. Ensure the requirements are documented by Grouping ,sorting and Categorizing

b. We need to follow the folder structure to document all the
customer,software ,system,powerpack,mechanical and electrical requirements
c. Also we need to ensure the priority is assigned for each software requirements by the help of
milestone attribute.

BP.3 Analyze software requirements

a. We need to analyze the software requirements are technically feasible to implement.

b. And do we have any risk in implementing the requirements.
c. And software requirements are feasible to test in future.
Note: This will be shown as evidence in risk attribute of the software requirements.
If we have risk in implementing the swf requirements we need to analyze the risk with expert and
resolve the risk.

BP.4 Analyze the impact on the operating environment

a. We need to ensure the software requirements are impacting the operating environment.
b. This can be analyzed by considering the things like RAM,ROM,CPU usage of controller, range of
analog signals like current,voltage,pressure and temperature.

BP.5 Develop verification criteria.

a. Verification criteria is written by the requirement engineer , the verification criteria will act as
the input for writing the test cases for testing the requirement.
b. In Verification criteria we should mention the conditions and scenarios to test the particular
requirements.

BP.6 Establish bidirectional traceability

We need to ensure the software requirements are linked with the system requirements.

BP.7 Ensure consistency

We need to ensure the software requirements written is consistent with the system requirements.

This can be ensured by peer review checklist.

BP.8 Communicate agreed software requirements.

Communicate the agreed software requirements and updates to software requirements to all relevant
Stakeholder(SW Architect, Developer,Application tester).

Level 2 - Managed:

The level 1 performed process is now implemented in a managed fashion (planned, monitored and
adjusted) and its work products are well established, controlled and maintained.

PA2.1 Performance Management

GP2.1.1 Identify the objectives for the performance of the process.

Here we need to ensure how the Goals (Quality Goals) are tracked and documented for the particular
process area.
EG: In our organization the metrics will be performed for each customer release in Software
requirements process area we will ensure the following

1. 100 % of the safety requirements should have expert approval

2. 100% of the safety requirements have the verification team acceptance
3. 100% Traceability should be established between customer requirements, system requirements
and software requirements.
GP2.1.2 Plan the performance of the process to fulfill the identified objectives.

Ensure Process activities and tasks are defined.

And the Effort estimation is planned for performing the task related to each process area.

Eg: If we take software requirements process area the task estimation should be available for writing the
requirements, for doing the impact analysis and for performing the review.

Also the CRs should be planned for performing the particular task and it should be assigned for
responsible requirement engineer.

Build plan and the effort estimation sheet is the output for this.

GP2 .1.3 Monitor the performance of the process against the plans

We need to ensure and track the task are performed as planned.

This can be ensured in daily stand up meeting or in status meeting or in management review meeting.

GP2 .1.4 Adjust the performance of the process.

If the task as not happened as per the plan we need to reschedule the estimated efforts by considering
resource load and leave plans. And the rationale (explanation) should be given as why the tasks are not
happened as planned.

If we have any risks and issues in proceeding the task we need to raised the risk in rims tool and assign
the team to resolve the issue.
GP2 .1.5 Define responsibilities and authorities for performing the process.

Ensure the roles and responsibilities of the persons are defined to work in the particular process area.

Eg: To work in SWE.1 process area ensure the software requirement engineers roles and responsibilities
are defined,

Roles And Authorities

GP2.1.6 Identify and make available resources to perform the process according to plan

Ensure the necessary human resource and the infrastructure resources like tools are available to work in
the project.
Also ensure the training plan and the skill metrics are available for each human resource who is working
the project.

Also ensure the loading percentage of each person ( as how much % the person working for each
program) should be documented.

EG: Venkatesh VW – 50% ,Ford -50%

Vinushree DTMCA – 50%,DPF -50%

Below Screenshots are taken from Resource Management plan:

GP2.1.7 Manage the interfaces between involved parties

Ensure the project communication plan is documented and wer