EXECUTIVE SUMMARY RESTful APIs are the industry standard used by companies to expose internal

A RESTful API defines a set of functions that developers can use to perform requests and receive responses via HTTP protocol, such as GET and POST. Because RESTful APIs use HTTP as a transport, they can be used by practically any programming language and are easy to test. It’s a requirement of a RESTful API that the client and server are loosely coupled and independent of each other, allowing

ATTACK VECTORS (EASY Exploitability): Any exposed API call can act like as an attack vector.

We can create a controller object to handle the REST requests (GET, POST). In this controller we can use action routing [48] to control which function will handle which request. In every function, we can do some computations with the data, make decisions and use the HTTP web client to construct and send responses to the partner end point URLs.

Establishing and enforcing policies, while providing infrastructure resources and services, consumable by orchestration and automation partners via standard APIs

Thus, the flexibility in SOA is made possible by loose coupling. However, optimization should be restricted to certain situations in SOA like when the Quality of Service (QoS) profiles are fixed and predetermined. Unfortunately, in the SOA environment optimization is an unfeasible expectation because of the dynamic environment of web services. Moreover, web service providers might not be willing to publish and create the profiles even though using QoS profiles are more reliable than other less-flexible optimization techniques. Thus, web services provide an organization with loosely coupled reusable software. Thus, this flexibility allows interoperability between systems to accomplish business functions. Further, business services can be completely allocated and decentralized over the Internet and collected by numerous communications

It defines the features available to the ruleset developers, describes how servers should work, and the behavior of the clients. The protocol and the framework were built using the agile software development method. Manageable sections were designed, built, and implemented in small increments. This allowed the framework to grow and for new features to be easily added, and minor releases helped the project move forward in a timely manner. The protocol was versioned which allowed the framework to continue to grow as well as new methods of gameplay to be created. Also, the client-server model allowed clients to be developed separately from game logic. Taking this into consideration, “Release-Reuse-Packages” and “Package by Feature” would be good options for this project. Since there are so many possibilities concerning what a customer can do with Thousand Parsec, Release-Reuse-Packages would give them the option of upgrading to a newer version or remaining with the old depending on their own intentions and how upgrading may effect their project. Since clients are developed apart from the game logic, and designs are done in short iterations, Package by Feature could also be a good fit for this

Mahmoud, Q.  (2005).  Service-Oriented Architecture (SOA) and Web Services: The Road to Enterprise Application Integration (EAI).  Retrieved from:  http://www.oracle.com/technetwork/articles/javase/soa-142870.html

Cloud Computing and Web Services have become well known services that companies have been using. Web services provide the ways that organizations can use applications to communicate with each other across the internet. Cloud computing provides various types of service, such as software as a service, where a provider gives the company software that they can use for their business functions. While this may seem that both types of services are different from each other, they do share similarities that companies should take notice. Service oriented architecture has also started to become a useful feature that helps with integration in companies. One problem is that some companies have difficulty in implementing service oriented architecture, but cloud computing has started to become an option that has caused an impact in service oriented architecture and integration.

(3) Web Services in the Cloud - instead of delivering full applications, this service allows users to access APIs for added functionality.

Drupal coding standards are independent of the version number, type and are "always-concurrent". All new code should follow current standards, regardless of initial type. Availed code found in an older version always needs updating, but it does not certainly have to be. Especially for larger code-bases (like Drupal core), updating the code of a previous version for your instant standards is too difficult a task. However, the code in current versions follows certain implementable standards.

PaaS provides sets of services and workflows that targets developers, who can use shared tools, technologies, processes and APIs to fast

The changeset method, however, comes with the need of data set construction in order to get to a certain version of it. For example, in order to check out the latest version of the data set, a build process is required starting from the initial version of the data set (version 1), incorporating each delta, all the way to the last version, traversing the complete version tree. A typical software project repository is composed of thousands of versions. Assuming most users are interested in the latest version of the data

45 Domain 5: Information Management and Data Security ..................................................................................................... 50 Domain 6: Interoperability and Portability .......................................................................................................................... 64 Section III. Operating in the Cloud ...................................................................................................................................... 73 Domain 7: Traditional Security, Business Continuity, and Disaster Recovery ..................................................................... 74 Domain 8: Data Center Operations ...................................................................................................................................... 89 Domain 9: Incident Response .............................................................................................................................................. 93 Domain 10: Application Security ........................................................................................................................................ 103 Domain 11: Encryption and Key Management .................................................................................................................. 129 Domain 12: Identity, Entitlement, and Access Management

The project aims to develop and sustain the necessary tooling that will assist Cloud application lifecycle management operations, using open standards and languages, where appropriate. As aforementioned, these operations are classified into three distinct categories: (1) application description, (2) application deployment and (3) application monitoring. Cloud application management framework (CAMF) will follow the Eclipse OSGi plug-in based software architecture for each of the aforementioned operations and will inherit the same look-and-feel that Eclipse users are accustomed to. To guarantee the quality of the resulting product, the project will follow designated development cycles with rigorous code reviews, unit tests and release cycles (eclipse, ND).

Software will undoubtedly undergo change after it is delivered to the customer. Change will occur because errors have been encountered, because the software must be adapted to accommodate changes in its external environment or because the customer requires functional or performance enhancements.