AppDev PRELIMS

Emerging technologies

New technologies that are currently developing or will be developed over the next five to ten years, and which will substantially alter the business and social environment.

Radical novelty

A characteristic of emerging technology where it fulfills a given function by using a different basic principle as compared to what previous technology used, or by putting existing technology to a new use.

Relatively fast growth

A characteristic of emerging technology that shows relatively fast growth rates across dimensions like funding, knowledge outputs, and actors involved compared to non-emerging technologies.

Coherence

A characteristic of emerging technology referring to the internal characteristics of a group being united, having logical interconnection, and persisting over time.

Prominent impact

A characteristic of emerging technology where it provides benefits for a wide range of sectors, transforms an industry, and exerts much enhanced economic influence.

Uncertainty and ambiguity

A characteristic of emerging technology arising because proposed applications are still malleable and the knowledge of possible outcomes is incomplete.

Augmented Reality (AR)

The technology that overlays computer-generated display, sound, text, and effects on a user's view of the real world, combining real and computer-based scenes.

Artificial Intelligence (AI)

The simulation of human intelligence processes, including learning, reasoning, and self-correction, by machines.

Machine learning

An application of AI that provides a machine with the ability to learn from experience like humans.

Quantum Computers

Computers that use quantum mechanics and qubits to perform calculations and solve some problems far more efficiently than a conventional computer.

Qubit

The basic unit of computation in quantum computers that is in a quantum superposition between two states, able to be a 0 and a 1 at the same time.

Industrial revolution

The systematic transformation of manufacturing through the integration of physical and digital systems to improve quality, lower costs, and increase efficiency.

First Industrial Revolution (Industry 1.0)

Began in the 18th century; the introduction of mechanical production using hydroelectric and steam-powered equipment.

Second Industrial Revolution (Industry 2.0)

Began in the 19th century; introduced new technological systems that use electricity, allowing for greater production and more sophisticated machines.

Third Industrial Revolution (Industry 3.0)

Began with the first computer era; evolved the use of electronics and information technology (IT) to automate a production process further.

Fourth Industrial Revolution (Industry 4.0)

The current and developing environment featuring disruptive and cutting-edge technologies such as IoT, robotics, VR, AR, and AI.

Big Data Analytics

The process of collecting, organizing, and analyzing large sets of data from different resources to discover patterns and support real-time decision-making.

Internet of Things (IoT)

A computing concept that describes the idea of everyday physical objects being connected to the Internet and being able to communicate and interact with other devices.

Cloud Computing

The general term for anything that involves delivering hosted services over the Internet.[cite: 12]

Systems development (or applications development)

A systematic process of defining, designing, testing, and implementing a new application.[cite: 12]

Requirements determination

The process of converting high-level user requirements into a list of detailed requirements that can be used as inputs for creating models.[cite: 12]

Requirement

A statement of what the system must perform or what characteristic it must have.[cite: 12]

Functional requirements

Requirements that are directly related to the process a system has to perform or data it needs to contain.[cite: 12]

Non-functional requirements

Requirements that pertain to behavioral properties that a system must have, defining how a system or software is supposed to be.[cite: 12]

Operational requirements

Specify the operating environment(s) in which the system must perform, as well as how these might change over time.[cite: 12]

Performance requirements

Deal with issues related to performance such as response time, capacity, and reliability of the system.[cite: 12]

Security requirements

Address issues with security, such as who has access to the system's data and the ability to protect data from disruption or data loss.[cite: 12]

Cultural and political requirements

Deal with issues related to cultural and political factors and legal requirements that affect the system.[cite: 12]

Requirements definition report

A documentation that lists the functional and non-functional requirements of a system in an outline format and defines the scope of the system or software.[cite: 12]

Requirements gathering (requirements elicitation)

The process of cooperating with clients or users to determine what requirements are needed.[cite: 12]

Interviews

The most commonly used requirement-gathering technique comprising interviewers and interviewees.[cite: 12]

Close-ended questions

Interview questions that require a specific answer, used when an analyst is looking for specific information.[cite: 12]

Open-ended questions

Interview questions that require the interviewee to answer in open text format, designed to gather rich information.[cite: 12]

Probing questions

Interview questions that follow up on what has just been discussed to learn more, encouraging the interviewee to expand on a previous response.[cite: 12]

Joint Application Development (JAD)

An information-gathering technique that allows the project team, users, and management to work together to identify requirements for the system under the direction of a facilitator.[cite: 12]

JAD Facilitator

A person who sets the meeting agenda and guides the JAD discussion but does not join in the discussion as a participant.[cite: 12]

Scribes

People who assist the JAD facilitator by recording notes, making copies, and so on.[cite: 12]

Questionnaires

A set of written questions used to obtain information from individuals, often used when there is a large number of people from whom information and opinions are needed.[cite: 12]

Sample

A subset of the population chosen to represent the population under study, particularly when selecting participants for questionnaires.[cite: 12]

Document Analysis

A form of qualitative research in which existing organizational documents are analyzed and interpreted by researchers to understand the current (as-is) system.[cite: 12]

Observation

The act of watching processes being performed; a powerful tool for gathering information about the as-is system by seeing the reality of a situation.[cite: 12]

Requirements analysis

The process where gathered requirements are analyzed to ensure that those requirements are actually required to solve conflicts affecting the system's design and development.[cite: 12]

Necessary

A characteristic of a good requirement meaning the requirement is really needed or specifies an essential factor on the system.[cite: 12]

Unambiguous

A characteristic of a good requirement meaning it is stated so that it should only be interpreted in one way (specific and easy to understand).[cite: 12]

Consistent

A characteristic of a good requirement meaning it should not have conflicts or overlaps with other requirements.[cite: 12]

Complete

A characteristic of a good requirement meaning it completely describes the necessary functionality that will result to meet the user's need.[cite: 12]

Singular

A characteristic of a good requirement meaning the statement includes only one requirement with no use of conjunctions like "and," "or," and "but."[cite: 12]

Feasible

A characteristic of a good requirement meaning it is achievable within system constraints such as time, cost, legal, and available resources.[cite: 12]

Verifiable

A characteristic of a good requirement meaning the implemented system can be tested (by analysis, inspection, or test cases) to prove the requirement has been met.[cite: 12]

Traceable

A characteristic of a good requirement meaning it has a unique identifier to trace all changes to it throughout the development life cycle.[cite: 12]

Checklist

A list of questions which the analyst will use to assess each requirement during requirements analysis.[cite: 12]

Unified modeling language (UML)

A visual modeling language that provides a visual means of developing and documenting object-oriented software and systems.[cite: 12]

Use-case diagram

A UML diagram whose purpose is to summarize and demonstrate the details of functional requirements and how they are used by different users.[cite: 12]

Actor

A person or a system that represents the role of someone interacting with the system or software.[cite: 12]

Primary actors

Actors that initiate interaction with the system or software.[cite: 12]

Secondary actors

Actors that are called upon by the system for support when the primary actor initiates an interaction with a use-case.[cite: 12]

Use-case

Represents the functionality of a system, initiated by an actor, and labeled with a descriptive verb-noun phrase.[cite: 12]

Subject boundary box

Represents the system's scope of which a set of use-cases are applied, separating use-cases from actors.[cite: 12]

Association relationship

A line between an actor and a use-case specifying that the actor interacts with the system and uses a certain functionality.[cite: 12]

Include relationship

A directed relationship representing the required use of functionality of one use-case by another in order to perform its task.[cite: 12]

Extend relationship

Indicates optional functionality under a certain base use-case, containing optional behavior.[cite: 12]

Generalization relationship

Represents a specialized child use-case that inherits properties and behavior of a more generalized parent use-case and may override its behavior.[cite: 12]