Information Systems Acquisition, Development & Implementation Flashcards

What is the first phase in system development life cycle (SDLC)?

Answer: Planning

The System Development Life Cycle (SDLC) typically begins with the planning phase, which is the foundational step for any project. This initial stage involves defining the project scope, objectives, feasibility, and resource requirements, as well as identifying stakeholders. It sets the direction for the entire development process, ensuring alignment with business goals before any design or coding begins.

Why is requirements gathering important?

Answer: To define system features and functions

Requirements gathering is a critical early step in system development where stakeholders' needs and expectations are collected and documented. This process clearly defines what the system must do, its functionalities, performance criteria, and user interface specifications. Accurate and comprehensive requirements are essential to ensure the developed system meets business objectives and user needs, preventing costly rework later.

Which testing type checks if the system meets specified requirements?

Answer: Acceptance testing

Acceptance testing is a formal testing process conducted to verify that a system meets the specified business requirements and is ready for deployment. It is typically performed by end-users or clients to ensure the system functions as expected in a real-world scenario and satisfies their operational needs. This type of testing confirms that the system is acceptable for operational use.

Why is documentation important in development?

Answer: It provides clear guidance and records

Documentation in system development is vital because it provides a clear, comprehensive record of the system's design, functionality, and operation. It serves as an essential reference for developers, users, and auditors, facilitating understanding, maintenance, future enhancements, and troubleshooting. Good documentation ensures knowledge transfer, reduces reliance on individual memory, and supports long-term system sustainability.

What is a key goal during system implementation?

Answer: Deploy system and train users

During the system implementation phase, a key goal is to successfully deploy the new system into the production environment, making it operational. Equally important is providing comprehensive training to end-users to ensure they can effectively operate and utilize the new system. This combination ensures a smooth transition, promotes user adoption, and maximizes the system's benefits.

Which methodology promotes iterative and collaborative development?

Answer: Agile

Agile methodology is an iterative and incremental approach to software development that emphasizes collaboration, flexibility, and rapid delivery of working software. It breaks projects into small, manageable cycles (sprints) and encourages continuous feedback from stakeholders. This methodology promotes adaptability to changing requirements and fosters a highly collaborative environment.

What is the role of change management in implementation?

Answer: Tracks and approves system changes

Change management in IT implementation is a structured process for controlling and documenting all modifications made to an IT system or its environment. It ensures that changes are properly reviewed, approved, tested, and implemented to minimize risks and disruptions to operations. This systematic approach maintains system stability, integrity, and compliance throughout its lifecycle.

Which factor is critical when acquiring new systems?

Answer: Vendor reliability and support

When acquiring new systems, assessing the vendor's reliability, reputation, and the quality of their ongoing support is critically important. A reliable vendor provides stable products, timely updates, and effective technical assistance, which are essential for the long-term operational success and maintenance of the system. Poor vendor support can lead to significant operational challenges, increased costs, and business disruption.

What does post-implementation review assess?

Answer: Project success and improvement areas

A post-implementation review (PIR) is conducted after a system has been deployed and is operational for some time. Its primary purpose is to evaluate whether the project met its original objectives, delivered expected benefits, and identify lessons learned for future projects. It assesses both the successes and areas requiring improvement in the project execution and the system's performance.