SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC)
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
projectsofme
Active In SP
**

Posts: 1,124
Joined: Jun 2010
#1
27-09-2010, 04:01 PM



.ppt   SDLC.ppt (Size: 579 KB / Downloads: 299)
ABSTRACT


STEPS INVOLVED IN SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC)


Preject identification and selection
Project initialisation and planning
Requirement anaysis
Design
Coding
Testing
Implementation
Maintainance

PROJECT IDENTIFICATION AND SELECTION

This identifies the need for a new system or enhance system.
Information need of an organisation as whole are examined and project and implimentation to meet these needs are identified.
Mainly three steps are involved in this:-
Request clarification:-many of the request is not clearly defined hence it becomes necessary to examinethem before considering them for system investigation.
2. Feasibility study:- a project and implimentation has to be feasible in 3 respect which are technical,economical and operational.
3.Request approval:-It is not necessary that all products are feasible,only few of them
are approval on the basis of cost,completion time and requirements.


Reply
project report helper
Active In SP
**

Posts: 2,270
Joined: Sep 2010
#2
15-10-2010, 04:41 PM


.doc   project Report new.doc (Size: 2.77 MB / Downloads: 196)
SYSTEM DEVELPOMENT LIFE CYCLE (SDLC)

SYSTEM DEVELOPMENT LIFE CYCLE


The Systems Development Life Cycle (SDLC) is a conceptual model used in project and implimentation management that describes the stages involved in an information system development project and implimentation from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method). Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of project and implimentations, but in the final analysis, the most important factor for the success of a project and implimentation may be how closely particular plan was followed.


Reply
projectsofme
Active In SP
**

Posts: 1,124
Joined: Jun 2010
#3
19-10-2010, 10:27 AM

For more information about this article,please follow the link:
elucidatarefs/sdlc.pdf
Reply
seminar class
Active In SP
**

Posts: 5,361
Joined: Feb 2011
#4
15-03-2011, 09:56 AM

Capability Maturity Model (CMM)
• A bench-mark for measuring the maturity of an
organization’s software process
• CMM defines 5 levels of process maturity based
on certain Key Process Areas (KPA)
CMM Levels
Level 5 – Optimizing (< 1%)
-- process change management
-- technology change management
-- defect prevention
Level 4 – Managed (< 5%)
-- software quality management
-- quantitative process management
Level 3 – Defined (< 10%)
-- peer reviews
-- intergroup coordination
-- software product engineering
-- integrated software management
-- training program
-- organization process definition
-- organization process focus
Level 2 – Repeatable (~ 15%)
-- software configuration management
-- software quality assurance
-- software project and implimentation tracking and oversight
-- software project and implimentation planning
-- requirements management
Level 1 – Initial (~ 70%)
SDLC Model
A framework that describes the activities
performed at each stage of a software
development project and implimentation.
SDLC Phases
• Systems Investigation
– Identify problems or opportunities
• Systems Analysis
– How can we solve the problem
• Systems Design
– Select and plan the best solution
• Systems Implementation
– Place solution into effect
• Systems Maintenance and Review
– Evaluate the results of the solution
Waterfall Model
• Requirements – defines needed
information, function, behavior,
performance and interfaces.
• Design – data structures, software
architecture, interface
representations, algorithmic details.
• Implementation – source code,
database, user documentation,
testing.
Waterfall Strengths
• Easy to understand, easy to use
• Provides structure to inexperienced staff
• Milestones are well understood
• Sets requirements stability
• Good for management control (plan, staff, track)
• Works well when quality is more important than cost or
Schedule
Waterfall Deficiencies
• All requirements must be known upfront
• Deliverables created for each phase are considered frozen –
inhibits flexibility
• Can give a false impression of progress
• Does not reflect problem-solving nature of software
development – iterations of phases
• Integration is one big bang at the end
• Little opportunity for customer to preview the system (until
it may be too late)


download full report
googleurl?sa=t&source=web&cd=4&ved=0CDMQFjAD&url=http%3A%2F%2Felucidata.com%2Frefs%2Fsdlc.pdf&ei=tOl-Ta2eK8n0cLedrd8G&usg=AFQjCNGgz5jXITfeDYRHa-8wUYiH2UdxuA
Reply
seminar flower
Super Moderator
******

Posts: 10,120
Joined: Apr 2012
#5
30-05-2012, 04:57 PM

Software Development Lifecycle Cycle


.pdf   Software Development Lifecycle Cycle.pdf (Size: 122.21 KB / Downloads: 35)

Life and its Cycles

Anything that exists over a period of time is said to have a life span, be it a living creature
or an event; For each of these life spans, there is a definite process of beginning and end,
be it for a butterfly or a human being

Events and their life cycles

Even having a meal at a restaurant has a life cycle. Similarly, the software process also
has its life cycle.

SW Engg phases

Just as human life starts from infancy and goes through childhood, youth, middle age, old
age and death, the software development life cycle has the following stages:
Requirements, Design, Coding, Testing, Production Rollout, and Maintenance. These
stages are formalized in different ways to form different Software Life Cycle models.

Waterfall model

In the mid 1960s, while working for the United States Department of Defense,
A.Enthoven and Henry Rowan developed a linear list of stages for the software
development. Winston Royce introduced the first S D L C model in 1970. This became
known as the Waterfall model. However, real project and implimentations seldom follow a sequential flow of
phases, and changes in between cause concern. A lot of patience is needed from
customers and accuracy in stating the requirements correctly at one go is of prime
importance. Customers are generally very very short on accuracy and patience.
Here is an example that explains the concept of a waterfall model. The waterfall model is
like ordering a platter in a restaurant. But it has its own risks, for example, requirement
changes. The waterfall works best when requirements are clear and unchanging.
In the early 1980s, the more flexible Incremental Model was introduced. It is also called
the Staged Delivery Model. This model performs the waterfall in overlapping sections,
attempting to compensate for the length of project and implimentations by producing usable functionality
earlier, in increments. All the requirements are collected at one shot. The technical
architecture is finalized upfront. The objectives are divided into several increments or
builds. The first build is developed and delivered. This is followed by the next portion
until all the objectives have been met. It is easier to build and design than a whole
project and implimentation. However, it has its own drawbacks.

Incremental MODEL

In the early 1980s, the more flexible Incremental Model was introduced. It is also called
the Staged Delivery Model. This model performs the waterfall in overlapping sections,
attempting to compensate for the length of project and implimentations by producing usable functionality
earlier, in increments. All the requirements are collected at one shot. The technical
architecture is finalized upfront. The objectives are divided into several increments or
builds. The first build is developed and delivered. This is followed by the next portion
until all the objectives have been met. It is easier to build and design than a whole
project and implimentation. However, it has its own drawbacks.
The Incremental Model is analogous to being served course by course in a restaurant after
ordering the whole meal upfront. In this case, incorporating change is not that difficult.
Delivering in phases builds the confidence of the customer as he sees the deliverables in
increments.
Reply
seminar flower
Super Moderator
******

Posts: 10,120
Joined: Apr 2012
#6
06-10-2012, 01:46 PM

Software development life cycle (SDLC):


.docx   srs.docx (Size: 36.13 KB / Downloads: 16)

A software development process, also known as a software development life cycle (SDLC), is a structure imposed on the development of a software product. Similar terms include software life cycle and software process. It is often considered a subset of systems development life cycle. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. Some people consider a lifecycle model a more general term and a software development process a more specific term. For example, there are many specific software development processes that 'fit' the spiral lifecycle model. ISO/IEC 12207 is an international standard for software lifecycle processes. It aims to be the standard that defines all the tasks required for developing and maintaining software.

Planning

An important task in creating a software program is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Skilled and experienced software engineers recognize incomplete, ambiguous, or even contradictory requirements at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect.
Once the general requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a scope document.
Certain functionality may be out of scope of the project and implimentation as a function of cost or as a result of unclear requirements at the start of development. If the development is done externally, this document can be considered a legal document so that if there are ever disputes, any ambiguity of what was promised to the client can be clarified.

Implementation, testing and documenting

Implementation is the part of the process where software engineers actually program the code for the project and implimentation.
Software testing is an integral and important phase of the software development process. This part of the process ensures that defects are recognized as soon as possible.
Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout development. This may also include the writing of an API, be it external or internal. The software engineering process chosen by the developing team will determine how much internal documentation (if any) is necessary. Plan-driven models (e.g., Waterfall) generally produce more documentation than Agile models.

Deployment and maintenance

Deployment starts after the code is appropriately tested, approved for release, and sold or otherwise distributed into a production environment. This may involve installation, customization (e.g. by setting parameters to the customer's values), testing, and possibly an extended period of evaluation.[citation needed]
Software training and support is important, as software is only effective if it is used correctly.
Maintaining and enhancing software to cope with newly discovered faults or requirements can take substantial time and effort, as missed requirements may force redesign of the software.[citation needed]

Planning

An important task in creating a software program is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Skilled and experienced software engineers recognize incomplete, ambiguous, or even contradictory requirements at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect.
Once the general requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a scope document.
Reply
Guest
Thinking To Register

 
#7
18-12-2012, 12:17 PM

Hi,
This is Sai Sankar Nallapaneni . I need ppt of Seminar on "SOFTWARE DEVELOPMENT LIFE CYCLE" . If any one had please forward to the mail saisankar.nallapaneni@gmail.com .
Thanking you
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Message
Type your reply to this message here.


Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  microwind software free download jaseelati 0 260 23-02-2015, 12:47 PM
Last Post: jaseelati
  software reuse seminar ppt jaseelati 0 286 30-12-2014, 04:59 PM
Last Post: jaseelati
  Development of Indian Sign Language Recognition System PPT study tips 2 1,020 20-09-2013, 10:00 AM
Last Post: seminar projects maker
  Software Agents pdf seminar projects maker 0 379 13-09-2013, 04:55 PM
Last Post: seminar projects maker
  Seminar Report On SOFTWARE REUSE pdf seminar projects maker 0 575 12-09-2013, 04:18 PM
Last Post: seminar projects maker
  DISTRIBUTED FILE SYSTEM-ENHANCEMENT AND FURTHER DEVELOPMENT PPT study tips 0 508 09-09-2013, 04:13 PM
Last Post: study tips
  STANSYS SOFTWARE SOLUTIONS study tips 0 299 29-08-2013, 01:00 PM
Last Post: study tips
  A Beginner’s Guide To Software Defined Radios PPT study tips 0 271 28-08-2013, 04:55 PM
Last Post: study tips
  FUNDAMENTALS OF SOFTWARE ENGINEERING PROJECT MANAGEMENT pdf study tips 0 408 22-08-2013, 03:55 PM
Last Post: study tips
  FOUNDRY SOFTWARE study tips 0 261 20-08-2013, 03:02 PM
Last Post: study tips