POM2 Baselines

Using Inspyred for Python.  (http://pypi.python.org/pypi/inspyred)
May switch to DEAP, since no SPEA2 in Inspyred.  (http://code.google.com/p/deap/)


NSGA2:
table of data: http://justpaste.it/1la9
charts image: http://i.imgur.com/Ceuw8.png

PAES:
table of data: http://justpaste.it/1laa
charts image: http://i.imgur.com/SAl9D.png

NumEvals above are > 10,000
NumEvals below are < 20

RRSL:
tables of data: http://unbox.org/stuff/var/joe/joe/fall2012/pom2rrslTesting/data/

The Cloud is Large

pom2:

http://i.imgur.com/IMzQj.png

games: 

http://aimazed2d-web-dev-env.elasticbeanstalk.com/

cloud pricing:

EC2 Service for Web Hosting a container for Game Applications

http://aws.amazon.com/ec2/pricing/

Cliff notes:

* ~ 10 cents per HOUR of CPU

* ~ 12 cents per GB of data transferred

RDS Service for Relational Database Storage

http://aws.amazon.com/rds/pricing/

Cliff notes:

* ~ 12 cents per GB of storage

Typically; standard projects can expect to pay ~72$/month.
Several high-end gaming companies use Amazon Web Services:http://aws.amazon.com/solutions/case-studies/

pom2 & fun in games

pom2 graph: http://i.imgur.com/ffATu.png

Plans for fun games:
 - Prepare cog. tests: i.e. What dungeon parameters lead to highest user play time
 - Collect data: game dumps user data to server
 - - - Dungeon parameters used, total play time, explore ratios, speed of movement, items collected, etc
 - Analyze data: keys2?

POM2

In 2008, Dr. Menzies authored a paper titled "Using Simulation to Investigate Requirements Prioritization Strategies". This paper showed the effects of project and requirement dynamism on the software development processes. In the Spring of 2008, he tasked his Artificial Intelligence class to expand on this model.

Thus, POM2 was born. One of the main differences between POM and POM2 is that POM focused on small teams and small projects. POM2 built its model around the 5 different branches proposed by Dr. Turner and Dr. Boehm. This varied the project size as well as introducing other factors.

• Personnel - The number skill level of the staff
  
• Dynamism - The amount of project change
• Criticality - The impact of failure after deployment
• Culture - How accepting the staff is of change
• Size - The total number of staff across all teams
  

POM2 implimented all of the branches excluding Personnel. With the information available to us, Personnel was a wash. Better people cost more and produced more. Less talented people cost less and produced less. This lead to a near zero effect.

POM2 was then put through a Monte Carlo simulator while a KEYS search engine isolated the interesting areas in the simulator.

The main discovery is that Agile development methods performed as well as or better than Plan based development methods in all areas, especially excelling in dynamic environments. Further research is needed into the Personell and Criticality branches of POM2 to fully flesh out the model.

POM2 was accepted as a short paper to ASE'09. The full version of the paper can be found here, and the short version can be found here.