The systems development life cycle (SDLC), or software development life cycle systems engineering, information systems and software engineering, the process of creation or modification of systems and models and methods that people using these systems. The term usually refers to computer or information.
In software engineering the underlying concept of 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 the systems analyst for an information system, including requirements, validation, development of training, and the user (stakeholders) property. Each SDLC should result in a high quality system that meets or exceeds customer expectations, within time and cost estimates, works effectively and efficiently in the current and future IT infrastructure, and is cheap to maintain and profitable to strengthen it.
Computer systems are complex and often for any business analyst, (especially with the recent emergence of Service Oriented Architecture) link the various traditional systems supplied by different vendors. To address this complexity, 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 sequence. Agile methodologies such as Scrum and XP are focused on lightweight processes that require rapid changes along the development cycle. Iterative methods like Rational Unified Process and dynamic approach to systems development, which focuses on the limited scope of the project and develop or improve products across multiple iterations. Sequential or great design from the beginning (BDUF) as the waterfall model, focus on full and proper planning of major projects and guide the risk of good and predictable results [citation needed]. Other models, such as anamorphic development tend to focus on one type of development that is driven design iterations of the function of development and adaptation.
Project management of a project can define a project life cycle (PLC) and SDLC, where activities otherwise. According to Taylor (2004) “life cycle of a project includes all activities of the project development cycle of systems designed to meet the product requirements.
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 in various parts of the situation and conduct an analysis of the project goals, analyzing what to do and an attempt by users to certain requirements can be defined in turn.
Requirements analysis sometimes requires that individuals or groups of customers and service parts to lay down detailed and precise, often involves a lot of communication and understand these needs. Requirement collection is the most important, the lack of communication arise at this stage, and this leads to validation errors and failures in the software.
Design
In the design of systems engineering functions and activities are described in detail, including screen layouts, business rules, process diagrams and other documentation. The result of this phase of the new system can be described as a set of modules or subsystems.
The design takes as the original entrance to the requirements of the requirements of approved document. For every need, a set of one or more design elements will result from the interviews, seminars and / or prototype efforts.
Design elements describe the desired software features in detail, and functional hierarchy diagrams usually the screen layout charts, 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 enough detail so that experienced programmers can use the software with minimal additional contribution to the development of the project description.
Test
The code has been tested at various levels in software testing. Unit testing, system and acceptance are often performed. This is a gray area that so many different opinions on what the final test and the amount, if any iteration occurs. Iteration is not generally a part of the waterfall model, but it usually happens in this phase. Now we understand how important it is for a business analyst to know the complete life cycle of a software application.
Posted in 
Tags: