Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Software Development Methods Methodologies

Software Development Methods Methodologies

Ratings: (0)|Views: 260 |Likes:
Published by Thomas John Bindi
Software development methodologies
Software development methodologies

More info:

Published by: Thomas John Bindi on Jun 26, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Software development methods/methodologiesOVERVIEW OF SOFTWARE DEVELOPMENT METHODS
A Software Development Method; otherwise known as Software DevelopmentMethodology refers to theframeworkthat is used to structure, plan, andcontrol the process of developing an information system. A wide variety of suchframeworks have evolved over the years, each with its own recognizedstrengths and weaknesses. What is worth noting of them is that one systemdevelopment methodology is not necessarily suitable for use by all projects.Each of the available methodologies is best suited to specific kinds of projects,based on various technical, organizational, project and team considerations.Any framework of a software development methodology consists of:
Asoftware development philosophy, with the approach or approaches ofthe software development process. This requires having a thoroughunderstanding of the intended method.
Multiple tools, models and methods, to assist in the software developmentprocess.These frameworks are often bound to some kind of organization, which furtherdevelops, supports the use, and promotes the methodology. The methodology isoften documented in some kind of formal documentation.
One of the oldest software development tools isflowcharting, which has itsroots in the 1920s. The software development methodology didn't emerge untilthe 1960s. According to Elliott (2004) theSystems development life cycle (SDLC) can be considered to be the oldest formalizedmethodologyfor building
information systems. The main idea of the SDLC has been "to pursue thedevelopment of information systems in a very deliberate, structured andmethodical way, requiring each stage of thelife cyclefrom inception of the ideato delivery of the final system, to be carried out in rigidly and sequentially". Themain target of this methodology in the 1960s has been "to develop large scalefunctionalbusiness systemsin an age of large scale business conglomerates.Information systems activities revolved around heavydata processingandnumber crunchingroutines".
Specific software development methodologies
Structured programmingsince 19691980s
Object-oriented programming(OOP) has been developed since the early1960s, and developed as the dominant programming methodology duringthe mid-1990s.
Scrum(development), since the late 1990s
Team software processdeveloped by Watts Humphrey at theSEI  2000s
Rational Unified Process(RUP) since 1998.
Agile Unified Process(AUP) since 2005 byScott Ambler 
Software development approaches
Every software development methodology has more or less its own approach tosoftware development. There is a set of more general approaches, which aredeveloped into several specific methodologies. These approaches are:
Waterfall: linear framework type.
Prototyping: iterative framework type
Incremental: combination of linear and iterative framework type
Spiral: combination linear and iterative framework type
Rapid Application Development (RAD): Iterative Framework Type. A b
Waterfall model
Thewaterfall modelis a sequential development process, in which developmentis seen as flowing steadily downwards (like a waterfall) through the phases ofrequirements analysis, design, implementation, testing (validation), integration,and maintenance. The first formal description of the waterfall model is oftencited to be an article published byWinston W. Roycein 1970 although Royce didnot use the term "waterfall" in this article.Basic principles of the waterfall model are:
Project is divided into sequential phases, with some overlap and splashback acceptable between phases.
Emphasis is on planning, time schedules, target dates, budgets andimplementation of an entire system at one time.
Tight control is maintained over the life of the project through the useof extensive written documentation, as well as through formal reviewsand approval/signoff by the user and information technology managementoccurring at the end of most phases before beginning the next phase.

Activity (29)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
roshaun007 liked this
mtmerin liked this
azharnizam liked this
roshaun007 liked this
roshaun007 liked this
kilama liked this
Steeza Smally liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->