Your SlideShare is downloading. ×
  • Like
Software Development Life Cycle.
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Software Development Life Cycle.

  • 2,067 views
Published

Presentation on SDLC and RAD model

Presentation on SDLC and RAD model

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,067
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SDPM & RAD Model Renuka R. Narang. CIS. ITM
  • 2. Introduction to S oftware D evelopment P rocess M odels
    • SDPM are Software development approaches that have been defined and designed to be used during the development process of a software.
    • Each process model follows a particular life cycle so as to ensure success in process of software development.
  • 3. Types of SDLC Models
    • Waterfall
    • Iterative
    • V-model
    • Spiral
    • Big bang
    • RAD
    • Prototyping
  • 4. RAD Model R apid A pplication D evelopment
    • Linear sequential software development process model
    • Emphasis is, an extremely short development cycle.
    • Uses a component based construction approach.
    • If the requirements are well understood and defined, and the project scope is constraint, RAD process enables a development team to create a fully functional system with in very short time period
  • 5. RAD
    • RAD is a concept, that products can be developed faster and of higher quality through:
      • Gathering requirements using workshops or focus groups
      • Prototyping and early, reiterative user testing of designs
      • The re-use of software components
      • A rigidly paced schedule that defers design improvements to the next product version
      • Less formality in reviews and other team communication
  • 6. Development Methodology
    • The Traditional Software Development Cycle follows a rigid sequence of steps with a formal sign-off at the completion of each step
    • RAD is a methodology that compresses the analysis, design, building, and testing phases into a series of short, iterative development cycles.
  • 7. Development Methodology
  • 8. Development Methodology
    • RAD projects are typically staffed with small integrated teams comprised of
      • Developers
      • End users
      • and IT technical resources.
    • These small teams are combined with
      • short iterative development cycles
      • optimized speed
      • unity of vision and purpose
      • effective informal communication
      • and simple project management
  • 9. RAD Model Phases
    • Business Modeling
      • The information flow among business functions is defined by answering questions like
        • what information drives the business process
        • what information is generated
        • who generates it
        • where does the information go
        • who processes it and so on
  • 10.
    • Data Modeling
    • The information collected from business modeling is
      • refined into a set of data objects ( entities ) that are needed to support the business.
      • The attributes (character of each entity) are identified and the relation between these data objects (entities) is defined
    RAD Model Phases
  • 11.
    • Process Modeling
    • The data object defined in the data modeling phase
      • are transformed to achieve the information flow necessary to implement a business function.
      • Processing descriptions are created for adding, modifying, deleting or retrieving a data object
    RAD Model Phases
  • 12.
    • Application Generation
    • Automated tools are used to facilitate construction of the software
    RAD Model Phases
  • 13.
    • Testing and Turn over
    • Many of the programming components have already been tested since RAD emphasis reuse .
    • This reduces overall testing time.
    • But new components must be tested and all interfaces must be fully exercised
    RAD Model Phases
  • 14. Advantages of RAD
    • RAD reduces the development time and reusability of components help to speed up development.
    • All functions are modularized so it is easy to work with
  • 15.
    • For large projects RAD requires highly skilled engineers in the team.
    • Both end customer and developer should be committed to complete the system in a much abbreviated time frame.
    • If commitment is lacking RAD will fail.
    • RAD is based on Object Oriented approach and if it is difficult to modularize the project the RAD Model may not work well.
    Disadvantages of RAD
  • 16.
    • Thank You 