Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Rapid application development
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==James Martin approach== [[File:RADModel.JPG|320px|thumb|right|Phases in the James Martin approach to RAD]] The James Martin approach to RAD divides the process into four distinct phases: # '''Requirements planning phase''' β combines elements of the system planning and systems analysis phases of the [[systems development life cycle]] (SDLC). Users, managers, and IT staff members discuss and agree on [[Business requirements|business needs]], [[Scope (project management)|project scope]], constraints, and system requirements. It ends when the team agrees on the key issues and obtains management authorization to continue. # '''User design phase''' β during this phase, users interact with [[Systems analyst|systems analysts]] and develop [[Model|models]] and [[Prototype|prototypes]] that represent all system processes, [[Input (computer science)|inputs]], and [[Output (computing)|outputs]]. The RAD groups or subgroups typically use a combination of [[joint application design]] (JAD) techniques and [[CASE tools]] to translate user needs into working models. ''User design'' is a continuous interactive process that allows users to understand, modify, and eventually approve a working model of the system that meets their needs. # '''Construction phase''' β focuses on program and application development task similar to the SDLC. In RAD, however, users continue to participate and can still suggest changes or improvements as actual screens or reports are developed. Its tasks are programming and application development, [[Computer programming|coding]], [[System integration|unit-integration]] and [[system testing]]. # '''Cutover phase''' β resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training. Compared with traditional methods, the entire process is compressed. As a result, the new system is built, delivered, and placed in operation much sooner.<ref>{{cite book|last1=Martin|first1=James|title=Rapid Application Development|date=1991|publisher=Macmillan|isbn=0-02-376775-8|pages=[https://archive.org/details/rapidapplication00mart/page/81 81β90]|url=https://archive.org/details/rapidapplication00mart/page/81}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)