Requirements management - Revision history

Tkokotas at 12:15, 20 December 2018

2018-12-20T12:15:09Z

← Older revision		Revision as of 12:15, 20 December 2018
Line 1:		Line 1:
			''Developed by Marine Camille Perceval''

	= Overview =		= Overview =

Tkokotas at 11:49, 9 November 2018

2018-11-09T11:49:26Z

← Older revision		Revision as of 11:49, 9 November 2018
Line 136:		Line 136:
	<references />		<references />

	[[Category:Project Management]][[Category:Systems Engineering]]		[[Category:Project Management]][[Category:Systems Engineering]][[Category:Purpose]][[Category:Scope]]

Tkokotas at 21:11, 24 October 2018

2018-10-24T21:11:05Z

← Older revision		Revision as of 21:11, 24 October 2018
Line 136:		Line 136:
	<references />		<references />

	[[Category:Project Management]][[Category:Systems ~~engineering~~]]		[[Category:Project Management]][[Category:Systems Engineering]]

Eniram: /* Requirements change management */

2014-12-01T13:20:42Z

Requirements change management

← Older revision		Revision as of 13:20, 1 December 2014
Line 90:		Line 90:
	== Requirements change management ==		== Requirements change management ==

	Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process<ref>Office of Government Commerce, UK, 'Managing changes to requirements', available online: http://webarchive.nationalarchives.gov.uk/20100503135839/http:/www.ogc.gov.uk/delivery_lifecycle_managing_changes_to_requirements.asp</ref>, mainly due to uncertainty and complexity in projects, and some examples of circumstances can be for instance:		Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process<ref>Office of Government Commerce, UK, 'Managing changes to requirements', available online: http://webarchive.nationalarchives.gov.uk/20100503135839/http:/www.ogc.gov.uk/delivery_lifecycle_managing_changes_to_requirements.asp</ref>, mainly due to uncertainty and [[complexity]] in projects, and some examples of circumstances can be for instance:

	* A change in the needs of the stakeholders, for example because of a lack of understanding		* A change in the needs of the stakeholders, for example because of a lack of understanding

Eniram: /* Requirements elicitation */

2014-12-01T13:20:12Z

Requirements elicitation

← Older revision		Revision as of 13:20, 1 December 2014
Line 57:		Line 57:
	* The stakeholders i.e. all the interested parties. This is the first source to be considered, as the system or product must meet the stakeholders’ desires and needs in the first place. Stakeholders have to be properly identified and their points of view have to be fully understood.		* The stakeholders i.e. all the interested parties. This is the first source to be considered, as the system or product must meet the stakeholders’ desires and needs in the first place. Stakeholders have to be properly identified and their points of view have to be fully understood.
	* The environment in which the system will exist and be performed and the system’s potential impact on it.		* The environment in which the system will exist and be performed and the system’s potential impact on it.
	*The possible interfaces with other existing systems and the associated requirements.		* The possible interfaces with other existing systems and the associated requirements.
	*The requirements specific to the implementation of the system		* The requirements specific to the implementation of the system

	The complete identification of the sources of requirement from the very beginning of the project is a way to avoid any unknown requirement to emerge later in the project process, which will have consequences in terms of time and money.		The complete identification of the sources of requirement from the very beginning of the project is a way to avoid any unknown requirement to emerge later in the project process, which will have consequences in terms of time and money. A [[Stakeholder Analysis]] will allow defining all the relevant stakeholders.

	Requirements elicitation consists in understanding the needs of the stakeholders or any source of requirements and collecting them for future analysis<ref name="six">Alan M. Davis, Ed Yourdon, Ann S. Zweig, ''Requirements Management Made Easy'', Omni-Vista, Inc.</ref>. In product development, it consists in determining all the features that need to be included in the product. The requirements can be elicited by observing, interviewing or questioning any known source of requirements.		Requirements elicitation consists in understanding the needs of the stakeholders or any source of requirements and collecting them for future analysis<ref name="six">Alan M. Davis, Ed Yourdon, Ann S. Zweig, ''Requirements Management Made Easy'', Omni-Vista, Inc.</ref>. In product development, it consists in determining all the features that need to be included in the product. The requirements can be elicited by observing, interviewing or questioning any known source of requirements.

Eniram: /* Requirements change management */

2014-12-01T13:02:07Z

Requirements change management

← Older revision		Revision as of 13:02, 1 December 2014
Line 101:		Line 101:
	* In a construction project, the need to adapt a new facility to other uses than the ones it was originally designed		* In a construction project, the need to adapt a new facility to other uses than the ones it was originally designed

	These changes are the reason why requirements management is needed throughout the life-cycle and not only in the first phases. Requirements management provides visibility, tracking and traceability of the requirements, which are crucial elements in case of such changing circumstances. The success in requirements management practices comes from the ability to accommodate such changes successfully. The inability to manage these changing requirements is often considered as a cause for project failure, impacting both cost and duration. ~~Traceability is one of the main ways to identify, understand and support a change and its impact.~~		These changes are the reason why requirements management is needed throughout the life-cycle and not only in the first phases. Requirements management provides visibility, tracking and traceability of the requirements, which are crucial elements in case of such changing circumstances. Traceability is one of the main ways to identify, understand and support a change and its impact. The success in requirements management practices comes from the ability to accommodate such changes successfully. The inability to manage these changing requirements is often considered as a cause for project failure, impacting both cost and duration<ref name="deux"/>.

	Of course, managing changes appears to be the most difficult task in requirements management.		Of course, managing changes appears to be the most difficult task in requirements management.

Eniram: /* Requirements change management */

2014-12-01T12:59:56Z

Requirements change management

← Older revision		Revision as of 12:59, 1 December 2014
Line 90:		Line 90:
	== Requirements change management ==		== Requirements change management ==

	Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process, mainly due to uncertainty and complexity in projects, and some examples of circumstances can be for instance:		Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process<ref>Office of Government Commerce, UK, 'Managing changes to requirements', available online: http://webarchive.nationalarchives.gov.uk/20100503135839/http:/www.ogc.gov.uk/delivery_lifecycle_managing_changes_to_requirements.asp</ref>, mainly due to uncertainty and complexity in projects, and some examples of circumstances can be for instance:

	* A change in the needs of the stakeholders, for example because of a lack of understanding		* A change in the needs of the stakeholders, for example because of a lack of understanding

Eniram: /* Definition of project success */

2014-12-01T12:45:04Z

Definition of project success

← Older revision		Revision as of 12:45, 1 December 2014
Line 20:		Line 20:
	Aaron et al.<ref name=''success''>Aaron, S.J., Don, D., Ofer, L., Alan, M.C., 2001. ''Project success: amultidimensional strategic concept.'' Long Range Plann. 34 (6), 699–725. </ref> define the success of a project in terms of the following criteria:		Aaron et al.<ref name=''success''>Aaron, S.J., Don, D., Ofer, L., Alan, M.C., 2001. ''Project success: amultidimensional strategic concept.'' Long Range Plann. 34 (6), 699–725. </ref> define the success of a project in terms of the following criteria:

	* The project efficiency: The achievement of the specified project goals, such as time, budget, performance and other requirements,		* The project efficiency: The achievement of the specified project goals, such as time, budget, performance and other requirements.

	* The impact on the customer ~~(any stakeholder with a strong interest in the project, who requires the services of the project management team, and usually who provides resources for the project)~~: The achievement of functional an technical performances, the solving of the customer's problem and the fulfilment of its needs, resulting in customer's satisfaction and loyalty.		* The impact on the customer: The achievement of functional an technical performances, the solving of the customer's problem and the fulfilment of its needs, resulting in customer's satisfaction and loyalty. A customer can be any stakeholder with a strong interest in the project, who requires the services of the project management team, and usually who provides resources for the project.

	* The business success, i.e. the impact and benefits on the performing organisation, such as profits, market share and growth,		* The business success, i.e. the impact and benefits on the performing organisation, such as profits, market share and growth.

	* The ability to prepare the organisation to future challenges, in terms of long-term benefits.		* The ability to prepare the organisation to future challenges, in terms of long-term benefits.

Eniram: /* Requirements change management */

2014-11-29T17:16:50Z

Requirements change management

← Older revision		Revision as of 17:16, 29 November 2014
Line 90:		Line 90:
	== Requirements change management ==		== Requirements change management ==

	Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process, and some ~~reasons for that~~ can be for instance:		Requirements definition is one of the first steps of a project process, because it allows the project to be properly defined by setting all the goals to be reached. However, requirements can emerge all along the life-cycle of the project process. In fact, it is not uncommon that the requirements change throughout the engineering process, mainly due to uncertainty and complexity in projects, and some examples of circumstances can be for instance:

	* A change in the needs of the stakeholders, for example because of a lack of understanding		* A change in the needs of the stakeholders, for example because of a lack of understanding
Line 101:		Line 101:
	* In a construction project, the need to adapt a new facility to other uses than the ones it was originally designed		* In a construction project, the need to adapt a new facility to other uses than the ones it was originally designed

	These changes are the reason why requirements management is needed throughout the life-cycle and not only in the first phases. Requirements management provides visibility, tracking and traceability of the requirements, which are crucial elements in case of such changing circumstances. The inability to manage these changing requirements is often considered as a cause for project failure, impacting both cost and duration. Traceability is one of the main ways to identify, understand and support a change and its impact.		These changes are the reason why requirements management is needed throughout the life-cycle and not only in the first phases. Requirements management provides visibility, tracking and traceability of the requirements, which are crucial elements in case of such changing circumstances. The success in requirements management practices comes from the ability to accommodate such changes successfully. The inability to manage these changing requirements is often considered as a cause for project failure, impacting both cost and duration. Traceability is one of the main ways to identify, understand and support a change and its impact.

	Of course, managing changes appears to be the most difficult task in requirements management.		Of course, managing changes appears to be the most difficult task in requirements management.


	= Application context =		= Application context =

Eniram at 17:01, 29 November 2014

2014-11-29T17:01:50Z

← Older revision		Revision as of 17:01, 29 November 2014
Line 10:		Line 10:

	Requirements management can be handled by using different kinds of tools, which can either be manual processes or specialised tools.		Requirements management can be handled by using different kinds of tools, which can either be manual processes or specialised tools.


	= Requirements management as a key for successful projects =		= Requirements management as a key for successful projects =