Iterative models of software development evolved to address issues raised by both waterfall and spiral approaches, with the goal of breaking large monolithic development projects into smaller, more easily managed iterations. Each iteration would produce a tangible deliverable (typically some executable element of the system under development).
The Objectory method  provides a good example of such an approach.In 1987, while assisting telecommunications company Ericsson AB with its software development efforts, and concerned with the shortcomings of earlier methods, Ivar Jacobson brought together a number of the development concepts he had been thinking about,such as use cases ,object-oriented design, and iterative development,to create a new approach to developing successful object-oriented applications. The Objectory method supported innovative techniques for requirements analysis, visual modeling of the domain, and an iterative approach to managing the execution of the project.In essence, Objectory would break down a project that might have been run in a large and inflexible waterfall manner into smaller,more easily understood, implemented,and tested iterations.Such an approach brought a number of important benefits for software quality:
The Objectory process was organized around three phases:
In its time, Objectory was considered to be a very successful software development method,and many of its key principles, such as use case analysis and design, continue to be widely used today.In 1991, after having worked closely with the Objectory process for several years, Ericsson AB purchased a major stake in Ivar Jacobson’s company(Objectory Systems), changing its name to Objectory AB.
In 1995,Objectory AB merged with the Rational Software Corporation, and shortly thereafter,the Rational Objectory Process version 4.0 was published, which incorporated elements of Grady Booch’s object-oriented analysis and design methodand Jim Rumbaugh’s object modeling technique(OMT ).Much of the procedural side of the Objectory method (such as use case modeling)was incorporated into the Rational Objectory Process, with the addition of many notational and diagramming elements from the OMT and Booch methods.
Ultimately, through an incremental process of extension and enhancement, the Rational Objectory Process evolved into the Rational Unified Process(RUP)version 5.0,which incorporated modeling and design extensions addressing business engineering, plus best practice guidance on configuration and change management, data engineering,and user interface design. The release of version 7 of RUP provides extensive best-practice guidance on traditional and agile software development and testing methods, such as the ability to optionally select an “extreme programming” style of development, as well as the means of customizing the RUP framework to support the user’s own specific agile approaches.
Agile Testing Related Interview Questions
|ETL Testing Interview Questions||Manual Testing Interview Questions|
|Selenium Interview Questions||Database Testing Interview Questions|
|Automation Testing Interview Questions||Software testing Interview Questions|
|Performance Testing Interview Questions||Embedded Testing Interview Questions|
|A/B Testing Interview Questions||Hadoop Testing Interview Questions|
Agile Testing Tutorial
Old-school Development And Testing
Agile Development And Testing
From Waterfall To Evolutionary Development And Test
How To Test A System That Is Never Finished
Implementing An Agile Testing Approach
Agile Testing In A Remote Or Virtual Desktop Environment
Testing A Derivatives Trading System In An Uncooperative Environment
A Mixed Approach To System Development And Testing: Parallel Agile And Waterfall Approach Streams Within A Single Project
Agile Migration And Testing Of A Large-scale Financial System
Agile Testing With Mock Objects: A Cast-based Approach
Agile Testing – Learning From Your Own Mistakes
Agile: The Emperor’s New Test Plan?
The Power Of Continuous Integration Builds And Agile Deve- Lopment
The Payoffs And Perils Of Offshored Agile Projects
The Basic Rules Of Quality And Management Still Apply To Agile
Test-infecting A Development Team
Agile Success Through Test Automation: An Extreme Approach
Talking, Saying, And Listening: Communication In Agile Teams
Very-small-scale Agile Development And Testing Of A Wiki
Agile Special Tactics: Soa Projects
The Agile Test-driven Methodology Experiment
When Is A Scrum Not A Scrum?
Analysis Of The Case Studies
My Agile Process
The Roll-out And Adoption Of My Agile Process
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.