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
programming environments

programming environments

Ratings: (0)|Views: 65 |Likes:
Published by j2will
This paper examines three different team-oriented programming environemnts and discusses the advantages of each. The three environments are the RUP, UML, and XP programming methods.
This paper examines three different team-oriented programming environemnts and discusses the advantages of each. The three environments are the RUP, UML, and XP programming methods.

More info:

Published by: j2will on Nov 25, 2009
Copyright:Attribution Non-commercial


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





RUNNING HEADS: Programming Environments

Team-Oriented Programming Environments
James Williams
University of Phoenix Online
February 09, 2009

Team-Oriented Programming Environments

According to Woody (2008), Microsoft Windows Vista consists of 50 million lines of
code, Red hat Linux 7.1 has 30 million lines of codes, and Apple\u2019s Mac OS X 10.4 has 86
million lines of code. Such huge and sophisticated programs are far beyond the capabilities of a
single programmer and require teams of programmers to develop. These operating systems are
indicative of the sophistication and features of most modern applications require the same
amount of coordination, control, and cooperation between multiple teams over extended periods
of time . . . such is the nature of modern programming efforts. The current trend in application
development is projected to increase in complexity as the changing work environments and
business marketplace are transformed by innovations, socio-economic, political, and the mobility
of the workforce issues confronting businesses today. This increasing complexity creates a need
for some means of binding the programming efforts of team members situated in widely
dispersed areas into an effective and efficient system. This need is satisfied through the use of
team-oriented programming. According to Moore and Deek (2006) the development of a
programming environment that is conducive to teamwork on large-scale software systems prior
to implementation is as important as schematic diagrams are to building a stereo system from
component parts.

This paper will examine three different team-oriented programming environments by
describing the basic features of each product, examining its strengths, and illustrating the type of
environment best suited for each team environment. The three team-oriented programming
environments are the Rational Unified Process, UML, and Extreme Programming systems.

Analyses of the Programming Environments
Rational Unified Process (RUP) Environment

Feiler, Dart, and Downing (1988) report the rational unified process (RUP) environment
saw its beginnings in 1985. RUP started with application development and the Ada programming
language. This environment was later extended to include the C++ programming language. RUP
provides increased productivity to teams of developers working on mission critical applications
and can be executed on a wide assortment of computer platforms. The RUP features include
syntactic and semantic completion, incremental compilation, integrated configuration
management, and version control. The RUP environment also provided tools for iterative
development, component-based architecture, program modeling, continuous developer testing,
requirements management, and automated testing. RUP runs equally well on mainframe, mid-
sized, and microcomputer systems and contained code generators and code debuggers for Unix
and Windows NT operating systems.

Feiler, Dart, and Downing (1988) describe the RUP environment as a programming
environment centered on a team-based model that included the programmers, sales
representatives, and customers. This environment encouraged active in-depth engagement in
both pre-sales and post-sales phases of the development and held the programming team
accountable for the success of their customers in both the implementation of the application and
the customer\u2019s goals for increased revenue expected from the new application.

The programming environment, as described by Fieler, Dart, and Downing, has a user
interface that appears complicated and daunting with an entirely different keyboard for input.
But, these authors assert that the user interface is easy to learn due its uniformity of editing a
single programming language for both program code and command invocation, and key strokes

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)//-->