Requirements engineering - Revision history

Tkokotas at 12:11, 20 December 2018

2018-12-20T12:11:07Z

← Older revision		Revision as of 12:11, 20 December 2018
Line 1:		Line 1:
			''Developed by Joakim Hornstrup''


	As part of systems engineering - requirements engineering is a discipline in developing requirements for a system.		As part of systems engineering - requirements engineering is a discipline in developing requirements for a system.
	Often, if a project is about creating a new system, then requirements are made to specify the system, in order to create common understanding among the involved parties in a project. Requirements specify the needs and conditions of a client to help developers understand the need they are fulfilling and how they should satisfy that need. Developers create the requirements on the basis of the needs, to specify what the product is supposed to do. Requirements engineering is regarded as crucial in a development process, because the outcome often creates the basis for getting financial support. It’s basically the formal link between stakeholders and developers. The requirements can be created either by the stakeholder who wants something built, as well as it can be the developer’s responsibility.		Often, if a project is about creating a new system, then requirements are made to specify the system, in order to create common understanding among the involved parties in a project. Requirements specify the needs and conditions of a client to help developers understand the need they are fulfilling and how they should satisfy that need. Developers create the requirements on the basis of the needs, to specify what the product is supposed to do. Requirements engineering is regarded as crucial in a development process, because the outcome often creates the basis for getting financial support. It’s basically the formal link between stakeholders and developers. The requirements can be created either by the stakeholder who wants something built, as well as it can be the developer’s responsibility.

Tkokotas at 20:12, 23 October 2018

2018-10-23T20:12:45Z

← Older revision		Revision as of 20:12, 23 October 2018
Line 146:		Line 146:
	[[Category:Project Management]]		[[Category:Project Management]]
	[[Category:Risk Management]]		[[Category:Risk Management]]
	~~[[Category:Requirements Management]]~~

Joh: /* Non-functional requirements */

2014-12-01T22:40:19Z

Non-functional requirements

← Older revision		Revision as of 22:40, 1 December 2014
Line 94:		Line 94:
	These lists exist as ISO standards listing certain qualities and its attributes, one example could be the ISO/IEC 25010:2011<ref name="Iso2011">["http://www.iso.org/iso/catalogue_detail.htm?csnumber=35733"] '' ISO/IEC 25010:2011 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models'' </ref> standard. The procedure is then to go through the list and select qualities determined by system type, application areas, goals or the stakeholder’s opinion. To ensure the selected qualities make sense, linking them to system goals will only strengthen the argument of why they should be applied to the system. The picture shows an example of a list with selected qualities and attributes.		These lists exist as ISO standards listing certain qualities and its attributes, one example could be the ISO/IEC 25010:2011<ref name="Iso2011">["http://www.iso.org/iso/catalogue_detail.htm?csnumber=35733"] '' ISO/IEC 25010:2011 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models'' </ref> standard. The procedure is then to go through the list and select qualities determined by system type, application areas, goals or the stakeholder’s opinion. To ensure the selected qualities make sense, linking them to system goals will only strengthen the argument of why they should be applied to the system. The picture shows an example of a list with selected qualities and attributes.

	[[File:Qualities.jpg\|thumb\|none\|300px\|Example on selected qualites and attributes]]		[[File:Qualities.jpg\|thumb\|none\|300px\|Example on selected qualites and attributes<ref name="QualityPic">["https://www.iso.org/obp/ui/#iso:std:iso-iec:25010:ed-1:v1:en"] '' ISO/IEC 25010:2011 - Quality in use characteristics and subcharacteristics'' </ref>]]

	The qualities are by no means less important than functional requirements, because if the qualities are not being addressed in an implementation then it is very likely the system will be completely unusable, regardless of how good the rest may be. Because qualities are often crosscutting concerns, it is much more difficult to modify an existing system with new qualities, than modifying it’s functionality. It is important that the defined qualities are clear and precise, without providing too much detail. It can be tempting to specify the qualities in detail, but that might exclude better solutions at the given moment.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>		The qualities are by no means less important than functional requirements, because if the qualities are not being addressed in an implementation then it is very likely the system will be completely unusable, regardless of how good the rest may be. Because qualities are often crosscutting concerns, it is much more difficult to modify an existing system with new qualities, than modifying it’s functionality. It is important that the defined qualities are clear and precise, without providing too much detail. It can be tempting to specify the qualities in detail, but that might exclude better solutions at the given moment.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>

Joh: /* Functional requirements */

2014-12-01T22:37:54Z

Functional requirements

← Older revision		Revision as of 22:37, 1 December 2014
Line 86:		Line 86:
	The method of the describing functional requirements can be complex and very hard to do. Though there exist various techniques and styles of specifying requirements. Each technique has an individual profile of pros and cons, which means it really depends on which kind of system the requirements are needed for. Among the well-known techniques, there are controlled languages, use cases, snow cards, detailed attributed tables, etc.		The method of the describing functional requirements can be complex and very hard to do. Though there exist various techniques and styles of specifying requirements. Each technique has an individual profile of pros and cons, which means it really depends on which kind of system the requirements are needed for. Among the well-known techniques, there are controlled languages, use cases, snow cards, detailed attributed tables, etc.
	An example on the snow card technique is shown in the picture below. The picture is a snow card template that contains valuable attributes one should consider when creating functional requirements. The idea to create a snow card for each requirement needed, until most functionality is covered or all business process is covered.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>		An example on the snow card technique is shown in the picture below. The picture is a snow card template that contains valuable attributes one should consider when creating functional requirements. The idea to create a snow card for each requirement needed, until most functionality is covered or all business process is covered.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>
	[[File:SnowCard.jpg\|thumb\|500px\|none\|Snow Card Template, a template on how to do functional requirements<ref name="~~Iso2011~~">["http://www.informit.com/articles/article.aspx?p=1929849&seqNum=15"] ''Snow Card Template - InformIT'' </ref>]]		[[File:SnowCard.jpg\|thumb\|500px\|none\|Snow Card Template, a template on how to do functional requirements<ref name="snow">["http://www.informit.com/articles/article.aspx?p=1929849&seqNum=15"] ''Snow Card Template - InformIT'' </ref>]]

	===Non-functional requirements===		===Non-functional requirements===

Joh: /* Functional requirements */

2014-12-01T22:37:23Z

Functional requirements

← Older revision		Revision as of 22:37, 1 December 2014
Line 86:		Line 86:
	The method of the describing functional requirements can be complex and very hard to do. Though there exist various techniques and styles of specifying requirements. Each technique has an individual profile of pros and cons, which means it really depends on which kind of system the requirements are needed for. Among the well-known techniques, there are controlled languages, use cases, snow cards, detailed attributed tables, etc.		The method of the describing functional requirements can be complex and very hard to do. Though there exist various techniques and styles of specifying requirements. Each technique has an individual profile of pros and cons, which means it really depends on which kind of system the requirements are needed for. Among the well-known techniques, there are controlled languages, use cases, snow cards, detailed attributed tables, etc.
	An example on the snow card technique is shown in the picture below. The picture is a snow card template that contains valuable attributes one should consider when creating functional requirements. The idea to create a snow card for each requirement needed, until most functionality is covered or all business process is covered.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>		An example on the snow card technique is shown in the picture below. The picture is a snow card template that contains valuable attributes one should consider when creating functional requirements. The idea to create a snow card for each requirement needed, until most functionality is covered or all business process is covered.<ref name="REBOOK" /><ref name="SWBOOK" /><ref name="SREBOOK"/>
	[[File:SnowCard.jpg\|thumb\|500px\|none\|Snow Card Template, a template on how to do functional requirements]]		[[File:SnowCard.jpg\|thumb\|500px\|none\|Snow Card Template, a template on how to do functional requirements<ref name="Iso2011">["http://www.informit.com/articles/article.aspx?p=1929849&seqNum=15"] ''Snow Card Template - InformIT'' </ref>]]

	===Non-functional requirements===		===Non-functional requirements===

Joh: /* Additional related material */

2014-12-01T22:34:42Z

Additional related material

← Older revision		Revision as of 22:34, 1 December 2014
Line 129:		Line 129:
	'''Links:'''		'''Links:'''
	*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB - Video presentation about introduction to requirements engineering		*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB - Video presentation about introduction to requirements engineering
	*http://dl.acm.org/citation.cfm?id=545779 - System Requirements Engineering book
	*http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method		*http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method
	*http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems		*http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems

Joh: /* Additional related material */

2014-12-01T22:34:15Z

Additional related material

← Older revision		Revision as of 22:34, 1 December 2014
Line 132:		Line 132:
	*http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method		*http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method
	*http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems		*http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems
	*http://sutlib2.sut.ac.th/sut_contents/H104135.pdf - A book about Systems Engineering and Analysis, this book cover most of the system and requirement engineering process
	*http://www.engr.sjsu.edu/~fayad/current.courses/cmpe202-fall2010/docs/Lecture-5/Tech-Req-Elicitation-Paper.pdf - Paper about requirements elicitation.		*http://www.engr.sjsu.edu/~fayad/current.courses/cmpe202-fall2010/docs/Lecture-5/Tech-Req-Elicitation-Paper.pdf - Paper about requirements elicitation.
	*http://dl.acm.org/citation.cfm?id=1869735 - Good book that covers the fundamentals of requirements engineering
	*http://www.saxo.com/dk/requirements-engineering_gerald-kotonya_hardback_9780471972082 - Also a good book that covers the fundamentals of requirements engineering with good techniques and methods.


	'''Books:'''		'''Books:'''
	* E.Hull, K. Jackson, J. Dick - Requirements Engineering 3rd edition		* E.Hull, K. Jackson, J. Dick - Requirements Engineering 3rd edition
	* S. Lauesen - Software Requirements		* S. Lauesen - Software Requirements
			* B. S. Blanchard, W. J. Fabrycky - Systems Engineering and analysis 4th edition
			* K. Pohl - Requirements Engineering: Fundamentals, Principles and Techniques
			* G. Kotonya, I. Sommerville - Requirements Engineering - Processes and techniqes

	= Reference =		= Reference =

Joh at 22:30, 1 December 2014

2014-12-01T22:30:36Z

← Older revision		Revision as of 22:30, 1 December 2014
Line 130:		Line 130:
	*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB - Video presentation about introduction to requirements engineering		*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB - Video presentation about introduction to requirements engineering
	*http://dl.acm.org/citation.cfm?id=545779 - System Requirements Engineering book		*http://dl.acm.org/citation.cfm?id=545779 - System Requirements Engineering book
	http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method		*http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method
	http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems		*http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems
	http://sutlib2.sut.ac.th/sut_contents/H104135.pdf - A book about Systems Engineering and Analysis, this book cover most of the system and requirement engineering process		*http://sutlib2.sut.ac.th/sut_contents/H104135.pdf - A book about Systems Engineering and Analysis, this book cover most of the system and requirement engineering process
	http://www.engr.sjsu.edu/~fayad/current.courses/cmpe202-fall2010/docs/Lecture-5/Tech-Req-Elicitation-Paper.pdf - Paper about requirements elicitation.		*http://www.engr.sjsu.edu/~fayad/current.courses/cmpe202-fall2010/docs/Lecture-5/Tech-Req-Elicitation-Paper.pdf - Paper about requirements elicitation.
	http://dl.acm.org/citation.cfm?id=1869735 - Good book that covers the fundamentals of requirements engineering		*http://dl.acm.org/citation.cfm?id=1869735 - Good book that covers the fundamentals of requirements engineering
	http://www.saxo.com/dk/requirements-engineering_gerald-kotonya_hardback_9780471972082 - Also a good book that covers the fundamentals of requirements engineering with good techniques and methods.		*http://www.saxo.com/dk/requirements-engineering_gerald-kotonya_hardback_9780471972082 - Also a good book that covers the fundamentals of requirements engineering with good techniques and methods.

Joh at 22:30, 1 December 2014

2014-12-01T22:30:00Z

← Older revision		Revision as of 22:30, 1 December 2014
Line 121:		Line 121:

	== Comparable standards / recommendations ==		== Comparable standards / recommendations ==
	http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=43564 - ISO/IEC 15288:2008<br/>		http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=43564 - ISO/IEC 15288:2008 - Systems and software engineering - System life cycle processes<br/>
	http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43693 - ISO/IEC 26702:2007		http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43693 - ISO/IEC 26702:2007 - Systems engineering -- Application and management of the systems engineering process<br/>
			http://www.iso.org/iso/catalogue_detail.htm?csnumber=35733 - ISO/IEC 25010:2011 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models


	== Additional related material ==		== Additional related material ==
	'''Links:'''		'''Links:'''
	*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB		*https://www.youtube.com/watch?v=Ec0s0z5uXQ8&list=PLuge2MomyEekzECuCppJesmkv1tmUHCkB - Video presentation about introduction to requirements engineering
	*http://dl.acm.org/citation.cfm?id=545779		*http://dl.acm.org/citation.cfm?id=545779 - System Requirements Engineering book
			http://www.wohlin.eu/rm_chapter05.pdf - A paper about the context method
			http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.365.8494 - A document specifying design and validation for software systems
			http://sutlib2.sut.ac.th/sut_contents/H104135.pdf - A book about Systems Engineering and Analysis, this book cover most of the system and requirement engineering process
			http://www.engr.sjsu.edu/~fayad/current.courses/cmpe202-fall2010/docs/Lecture-5/Tech-Req-Elicitation-Paper.pdf - Paper about requirements elicitation.
			http://dl.acm.org/citation.cfm?id=1869735 - Good book that covers the fundamentals of requirements engineering
			http://www.saxo.com/dk/requirements-engineering_gerald-kotonya_hardback_9780471972082 - Also a good book that covers the fundamentals of requirements engineering with good techniques and methods.


	'''Books:'''		'''Books:'''

Joh at 22:09, 1 December 2014

2014-12-01T22:09:35Z

← Older revision		Revision as of 22:09, 1 December 2014
Line 92:		Line 92:
	Defining quality like that can in itself be pretty broad, and could mean different things, that’s why it is also important to specify the quality attributes. Quality attributes is a set of attributes that helps understanding how to achieve the quality. So if we take the computer example again, the quality attributes of reliable could be: error tolerant, consistent and simple. Defining qualities and its attributes are hard and complex to define precisely. That’s why there exist quality lists that are made as standards, to help define systems.		Defining quality like that can in itself be pretty broad, and could mean different things, that’s why it is also important to specify the quality attributes. Quality attributes is a set of attributes that helps understanding how to achieve the quality. So if we take the computer example again, the quality attributes of reliable could be: error tolerant, consistent and simple. Defining qualities and its attributes are hard and complex to define precisely. That’s why there exist quality lists that are made as standards, to help define systems.

	These lists exist as ISO standards listing certain qualities and its attributes, one example could be the ISO/IEC 25010:2011 standard. The procedure is then to go through the list and select qualities determined by system type, application areas, goals or the stakeholder’s opinion. To ensure the selected qualities make sense, linking them to system goals will only strengthen the argument of why they should be applied to the system. The picture shows an example of a list with selected qualities and attributes.		These lists exist as ISO standards listing certain qualities and its attributes, one example could be the ISO/IEC 25010:2011<ref name="Iso2011">["http://www.iso.org/iso/catalogue_detail.htm?csnumber=35733"] '' ISO/IEC 25010:2011 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models'' </ref> standard. The procedure is then to go through the list and select qualities determined by system type, application areas, goals or the stakeholder’s opinion. To ensure the selected qualities make sense, linking them to system goals will only strengthen the argument of why they should be applied to the system. The picture shows an example of a list with selected qualities and attributes.

	[[File:Qualities.jpg\|thumb\|none\|300px\|Example on selected qualites and attributes]]		[[File:Qualities.jpg\|thumb\|none\|300px\|Example on selected qualites and attributes]]