Upgrade to remove ads
ISBB Chapter 10 - Information Systems Development
Terms in this set (16)
A group of methodologies that utilize incremental changes with a focus on quality and attention to detail.
Build vs. Buy Decision
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.
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.
Refers to systems in which nonprogrammers can create working applications.
Implementation Methodology - Direct Cutover
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 - Parallel Operation
The old and new system are used simultaneously for a limited period of time.
Implementation Methodology - Phased Implementation
Different functions of the new application are implemented in phases, adding functionality as the phases are implemented.
Implementation Methodology - Pilot Implementation
A subset of the organization starts using the new system before the rest of the organization.
Join Application Development
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.
A methodology that focuses on taking an initial idea and developing a minimum viable product (MVP).
Making changes, corrections and improvement to a system already in use by a company.
Minimum Viable Product
A working software application with just enough functionality to demonstrate the idea behind the project.
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.
Rapid Application Development
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.
Systems Development Life Cycle
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.
When companies have the options to license functions provided by other companies instead of writing the code themselves.
YOU MIGHT ALSO LIKE...
Computer Essentials Chapter 13
Info Tech Ch. 12
Chapter 12: Building Info Systems
OTHER SETS BY THIS CREATOR
Real Estate Appraisal: Chapter 10 Income Approach…
TOM 301 Definitions
TOM 301 FINAL