Kap 9 Introduktion till informatik

DevOps

An approach to managing IS projects that focuses on the collaboration between engineers from development and operations, not only during the development of a system, but throughout its entire life cycle.

Enterprise licence

A type of software licences that is usually negotiated and covers all users within an organisation. Also known as a "volume licence".

External acquisition

The process of purchasing an existing information system from an external organisation or vendor.

Human-computer interface (HCI)

The point of contact between an information system and its user.

Information systems planning

A formal process for identifying and assessing all possible information systems development projects of an organisation.

Intangible benefit

A benefit of using a particular system or technology that is difficult to quantify.

Intangible cost

A cost of using a particular system or technology that is difficult to quantify.

Joint application design (JAD)

A special type of group meeting in which all (or most) users meet with a systems analyst to jointly define and agree on system requirements or designs.

Making the business case

The process of identifying, quantifying, and presenting the value provided by an information system.

Net-present-value analysis

A type of cost-benefit analysis of the cash flow streams associated with an investment.

Non-capital expenditure

Money spent on repairs, supplies, payroll, and other operating expenses (the same as operational expenditure).

Open source software

Software for which the source code is freely available for use and/or modification.

Operational expenditure

Money spent on repairs, supplies, payroll, and other operating expenses.

Patch management system

An online system that utilises web services to automatically check for software updates, downloading and installing these "patches" as they are made available.

Perfective maintenance

Making enhancements to improve the processing performance or interface usability or adding desired but not necessarily required system features (in other words, "bells and whistles").

Adaptive maintenance

Making changes to an information system to make its functionality meet changing business needs to migrate it to a different operating environment.

Agile methodology

An evolutionary systems development approach that focuses on creating small, client-approved parts of the system as the project progresses rather than delivering one large application at the end of the project.

Alpha testing

Testing performed by the development organisation to assess whether the entire system meets the design requirements of the user.

Beta testing

Testing performed by actual system users with actual data in their work environment.

Break-even analysis

A type of cost-benefit analysis to identify at what point (if ever) tangible benefits equal tangible costs.

Capital expenditure

Money spent to acquire or improve a long-term asset such as a piece of equipment or a building.

Change request management

A formal process that ensures that any proposed system changes are documented, reviewed for potential risks, appropriately authorised, prioritised and carefully managed.

Click-wrap licence

A type of software licence primarily used for downloaded software that requires computer users to accept the licence terms by clicking a button before installing software.

Corrective maintenance

Making changes to an information system to repair flaws in its design, coding or implementation.

Cost-benefit analysis

Techniques that contrast the total expected tangible costs versus the tangible benefits of an investment.

Data flows

Data moving through an organisation or within an information system.

Developmental testing

Testing performed by programmers to ensure that each module of a new program is error free.

Discount rate

The rate of return used by an organisation to compute the present value of future cash flows.

Preventive maintenance

Making changes to a system to reduce the chance of future system failure.

Processing logic

The steps by which data are transformed or moved, as well as a description of the events that trigger these steps.

Productive paradox

The observation that productivity increases at a rate that is lower than expected when new technologies are introduced.

Project manager

The person most responsible for ensuring that a project is successfully completed.

Prototyping

An iterative systems development process in which requirements are converted into a working system that is continually revised through close interaction between analysts and users.

Proxy variable

An alternative measurement of outcomes; used when it is difficult to determine and measure direct effects.

Pseudocode

A way to express processing logic independent of the actual programming language being used.

Recurring cost

An ongoing cost that occurs throughout the life cycle of systems development, implementation, and maintenance.

Request for proposal (RFP)

A communication tool indicating buyer requirements for a proposed system and requesting information or soliciting bids for potential vendors.

Requirement collection

The process of gathering and organising information from users, managers, customers, business processes, and documents to understand how a proposed information system should function.

Shrink-wrap licence

A type of licences that is used primarily for consumer products; the contract is activated when the shrink wrap on the package has been removed.

Software asset management (SAM)

A set of activities performed to better manage an organisation's software infrastructure by helping to consolidate and standardise software titles, decide when to retire unused software, or decide when to upgrade or replace software.

Software bug

An error or flaw in a computer program or system that causes it to produce an incorrect or unexpected result or to behave in unintended ways.

System conversion

The process of decommissioning the current system and installing a new system in an organisation.

Systems analysis and design

The process of designing, building, and maintaining information systems.

Systems analyst

The primary person responsible for performing systems analysis and design activities.

Systems benchmarking

The use of standardised performance tests to compare different systems.

Systems development controls

Systems development processes and procedures used to ensure that necessary security features are implemented and enabled and that proper change management processes are followed.

Systems integration

Linking together different computing systems and software applications physically or functionally to act as a coordinated whole.

Systems maintenance

The process of systematically repairing and/or improving an information system.

Systems development life cycle (SDLC)

A model describing the life cycle of an information system from conception to retirement.

Systems planning and selection

The first phase of the systems development life cycle, in which potential projects are identified, selected, and planned.

Systems analysis

The second phase of the systems development life cycle, in which the current ways of doing business are studied and alternative replacement systems are proposed.

Systems design

The third phase of the systems development life cycle, in which details of the chosen approach are developed.

Systems implementation

The fourth phase of the systems development life cycle in which the information system is programmed, tested, installed, and supported.

Tangible benefits

A benefit of using a particular system or technology that is quantifiable.

Tangible cost

A cost of using a particular system or technology that is quantifiable.

Total cost of ownership (TCO)

The cost of owning and operating a system, including the total cost of acquisition, as well as all associated with its ongoing use and maintenance.

Total economic impact (TEI)

Method for assessing the costs and benefits of a system that takes into account impact on IT (i.e., project cost), the impact on the business (i.e., business benefits), future options created (i.e., future flexibility), as well as the associated risks or uncertainty associated with the new system.

Usability

A system's quality of being easy to use and aesthetically pleasing.

Volume licence

A type of software licences that is usually negotiated and covers all users within an organisation. Also known as an "enterprise licence".

Weighted multicriteria analysis

A method for deciding among different information systems investments or alternative designs for a given system in which requirements and constraints are weighted on the basis of their importance.