Chapter 7: Systems Development Flashcards
A group of methodologies that utilize incremental changes with a focus on quality and attention to detail.
Agile Methodologies
When an organization decides that a new software program needs to be developed, they must determine if it makes more sense to build it themselves or to purchase it from an outside company.
Build vs. Buy Decision
As new systems are brought online and old systems are phased out, it becomes important to manage the way change is implemented in the organization.
Change Management
Refers to systems in which nonprogrammers can create working applications.
End-User Computing
The old and new system are used simultaneously for a limited period of time.
Implementation Methodology – Parallel Operation
The organization selects a particular date that the old system is not going to be used. On that date, the old system is turned off and the new one is operational.
Implementation Methodology – Direct Cutover
Different functions of the new application are implemented in phases, adding functionality as the phases are implemented.
Implementation Methodology – Phased Implementation
subset of the organization starts using the new system before the rest of the organization.
Implementation Methodology – Pilot Implementation
A methodology that involves the client or end user in the design and development of an application, through a succession of collaborative workshops called JAD sessions.
Joint Application Development
A methodology that focuses on taking an initial idea and developing a minimum viable product (MVP).
Lean Methodology
Making changes, corrections and improvement to a system already in use by a company.
Maintenance
A working software application with just enough functionality to demonstrate the idea behind the project.
Minimum Viable Product (MVP)
A model that illustrates the constraints of project management: time,cost, and quality. A manager cannot change one of the constraints without impacting the others.
Quality Triangle
A development methodology that focuses on quickly building a working model of the software, getting feedback from users, and then using that feedback to update the working model.
Rapid Application Development:
This methodology developed in the 1960s to manage the large software projects associated with corporate systems running on mainframes. Phases are Preliminary Analysis, Systems Analysis, Systems Design, Programming, Testing, Implementation and Maintenance.
Systems Development Life Cycle