SlideShare uma empresa Scribd logo
1 de 15
Introduction
   RAD - Rapid application development.
   It is adoption of waterfall model, It aims at
    developing a software in a short span of time.
   It concentrates on input output source and
    destination of information.
   It is based on Model Phases.
Model Phases
   Business modeling
   Data modeling
   Process modeling
   Application generation
   Testing and turnover
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 process it and so
    on.
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.
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.
Application Generation
   Automated tools are used to facilitate
    construction of the software;
   Even they use the 4th GL techniques.
   The term fourth-generation programming
    language (abbreviated 4GL) is better
    understood to be a fourth generation
    environment; packages of systems
    development software including very high
    level programming languages.
Testing and Turnover
   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 Requirements
   Case tool : Computer-aided software
    engineering (CASE) is a set of tools and
    methods to a software system which
    results in high-quality, defect-free, and
    maintainable software products.
   Data dictionary : Is a centralized
    repository of information about data such
    as meaning, relationships to other data,
    origin, usage, and format.
   Storyboard : A storyboard is an area
    where there will be a series of static
    images or sketches that when played in a
    fast sequence, will appear as an animation.

   Risk Register : It acts as a central
    repository for all risks identified by the
    project or organisation and, for each risk,
    includes information such as risk
    probability, impact, counter-measures, risk
    owner and so on.
Advantages
   Quick initial reviews are possible.
   Constant integration isolate problems
    and encourage customer feedback.
   Flexible and adaptable to changes.
   RAD realizes an overall reduction in
    project risk.
   RAD generally incorporates short
    development cycles - users see the
    RAD product quickly.
Disadvantage
   Requires a systematic approach for
    modularized.
   Requires highly skilled and well-trained
    developers.
   Product may lose its competitive edge
    because of insufficient core functionality
    and may exhibit poor overall quality.
Conclusion
   Requires minimal planning in favor of rapid
    prototyping.

   Instead of using codes, developers use
    different tools and software development
    kits and bring them all together to create a
    software.

    Developers who are time challenged could
    use this application development.
   Users’ feedbacks are important in this
    development cycle since they will suggest
    whether the program will fit to their
    specifications and needs.

   Businesses will also appreciate this
    software as it’s aimed to answer specific
    problems.
THANK YOU

Mais conteúdo relacionado

Mais procurados

Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9
koolkampus
 

Mais procurados (20)

Spiral model presentation
Spiral model presentationSpiral model presentation
Spiral model presentation
 
Architecture design in software engineering
Architecture design in software engineeringArchitecture design in software engineering
Architecture design in software engineering
 
Spiral model
Spiral modelSpiral model
Spiral model
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process Models
 
Evolutionary models
Evolutionary modelsEvolutionary models
Evolutionary models
 
Waterfall model
Waterfall modelWaterfall model
Waterfall model
 
Waterfall model in SDLC
Waterfall model in SDLCWaterfall model in SDLC
Waterfall model in SDLC
 
Software Process Models
Software Process ModelsSoftware Process Models
Software Process Models
 
Iterative model
Iterative modelIterative model
Iterative model
 
Overview of UML Diagrams
Overview of UML DiagramsOverview of UML Diagrams
Overview of UML Diagrams
 
Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9
 
Use Case Diagram
Use Case DiagramUse Case Diagram
Use Case Diagram
 
Software design
Software designSoftware design
Software design
 
Software Engineering - Spiral Model
Software Engineering - Spiral ModelSoftware Engineering - Spiral Model
Software Engineering - Spiral Model
 
Agile software development
Agile software developmentAgile software development
Agile software development
 
software engineering
software engineeringsoftware engineering
software engineering
 
Waterfall model ppt final
Waterfall model ppt  finalWaterfall model ppt  final
Waterfall model ppt final
 
Spiral model
Spiral modelSpiral model
Spiral model
 
Design Pattern in Software Engineering
Design Pattern in Software EngineeringDesign Pattern in Software Engineering
Design Pattern in Software Engineering
 
Cocomo model
Cocomo modelCocomo model
Cocomo model
 

Semelhante a Rad model

Rad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
Rad model arnav.ppt Rad model arnav.pptRad model arnav.pptRad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
Rad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
ArnavPlayz
 
rad model rad model rad model rad model.ppt
rad model rad model rad model rad model.pptrad model rad model rad model rad model.ppt
rad model rad model rad model rad model.ppt
ArnavPlayz
 

Semelhante a Rad model (20)

Rad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
Rad model arnav.ppt Rad model arnav.pptRad model arnav.pptRad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
Rad model arnav.ppt Rad model arnav.pptRad model arnav.ppt
 
rad model rad model rad model rad model.ppt
rad model rad model rad model rad model.pptrad model rad model rad model rad model.ppt
rad model rad model rad model rad model.ppt
 
The Waterfall Model & RAD MODEL
 The Waterfall Model &  RAD MODEL The Waterfall Model &  RAD MODEL
The Waterfall Model & RAD MODEL
 
Software Development Life Cycle.
Software Development Life Cycle.Software Development Life Cycle.
Software Development Life Cycle.
 
What is jad_session
What is jad_sessionWhat is jad_session
What is jad_session
 
Rad model
Rad modelRad model
Rad model
 
Efficiency in Action The Power of Rapid Application Development Tools.pdf
Efficiency in Action The Power of Rapid Application Development Tools.pdfEfficiency in Action The Power of Rapid Application Development Tools.pdf
Efficiency in Action The Power of Rapid Application Development Tools.pdf
 
Rad model
Rad modelRad model
Rad model
 
Waterfall model
Waterfall modelWaterfall model
Waterfall model
 
RAD MODEL.pptx
RAD MODEL.pptxRAD MODEL.pptx
RAD MODEL.pptx
 
Software Development Today Everything You Need To Know.pdf
Software Development Today Everything You Need To Know.pdfSoftware Development Today Everything You Need To Know.pdf
Software Development Today Everything You Need To Know.pdf
 
Session3
Session3Session3
Session3
 
A Basic Introduction to Creating a Software Requirements Specification
A Basic Introduction to Creating a Software Requirements SpecificationA Basic Introduction to Creating a Software Requirements Specification
A Basic Introduction to Creating a Software Requirements Specification
 
Yii Framework in the RAD context + Mashup demo built on YII
Yii Framework in the RAD context + Mashup demo built on YIIYii Framework in the RAD context + Mashup demo built on YII
Yii Framework in the RAD context + Mashup demo built on YII
 
What is rad model
What is rad modelWhat is rad model
What is rad model
 
Satish_Vishwa
Satish_VishwaSatish_Vishwa
Satish_Vishwa
 
Uml 2.x
Uml 2.xUml 2.x
Uml 2.x
 
Software design.edited (1)
Software design.edited (1)Software design.edited (1)
Software design.edited (1)
 
Software Engineering Overview
Software Engineering OverviewSoftware Engineering Overview
Software Engineering Overview
 
Srikanth QA Analyst
Srikanth QA AnalystSrikanth QA Analyst
Srikanth QA Analyst
 

Mais de Sneha Chopra

Mais de Sneha Chopra (8)

Data structures
Data structuresData structures
Data structures
 
Embedded System
Embedded SystemEmbedded System
Embedded System
 
E.s unit 6
E.s unit 6E.s unit 6
E.s unit 6
 
E.s unit 4 and 5
E.s unit 4 and 5E.s unit 4 and 5
E.s unit 4 and 5
 
E.s (2)
E.s (2)E.s (2)
E.s (2)
 
Computer Graphics
Computer GraphicsComputer Graphics
Computer Graphics
 
Multimedia
MultimediaMultimedia
Multimedia
 
Modern Operating System Windows Server 2008
Modern Operating System  Windows Server 2008Modern Operating System  Windows Server 2008
Modern Operating System Windows Server 2008
 

Rad model

  • 1.
  • 2. Introduction  RAD - Rapid application development.  It is adoption of waterfall model, It aims at developing a software in a short span of time.  It concentrates on input output source and destination of information.  It is based on Model Phases.
  • 3. Model Phases  Business modeling  Data modeling  Process modeling  Application generation  Testing and turnover
  • 4. 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 process it and so on.
  • 5. 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.
  • 6. 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.
  • 7. Application Generation  Automated tools are used to facilitate construction of the software;  Even they use the 4th GL techniques.  The term fourth-generation programming language (abbreviated 4GL) is better understood to be a fourth generation environment; packages of systems development software including very high level programming languages.
  • 8. Testing and Turnover  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.
  • 9. RAD Requirements  Case tool : Computer-aided software engineering (CASE) is a set of tools and methods to a software system which results in high-quality, defect-free, and maintainable software products.  Data dictionary : Is a centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format.
  • 10. Storyboard : A storyboard is an area where there will be a series of static images or sketches that when played in a fast sequence, will appear as an animation.  Risk Register : It acts as a central repository for all risks identified by the project or organisation and, for each risk, includes information such as risk probability, impact, counter-measures, risk owner and so on.
  • 11. Advantages  Quick initial reviews are possible.  Constant integration isolate problems and encourage customer feedback.  Flexible and adaptable to changes.  RAD realizes an overall reduction in project risk.  RAD generally incorporates short development cycles - users see the RAD product quickly.
  • 12. Disadvantage  Requires a systematic approach for modularized.  Requires highly skilled and well-trained developers.  Product may lose its competitive edge because of insufficient core functionality and may exhibit poor overall quality.
  • 13. Conclusion  Requires minimal planning in favor of rapid prototyping.  Instead of using codes, developers use different tools and software development kits and bring them all together to create a software.  Developers who are time challenged could use this application development.
  • 14. Users’ feedbacks are important in this development cycle since they will suggest whether the program will fit to their specifications and needs.  Businesses will also appreciate this software as it’s aimed to answer specific problems.