SDLC Model images, SDLC Models, Software Development Life Cycle (SDLC)

types of software

- system software - application software

RAD Model

Changing requirements can be accommodated, progress can be measured. Hard to manage, Dependent on strong team members Uses prototypes in sequence to produce Application code.

Big Bang Model

Just go and do it, very little planning, not good for long projects.

SDLC

This describes the life of the application, including all of the stages involved in the development, testing, installation, and maintenance of a program.

Iterative Model

This model starts with initial planning and research. Then begins a cycle -- consisting of planning, requirements, analysis and design, implementation, testing, and evaluation -- which repeats as needed until the decision is made to do deployment.

Software

collection of clearly defined computer instructions (by programmers) that directs a computer processor to carry out specific operations

why SDLC?

common, repeatable defined software development process to create software to produce, higher quality systems, fewer resources in less time, predictable manner, proper documentation of all critical information, maximum management control over the development life cycle.

Phase 4: construction and unit testing

follow design and requirement specifications to build the software. develop programming code, perform unit testing debugging

Application Software

handles common and specialized tasks a user wants to perform

Phase 7: Operations and Maintenance

- improve post deployment - update as upgrades becomes available - end user support, helpdesk/customer support team, fix defect (developers), handle change requests to add new functionality

Spiral Model

An adaptive SDLC approach that cycles over and over again through development activities until completion

Phase I: Planning

Define the project objectives and constraints are, do a preliminary analysis, finalize the scope of work.

Agile Model

Describes a set of principles for software development under which requirement's and solutions evolve though the collaborative effort of self organizing, cross functional teams. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement and it encourages rapid and flexible response to change.

Phase 3: Design

In this phase details of requirements will be implemented and then make an architect. Architecture is developed. Technology is identified to help you get there. Artifacts are designed.

system software

Programs that support the execution and development of other programs, controls the basic functions of a computer, usually pre-installed

Software Development Life Cycle

Structured framework and an idealistic method, A tool created to guide the project from start to finish. A detailed plan to create, improve, support and update software applications

Waterfall Model

an SDLC approach that assumes the phases can be completed sequentially with no overlap. First Process model introduced.

Phase 2: Requirements & Analysis

elicit requirements, analyze them, organize/prioritize, document and communicate these requirements

Phase 6: Deployment

formal release, install software into customer's environment. package or install software application. release notes, documentation, conduct user training

Phase 5: Integration & System Testing

integrate the DESIGN and REQUIREMENT SPECIFICATIONS and build that software bring all the software modules together into a prepared testing environment - QA - check software for errors, bugs, interoperability, perform integrated testing, document defects, resolve defects, repeat system testing

V-Model

modified Waterfall model that provides for back references for VERIFICATION and VALIDATION