Fichas
Java Software Development Units 4-5
Fichas del conjunto (51)
- 1recursive associationAn association where the links connect objects belonging to
the same class. - 2access modifierOne of the keywords public, protected and private, specifying
the extent to which class members are accessible from outside the class. In the
absence of one of these keywords the default package access applies. - 3application programming interface (API)In M256 this term refers to the predefined
Java packages. More generally, the services offered by a component may be referred to
as the component’s API. - 4behaviour (of an object)An object’s set of responsibilities
- 5class memberAn element of a class definition, such as an instance variable, method
or constructor. - 6cohesionA measure of how strongly related and focused the responsibilities of a
component are. High cohesion is considered desirable. - 7componentOn this course, unless indicated to the contrary, taken to mean an object oriented software component.
- 8component-based approachAn approach to software development based on the
philosophy of reusing existing components, and of structuring the software into
interacting components which may be reused. - 9component-based softwareSoftware created using a component-based approach.
- 10compositionReusing a class through an instance of the class being part of the state
of an object of a new class. - 11coordinating objectThe core system object through which the user interface
accesses the services of the core system. - 12couplingA measure of the extent to which a component is dependent on other
components. Low coupling is considered desirable. - 13copy constructorA constructor that returns a copy of its argument, i.e. a different
object of the same class with the same state. - 14data hidingProtecting an object’s implementation details by restricting access to
them - 15decompilerA tool that takes compiled Java files and derives the source code
- 16defensive copy (of an object)A distinct object with the same state as the original
- 17design for reuseProducing components as part of developing new software, or
specifically as marketable commodities. - 18design with reuseUsing existing components in creating a new piece of software
- 19efficiencyA measure of how well a system carries out its tasks
- 20encapsulationThe packaging together in an object of data and the operations that
can be applied to that data. - 21engineering componentsThe tangible artefacts designed and constructed by
engineers. - 22getter methodA method enabling clients to discover the value of an instance
variable. - 23immutable objectAn object whose state cannot be changed.
- 24implementation details (of a class)How the class is coded, including the code for its
methods and constructors, and the declaration of its instance variables. - 25incremental prototypingSuccessively modifying and augmenting a prototype until it
meets all the requirements. - 26incremental software developmentAn approach to software development where the
requirements of the software are partitioned and partitions developed separately. - 27integrity (of a package)The consistency of the states of the objects in the package
with any invariants on the objects. - 28integrity (of an object)The validity of an object’s state, that is, the consistency of the
values of its instance variables with any invariants on the object. - 29JAR fileA form of zip file used to distribute compiled Java code, documentation and
other information required for software to be used. - 30maintainabilityThe extent to which software is easily maintained.
- 31multiple releases (of software)Prototypes handed over to the client at various stages
of the software’s development. - 32mutable objectAn object whose state can be changed.
- 33object-oriented software componentOne or more classes grouped together in
some way to form a piece of software that has a well-defined purpose and that can be
combined with other pieces of software to construct a larger system. - 34packageA Java mechanism for grouping classes together to form an object-oriented
software component. - 35polymorphismThe capability for objects of different classes to respond to the same
message in a manner appropriate for each object. - 36portabilityA measure of how easily a system can run on different platforms.
- 37post-conditionWhat is achieved by invoking a method, if its pre-conditions are
satisfied. - 38pre-conditionA restriction on the circumstances under which a method may be
invoked. - 39privacy leakA situation where it may be possible for a client to access and improperly
manipulate the state of an object. - 40protocol (of a class)The specifications of the methods defined in a class, together
with the specifications of inherited methods, which define the corresponding messages
that its objects will respond to. - 41protocol (of a component)The combined protocols of the component’s classes,
defining how clients can interact with the component. - 42responsibility (of a component)The services that the component offers.
- 43responsibility (of an object)The tasks, or services, carried out by the object on
receipt of appropriate messages. - 44reusabilityA measure of the extent to which existing artefacts have been used during
the development of the software in question, and the extent to which the software itself
offers artefacts for reuse. - 45setter methodA method enabling clients to change the value of an instance variable
in a controlled way. - 46software componentA piece of software with a well-defined purpose that can be
combined with other pieces of software to construct a larger system. On this course,
unless the context indicates otherwise, the term is taken to mean object-oriented
software component - 47specification (of a method)A description of the purpose and usage of a method,
including its pre-conditions and post-conditions. - 48specification (of an engineering component)A description of the engineering
component’s interface, requirements and services. - 49specification (of an object-oriented software component)A description of how to
interact with the component, and of its requirements and services. - 50testabilityA measure of how easily a system can be tested.
- 51unnamed packageThe default Java package for a user-defined class
Información
- Descripción
- Java Software Development Fichas sobre Java Software Development Units 4-5, creado por nina.evangelou el 17/09/2013.
- Creado por
- nina.evangelou
- Visitas
- 100
- Etiquetas
- Valoración