A Description of A User Case Scenario of the use of the Unified Process Methodology and the Extreme Programming Methodology


Game software development is one of the most difficult types of software developments, which a software development team, has to develop. In the article chosen this week, the game development cycle, was analyzed, in order to understand The Unified Process or UP methodology and how it compare with the EXtreme Programming or XP methodology. The paper presented a hypothesis, which claims that the choice of the process for game software development, does not affect, the benefits of the game.

The senior and junior students of a college, came together for the development of video games, using the UP and the XP methodology, in order to study and compare these two widely-used software development processes. Teams of students, developed two different games, using the UP and the XP methodologies, in order to evaluate these methodologies and compare the two. Iterative and incremental, user case driven, architecture-centric and risk acknowledging are the four key elements of the Unified Process methodology according to Hunt. Inception, elaboration, construction and transition are the four phases of UP, and a distinct task, is accomplished at each of the stage. Requirements, analysis, design, implementation and testing are the disciplines or workflows of the UP methodology. An empirical analysis was conducted, in a software engineering course, about the XP and UP methods, during a 15 week period, by a group of students.

The class of twenty two students, were organized in six teams, which resulted in four team of four and two team of three people. The development of two games was carried out, using the built-in features of the Java language. Each team developed their product, using either the XP or the UP model, and the Super Nintendo game Super R-Type was used as the projects’ requirements, for one of the projects. The Super Nintendo game Castlevania: Dracula X was used for the requirements of a second project. Five steps were used to complete the project, in each step the UP or the XP methods were used, by each team.

The correspondent phases of the XP or UP model were used, in each of the five steps, to complete the product. Questionnaires were used by the researchers for the students, in order to see how the students felt, about them using the XP or the UP model.

The Eclipse Metric plug-in was used to collect twenty two metrics, in order to examine the code developed by each of the teams. The gathering and analysis, system design, system implementation and system testing, were the four categories, in which the questions were grouped. In terms of time spent on the project using the XP and UP methodology, the students claimed that the requirements gathering and the analysis, required less time, than the testing and implementation of the product. The most difficult activity was the implementation for both models, for each of the teams.

The majority of students felt, that the XP methodology though, was a much better methodology, than the UP methodology for their program. I feel the same way, although I haven’t actually done any project with the XP model, I thinks this model is one of the most revolutionizing methodology, in computer programming and software development, due to paired programming aspects of this methodology.




Thank you, for reading this article!!!



Add a Comment

Hernando Cadet

Hi every one, I obtained a bachelor's degree in Bioinformatics back in 2006, from Claflin University, after I received my bachelor's degree, I gained full time employment as a software engineer at a Video Relay Service company, maintaining databases and developing software for a new developed device called the VPAD.

I worked at that company for two years, then I became a web developer, and worked for a magazine for three years. After that job, I worked as a Drupal web developer, as a subcontractor for the NIH, for a year and then left the job to go back to school.

Hernando Cadet

Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without

Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without revolutionary ROI.