1978年五行属什么| 空调水滴是什么模式| 砸是什么意思| 5月6号是什么星座| 结核t细胞阳性说明什么| 阿卡波糖什么时候吃| 口腔溃疡吃什么药好得快| 莲子心有什么功效| 徐长卿是什么药| 为什么会得肠胃炎| 甲状腺有什么症状| 痔疮的表现症状是什么| 小便发红是什么症状男| 什么叫资本运作| 线索细胞阳性是什么意思| 头顶出汗是什么原因| 牙齿痛挂什么科| 咳白色泡沫痰吃什么药| 匮乏是什么意思| 肺肿瘤吃什么好| 葡萄糖为什么叫葡萄糖| 男人眼角有痣代表什么| 忠武路演员是什么意思| 622188开头是什么银行| 王加申念什么| 高姿属于什么档次| 江小白加雪碧什么意思| 五色土有什么风水作用| 鸟飞到头上什么预兆| 十月一是什么星座| 什么是皮包公司| 头总是昏昏沉沉的是什么原因| 天高云淡是什么季节| 赘疣是什么意思| mect是什么意思| 央企董事长什么级别| 壮字五行属什么| 蚊子讨厌什么气味| gfr医学上是什么意思| 手术后吃什么营养品好| 鬼针草能治什么病| 立事牙疼吃什么药| 什么是刑事拘留| 丝丝入扣是什么意思| 咳嗽有痰挂什么科| 血糖高能吃什么食物| 过期药品属于什么垃圾| 耳朵真菌感染用什么药最好| 一什么扇子| 沵是什么意思| 01年属什么| 抓龙筋什么意思| 心脏跳得快是什么原因| 耳朵发炎吃什么药| fwb是什么意思| 医院三甲是什么意思| 例假血是黑色的是什么原因| 最近有什么病毒感染| 离婚的女人叫什么| 名分是什么意思| 黄花菜长什么样子| 脚腕筋疼是什么原因| 甲状腺彩超挂什么科| 南北朝后面是什么朝代| 中国为什么叫中国| 花甲是什么意思| 用盐洗头发有什么好处| 94年属什么今年多大| 戾气重是什么意思| 坐月子可以吃什么零食| 廉航是什么意思| 咽炎吃什么药好| 陪跑什么意思| 二人世界是什么意思| 吃什么流产最快| mb是什么意思| 中气是什么意思| 农历5月是什么星座| 尤加一笔是什么字| 脑血栓前兆是什么症状表现| green是什么颜色| 耳石症是什么意思| 拜阿司匹林和阿司匹林有什么区别| 尿酸高不能吃什么蔬菜| 灰指甲什么症状| 嘴苦吃什么药| 杂菌2个加是什么意思| 什么是直肠炎| 大暑是什么意思| 白细胞一个加号什么意思| 六六无穷是什么意思| 晨尿泡沫多是什么原因| 什么是类风湿性关节炎| 胃炎吃什么食物好养胃| 狗的五行属什么| 印度什么人种| 弱智的人有什么表现| 阴毛变白是什么原因| 送礼送什么比较好| 为什么会长瘤| 咽炎吃什么药效果好| bpd是什么意思| 气血不足吃什么中成药最好| 头部爱出汗是什么原因| 尼泊尔人是什么人种| 为什么明星都不戴黄金| 风情万种的意思是什么| 点痣不能吃什么东西| 什么人容易得心理疾病| 吃什么安神有助于睡眠| 3月20日什么星座| 痔疮什么东西不能吃| 什么是匝道图片| 心火吃什么药| 什么蛇不咬人| dx是什么药| 减肥吃什么药效果最好| 三碘甲状腺原氨酸高是什么意思| 查血糖是什么检查项目| qd医学上是什么意思| 猴日冲虎是什么意思| 圣女果是什么水果| 男性补肾壮阳吃什么药效果比较好| 流产有什么症状| 什么程度算节食减肥| 来例假头晕是什么原因| 血糖高是什么原因引起| 吸渣体质是什么意思| 710是什么意思| 二五八万是什么意思| 浑水摸鱼什么意思| 腿部肿胀是什么原因引起的| 为什么啊| 铜绿假单胞菌用什么抗生素| 视力s和c代表什么| 雌堕什么意思| 晚生是什么意思| 双生痣是什么意思| 唐氏综合征是什么原因造成的| 高密度灶是什么意思| 记性不好吃什么药| 1963年发生了什么| 无所不用其极是什么意思| 氯雷他定片主治什么| 肠道紊乱的症状是什么| 重逢是什么意思| 亲嘴什么感觉| 乳腺瘤不能吃什么| 咳嗽痰多是什么原因| 腱鞘炎要挂什么科| 过人之处是什么意思| 锦鲤是什么意思| 12月份什么星座| 什么牛什么毛| 兔子五行属什么| 梦见包被偷了什么预兆| 什么是狐臭| 耳朵老是痒是什么原因| 什么是五行| 洋姜学名叫什么| 狗狗吃胡萝卜有什么好处| 复仇者用什么武器| 6月27号是什么星座| 猪生肠是什么部位| 满月针最晚什么时候打| 什么河水| 三月什么星座| 猫什么时候发情| 五月三十一号是什么星座| 微博id是什么| 什么茶解暑| 传媒公司主要做什么| 马齿苋不能和什么一起吃| 三严三实是什么| 囊中羞涩什么意思| 什么是盆底肌| 戴玉手镯有什么好处| 台球杆什么牌子的好| 4月10号是什么星座| 血沉高是什么意思| cy是什么意思| 吃什么皮肤白的最快| 极有家是什么意思| 却的偏旁叫什么| 什么可以代替润滑油| may是什么意思| 法令纹深代表什么面相| 松字五行属什么| mup是什么意思| 艾灸是什么东西| 炼奶是什么| 眼皮红肿是什么原因引起的| 三七粉主要治什么病| 左下腹疼挂什么科| 江苏有什么山| 小蓝瓶是什么| sph是什么意思| 穿孔是什么意思| 梦到自行车丢了是什么意思| 什么是部首| 男性尿路感染有什么症状| 八面玲珑指什么生肖| c反应蛋白低说明什么| 前胸贴后背是什么意思| 家里进黄鼠狼是什么预兆| 尿蛋白质阳性什么意思| 54岁属什么的| 不可什么什么| 象牙塔比喻什么| 大便排不出来是什么原因| 每天早上起床头晕是什么原因| 山根是什么| 清油是什么油| 为什么心里老是想着死| 木棉花什么时候开花| 吃头孢不能吃什么水果| 读书有什么好处| 24属什么生肖| 感染性发热是什么意思| 异性是什么意思| 亲夫是什么意思| 发票抬头是什么| 女人耳鸣是什么前兆| 为什么冬吃萝卜夏吃姜| 医学ns是什么意思| 为什么屎是臭的| 知青是什么| osd是什么意思| 农历五月二十八是什么日子| 卟啉症是什么病| 一个金字旁一个川读什么| 女性吃大肠有什么好处| 白头翁吃什么| 远视储备是什么意思| 榴莲为什么这么贵| 十一月份出生的是什么星座| 7月26日什么星座| 浮夸是什么意思| 夜间睡觉流口水是什么原因| 太息是什么意思| 手腕痛挂什么科| 拔牙能吃什么| 牛肉饺子配什么菜好吃| 火龙果不能和什么一起吃| 什么烟好抽又便宜| 黑户是什么| 腱鞘炎是什么病| 沉香对人体有什么好处| 牙齿发酸是什么原因| 拉肚子不能吃什么食物| 一个三点水一个除念什么| 儿女双全什么意思| 哪吒为什么叫哪吒| 十二星座什么第一名| 不修边幅是什么意思| 2003年的羊是什么命| 婴儿呛奶是什么原因引起的| oppo最新款是什么型号| 稀字五行属什么| 不治身亡是什么意思| vm是什么意思| 七月七是什么星座| 辛未日五行属什么| 膝盖疼痛吃什么药| 百度Jump to content

阴囊湿疹用什么药效果最好

From Wikipedia, the free encyclopedia
百度   李天明说,整个过程不到两分钟,车上的游客非常兴奋,一边拍照一边惊叹运气太好了大熊猫太可爱了!但同时又有游客提醒,不要吓到它了。

Rapid application development (RAD), also called rapid application building (RAB), is both a general term for adaptive software development approaches, and the name for James Martin's method of rapid development. In general, RAD approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even instead of design specifications.

RAD is especially well suited for (although not limited to) developing software that is driven by user interface requirements. Graphical user interface builders are often called rapid application development tools. Other approaches to rapid development include the adaptive, agile, spiral, and unified models.

History

[edit]

Rapid application development was a response to plan-driven waterfall processes, developed in the 1970s and 1980s, such as the Structured Systems Analysis and Design Method (SSADM). One of the problems with these methods is that they were based on a traditional engineering model used to design and build things like bridges and buildings. Software is an inherently different kind of artifact. Software can radically change the entire process used to solve a problem. As a result, knowledge gained from the development process itself can feed back to the requirements and design of the solution.[1] Plan-driven approaches attempt to rigidly define the requirements, the solution, and the plan to implement it, and have a process that discourages changes. RAD approaches, on the other hand, recognize that software development is a knowledge intensive process and provide flexible processes that help take advantage of knowledge gained during the project to improve or adapt the solution.

The first such RAD alternative was developed by Barry Boehm and was known as the spiral model. Boehm and other subsequent RAD approaches emphasized developing prototypes as well as or instead of rigorous design specifications. Prototypes had several advantages over traditional specifications:

  • Risk reduction. A prototype could test some of the most difficult potential parts of the system early on in the life-cycle. This can provide valuable information as to the feasibility of a design and can prevent the team from pursuing solutions that turn out to be too complex or time-consuming to implement. This benefit of finding problems earlier in the life-cycle rather than later was a key benefit of the RAD approach. The earlier a problem can be found the cheaper it is to address.
  • Users are better at using and reacting than at creating specifications. In the waterfall model it was common for a user to sign off on a set of requirements but then when presented with an implemented system to suddenly realize that a given design lacked some critical features or was too complex. In general most users give much more useful feedback when they can experience a prototype of the running system rather than abstractly define what that system should be.
  • Prototypes can be usable and can evolve into the completed product. One approach used in some RAD methods was to build the system as a series of prototypes that evolve from minimal functionality to moderately useful to the final completed system. The advantage of this besides the two advantages above was that the users could get useful business functionality much earlier in the process.[2]

Starting with the ideas of Barry Boehm and others, James Martin developed the rapid application development approach during the 1980s at IBM and finally formalized it by publishing a book in 1991, Rapid Application Development. This has resulted in some confusion over the term RAD even among IT professionals. It is important to distinguish between RAD as a general alternative to the waterfall model and RAD as the specific method created by Martin. The Martin method was tailored toward knowledge intensive and UI intensive business systems.

These ideas were further developed and improved upon by RAD pioneers like James Kerr and Richard Hunter, who together wrote the seminal book on the subject, Inside RAD,[3] which followed the journey of a RAD project manager as he drove and refined the RAD Methodology in real-time on an actual RAD project. These practitioners, and those like them, helped RAD gain popularity as an alternative to traditional systems project life cycle approaches.

The RAD approach also matured during the period of peak interest in business re-engineering. The idea of business process re-engineering was to radically rethink core business processes such as sales and customer support with the new capabilities of Information Technology in mind. RAD was often an essential part of larger business re engineering programs. The rapid prototyping approach of RAD was a key tool to help users and analysts "think out of the box" about innovative ways that technology might radically reinvent a core business process.[4][5]

Much of James Martin's comfort with RAD stemmed from Dupont's Information Engineering division and its leader Scott Schultz and their respective relationships with John Underwood who headed up a bespoke RAD development company that pioneered many successful RAD projects in Australia and Hong Kong.

Successful projects that included ANZ Bank, Lend Lease, BHP, Coca-Cola Amatil, Alcan, Hong Kong Jockey Club and numerous others.

Success that led to both Scott Shultz and James Martin both spending time in Australia with John Underwood to understand the methods and details of why Australia was disproportionately successful in implementing significant mission critical RAD projects.

James Martin approach

[edit]
Phases in the James Martin approach to RAD

The James Martin approach to RAD divides the process into four distinct phases:

  1. 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 needs, project scope, constraints, and system requirements. It ends when the team agrees on the key issues and obtains management authorization to continue.
  2. User design phase – during this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, inputs, and 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.
  3. 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, coding, unit-integration and system testing.
  4. 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.[6]

Advantages

[edit]

In modern Information Technology environments, many systems are now built using some degree of Rapid Application Development[7] (not necessarily the James Martin approach). In addition to Martin's method, agile methods and the Rational Unified Process are often used for RAD development.

The purported advantages of RAD include:

  • Better quality. By having users interact with evolving prototypes the business functionality from a RAD project can often be much higher than that achieved via a waterfall model. The software can be more usable and has a better chance to focus on business problems that are critical to end users rather than technical problems of interest to developers. However, this excludes other categories of what are usually known as Non-functional requirements (AKA constraints or quality attributes) including security and portability.
  • Risk control. Although much of the literature on RAD focuses on speed and user involvement a critical feature of RAD done correctly is risk mitigation. It's worth remembering that Boehm initially characterized the spiral model as a risk based approach. A RAD approach can focus in early on the key risk factors and adjust to them based on empirical evidence collected in the early part of the process. E.g., the complexity of prototyping some of the most complex parts of the system.
  • More projects completed on time and within budget. By focusing on the development of incremental units the chances for catastrophic failures that have dogged large waterfall projects is reduced. In the Waterfall model it was common to come to a realization after six months or more of analysis and development that required a radical rethinking of the entire system. With RAD this kind of information can be discovered and acted upon earlier in the process.[2][8]

Disadvantages

[edit]

The purported disadvantages of RAD include:

  • The risk of a new approach. For most IT shops RAD was a new approach that required experienced professionals to rethink the way they worked. Humans are virtually always averse to change and any project undertaken with new tools or methods will be more likely to fail the first time simply due to the requirement for the team to learn.
  • Lack of emphasis on Non-functional requirements, which are often not visible to the end user in normal operation.
  • Requires time of scarce resources. One thing virtually all approaches to RAD have in common is that there is much more interaction throughout the entire life-cycle between users and developers. In the waterfall model, users would define requirements and then mostly go away as developers created the system. In RAD users are involved from the beginning and through virtually the entire project. This requires that the business is willing to invest the time of application domain experts. The paradox is that the better the expert, the more they are familiar with their domain, the more they are required to actually run the business and it may be difficult to convince their supervisors to invest their time. Without such commitments RAD projects will not succeed.
  • Less control. One of the advantages of RAD is that it provides a flexible adaptable process. The ideal is to be able to adapt quickly to both problems and opportunities. There is an inevitable trade-off between flexibility and control, more of one means less of the other. If a project (e.g. life-critical software) values control more than agility RAD is not appropriate.
  • Poor design. The focus on prototypes can be taken too far in some cases resulting in a "hack and test" methodology where developers are constantly making minor changes to individual components and ignoring system architecture issues that could result in a better overall design. This can especially be an issue for methodologies such as Martin's that focus so heavily on the user interface of the system.[9]
  • Lack of scalability. RAD typically focuses on small to medium-sized project teams. The other issues cited above (less design and control) present special challenges when using a RAD approach for very large scale systems.[10][11][12]

See also

[edit]

Practical concepts to implement RAD:

Other similar concepts:

References

[edit]
  1. ^ Brooks, Fred (1986). Kugler, H.J. (ed.). No Silver Bullet Essence and Accidents of Software Engineering (PDF). Information Processing '86. Elsevier Science Publishers B.V (North-Holland). ISBN 0-444-70077-3. Retrieved 2 July 2014.
  2. ^ a b Boehm, Barry (May 1988). "A Spiral Model of Software Development" (PDF). IEEE Computer. doi:10.1109/2.59. S2CID 1781829. Archived from the original (PDF) on 29 March 2018. Retrieved 1 July 2014.
  3. ^ Kerr, James M.; Hunter, Richard (1993). Inside RAD: How to Build a Fully Functional System in 90 Days or Less. McGraw-Hill. ISBN 0-07-034223-7.
  4. ^ Drucker, Peter (3 November 2009). Post-Capitalist Society. Harper Collins e-books. ISBN 978-0887306204.
  5. ^ Martin, James (1991). Rapid Application Development. Macmillan. ISBN 0-02-376775-8.
  6. ^ Martin, James (1991). Rapid Application Development. Macmillan. pp. 81–90. ISBN 0-02-376775-8.
  7. ^ "The Disintegration of AD: Putting it Back Together Again" (PDF). gartner.com.br. Retrieved 13 April 2010.
  8. ^ Beck, Kent (2000). Extreme Programming Explained. Addison Wesley. pp. 3–7. ISBN 0201616416.
  9. ^ Gerber, Aurona; Van Der Merwe, Alta; Alberts, Ronell (16–18 November 2007). "Practical Implications of Rapid Development Methodologies". Proceedings of the Computer Science and Information technology Education Conference, CSITEd-2007. Computer Science and IT Education Conference. Mauritius. pp. 233–245. CiteSeerX 10.1.1.100.645. ISBN 978-92025-08-07-6.
  10. ^ Andrew Begel, Nachiappan Nagappan (September 2007). "Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study" (PDF). First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007). pp. 255–264. doi:10.1109/esem.2007.12. ISBN 978-0-7695-2886-1. S2CID 1941370.
  11. ^ Maximilien, E.M.; Williams, L. (2003). "Assessing test-driven development at IBM". 25th International Conference on Software Engineering, 2003. Proceedings. pp. 564–569. doi:10.1109/icse.2003.1201238. ISBN 0-7695-1877-X. S2CID 16919353.
  12. ^ Stephens, Matt; Rosenberg, Doug (2003). Extreme Programming Refactored: The Case Against XP. doi:10.1007/978-1-4302-0810-5. ISBN 978-1-59059-096-6. S2CID 29042153.

Further reading

[edit]
拉磨是什么意思 派出所传唤是什么意思 世界上最毒的蜘蛛叫什么 高血压属于什么科 一产二产三产分别包括什么
做梦坐飞机是什么意思 中午吃什么饭家常菜 右脚后跟疼是什么原因 减肥期间吃什么主食 脊膜瘤是什么样的病
攻读学位填什么 什么人不用电 肚子痛什么原因 羟苯乙酯是什么 斜视是什么症状
鸩杀是什么意思 adr是什么意思 什么心什么气 什么是裙带菜 黄色分泌物是什么原因
己巳是什么意思hcv8jop4ns1r.cn 胰腺炎的症状是什么hcv9jop5ns8r.cn 519是什么星座hcv8jop6ns1r.cn other是什么意思hcv9jop5ns3r.cn 茉莉龙珠是什么茶hcv7jop5ns4r.cn
葛根粉有什么功效hcv9jop5ns6r.cn 有炎症吃什么药0297y7.com 呼吸衰竭是什么意思hanqikai.com 什么有什么zsyouku.com 什么应外合hcv8jop7ns6r.cn
泰勒为什么叫霉霉hcv8jop9ns1r.cn 一个令一个瓦念什么hcv9jop6ns7r.cn 正方体体积公式是什么hcv9jop5ns4r.cn 省略号的作用是什么hcv8jop2ns5r.cn 南京为什么叫金陵hcv7jop4ns6r.cn
清明节吃什么jiuxinfghf.com 孩子肚子疼是什么原因hcv8jop9ns9r.cn 梦见挖土豆是什么意思hcv8jop9ns5r.cn 活字印刷术是什么时候发明的hlguo.com 梦见挖坑什么意思hcv7jop5ns0r.cn
百度