customer Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > person or group > person > customer

Next person: departmental manager Up: person, stakeholder Previous person: stakeholder

customer comparison table

Subject make like concern with has definition be have goal want understand agree on is a subtopic of involve in is a synonym of expect is a kind of make decisions about demand

person requirements better if they are expressed in terms of use cases person or group

stakeholder A person or organization that may be affected by the success or failure of a project or organization requirements better if they are expressed in terms of use cases requirements 1.4 - Stakeholders in Software Engineering person

customer to feel involved in the software engineering process resulting in fewer mistakes being made and greater acceptance of the finished product software that helps their organization save or make money, typically by making the users and the organization as a whole more productive reliability A person who make decisions about ordering and paying for software (in contrast to user); customers are those who have the problem that is being solved by the development of software a user of software either to increase profits or to run their business more effectively software that solves problems at an acceptable cost in terms of money paid and resources used the architecture so they can be confident the software is being designed well and can monitor development progress requirements 1.4 - Stakeholders in Software Engineering requirements analysis, user interface design and deployment, and also may play a role in design, quality assurance and project management client software to be of high quality and to be produced rapidly stakeholder ordering and paying for the software new and updated software

Subject	make	like	concern with	has definition	be	have goal	want	understand	agree on	is a subtopic of	involve in	is a synonym of	expect	is a kind of	make decisions about	demand
person								requirements better if they are expressed in terms of use cases						person or group
stakeholder				A person or organization that may be affected by the success or failure of a project or organization				requirements better if they are expressed in terms of use cases	requirements	1.4 - Stakeholders in Software Engineering				person
customer	to feel involved in the software engineering process resulting in fewer mistakes being made and greater acceptance of the finished product	software that helps their organization save or make money, typically by making the users and the organization as a whole more productive	reliability	A person who make decisions about ordering and paying for software (in contrast to user); customers are those who have the problem that is being solved by the development of software	a user of software	either to increase profits or to run their business more effectively	software that solves problems at an acceptable cost in terms of money paid and resources used	the architecture so they can be confident the software is being designed well and can monitor development progress	requirements	1.4 - Stakeholders in Software Engineering	requirements analysis, user interface design and deployment, and also may play a role in design, quality assurance and project management	client	software to be of high quality and to be produced rapidly	stakeholder	ordering and paying for the software	new and updated software

Next person: departmental manager Up: person, stakeholder Previous person: stakeholder