SDLC Phases
Development Methodologies
Programming Languages
Build vs Buy
System Implementation
100

The first phase where feasibility and project possibilities are analyzed.

Preliminary Analysis

100

This methodology was first developed in the 1960s to manage large software projects associated with corporate systems running on mainframes.

systems-development life cycle (SDLC)

100

The first generation programming language written in binary.

Machine Code

100

The decision between developing software internally or purchasing it.

Build vs Buy

100

This implementation methodology selects a particular date to stop using the old system entirely. 

Direct Cutover

200

The result of the system analysis phase, this specific document details exactly what the system is supposed to do.

system-requirements document

200

This methodology focuses on quickly building a working model of the software, getting feedback from users, and then updating the model.

RAD (Rapid Application Development)

200

This generation of language is called machine code and is programmed by directly setting actual ones and zeroes.

first-generation

200

The challenge when modifying purchased software during updates.

Customization Management

200

During this final phase, IT management must ensure the system continues to stay aligned with business priorities and runs well.

maintenance phase

300

In the testing phase, this specific type of test checks individual parts of the code for errors or bugs.

unit test

300

Based on a 2001 "Manifesto," these methodologies utilize small cross-functional teams and daily status meetings.

agile methodologies

300

This runtime program must be installed to interpret and run Java code on different types of operating systems.

Java Virtual Machine (JVM)

300

When departments outside of the IT department develop their own specific applications, it is referred to by this term.

end-user computing (or end-user development)

300

This implementation methodology is the least risky but by far the most expensive because work is duplicated

Parallel Operation

400

A key part of the preliminary analysis step is this type of analysis, which evaluates technical, economic, and legal factors.

feasibility analysis

400

In the lean methodology, this is a working software application with just enough functionality to demonstrate the idea behind the project. 


minimum viable product (MVP)

400

This type of programming language is designed to allow a programmer to define a specific starting point for the program and then execute sequentially.

procedural programming language

400

This person's role is to make various purchased systems and the existing systems at the organization work together.

Systems Integrator

400

In this implementation approach, different functions of the new application are used as functions from the old system are turned off.

Phased Implementation