1 / 21

RAPID DEVELOPMENT

RAPID DEVELOPMENT. 06 PLM - Group 9 Aditya Gisheila. Femme Sabaru. Aninda Harapan. Harry. Andrew Kosugih BINUS University. ABSTRACT.

sylvie
Download Presentation

RAPID DEVELOPMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAPID DEVELOPMENT 06 PLM - Group 9 Aditya Gisheila. Femme Sabaru. Aninda Harapan. Harry. Andrew Kosugih BINUS University

  2. ABSTRACT • Rapid development to some people is consists of the application of a single pet tool or method.Rapid development is merely a descriptive phrase that contrasts with "slow and typical development". Rapid development is a generic term that means the same thing as "speedy development" or "shorter schedules". It means developing software faster than you do now.Rapid-development project, then, is any project that needs to emphasize development speed.

  3. Chapter 1background • Today, taking less time to conceive, develop, and implement an information system can provide the organization with a competitive advantage. In addition, as evidenced by the CHAOS study, larger projects that take longer to develop are riskier than smaller and shorter projects. • According to Satzinger: "a collection of development approaches, techniques, tools, and technologies, each of which has been proven to shorten development schedules under some conditions." • This means that different development approaches, tools, techniques, and so forth can be mixed and matched depending on the project.

  4. Chapter 1scope • What RAD (Rapid Application Development) is • The advantages if we use RAD in our SDLC • The drawbacks of RAD • Comparewith the other SDLC development methodology which is the Agile Development method.

  5. Chapter 1objective and benefits • Objective • Createa writing that can help people in understanding RAD method easier. Because some statement in this writing based on trusted reference. So, it’ll increase people’s efficiency in finding sources when understanding the RAD method. • Benefits • We can fulfill one requirement to pass the Teori-TeoriLanjutansubject. • We can help people more understand the RAD method. • We learn how to write a proper paper

  6. Chapter 1methodology • Literature Study We research from any source, especially on books and journals, which has relationship with this research

  7. Chapter 2LITERATURE REVIEW • System Collectionof interrelated components that function together to achieve some outcome. • Development The act or process of growing or causing something to grow or become larger or more advanced • Life Cycle Seriesof stages through which something (as an individual, culture, or manufactured product) passes during its lifetime. • Rapid Application Development Mergerof various structure and techniques (especially the Data- Driven information engineering) with prototyping techniques and joint application development techniques to accelerate systems development.

  8. Chapter 2literature review • Prototyping Atechnique for quickly building a functioning, but incomplete model of information system using rapid application development tools. • Joint Application Development Processthat accelerates the design of information technology solutions. • Prototype Smallerscale, representative or working model of the users requirements or a proposed design for an information system. • Rapid Happeningin a short amount of time; happening quickly

  9. Chapter 3discussion • What is Rapid Development Collectionof methodologies that emerged in response to the weaknesses of waterfall development and its variations. Rapid Application Development is also a system development strategy that focuses on the speed of development through the extensive involvement of users during construction of a system prototype that later will be a final system (or a certain version). Severalways in conducting the Rapid Application Development: • Iterative Development • System Prototyping • Throwaway Prototyping

  10. Chapter 3discussion • ADVANTAGES OF RAPID DEVELOPMENT • Useful to projects where the user requirements’ are uncertain and unclear • It pushes the users to be active and management participation to encourage end user enthusiasm in of the project • Projects have visibility and more support due to the extensive involvement of users during the process • Users and management can see the solutions that are software-based and work faster than model-driven development • Error and bugs are detected earlier in the prototype than in system modeling • Testing and training are additional aspects of the basic prototyping approach • Iterative approach is a process that is more “natural” because change is the factor that is expected during development

  11. Chapter 3discussion • DISADVANTAGES OF RAPID DEVELOPMENT • Some people thinks that the Rapid Application Development pushes the idea of “coding, implementing, and fixing” that increases the lifetime cost that is needed to operate, support and maintain the system • Rapid Application Development Prototypes can easily solve wrong problems because of the shortened or neglected problem analysis • RAD-based prototype may make the analysts feel small in considering other valuable technical alternatives • Sometimes it is better to throw away prototypes, but stakeholders are often reluctant to go so because they think that it is a loss of time and effort of the product • Accentuation on speed can have negative impact on quality that is caused by shortcuts badly advised through the methodology

  12. CHAPTER 3DISCUSSION • STEPS IN RAPID DEVELOPMENT • Planning • Analysis • Design • Implementation

  13. Chapter 3discussion • STEPS IN RAPID DEVELOPMENT • Planning • During project initiation • During project management

  14. Chapter 3discussion • STEPS IN RAPID DEVELOPMENT • Analysis • Analysis strategy • Requirement Gathering • System Proposal

  15. Chapter 3discussion • STEPS IN RAPID DEVELOPMENT • Design • Design Strategy • Architecture Design • Database and file specification • Program Design

  16. Chapter 3discussion • STEPS IN RAPID DEVELOPMENT • Implementation • System construction • Installation • Support Plan

  17. Chapter 3discussion • AGILE DEVELOPMENT VS RAPID DEVELOPMENT

  18. Chapter 4conclusion • CONCLUSION • There are several ways in conducting the Rapid Application Development: • Iterative Development • System Prototyping • Throwaway Prototyping • Basically the Rapid Development consist four important phases: • Planning • Analysis • Design • Implementation

  19. Chapter 4conclusion • The best methodology that can be adapted is using Rapid Application Development in Throwaway Prototyping method. It provides the most excellent result in prototype implementation. • The RAD (Rapid Application Development) process only requires a small amount of highly skilled and trained peoples to work together in perform prototyping and construction of the software product, especially in dealing new technologies and techniques are crucial.

  20. CHAPTER 4CONCLUSION • SUGGESTION • RAD (Rapid Application Development) should be implemented in creating a system module in order to reduce maximum cost for organizational effective and efficient budget for short period of time. • Highly risk operational method in implementing RAPID APPLICATION DEVELOPMENT that the systems are related one to another which can effect to the other system if one of them is error. It needs well-done preparation and good backup plan. • Special trained developers and designer are required.

  21. Thank you

More Related