Programming Environments - Case Study Example

Team Oriented Programming Environments UML programming stands for Unified Modelling Language, which provides a “uniform definition of modelling a program.” (Perry, 2001:425). It is useful for database designers and database application writers, because a company which models a particular program will also have the option to share that program with other developers who are in the process of writing similar programs. The UML is not emerging as the defacto standard that is used in software analysis and modelling. The benefits associated with its use are as follows: (a) designs completed using UML can be re-used (b) Since the UML design can use different programming and database systems, it offers the facility of tool interoperability (c) it allows the facility of use in a team programming environment (d) data in the UML design appears alongside the resources, which can be tracked with the UML’s objects and (e) UML also allows the facility for dependency tracking.(Perry, 2001:426). Thus on this basis, UML modelling is useful in the context of software modelling because while it aid in software modelling, it does not replace programming, but rather enhances the programming such that the design of one system can also be used with other systems in order to improve overall online productivity. The disadvantages that are cited in the use of Unified Modelling Language, which have also produced resistance to their use in software modelling programs is their high cost. While it is an expensive option to use, it is not necessarily cost effective as well.(Arishom et al, 2006). As compared to this, the object oriented programming is based upon a rational model wherein as realists, we acknowledge that there is no single process, technique or language that would be applicable in all situations. Aspect oriented programming, associated with Gregor Kiczalis, can best be described through examples. For instance, when a change is required to an existing database that is also likely to impact upon other material in the database, most people would effect these changes by searching through the code and inserting calls to the logging method at appropriate places.(www.ibm.com). In a well structured system, such changes required may be minimal, but most systems are not so well structured that they require only a few changes; rather they may require lots of changes and a hierarchy of classes would be required to handle different files and databases. In the case of object oriented systems, the kinds of classes that are produced are difficult to change because the code cannot be reused. As a result, the nature of logging required is one that can cross cut across various systems, rather than being isolated into one or two systems and accomplish this end without changing the architecture. Aspect oriented programming that is based on rational methods therefore does not replace the programming that already exists, rather it works in conjunction with them to improve utility. Thus rational programming is similar to UML programming in that it does not replace already existing programming, but works in conjunction with it to improve the utility and functionality of the program. However it is not as expensive as UML. Extreme programming on the other hand, has been described as a deliberate and disciplined approach to software development.(www.extremeprogramming.org). As a result, the application of such methods will be especially relevant when working with risky projects that are dynamic and where the requirements are constantly changing. When extreme programming is used, simple rules and practices are applied, customers are also involved in the software development process and all these elements work together in a coordinated way, with unproductive activities being trimmed or eliminated in order to reduce the levels of frustration associated with using it. (www.extremeprogramming.com) Extreme programming therefore basically involves the coordination of all the various elements involved in a project and developing software on the basis of simplicity, communication and feedback. Software is developed in a manner wherein every element that contributes to it is considered a part of the team that is responsible for generating the project. One of the basic rules is simplicity, therefore planning and tracking is done using simple means, to determine what must be done next and in estimating the time frames for completion of the project. A team that follows the extreme programming style is based upon an integrated system. Programmers write the code for the software in pairs and in such a manner that it is consistent and can be understood by everyone and improved as may be necessary. The essence of extreme programming is simplicity, and it is similar to the UML programming because it also based upon the development of consistent, uniform code that can be applied uniformly across a variety of systems and can be used by a cross spectrum of programmers. But unlike the UML systems, the focus of extreme programming is simplicity and this also means that costs are kept down, whereas one of the greatest criticisms of UML, as mentioned earlier is its high costs. Extreme programming is also effective, whereas the efficacy of extreme programming has been questioned. It differs from the other two forms of programming because it is tightly disciplined and structured. Rational programming on the other hand, is different from extreme programming because it is specifically logged in a manner that enables it to network across different systems, without changing the basic structure of the architecture that is used in the system. Feedback is a characteristic of only the extreme programming system. When the objective of achieving group software development is concerned, it may thus be noted that extreme programming may offer the best possible solutions. Firstly, the basic premise is simplicity, as a result the programming produced is simple and can be comprehended easily by members of the group. Secondly, the code used is consistent and programmers write software code in pairs, which allows everyone to not only understand it easily but also to improve upon it as and when necessary. Since feedback is also an integral part of the extreme programming system, it allows various members of the team to provide their inputs which can then be integrated into the system. This is yet another aspect of extreme programming that is conducive towards team work. Since all elements of extreme programming are considered to be a part of an integrated system, it helps to provide an integrated framework which supports group work and working in teams. UML may be the least suited for team work. It provides uniformity in the modelling environment which is conducive towards the achievement among members of a team working on software, but its efficacy has been disputed in this respect. Since it may be a more expensive solution to use, it may not necessarily support widespread use among various members of a team. It may also be more complex to operate, understand and use across the system as compared to extreme programming and may not therefore be as suited to team work as extreme programming is. Rational programming may be helpful in team work, because it allows for interaction and networking among various systems. This allows members of different teams working on different systems to effectively network with each other. But the system may also be useful in that it recognizes that amendments and changes that are to be made to systems rarely call for minor changes; as a result the inherent complexity in software programming is recognized at the outset. Where extreme programming is concerned however, the objective at the very outset is to achieve simplicity and clarity, this facilitates comprehension among all members of a team through the absence of complexity. Being the only system that also allows for effective feedback and integrates every element of the software production process into an integrated whole, it is best suited for team work, where different members of a team must work on different projects as a coordinated whole and as an integrated entity. Unlike the other two kinds of software, extreme programming is directed towards ensuring clarity and comprehension, simplicity and structure which facilitates communication and understanding among members of a team. References: Arisholm, Erik, Briand, Lionel C, Hove, Siw Elisabeth and Labiche, Yvan, 2006. “The impact of UML documentation on software maintenance: an experimental evaluation”, IEEE Computer Society, http://www2.computer.org/portal/web/csdl/doi/10.1109/TSE.2006.59; Extreme Programming: A gentle introduction. http://www.extremeprogramming.org/; Perry, Greg, 2001. “Sams teach yourself programming in 24 hours”, Sams Publishing Read More