Chapter 17 Developing Software to Streamline Operations Flashcards
legacy system
conversion
software customization
off-the-shelf application software
A legacy system is an old system that is fast approaching or beyond the end of its useful life within an organization.
Conversion is the process of transferring information from a legacy system to a new system.
Software customization modifies software to meet specific user or business requirements.
Off-the-shelf application software supports general business processes and does not require any specific software customization to meet the organization’s needs.
SDLC and its associated 7 activities (PADDTIM)
The systems development life cycle (SDLC) is the overall process for developing information systems, from planning and analysis through implementation and maintenance. The SDLC is the foundation for all systems development methods, and hundreds of different activities are associated with each phase. These activities typically include determining budgets, gathering system requirements, and writing detailed user documentation.
Planning
Analysis
Design
Development
Testing
Implementation
Maintenance
6 different forms of system testing (ADISUU)
Alpha testing: Assess if the entire system meets the design requirements of the users.
Development testing: test the system to ensure it’s bug-free
Integration testing: verify that separate systems can work together, passing data back and forth correctly.
System testing: Verify that the units or pieces of code function correctly when integrated.
User Acceptance Testing (UAT): Determine if the system satisfies the user and business requirements.
Unit testing: Test individual units or pieces of code for a system.
4 Methods of implementation (PPPP)
Parallel Implementation: Uses both the legacy system(an old system that is fast approaching or beyond the end of its useful life within an organization) and new system until all users verify that the new system functions correctly.
Plunge(浸す、突っ込める) Implementation: Discards the legacy system and immediately migrates all users to the new system.
Pilot Implementations: Assigns a small group of people to use the new system until it is verified that it works correctly; then the remaining users migrate to the new system.
Phased Implementation: Installs the new system in phases (for example, by department) until it is verified that it workds correctly.