Systems Analysis Procedure
The purpose of the Systems Analysis Procedure is to create documents that define the functions the system will perform. The Systems Analysis Procedure also creates an acceptance test plan—which describes how to test system functions—and a beta test plan—which describes how to conduct a user test of those functions.
The Systems Analysis Procedure applies to all software products and updates released by the company. (6 pages, 1270 words)
Systems Analysis Responsibilities:
The Systems Analyst is responsible for developing and communicating the overall design approach that addresses the customer requirements, as well as producing the test plans.
Systems Analysis Definitions:
Systems analysis – Work that involves applying analytical processes to the planning, design, and implementation of new and improved information systems to meet the business requirements of customer organizations; phase of the SDLC in which the current system is studied and alternative replacement systems are proposed.
Systems development life cycle (SDLC) – A method for developing information systems, made up of five main stages: analysis, design, development, implementation, and evaluation. Each stage is further comprised of several components (for example, the development stage includes programming, debugging, testing, and documenting).
Systems Analysis Procedure Activities
- Systems Analysis-Introduction
- Systems Analysis-Requirements
- Systems Analysis-Information Flows Documentation
- Systems Analysis-Acceptance Test Plan
- Systems Analysis-Beta Test Plan
- Systems Analysis-Review
Systems Analysis Procedure References
- ISO/IEC 12207:1995- Information Technology-software Life Cycles Processes
- IEEE/EIA 12207.0-Standard Industry Implementation of International Standard ISO/IEC 12207:1995(ISO/IEC 12207) Standard for Information Technology Software Life Cycle Processes