representation Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > representation

Next subject: requirement Up: subject Previous subject: release

representation comparison table

Subject include have be not be write at is a synonym of is a subtopic of have example write prematurely become clarify describe hide have purpose divide up into use has definition read entrench review provide waste represent have dependency / with draw as contain adhere to see also write for

abstraction 9.2 - Principles Leading to Good Design details which can be shown
at a later stage of design
by the compiler or run-time system
by the use of default values
A representation that captures only essential aspects of something, reducing the complexity apparent to the abstraction's user

code

coding technique encoding technique 7.4 - The Basics of User Interface Design A way of representing information so as to communicate it to the user; e.g. using text, colour, icons, grouping, sound etc.

diagram a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it 7.4 - The Basics of User Interface Design

document 9.6 - Writing a Good Design Document Anything written that that describes software a particular audience

documentation requirements, designs, user documentation, instructions for testers and project plans as short and succinct as possible all stages of development 1.8 - The Eight Themes Emphasized in this Book just to meet specific deadlines because writing documents then becomes the objective, instead of solving problems to document decisions and to communicate them to others if it is excessively voluminous, poorly written or not made readily available poorly made decisions that are hard to change the information the readers will need, and must be organized in a way so that the readers can find what they need easily resources if it is never read standards for the company

language The Basics of Java language^2

model understandable by clients and users so they can participate in the development process as much as possible 5.1 - What is UML? the core of documentation describing the system a software system a standard notation such as UML so that everybody who looks at it will interpret it the same way An abstract representation of a system, that conveys a certain aspect of it in an understandable and analyzable way insights about the system when software engineers analyze it many classes from the framework if the system is being built using a framework model^2

name

package the same as package^2 in Java difficult to use if it depends on many other packages, since using it will also necessitate importing its dependent packages 9.4 - Software Architecture classes A collection of modelling elements that are grouped together because they are logically related a Java package another package if there is a dependency between an element in one package and an element in another as a box, with a smaller box attached above its top left corner package^3

scenario 7.3 - Developing Use Case Models of Systems the associated use case An instance of a use case that expresses a specific occurrence of the use case with a specific actor operating at a specific time and using specific data

schedule 11.3 - Cost Estimation The allocation of tasks to time periods

slot similar to a hook except that a slot must be filled in 3.3 - Frameworks: Reusable Subsystems A missing part in a framework that is filled in by the application developer who is adapting the framework to suit his or her needs

stereotype 5.6 - More Advanced Features of Class Diagrams the �interface� notation for indicating an interface in a UML diagram by drawing it as a class rectangle, with the expression �interface� at the top, and (optionally) a list of supported operations A way to use some of the standard UML notation to represent something special

Next subject: requirement Up: subject Previous subject: release

Subject	include	have	be not	be	write at	is a synonym of	is a subtopic of	have example	write prematurely	become	clarify	describe	hide	have purpose	divide up into	use	has definition	read	entrench	review	provide	waste	represent	have dependency / with	draw as	contain	adhere to	see also	write for
abstraction							9.2 - Principles Leading to Good Design						details which can be shown at a later stage of design by the compiler or run-time system by the use of default values				A representation that captures only essential aspects of something, reducing the complexity apparent to the abstraction's user
code
coding technique						encoding technique	7.4 - The Basics of User Interface Design										A way of representing information so as to communicate it to the user; e.g. using text, colour, icons, grouping, sound etc.
diagram		a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it					7.4 - The Basics of User Interface Design
document							9.6 - Writing a Good Design Document										Anything written that that describes software												a particular audience
documentation	requirements, designs, user documentation, instructions for testers and project plans			as short and succinct as possible	all stages of development		1.8 - The Eight Themes Emphasized in this Book		just to meet specific deadlines because writing documents then becomes the objective, instead of solving problems					to document decisions and to communicate them to others				if it is excessively voluminous, poorly written or not made readily available	poorly made decisions that are hard to change		the information the readers will need, and must be organized in a way so that the readers can find what they need easily	resources if it is never read					standards for the company
language							The Basics of Java																					language^2
model				understandable by clients and users so they can participate in the development process as much as possible			5.1 - What is UML?			the core of documentation describing the system		a software system				a standard notation such as UML so that everybody who looks at it will interpret it the same way	An abstract representation of a system, that conveys a certain aspect of it in an understandable and analyzable way				insights about the system when software engineers analyze it					many classes from the framework if the system is being built using a framework		model^2
name
package			the same as package^2 in Java	difficult to use if it depends on many other packages, since using it will also necessitate importing its dependent packages			9.4 - Software Architecture								classes		A collection of modelling elements that are grouped together because they are logically related						a Java package	another package if there is a dependency between an element in one package and an element in another	as a box, with a smaller box attached above its top left corner			package^3
scenario							7.3 - Developing Use Case Models of Systems				the associated use case						An instance of a use case that expresses a specific occurrence of the use case with a specific actor operating at a specific time and using specific data
schedule							11.3 - Cost Estimation										The allocation of tasks to time periods
slot				similar to a hook except that a slot must be filled in			3.3 - Frameworks: Reusable Subsystems										A missing part in a framework that is filled in by the application developer who is adapting the framework to suit his or her needs
stereotype							5.6 - More Advanced Features of Class Diagrams	the �interface� notation for indicating an interface in a UML diagram by drawing it as a class rectangle, with the expression �interface� at the top, and (optionally) a list of supported operations									A way to use some of the standard UML notation to represent something special