Systems Gathering Requirements Document
Systems Gathering � PAGE * MERGEFORMAT �1�
Running head: SYSTEMS GATHERING REQUIREMENTS DOCUMENT
Systems Gathering Requirements Document
University Of Phoenix
September 29, 2008
�
Systems Gathering Requirements Document
During the systems planning phase a feasibility analysis was performed in determining if purchasing a software program would meet the demands of operations (need), technical (practicality), and economic (financial) factors of the project. Given the fact that over time, collateral analysts spend a tremendous amount of time manually calculating borrowing base ineligibles from cumbersome agings, management along with the IT department have approved the request to purchase the software program. The assessment was performed by departmental bank management, IT department, the software developer, and the departmental liaison. In order for the project to move forward to phase two of the SDLC, the system analysis phase must be accepted.
IN THE SYSTEMS ANALYSIS PHASE OF THE SDLC, YOU USE MODELS AND OTHER DOCUMENTATION TOOLS TO VISUALIZE AND DESCRIBE THE PROPOSED SYSTEM. THE OVERALL OBJECTIVE OF THE SYSTEMS ANALYSIS PHASE IS TO UNDERSTAND THE PROPOSED PROJECT, ENSURE THAT IT WILL SUPPORT BUSINESS REQUIREMENTS, AND BUILD A SOLID FOUNDATION FOR SYSTEM DEVELOPMENT (SHELLY, CASHMAN & ROSENBLATT, 2004, P. 92,¶ 1).
Resulting in the design of the overall system called the system requirements document of the systems analysis phase. However, before the system requirements document can be written the systems analyst must gather information that will be recognized. This document will discuss the various methods to be used to determine requirements for the proposed system.
The first process in gathering requirements is to conduct interviews with managers, department heads, and users. During this process questions are formed and information is gathered. One main question that a systems analyst will ask is, "Do you see any advantages in the proposed system?" The
Running head: SYSTEMS GATHERING REQUIREMENTS DOCUMENT
Systems Gathering Requirements Document
University Of Phoenix
September 29, 2008
�
Systems Gathering Requirements Document
During the systems planning phase a feasibility analysis was performed in determining if purchasing a software program would meet the demands of operations (need), technical (practicality), and economic (financial) factors of the project. Given the fact that over time, collateral analysts spend a tremendous amount of time manually calculating borrowing base ineligibles from cumbersome agings, management along with the IT department have approved the request to purchase the software program. The assessment was performed by departmental bank management, IT department, the software developer, and the departmental liaison. In order for the project to move forward to phase two of the SDLC, the system analysis phase must be accepted.
IN THE SYSTEMS ANALYSIS PHASE OF THE SDLC, YOU USE MODELS AND OTHER DOCUMENTATION TOOLS TO VISUALIZE AND DESCRIBE THE PROPOSED SYSTEM. THE OVERALL OBJECTIVE OF THE SYSTEMS ANALYSIS PHASE IS TO UNDERSTAND THE PROPOSED PROJECT, ENSURE THAT IT WILL SUPPORT BUSINESS REQUIREMENTS, AND BUILD A SOLID FOUNDATION FOR SYSTEM DEVELOPMENT (SHELLY, CASHMAN & ROSENBLATT, 2004, P. 92,¶ 1).
Resulting in the design of the overall system called the system requirements document of the systems analysis phase. However, before the system requirements document can be written the systems analyst must gather information that will be recognized. This document will discuss the various methods to be used to determine requirements for the proposed system.
The first process in gathering requirements is to conduct interviews with managers, department heads, and users. During this process questions are formed and information is gathered. One main question that a systems analyst will ask is, "Do you see any advantages in the proposed system?" The
References: Shelly, G. B., Cashman, T. J., & Rosenblatt, H. J. (2004). Chapter 3: Requirements Modeling. In _Systems Analysis and Design_ (5th ed., p. 92). Course Technology. Retrieved September 28, 2008, from http://ecampus.phoenix.edu/content/eBookLibrary2/content/ereader.aspx?assetmetaid=3df7b872-d3c7-4c1f-a0fe-5ed46961030c&assetdataid=c2047d4b-7855-450e-b51e-6e007038bd6a