GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Kostenlos registrieren

Karteikarten

Java Software Development  Unit 1

nina.evangelou Java Software Development Englisch 79 Karten

Karten in diesem Stapel (79)

  1. 1abstractionA description that focuses on the essential features of a problem and
    ignores other details.
  2. 2activation rectangleAn element in a sequence diagram that represents a period
    during which a particular object is active.
  3. 3adaptive methodA method of software development which embraces change by
    building space for it into the schedule.
  4. 4analysisIn this context, analysis involves analysing the specified requirements and
    expressing, in computing terms, what the software system should do.
  5. 5applicationA program that performs a specific function directly for the user and, in
    effect, turns the computer intoaspecialised computer, such as a word processor or web
    browser.
  6. 6behaviour (of a software system)The set of tasks the system performs.
  7. 7CASE (computer-aided software engineering) toolA software tool used to help in
    some aspect of software development.
  8. 8classA template that serves to describe all instances (objects) of that class. It defines
    the type of data held by the objects and the object’s operations
  9. 9clientThis term has two main meanings in the context of software development: (i) the
    object in a collaboration which requests a service: (ii) the person(s) commissioning the
    software.
  10. 10code-based testing toolA testing tool that automatically analyses code and
    produces test cases
  11. 11coding toolA CASE tool that aids writing or running code
  12. 12collaborationOne object requesting a service from another object.
  13. 13collaboratorA participant in a collaboration.
  14. 14core systemThe part of the system that is distinct from the user interface and that
    usually contains objects corresponding to real-world entities
  15. 15designDeciding how the system will meet the specified requirements
  16. 16design toolA CASE tool that aids some aspect of design
  17. 17designerA developer whose role is to work on the design stages of a project
  18. 18detailed design and implementationDeciding which existing classes can be reused
    and what programming constructs are appropriate as well as writing the actual code.
  19. 19developing a conceptual modelAnalysing the requirements to determine the classes
    and connections between them that appropriately model the key concepts in the real world area the system is being written for.
  20. 20developing a user interfaceDesigning the user interface and determining how it will
    communicate with the core system.
  21. 21developing dynamic modelsDesigning and comparing models of the interactions
    among objects which will achieve the tasks required of the system.
  22. 22doc formA form of Java comment marked by /**at the beginning and */ at the end.
  23. 23dynamic modelAn illustration of events occurring in a system over time
  24. 24identifierA label that is used to refer to an object in a system.
  25. 25implementationTranslating a design into program code.
  26. 26in-house standardsA company’s specified standards to which its software must
    adhere
  27. 27integrated development environment (IDE)A software tool which facilitates many of
    the tasks associated with writing and running programs in a specific language.
  28. 28call or invoke (a method)To execute a method’s code.
  29. 29iterationOne cycle through the phases involved in an iterative method.
  30. 30iterative methodAn adaptive method of software development in which phases are
    repeated iteratively in a systematic manner.
  31. 31Java applicationA program run directly by the Java Virtual Machine.
  32. 32JavadocA software tool which extracts doc comments from a Java program and from
    them provides a description of elements of the program, such as methods, output in the
    form of an HTML file.
  33. 33JUnitA software tool that assists with testing Java classes.
  34. 34large-scale projectA project in which the amount and complexity of detail involved
    cannot readily be handled by one or two people, so that the project is best carried out
    by a team of people, with different individuals working on different aspects of the
    project.
  35. 35lifelineAn element in a sequence diagram that represents the time during which an
    object exists.
  36. 36linkA connection between two objects.
  37. 37maintenanceThe phase of software development associated with keeping the system
    working to the satisfaction of its users.
  38. 38messageA request by one object for another object to provide a service.
  39. 39modelling languageA specification of how models should be constructed so that
    their meaning is unambiguous.
  40. 40objectA collection of data and a set of operations that can be applied to the data.
  41. 41object diagramAn illustration of objects and the links between them.
  42. 42Object Management Group (OMG)A consortium of computing companies which
    sets standards across the software industry, including the UML standards
  43. 43phaseA stage of software development.
  44. 44predictive methodA method of software development which is largely based on the
    waterfall method and which therefore benefits from simplicity of planning, and
    predictability.
  45. 45program documentationComments and explanations designed to assist someone in
    understanding the implementation of software, what it does and how to use it.
  46. 46programmerA developer whose role is to implement the code.
  47. 47project documentationA written description of the activities, decisions and
    outcomes of a project’s phases.
  48. 48project failureA situation where a project fails to deliver the client’s requirements in
    some way (e.g. in terms of cost, development time, or functionality).
  49. 49project managerA person who plans and oversees the running of a software
    development project.
  50. 50project managerA person who plans and oversees the running of a software
    development project.
  51. 51prototypeAn early working version of a system or part of it
  52. 52requirementsWhat is required of the system.
  53. 53requirements analystSomeone usually involved in the early stages of a project who
    elicits and analyses the requirements of a proposed system. They may also become
    involved in preliminary aspects of design.
  54. 54requirements specificationEliciting and analysing what the client wants in order to
    produce a detailed and complete specification of the tasks required (i.e. the required
    functionality) of the system.
  55. 55reviewA point within an iterative software development method where developers and
    clients can take changes into account.
  56. 56sequence diagramAn illustration of objects collaborating to carry out a particular
    task.
  57. 57serverThe object in a collaboration that provides a service.
  58. 58software developerAn umbrella title, referring to someone who takes on one or more
    of a range of jobs within software development.
  59. 59software developmentt A planned, phased process, involving modelling different
    aspects of the software as well as implementing, testing and maintaining it.
  60. 60software development methodA particular set of development phases applied in a
    particular order.
  61. 61software engineeringA term used to refer to a wide range of concerns connected
    with carrying out systematic software development.
  62. 62software modelAn illustration or description of the software, or of part of it, which
    emphasises certain aspects and omits others.
  63. 63software systemA program which is large in the sense that it carries out a number of
    tasks, some of which may be complex.
  64. 64software testerA developer whose role is to test the software as it is being
    developed.
  65. 65state (of a system)The objects, their attribute values and the links between them,
    which constitute the system at a particular time
  66. 66state (of an object)The value of the object’s attributes.
  67. 67static modelAn illustration of the state of the system, or part of it, at a particular time.
  68. 68strict UML diagramA diagram that adheres strictly to the UML standard.
  69. 69system codeThe source code which, when run, generates the system
  70. 70systems analystA developer who is a technical expert in software systems and
    whose role is to analyse the feasibility of a proposed system and how it will impact on the
    client’s business practices.
  71. 71target languageThe language in which the planned software is to be implemented
  72. 72technical writerer A developer whose role is to develop user documentation.
  73. 73test driver toolA testing tool that executes the software being tested with specified
    inputs.
  74. 74testingThe activities that take place at each phase of development to ensure that the
    phases of development are consistent and complete with respect each other, and also
    consistent and complete with respect to the requirements.
  75. 75testing toolA CASE tool that aids some aspect of testing.
  76. 76UML standardThe currently accepted specification of what is valid UML and how it
    should be used.
  77. 77UML-type diagramA diagram that varies in some small way from the strict UML
    standard.
  78. 78UML (Unified Modeling Language)A modelling language based on diagrams
  79. 79waterfall methodA traditional and idealised view of developing software by strictly
    following a sequence of phases.

Informationen

Beschreibung
Java Software Development Karteikarten am Java Software Development  Unit 1, erstellt von nina.evangelou am 17/09/2013.
Erstellt von
nina.evangelou
Aufrufe
168
Verlauf
  • Erstellt von nina.evangelou · 17 Sep 2013
  • Kopiert von nina.evangelou · 17 Sep 2013
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck