A

Access Level

- Defines the state of a variable, class, module, or structure, whether they can be
accessed publicly, privately, or with any other type of restrictions.

Assembly

- Logical unit of code

Application architect

- Has a lot of synonyms title in the industry, but the most commonly used ones are
solution architect and enterprise architect.

Agile

- SDLC methodology combines the iterative and incremental framework to create a

high quality system.

Agile Manifesto

- Most realistic approach in SDLC methodology.

B
ByVal

- Passing of variables by value; these elements will be protected from any changes
made in the calling class or method.

ByRef

- Passing of variables by reference; the changes you made to those variables in the
class or in the method will also reflect to the ones in the modules or in the
procedures.

Baseline

- Set of mark points that indicate that a step in program development process is
already done.
Business Management

- Planning, organizing, allocating, and controlling resources to achieve the expected

goal.

Background questionnaire

- Type of questionnaire that will help the proponents in making the system better by
suiting it to the common needs of a particular group of users.

Baseline checklist

- Includes all the necessary things the your team must do in every phase and not in
every loop of it.

C
Call

- The keyword you can use when you want to apply the procedure stored in a
module or in a class to another container like a class itself.

CDbl

- Forces conversion of whole numbers or currency to a double precision point.

Class

- Individual part of a program that serves as a template for objects.

Cint

- Data type that checks if the input is an integer.

Code view/Code editor

- The window where you write most of the code

Control

- Object added in a form

Control Structure

- Used to direct the programs flow for it is involve in every decision that an
application must do.

Control Module

- The head module

Control Couple

- Arrow with shaded circle.

Coupling

- Refers to how closely related two modules are.

Critical Design Review

- The second type of review which evaluates and judge whether the prototype
system achieved the planned design and standards.

Client Side

- Generally the company that needs a particular system to be created.

Contextual Interview

- Best method to use in the beta system is an improved version of the system the
target users are already familiar using with.

Code Comment

- Refers to the description of each part or module of the program and its main
purpose is to help maintaining and checking the whole system.

D
Design View

- Allows you to add text and elements and then position to size them and set there
properties using special menus or the properties window.
Dim

- Used to declare variables and allocate memory for them

Definite

- Term used to describe when you know how many times the procedure will
execute.

Data Couple

- Arrow with empty circle.

Developers

- The people who are task to plan and develop a program.

Design Reviews

- Are conducted to see if the current system developments standings are in

accordance with the design objectives.

Design Document

- The collection of all the things to be discussed in the review meeting, the
presentation of a particular review should refer to this document.

Developer

- One who writes the code

E
Encapsulation

- The process of putting data, methods, properties together in a single class.

Event

- Something that happens in your programs GUI when a mouse function is

performed in a control.
Entity

- The term used to represent an employee or a person involved in the project

development.

Evolutionary Prototyping

- Involves the analysis of the minimal requirements and creating a prototype from it.

Extensible Markup Language

- Used ti document structured content like executable codes written in various

programming languages.

F
Function

- Used when you want the procedure to return a value to the calling code

For Loop

- Utilized when you know both the starting point and end point of the loop.

First Click Testing

- Technique used to determine if the first navigation link that will lead to the
completion of a particular task on the system can be found easily.
 G

H
Hierarchical Program Organization

- One of the best charts to use when implementing structured programming since
both focuses on group or codes or modules.

I
If-then

- Provides an action if the condition is met

If-then-else

- Statement that enables you to execute another course of action when the
condition is true or false.

Indefinite

- Term used to describe when the number of times the procedure will execute
depends on other things like a user input.

Infinite Loop

- Term for a loop that never finishes

Iterative

- Gives permission on repeating the cycle continually until the desired look, feel and
functionality of the system is achieved.
Interface Control Document

- States information about the relationship of the target users to the systems
interface, the system to the hardware device and/ or the program module to
another module.

L
Logical Structure

- Pertains to a step-by-step execution to a program.

Loops

- Used to repeat a task again and again as long as the condition is met.

Loop Control Variable

- Value provided that will control how many times the loop will repeat.

Library Module

- Module that can be use by any control module

Lead Developer

- Similar to a developer; also writes the code

 M
Menu Bar

- Contains the name of the menus that can be used in constructing the application.

Modifiers

- Defines the access level of a declared element, like class.

Module

- Is a separate code or part of a program that stores different functionality that can
Be executed when needed.

Microsoft Visio

- Used in creating accurate graphical representation.

N
Namespace

- The logical grouping of a systems related components

Naming Conventions

- Pertains to a uniform way of naming each element, object, etc. in the environment.

0
 P
Parameter

- Signifies how we want an argument to be passed to a procedure.

Properties window

- Shows the properties of a selected object or control

Preliminary Design Review

- The first of the four types of design review that evaluates If the planned design
and standards are feasible and achievable within the given time frame and
resources.

Production Readiness Review

- Evaluates the program, the user’s manual, and all other documents are complete,
thus giving signal that the system is ready for production, marketing, and
implementing.

Project Development Process

- The process pertains to the overall creation, delivering, marketing and any other
procedure which involves finishing a project or achieving that projects goal.

Persona

- Represents a set of people with almost the same qualities.

Q
Quantitative Findings

- Collection of measurable and objective scores.

Qualitative Findings
 - The collection based on the subjective ratings that usually relies on description
rather than numbers.

S
Solution Explorer Window

- List of all the files and objects associated with current project.

Structure

- This element is like class that defines a value type.

Sub-procedure

- Used by programmers when they don’t want the procedure itself to pass an output
or value to the class that calls it.

Sequential Structure

- Easiest type of control structure because it does not involve decision- making; the
programs flow depends on the step-by-step execution of it. First line first, then
proceed to the second is the mechanism of the structure.

Spaghetti Code

- Code created in unstructured way.

Subordinate Module

- Module that is connected to a control module.

Subject Matter Expert

- Usually consisting of direct users of the system, clients and representative

individual of a client company.
System Analyst

- Also referred to as functional analyst that connects the gap between application
architect and SME.

Software Tester

- Finds and debugs errors of the system.

Spiral

- Combination iterative and linear framework types, it means that this model makes
use the flexibility of prototyping model and the orderly mannered sequence of
waterfall.

Scrum

- Dubbed as the most popular agile approach due to its easy-to-understand

concept.

Sprint

- The combination of the program development process in every loop of the

software development life cycle and it usually last from two weeks to a month.

System Documentation

- Is done when all the deliverables are ready, but that approach is risky and might
require someone to go back again to each phases of the program development to
document all the details properly.

Software Document

- Includes code comment and technical documents.

Scope Statement

- Helps in identifying what is in and out for the overall system or specific sections of
it and aids in preventing scope creep.

Scope Creep

- The result of the costumers or clients late realization of some requirements.

 T
Title Bar

- Located at the top most edge containing the window name.

Toolbox

- Consist of controls, containers, report controls, and all the other essential objects
in creating a forms interface.

Top-Down Design

- Process of dividing modules into small parts.

Test Readiness review

- The third type of design review that evaluates the prototype programs capability
for testing procedures.

Test Technique

- Defined way of executing the program and finding errors along the way.

Test Plan

- Contains the important details on how the usability test will be conducted.

Task Completion Time

- Refers to the average time the set of respondents was able to finish a task-
scenario.

Task Success Rate

- Refers to the number and percentage of respondents who complete the scenario
on their first try.

Task Failure Rate

- Refers to the percentage of the respondents who encountered problems and

confusion while doing the given task that hinders them to accomplish it.
Task Repetition Frequency

- Refers to the percentage of respondents who went back to the starting point of
previous step to accomplish the indicated task-scenario.

Throwaway Prototyping

- Type of prototyping involves creating a considerable weak prototype from a

minimal list of requirements.

U
Unified Modeling Language

- The most implemented language for describing and modeling systems design and
architecture that is commonly connected to software engineering.

Usability Questionnaire

- Type of questionnaire where the respondents answer the question that are related
to their experiences about the task scenarios and the overall look of the beta
system itself.

V
Vb.Net

- OOP language from Microsoft that first appeared in 2002.

X
Y