SDLC for a Business Analyst

The systems development life cycle (SDLC), or Software Development Life Cycle in systems engineering, information systems and software engineering, the process of creation or modification of systems and models and methods that people use these systems. The term generally refers to computer or information.

In software engineering the concept underlying many types of SDLC methodologies of software development. These methods provide the framework for planning and control of the creation of an information system: the process of software development.

Systems Development Life Cycle (SDLC) is a process used by a systems analyst for an information system, including requirements, validation, development of training, and the user (stakeholder) property. Each SDLC should result in a high quality system that meets or exceeds customer expectations, completed within the time and cost estimates, works effectively and efficiently in current and future IT infrastructure, and is inexpensive to maintain and cost effective for strengthen.

Computer systems are complex and often for any business analyst, (particularly with the recent emergence of Service-Oriented Architecture) link various traditional systems supplied by different vendors. To handle these complexities, a number of SDLC models or methodologies are made, as the “cascade”, “spiral”, Agile, rapid prototyping, “incremental” and “sync and stabilize”.

SDLC models can be described along a spectrum of agile iterative sequential order. Agile methodologies like XP and Scrum focus on lightweight processes that require rapid changes along the development cycle. Iterative methods like Rational Unified Process and Dynamic Systems Development Method, which focuses on the limited scope of the project and develop or improve products through multiple iterations. Sequential or big-design up front (BDUF) models such as Waterfall, focus on the full and proper planning of major projects and guide the risk to obtain good results and predictable [citation needed]. Other models, such as anamorphic development, tend to focus on one type of development that is driven by design iterations of the function of development and adaptation.

Project management of a project can be defined with a project life cycle (PLC) and a SDLC, where something different activities. According to Taylor (2004) “Life cycle of a project includes all activities of the project, the development cycle of systems designed to meet the requirements of the product.

Related your content:  Important Facts About Small Business Administration Loans

Systems Analysis

The purpose of the analysis system is to determine where the problem is an attempt to solve the system. This step is to break the system into several pieces about the situation and conduct an analysis of the objectives of the project, breaking down what needs to be done and an attempt to users so that certain requirements can be defined in turn.

Requirements analysis sometimes requires individuals or groups of client and service sides to lay down detailed and precise, often involves a lot of communication and understand these needs. Collection requirement is the most crucial such as communication gaps arise at this stage, and this leads to validation errors and bugs in the software.


In the design of systems engineering functions and activities are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this phase of the new system will be described as a set of modules or subsystems.

The design takes as the original entrance to the requirements of approved document requirements. For each requirement, a set of one or more design elements are produced as a result of interviews, seminars and / or prototype efforts.

Design elements describe the desired software features in detail, and usually functional hierarchy diagrams, screen layout diagrams, tables, business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a complete data dictionary. These design elements are intended to use the software in sufficient detail so that experienced programmers can use the software with minimal additional input for developing the project description.


The code has been tested at various levels in testing the software. Unit testing, system and acceptance are often performed. This is a gray area that so many different opinions on what the final testing and how much if any iteration occurs. Iteration is not generally a part of the waterfall model, but usually what happens in this phase. Now we understood how it is important for a Business Analyst to know the complete life cycle of a software application.

by David Vilson

Share This Post

Post Comment