Object Oriented Software Engineering   View all facts   Glossary   Help

subject > process

process
subject			fact

process	has definition Anything that operates for a period of time, normally consuming resources during that time and using them to create a useful result
	is a kind of subject
	see also process^2

Kinds of process :

• analysis (9 kinds, 2 facts)
• build (5 facts) - The process of compiling and integrating all the components of the software, incorporating any changes since the last build
• business process (4 facts) - A process performed by people in an organization
• casting (4 facts)
• compilation (1 kind, 3 facts) - The process of translating source code into code that is executable by a computer
• construction (4 facts) - A term often applied to the latter stages of design and to programming, even though the analogy with construction in other areas of engineering is weak
• contracting-out (3 facts) - Paying to have software (typically custom software) developed by some other organization
• cost estimation (1 kind, 7 facts) - The process of estimating the effort and elapsed time of an activity or project
• cost estimation technique (1 kind, 3 facts)
• defining the problem (4 facts) - A part of requirements and specification that involves narrowing down the scope of the system by determining the precise problem that needs solving
• deployment (6 facts) - The process of distributing and installing software as well as any other components of a system; deployment also includes managing the transition from any previous system, The process of distributing and installing the software and any other components of the system such as databases, special hardware etc. It also involves managing the transition from any previous system
• design (14 kinds, 13 facts) - The problem-solving process whose objective is to find and describe a way to implement the system's functional requirements, while respecting the constraints imposed by the non-functional requirements, and while adhering to general principles of good quality
• deterioration (3 facts) - The tendency of software to accumulate defects as time passes due to errors being made during maintenance
• development (5 kinds, 5 facts) (software engineering process) - A process used to develop software
• dynamic binding (8 facts) (late binding, virtual binding) - The process of binding a call to a particular method. This is performed dynamically at run-time due to the presence of polymorphism
• engineering (7 kinds, 5 facts) - The process of solving problems by applying, in a disciplined, systematic and ethical way, scientific and economic knowledge and principles to the design and maintenance of products or processes
• enumerating attributes (3 facts)
• evolution (4 facts) - The process by which software is modified over the course of its lifetime to meet changing requirements and as problems are fixed or reengineering is performed
• generalization^2 (4 facts) - The process of creating a relationship between a set of similar entities and another entity that contains the common aspects of those entities
• gold-plating (3 facts) - Building a list of requirements that does more than needed
• implementation (3 facts) - The process of converting a design into an executable software system by programming and related activities
• internationalization (3 facts) - The process of ensuring that a system can be easily adapted to different locales
• localization (3 facts) - The process of adapting a system to a particular locale
• maintenance (6 kinds, 4 facts) - In the context of software, any process involving modifying software following its general release to users
• modelling (4 kinds, 10 facts) - The process of creating a model
• obsolescence (3 facts) - The tendency for a technology to reach a state where it is no longer useful, is superseded by better technology or must be upgraded in order to continue to function correctly
• programming (5 facts)
• project management (1 kind, 7 facts) - All the activities needed to plan and execute a project.
• project scheduling (5 facts) - The process of deciding what sequence the various activities will be done, and when they should start and complete
• propagation (6 facts) - A mechanism whereby an operation in an aggregate is implemented by having the aggregate perform that operation on its parts - in other words, the operation is propagated to the parts
• quality assurance (14 facts) - The process of ensuring that the quality of a product or process is sufficient to meet the needs of the stakeholders
• requirements and specification (7 facts)
• requirements creep (6 facts) - The tendency for the set of requirements to relentlessly increase in size during the course of development, resulting in a system that is more expensive and complex than originally intended
• requirements elicitation (4 facts) - The process of actively asking stakeholders to describe their view of the requirements; an important aspect of requirements gathering
• requirements gathering (5 kinds, 4 facts) - A step in requirements analysis in which information is obtained that will form the basis of the requirements
• reviewing (1 kind, 3 facts) - The process of systematically proceeding through a software document to perform a function such as validation, or verification
• risk management (4 facts) - The process of evaluating risks and taking corrective action, including revising plans, on a regular basis
• scheduling (4 facts) - Determining the sequence of tasks, plus deciding when the tasks should start, and setting deadlines for when they must be complete
• serialization (4 facts) - A process in Java by which every object is converted by an ObjectOutputStream into a binary form for transmission, and then reconstructed when it is received by an ObjectInputStream
• software change (4 facts)
• software development (5 facts)
• software engineering (3 kinds, 23 facts) - The process of solving customers problems by the systematic development and evolution of large, high-quality software systems within cost, time and other constraints. The application of engineering to software systems of any kind, The systematic activities involved in the design, implementation and testing of software to optimize its production and support, (1) The application of a systematic, disciplined, quantifiable approach to the development, operation, maintenance of software; that is, the application of engineering to software. (2) The study of approaches as in (1)
• technique for prototyping class diagrams (4 facts)
• test-fix-test cycle (4 facts) - The cycle in which software developers repeatedly run tests, discover and fix defects, and then retest. This continues until quality objectives are met
• tracking (4 facts) - In the context of project management, he process of determining how well you are sticking to the cost estimate and schedule
• validation (3 facts) - The process of ensuring that requirements and designs solve the customer's problem
• verification (4 kinds, 3 facts) - The process of ensuring that the design or implementation conforms to the requirements; the process of ascertaining that the software has no defects