MBA 703-Ch 10 (ISBB)

Help system.

A help system gives detailed documentation regarding the programming language.

1) Preliminary Analysis

A request for a replacement or new system is first reviewed

Editor

An editor is used for writing the program. Commands are automatically color coded by the IDE to identify command types. For example, a programming comment might appear in green and a programming statement might appear in black

Cutover

Cutover involves switching from the old system to the new software. Timing of the cutover phase is crucial and is usually done when there is low activity.

Debugging tool

Debugging assists the developer in locating errors and finding solutions.

Object- oriented programming language

Designed so that the programmer defines "objects" that can take certain actions based on input from the user. In other words, a procedural program focuses on the sequence of activities to be performed while an object oriented program focuses on the different items being manipulated

Procedural Programming Language

Designed to allow a programmer to define a specific starting point for the program and then execute sequentially. (all early programming languages worked this way)

Systems Development Life Cycle (SDLC)

Developed in the 1960s to manage the large software projects associated with corporate systems running on mainframes. designed to manage large projects that include multiple programmers and systems that have a large impact on the organization. It requires a clear, upfront understanding of what the software is supposed to do and is not amenable to design changes.

Construction

In the construction phase the application developers, working with the users, build the next version of the system through an interactive process. Changes can be made as developers work on the program

Testing

In the testing phase the software program developed in the programming phase is put through a series of structured tests. The first is a unit test, which evaluates individual parts of the code for errors or bugs. This is followed by a system test in which the different components of the system are tested to ensure that they work together properly. Finally, the user acceptance test allows those that will be using the software to test the system to ensure that it meets their standards. Any bugs, errors, or problems found during testing are resolved and then the software is tested again.

User Design

In the user design phase representatives of the users work with the system analysts, designers, and programmers to interactively create the design of the system. A Joint Application Development (JAD) session brings all of the stakeholders for a structured discussion about the design of the system

System Analysis

In this phase one or more system analysts work with different stakeholder groups to determine the specific requirements for the new system. No programming is done in this step. Instead, procedures are documented, key players/users are interviewed, and data requirements are developed in order to get an overall impression of exactly what the system is supposed to do

Requirements planning

In this phase the overall requirements for the system are defined, a team is identified, and feasibility is determined.

System Design

In this phase, a designer takes the system requirements document created in the previous phase and develops the specific technical details required for the system. It is in this phase that the business requirements are

Lean Methodology

Lean focuses on taking an initial idea and developing a Minimum Viable Product (MVP)

Implementation

Once the new system is developed and tested, it has to be implemented in the organization. This phase includes training the users, providing documentation, and data conversion from the previous system to the new system.

Programming

Programming is the the process of creating a set of logical instructions for a digital device to follow using a programming language. Software is created via programming.

Minimum Viable Product (MVP)

The MVP is a working software application with just enough functionality to demonstrate the idea behind the project. Once the MVP is developed, the development team gives it to potential users for review. Feedback on the MVP is generated in two forms. First, direct observation and discussion with the users and second, usage statistics gathered from the software itself.

Programming

The code finally gets written in the programming phase. Using the system design document as a guide, programmers develop the software.

Compiler/Interpreter

The compiler/interpreter converts the programmer's source code into machine language so it can be executed/run on the computer.

Maintenance

This final phase takes place once the implementation phase is complete. In the maintenance phase the system has a structured support process in place. Reported bugs are fixed and requests for new features are evaluated and implemented. Also, system updates and backups of the software are made for each new version of the program

Computer Aided Software Engineering (CASE)

This tool allow a designer to develop software with little or no programming. Instead, the CASE tool writes the code for the designer. CASE tools come in many varieties. Their goal is to generate quality code based on input created by the designer.

Check-in/check-out mechanism

This tool allows teams of programmers to work simultaneously on a program without overwriting another programmer's code.

Agile and Iterative Development

You should notice how the building blocks of the developing system move from left to right, a block at a time, not the entire project. Blocks that are not acceptable are returned through feedback and the developers make the needed modifications.

Fourth Generation Languages

a class of programming tools that enable fast application development using intuitive interfaces and environments. Many times, a fourth-generation language has a very specific purpose, such as database interaction or report-writing. These tools can be used by those with very little formal training in programming and allow for the quick development of applications and/or functionality. Examples of fourth-generation languages include: Clipper, FOCUS, SQL, and SPSS.

Agile methodologies

a group of methodologies that utilize incremental changes with a focus on quality and attention to detail. Each increment is released in a specified period of time (called a time box), creating a regular release schedule with very specific objectives.

Third Generation Languages

are not specific to the type of hardware on which they run and are similar to spoken languages. Most third-generation languages must be compiled. The developer writes the program in a form known generically as source code, then the compiler converts the source code into machine code, producing an executable file. Well known third-generation languages include BASIC, C, Python, and Java.

Rapid Application Development (RAD)

focuses on quickly building a working model of the software, getting feedback from users, and then using that feedback to update the working model. After several iterations of development, a final version is developed and implemented.

Second Generation Languages aka Assembly Language

uses English-like phrases rather than machine-code instructions, making it easier to program. An assembly language program must be run through an assembler, which converts it into machine code.

First Generation Languages

were called because machine code programming was done in the format the machine/computer could read. So programming was done by directly setting actual ones and zeroes (the bits) in the program using binary code

The Systems Development Life Cycle's phases

1) Preliminary Analysis 2) System Analysis 3) System Design 4) Programming 5) Testing 6) Implementation 7) Maintenance

RAD methodology consists of four phases:

1) Requirements Planning 2) User Design 3) Construction 4) Cutover