Planning for Requirements Management - Requirements Engineering and Management for Software Development Projects - page 111

methodology. It will also record the version control methodology of project's soft-
ware artifacts including check-in and check-out procedures.
SQAP would enumerate the quality control activities selected for the estab-
lishment of project requirements. It will include pass/fail criteria, defect reporting
and resolution methodology as well as escalation methodology and mechanisms in
case of disputed decisions.
The project schedule would contain various timelines for the establishment of
project requirements, performance of quality control activities, list of artifacts
needing approval from customer, and submission for and receipt of approvals.
7.6.4 Requirements Change Control and Management
Greek Philosopher Heraclitus said, ''There is nothing permanent except Change.''
Hardly any project is ever completed without some changes being requested and
implemented. So, it is very important that we plan for receiving and implementing
change requests. Change management forms part of the configuration management
process. Therefore, it is planned for in the SCMP. As it is rather not possible to
predict the timelines for receiving the change requests, so, the project schedule
would not contain any change management activities. The SCMP would however,
contain all the activities pertaining to change management including receipt of
change requests, recording them, analyzing them, implementation strategy,
implementation, quality control activities, and measurement and metrics to ana-
lyze the impact of change requests on the project.
7.6.5 Requirements Tracing, Tracking and Reporting
Requirements are to be traced through all the activities of software development so
as not miss any of them at any stage. This will ensure a software product that truly
meets all the requirements of the end user as well as those of other stakeholders.
Tracking and reporting of the requirements engineering activities provide needed
information to all the stakeholders and keep them on the same page. Therefore, all
these activities need to be planned. SPMP contains the information on the meth-
odology, periodicity and tools used in tracing of the requirements through the
software development. SPMP would also include information on the methodology
used for tracking and reporting on the requirements engineering activities as well
as the formats and templates used for reporting the performance of the require-
ments engineering activities in the project. SPMP would also enumerate the
agencies responsible for tracing, tracking and reporting activities, the periodicity
of reporting as well as the agencies that receive the reports. The storage of the
documents used in tracing, tracking and reporting is defined in the SCMP.