Agile software development is a conceptual framework for undertaking software engineering projects. There are a number of agile software development methodologies e.g. Crystal Methods, Dynamic Systems Development Model (DSDM), and Scrum

Most agile methods attempt to minimize risk by developing software in short timeboxes, called iterations, which typically last one to four weeks. Each iteration is like a miniature software project of its own, and includes all the tasks necessary to release the mini-increment of new functionality: planning, requirements analysis, design, coding, testing, and documentation. While an iteration may not add enough functionality to warrant releasing the product, an agile software project intends to be capable of releasing new software at the end of every iteration. At the end of each iteration, the team reevaluates project priorities.

Agile methods emphasize realtime communication, preferably face-to-face, over written documents. Most agile teams are located in a bullpen and include all the people necessary to finish the software. At a minimum, this includes programmers and the people who define the product such as product managers, business analysts, or actual customers. The bullpen may also include testers, interface designers, technical writers, and management.

Agile methods also emphasize working software as the primary measure of progress. Combined with the preference for face-to-face communication, agile methods produce very little written documentation relative to other methods.

MDA provides an open, vendor-neutral approach to the challenge of interoperability, building upon and leveraging the value of OMG's established modeling standards: Unified Modeling Language (UML); Meta-Object Facility (MOF); and Common Warehouse Meta-model (CWM). Platform-independent Application descriptions built using these modeling standards can be realized using any major open or proprietary platform, including CORBA, Java, .NET, XMI/XML, and Web-based platforms.

As new platforms and technologies emerge, MDA enables rapid development of new specifications that use them, streamlining the process of integration. In this way, MDA goes beyond middleware to provide a comprehensive, structured solution for application interoperability and portability into the future. Creating Application and Platform Descriptions in UML provides the added advantage of improving application quality and portability, while significantly reducing costs and time-to-market.

The architecture encompasses the full range of pervasive services already specified by OMG, including Directory Services, Event Handling, Persistence, Transactions, and Security. The core logic of many of these services is already available for multiple implementation technologies; for instance, Sun's J2EE platform uses Java interfaces to CORBA's long-established transactions and security services. MDA makes it easier and faster to design similar multiple-platform interfaces to common services.

Most importantly, MDA enables the creation of standardized Domain Models for specific vertical industries. These standardized models can be realized for multiple platforms now and in the future, easing multiple platform integration issues and protecting IT investments against the uncertainty of changing fashions in platform technology.

Open source culture is the creative practice of appropriation and free sharing of found and created content. Examples include collage, found footage film, music, and appropriation art. Open source culture is one in which fixations, works entitled to copyright protection, are made generally available. Participants in the culture can modify those products and redistribute them back into the community or other organizations.

The rise of open-source culture in the 20th century resulted from a growing tension between creative practices that involve appropriation, and therefore require access to content that is often copyrighted, and increasingly restrictive intellectual property laws and policies governing access to copyrighted content. The two main ways in which intellectual property laws became more restrictive in the 20th century were extensions to the term of copyright (particularly in the United States) and penalties, such as those articulated in the Digital Millennium Copyright Act (DMCA), placed on attempts to circumvent anti-piracy technologies.

The idea of an "open source" culture runs parallel to "Free Culture," but is substantively different. Free culture is a term derived from the free software movement, and in contrast to that vision of culture, proponents of OSC maintain that some intellectual property law needs to exist to protect cultural producers. Yet they propose a more nuanced position than corporations have traditionally sought. Instead of seeing intellectual property law as an expression of instrumental rules intended to uphold either natural rights or desirable outcomes, an argument for OSC takes into account diverse goods (as in "the Good life") and ends.

The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. Also known as the spiral lifecycle model, it is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive and complicated projects.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project