person Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

Next person or group: team Up: person or group Previous person or group: patterns community

person comparison table

Subject make decisions about reuse have expect make license in be take personal responsibility for is a kind of is a synonym of is a subtopic of agree on license involve in want understand have role like design participate in perform apply has definition demand concern with have goal adhere to

customer ordering and paying for the software software to be of high quality and to be produced rapidly to feel involved in the software engineering process resulting in fewer mistakes being made and greater acceptance of the finished product a user of software stakeholder client 1.4 - Stakeholders in Software Engineering requirements requirements analysis, user interface design and deployment, and also may play a role in design, quality assurance and project management 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 software that helps their organization save or make money, typically by making the users and the organization as a whole more productive 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 new and updated software reliability either to increase profits or to run their business more effectively

departmental manager person 11.1 - What is Project Management? requirements better if they are expressed in terms of use cases activities such as hiring, building morale, and issuing the final directions

domain expert person 4.1 - Domain Analysis requirements better if they are expressed in terms of use cases Somebody with expertise in a given domain, but who may or may not have expertise in software

engineer established designs sufficient engineering education and experience to be licensed most countries in order to legally perform consulting or self-employed work where you call yourself an 'engineer' work person 1.3 - Software Engineering as a Branch of the Engineering Profession before the 1940's in most jurisdictions that omitting design documentation or documenting a design after it is complete is unacceptable, leads to serious mistakes, and makes planning for construction impossible to put knowledge to use in innovative ways to solve problems artefacts following well accepted practices which normally involve the application of science, mathematics and economics well-understood principles A person who performs engineering (in contrast to scientist). The term engineer is legally reserved, in many jurisdictions, for those who have obtained engineering education and experience, and perform engineering within a company or else have been granted a license, or some other form of certification, to offer engineering services to the public a code of ethics

moderator person facilitator 4.6 - Some Techniques for Gathering and Analyzing Requirements requirements better if they are expressed in terms of use cases brainstorming discussions if he or she wishes A person who leads a brainstorming session

scientist person 1.8 - The Eight Themes Emphasized in this Book requirements better if they are expressed in terms of use cases to seek out new knowledge A person who seeks new knowledge about nature (in contrast to engineer)

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

Next person or group: team Up: person or group Previous person or group: patterns community

Subject	make decisions about	reuse	have	expect	make	license in	be	take personal responsibility for	is a kind of	is a synonym of	is a subtopic of	agree on	license	involve in	want	understand	have role	like	design	participate in	perform	apply	has definition	demand	concern with	have goal	adhere to
customer	ordering and paying for the software			software to be of high quality and to be produced rapidly	to feel involved in the software engineering process resulting in fewer mistakes being made and greater acceptance of the finished product		a user of software		stakeholder	client	1.4 - Stakeholders in Software Engineering	requirements		requirements analysis, user interface design and deployment, and also may play a role in design, quality assurance and project management	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		software that helps their organization save or make money, typically by making the users and the organization as a whole more productive					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	new and updated software	reliability	either to increase profits or to run their business more effectively
departmental manager									person		11.1 - What is Project Management?					requirements better if they are expressed in terms of use cases					activities such as hiring, building morale, and issuing the final directions
domain expert									person		4.1 - Domain Analysis					requirements better if they are expressed in terms of use cases							Somebody with expertise in a given domain, but who may or may not have expertise in software
engineer		established designs	sufficient engineering education and experience to be licensed			most countries in order to legally perform consulting or self-employed work where you call yourself an 'engineer'		work	person		1.3 - Software Engineering as a Branch of the Engineering Profession		before the 1940's in most jurisdictions			that omitting design documentation or documenting a design after it is complete is unacceptable, leads to serious mistakes, and makes planning for construction impossible	to put knowledge to use in innovative ways to solve problems		artefacts following well accepted practices which normally involve the application of science, mathematics and economics			well-understood principles	A person who performs engineering (in contrast to scientist). The term engineer is legally reserved, in many jurisdictions, for those who have obtained engineering education and experience, and perform engineering within a company or else have been granted a license, or some other form of certification, to offer engineering services to the public				a code of ethics
moderator									person	facilitator	4.6 - Some Techniques for Gathering and Analyzing Requirements					requirements better if they are expressed in terms of use cases				brainstorming discussions if he or she wishes			A person who leads a brainstorming session
scientist									person		1.8 - The Eight Themes Emphasized in this Book					requirements better if they are expressed in terms of use cases	to seek out new knowledge						A person who seeks new knowledge about nature (in contrast to engineer)
stakeholder									person		1.4 - Stakeholders in Software Engineering	requirements				requirements better if they are expressed in terms of use cases							A person or organization that may be affected by the success or failure of a project or organization