Development https://store.theartofservice.com/the-development-toolkit.html.

Development

Integrated development environment
An integrated development environment (IDE) or interactive development environment is a software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger. Several modern IDEs integrate with Intelli-sense coding features.

Integrated development environment
Many modern IDEs also have a class browser, an object browser, and a class hierarchy diagram, for use in object-oriented software development.

Integrated development environment Overview
IDEs are designed to maximize programmer productivity by providing tight-knit components with similar user interfaces. IDEs present a single program in which all development is done. This program typically provides many features for authoring, modifying, compiling, deploying and debugging software. This contrasts with software development using unrelated tools, such as vi, GCC or make.

Tighter integration of all development tasks has the potential to improve overall productivity beyond just helping with setup tasks

Some IDEs are dedicated to a specific programming language, allowing a feature set that most closely matches the programming paradigms of the language. However, there are many multiple-language IDEs, such as Eclipse, ActiveState Komodo, IntelliJ IDEA, Oracle JDeveloper, NetBeans, and Microsoft Visual Studio. Xcode, Xojo and Delphi are dedicated to a closed language or set of programming languages.

While most modern IDEs are graphical, text-based IDEs such as Turbo Pascal were in popular use before the widespread availability of windowing systems like Microsoft Windows and the X Window System (X11). They commonly use function keys or hotkeys to execute frequently used commands or macros.

Integrated development environment History
IDEs initially became possible when developing via a console or terminal

Maestro I is a product from Softlab Munich and was the world's first integrated development environment 1975 for software. Maestro I was installed for 22,000 programmers worldwide. Until 1989, 6,000 installations existed in the Federal Republic of Germany. Maestro I was arguably the world leader in this field during the 1970s and 1980s. Today one of the last Maestro I can be found in the Museum of Information Technology at Arlington.

One of the first IDEs with a plug-in concept was Softbench. In 1995 Computerwoche commented that the use of an IDE was not well received by developers since it would fence in their creativity.

Integrated development environment Visual programming
Visual programming is a usage scenario in which an IDE is generally required. Visual IDEs allow users to create new applications by moving programming, building blocks, or code nodes to create flowcharts or structure diagrams that are then compiled or interpreted. These flowcharts often are based on the Unified Modeling Language.

This interface has been popularized with the Lego Mindstorms system, and is being actively pursued by a number of companies wishing to capitalize on the power of custom browsers like those found at Mozilla

This approach is also used in specialist software such as Openlab, where the end users want the flexibility of a full programming language, without the traditional learning curve associated with one.

Integrated development environment Language support
Some IDEs support multiple languages, such as Eclipse, IntelliJ IDEA, MyEclipse or NetBeans, all based on Java, or MonoDevelop, based on C#.

Integrated development environment Language support
Support for alternative languages is often provided by plugins, allowing them to be installed on the same IDE at the same time. For example, Eclipse and Netbeans have plugins for C/C++, Ada, GNAT (for example AdaGIDE), Perl, Python, Ruby, and PHP, which are selected between automatically based on file extension, environment or project settings.

Integrated development environment Attitudes across different computing platforms
Unix programmers can combine command-line POSIX tools into a complete development environment, capable of developing large programs such as the Linux kernel and its environment

On the various Microsoft Windows platforms, command-line tools for development are seldom used. Accordingly, there are many commercial and non-commercial solutions, however each has a different design commonly creating incompatibilities. Most major compiler vendors for Windows still provide free copies of their command-line tools, including Microsoft (Visual C++, Platform SDK, .NET Framework SDK, nmake utility), Embarcadero Technologies (bcc32 compiler, make utility).

IDEs have always been popular on the Apple Macintosh's Mac OS, dating back to Macintosh Programmer's Workshop, Turbo Pascal, THINK Pascal and THINK C environments of the mid-1980s. Currently Mac OS X programmers can choose between native IDEs like Xcode and open-source tools such as Eclipse and Netbeans. ActiveState Komodo is a proprietary IDE supported on the Mac OS.

With the advent of cloud computing, some IDEs are available online and run within web browsers; example of this are Codeanywhere and Cloud9 IDE.

Microsoft Office 2010 History and development
Development started in 2007 while Microsoft was finishing work on Office 12, released as Microsoft Office The version number 13 was skipped because of the fear of the number 13. It was previously thought that Office 2010 (then called Office 14) would ship in the first half of 2009.

On January 10, 2009, screenshots of an Office 2010 alpha build were leaked by a tester.

On April 15, 2009, Microsoft confirmed that Office 2010 would be released in the first half of They announced on May 12, 2009, at a Tech Ed event, a trial version of the 64-bit edition. The Technical Preview 1 (Version: ) was leaked on May 15, 2009.

An internal post-beta build was leaked on July 12, This was newer than the official preview build and included a "Limestone" internal test application (note: the EULA indicates Beta 2). On July 13, 2009, Microsoft announced Office 2010 at its Worldwide Partner Conference 2009.

On July 14, 2009, Microsoft started to send out invitations on Microsoft Connect to test an official preview build of Office On August 30, 2009, the beta build 4417 was leaked on the internet via torrents.

The public beta was available to subscribers of TechNet, MSDN and Microsoft Connect users on November 16, On November 18, 2009, the beta was officially released to the general public at the Microsoft Office Beta website, which was originally launched by Microsoft on November 11, 2009, to provide screenshots of the new office suite. Office 2010 Beta was a free, fully functional version and expired on October 31, 2010.

In an effort to help customers and partners with deployment of Office 2010, Microsoft launched an Office 2010 application compatibility program with tools and guidance available for download. On February 5, 2010, the official release candidate build was available to Connect and MSDN testers. It was leaked to torrent sites. A few days after, the RTM Escrow build was leaked.

Microsoft announced the RTM on April 15, 2010, and that the final version was to have speech technologies for use with text to speech in Microsoft OneNote, Microsoft PowerPoint, Microsoft Outlook, and Microsoft Word

On June 15, 2010, Office 2010 was released to retail customers.

On November 17, 2010, Microsoft sent out invitations to a select number of testers at the Microsoft Connect portal to test a beta build of Office 2010 Service Pack 1 (SP1). The final version was released to the public on June 27, 2011, with a version number of

On April 8, 2013, a beta build of Office 2010 Service Pack 2 (SP2) was released. The final version was released on July 16, 2013, with a version number of

Microsoft Office 2007 Development
The first beta of Microsoft Office 2007, referred to as Beta-1 in s sent to a small number of testers, was released on November 16, The Beta-1 Technical Refresh was released to testers on March 13, The Technical Refresh fixed issues in installing with Windows Vista build 5308.

Office 2007 Beta 2 was announced by Bill Gates at WinHEC 2006, and was initially released to the public at no cost from Microsoft's web site

The beta versions continued to function in a reduced functionality mode after February 1, If users downloaded the Technical Refresh to update Beta 2, then users could use its full functionality until March 31, 2007 for client products and May 15, 2007 for server products. The Beta program ended on November 8, 2006, when Microsoft declared the product "Released to Manufacturing" (RTM) and started manufacturing the final product. After RTM, the availability of the beta download ended.

Office 2007 was released to volume licensing customers on November 30, 2006, and to the general public on January 30, 2007.

Development started in 2010 while Microsoft was finishing work on Office 14, released as Microsoft Office On January 30, 2012, Microsoft released a technical preview of Office 15, build , to a selected group of testers bound by non-disclosure agreements.

On July 16, 2012, Microsoft held a press conference to show off Office 2013 and to release the Consumer Preview. The Office 2013 Consumer Preview is a free, fully functional version but will expire 60 days after the final product's release. An update was issued for the Office 2013 Customer Preview suite on October 5.

Office 2013 was released to manufacturing on October 11, It was made available to TechNet and MSDN subscribers on October 24. On November 15, 2012, 60-days trial versions of Microsoft Office 2013 Professional Plus, Project Professional 2013 and Visio Professional 2013 were made available to the public over the Internet. Microsoft has released Office 2013 for general availability on 29 January 2013.

C (programming language) Early developments
The initial development of C occurred at AT&T Bell Labs between 1969 and 1973; according to Ritchie, the most creative period occurred in It was named "C" because its features were derived from an earlier language called "B", which according to Ken Thompson was a stripped-down version of the BCPL programming language.

The origin of C is closely tied to the development of the Unix operating system, originally implemented in assembly language on a PDP-7 by Ritchie and Thompson, incorporating several ideas from colleagues. Eventually they decided to port the operating system to a PDP-11. B's inability to take advantage of some of the PDP-11's features, notably byte addressability, led to the development of an early version of C.

The original PDP-11 version of the Unix system was developed in assembly language

Browser extension Development
Examples of those frameworks are Add-ons Framework which allows developer to build cross browser extensions for Internet Explorer, Firefox, Chrome, Safari and Opera, and the Crossrider development framework which allows developers to build cross browser extensions for Internet Explorer, Firefox, Chrome and Safari.

Cloud gaming Recent developments
In the year 2000, G-cluster, the original pioneer of cloud gaming demonstrated the technology on Electronic Entertainment Expo, E3. The original offering was cloud gaming service over WiFi to handheld devices.

Video Game developer Crytek began research on a cloud gaming system in 2005 for their game Crysis, but halted development in 2007 to wait until the infrastructure and cable net providers were up for the task.

On November 18, 2010, SFR launched a commercial cloud gaming service on IPTV in France, powered by G-cluster technology.

On March 10, 2010, OnLive officially launched

On February 27, 2011, Gaikai, which allows game publishers and others to embed free streaming gameplay trials on their web sites, launched its open beta with games from Electronic Arts including Dead Space 2, Mass Effect 2, and Sims 3

On March 10, 2011,Cloud Union, a Chinese cloud gaming company, launched cloud gaming services in China.

On April 28, 2011, Free, a French Internet service provider, launched "GameTree TV", a gaming on demand platform for the Freebox Revolution, its advanced IPTV set-top-box. The service is based on the GameTree TV platform by TransGaming Inc.

On September 8, 2011, Ubitus, a Taiwanese cloud computing company, launched G CLOUD service based on its product GameCloud, on NTT docomo LTE commercial network with NHN Japan collaboration

In July 2012, Sony purchased the largest cloud gaming service provider, Gaikai, for US$ 380 million.

In July 2012, Cloud Union's cloud gaming service subscribers exceeded 300,000.

In August 2012, Square Enix launched their Core Online games service, which offers free and advertising-supported access to some games from their catalog via a web browser. As of February 2013, there are four games available through the service: Hitman: Blood Money, Lara Croft and the Guardian of Light, Mini Ninjas and Tomb Raider: Underworld.

September 11, 2012 saw the launch of CiiNOW, a new cloud gaming platform. CiiNOW claims to have pioneered a new approach called hybrid streaming. Hybrid streaming consists of streaming graphics primitives as well as video simultaneously. It utilizes some processing on a client to achieve better quality at lower bandwidth.

October 11, 2012, Orange launches commercial cloud gaming service to all of its IPTV subscribers in France powered by G-cluster technology.

February 20, 2013, during the PlayStation 4 announcement, Sony revealed that it will use its new acquisition of Gaikai to power cloud gaming services for the PlayStation 4, with the eventual goal of making the entire PlayStation catalog available to stream.

On April 17, 2013 the first open source cloud gaming system, GamingAnywhere, was released. GamingAnywhere allows researchers to test their new ideas on a real testbed, service providers to build their services on top of it, and end users to set up game servers using their home workstations (and play anywhere, anytime).

At the Electronic Entertainment Expo in 2013, Sony announced that PlayStation’s cloud gaming services will be available in the United States in The service will be powered by Gaikai and stream PlayStation 3 titles to owners of PlayStation 4, PlayStation 3, and PlayStation VITA.

American Registry for Internet Numbers Policy development services
Policy development services facilitate the development of policy for the technical coordination and management of Internet number resources.

All ARIN policies are set by the community. Everyone is encouraged to participate in the policy development process at public policy meetings and on the Public Policy Mailing List. The ARIN Board of Trustees ratifies policies only after:

discussion on mailing lists and at meetings;

ARIN Advisory Council recommendation;

community consensus in favor of the policy; and

The community develops policies by following a formal Policy Development Process as outlined at The Number Resource Policy Manual, ARIN’s complete set of current policies, is available at

Membership is not required to participate in ARIN’s policy development process or to apply for Internet number resources.

Maintaining discussion lists

Debian Development procedures
Software packages in development are either uploaded to the project distribution named unstable (also known as sid), or to the experimental repository

After a version of a software package has remained in unstable for a certain length of time (depending on the urgency of the software's changes), that package is automatically migrated to the testing distribution. The package's migration to testing occurs only if no serious (release-critical) bugs in the package are reported and if other software needed for package functionality qualifies for inclusion in testing.

Since updates to Debian software packages between official releases do not contain new features, some choose to use the testing and unstable distributions for their newer packages

After the packages in testing have matured and the goals for the next release are met, the testing distribution becomes the next stable release. The timing of the release is decided by the Release Managers, and in the past the exact date was rarely announced earlier than a couple of weeks beforehand.

Debian Time-based development schedule
For Debian 6.0 (squeeze) a new policy of time-based development freezes on a two-year cycle was announced

Citizendium Later developments
At the project's one-year anniversary in September 2007, Citizendium included 3000 articles written and revised by 2000 people

Citizendium was honored on 5 December 2007, as an award finalist of the Society for New Communications Research. The Society describes itself as a nonprofit global think-tank "dedicated to the advanced study of new communications tools, technologies and emerging modes of communication, and their effect on traditional media, professional communications, business, culture and society". The Society chose Citizendium for an award because it considered it "a leading organization" in these respects.

Library writer Walt Crawford noted in April 2009 that Citizendium appeared to be in an "extended lull", with a constant rate of creation of new articles at around 13–14 per day and a decline in the number of active authors

The project had a core of 25 contributors who made more than 100 edits a month, with 90 participants making at least one edit, during March 2010

Baidu Development In 1994, Robin Li joined IDD Information , a New Jersey division of Dow Jones and Company, where he helped develop software for the online edition of the Wall Street Journal. He also worked on developing better algorithms for search engines and remained at IDD Information from May 1994 to June 1997.

Baidu Development In 1996, while at IDD, Li developed the RankDex site-scoring algorithm for search engines results page ranking and received a US patent for the technology. He later used this technology for the Baidu search engine.

Baidu Development On July 31, 2012, Baidu announced they would team up with Sina to provide mobile search results.

Baidu Development On November 18, 2012, Baidu announced that they would be partnering with Qualcomm to offer free cloud storage to Android users with Snapdragon processors.

Baidu Development On August 2, 2013, Baidu launched Personal Assistant app for businessperson, to help CEOs, managers and the white-collars manage their business relationships.

Baidu Development On August 14, 2013, Baidu announced that its wholly owned subsidiary Baidu (Hong Kong) Limited has signed a definitive merger agreement (the "Agreement") to acquire a 100 percent equity interest in 91 Wireless Web-soft Limited from NetDragon Web-soft Inc.

Communications protocol Protocol development
For communication to take place, protocols have to be agreed upon. Recall that in digital computing systems, the rules can be expressed by algorithms and datastructures, raising the opportunity of hardware independence. Expressing the algorithms in a portable programming language, makes the protocolsoftware operating system independent. The sourcecode could be considered a protocol specification. This form of specification, however is not suitable for the parties involved.

For one thing, this would enforce a source on all parties and for another, proprietary software producers would not accept this

This activity is referred to as protocol development

It should be noted though that in some cases protocol standards are not sufficient to gain widespread acceptance i.e. sometimes the sourcecode needs to be disclosed enforced by law or the government in the interest of the public.

Alibaba Group Research and development
Alibaba introduced the Alibaba Group R&D institute in One year later, Alibaba filed around 350 patent and utiliy model applications.

Béla H. Bánáthy White Stag Leadership Development Program
Following on his interest in leadership development for youth that he had nurtured in Hungary, in 1957 Bánáthy began experimenting with a concept for a leadership development program

As part of his master's degree program in counseling psychology at San José State University, he wrote a thesis titled "A Design for Leadership Development in Scouting"

In the 1970s, due to the success of the White Stag program, Bánáthy was appointed to the Interamerican Scout Committee and participated in three interamerican "Train the Trainer" events in Mexico, Costa Rica, and Venezuela. He guided their national training teams in designing leadership development by design programs. Béla also taught in Sunday School and was on the Board of the United Methodist Church of the Wayfarer in Carmel, California.

BitTorrent Development
An unimplemented (as of February 2008) unofficial feature is Similarity Enhanced Transfer (SET), a technique for improving the speed at which peer-to-peer file sharing and content distribution systems can share data

BitTorrent Development
As of December 2008, BitTorrent, Inc. is working with Oversi on new Policy Discover Protocols that query the ISP for capabilities and network architecture information. Oversi's ISP hosted NetEnhancer box is designed to "improve peer selection" by helping peers find local nodes, improving download speeds while reducing the loads into and out of the ISP's network.

Device driver Development
Writing a device driver requires an in-depth understanding of how the hardware and the software of a given platform function

The task of writing drivers thus usually falls to software engineers or computer engineers who work for hardware-development companies

The Kernel-Mode Driver Framework (KMDF) model continues to allow development of kernel-mode device drivers, but attempts to provide standard implementations of functions that are known to cause problems, including cancellation of I/O operations, power management, and plug and play device support.

Apple has an open-source framework for developing drivers on Mac OS X called the I/O Kit.

Art history Other recent developments
In recent years there have been advances on the history and development of Fine Art. A Most notable example being Larry Shiners The Invention of Art: A Cultural History which proposes that Fine Art is a modern invention due to social transformations of the 18th century.

"There was a traditional “system of the arts” in the West before the eighteenth century

Similar ideas have been expressed by Pierre Bourdieu, Paul Mattick, and Terry Eagleton.

"It is a sad fact: art history lags behind the study of the other arts..

The development of good colour photography, now held digitally and available on the internet or by other means, has transformed the study of many types of art, especially those covering objects existing in large numbers which are widely dispersed among collections, such as illuminated manuscripts and Persian miniatures, and many types of archaeological artworks.

JavaScript Later developments
JavaScript has become one of the most popular programming languages on the web

JavaScript Later developments
In January 2009, the CommonJS project was founded with the goal of specifying a common standard library mainly for JavaScript development outside the browser.

JavaScript Development tools
Within JavaScript, access to a debugger becomes invaluable when developing large, non-trivial programs. Because there can be implementation differences between the various browsers (particularly within the Document Object Model), it is useful to have access to a debugger for each of the browsers that a web application targets.

Script debuggers are available for Internet Explorer, Firefox, Safari, Google Chrome, and Opera.

Three debuggers are available for Internet Explorer: Microsoft Visual Studio is the richest of the three, closely followed by Microsoft Script Editor (a component of Microsoft Office), and finally the free Microsoft Script Debugger which is far more basic than the other two

Web applications within Firefox can be debugged using the Firebug add-on, or the older Venkman debugger. Firefox also has a simpler built-in Error Console, which logs and evaluates JavaScript. It also logs CSS errors and warnings.

Opera includes a set of tools called Dragonfly.

WebKit's Web Inspector includes a JavaScript debugger, which is used in Safari. A modified version is used in Google Chrome.

Some debugging aids are themselves written in JavaScript and built to run on the Web. An example is the program JSLint, developed by Douglas Crockford who has written extensively on the language. JSLint scans JavaScript code for conformance to a set of standards and guidelines.

Burroughs Corporation Developments and innovations
The Burroughs Corporation developed three highly innovative architectures, based on the design philosophy of "language directed design". Their machine instruction sets favored one or many high level programming languages, such as ALGOL, COBOL or FORTRAN. All three architectures were considered mainframe class machines:

The Burroughs large systems machines started with the B5000 in 1961

Burroughs produced the B2500 or "medium systems" computers aimed primarily at the business world. The machines were designed to execute COBOL efficiently. This included a BCD (Binary Coded Decimal) based arithmetic unit, storing and addressing the main memory using base 10 numbering instead of binary. The designation for these systems was Burroughs B2500 through B49xx, followed by Unisys V-Series V340 through V560.

Burroughs produced the B1700 or "small systems" computers that were designed to be microprogrammed, with each process potentially getting its own virtual machine designed to be the best match to the programming language chosen for the program being run.

The smallest general-purpose computers were the B700 "microprocessors" which were used both as stand-alone systems and as special-purpose data-communications or disk-subsystem controllers.

Burroughs also manufactured an extensive range of accounting machines including both stand-alone systems such as the Sensimatic, L500 and B80, and dedicated terminals including the TC500 and specialised check processing equipment.

In 1982, Burroughs began producing personal computers, the B20 and B25 lines with the Intel 8086/8088 family of 8-bit chips as the processor. These ran the BTOS Operating System, which Burroughs licensed from Convergent Technologies. These machines implemented an early Local Area Network to share a hard disk between workgroup users. These microcomputers were later manufactured in Kunming, China for use in China under agreement with Burroughs.

Burroughs collaborated with University of Illinois on a multiprocessor architecture developing the ILLIAC IV computer in the early 1960s. The ILLIAC had up to 128 parallel processors while the B6700 & B7700 only accommodated a total of 7 CPUs and/or IO units (the 8th unit was the memory tester).

Burroughs made military computers, such as the D825 (the "D" prefix signifying it was for defense industrial use), in its Great Valley Laboratory in Paoli, Pennsylvania. The D825 was, according to some scholars, the first true multiprocessor computer. Paoli was also home to the Defense and Space Group Marketing Division.

In 1964 Burroughs had also completed the D830 which was another variation of the D825 designed specifically for real-time applications, such as airline reservations

Burroughs developed a half-size version of the D825 called the D82, cutting the word size from 48 to 24 bits and simplifying the computer's instruction set

Vendor relationship management VRM development work
As of August 2010 ProjectVRM lists nineteen VRM development efforts. These include:

Linux Current development
Torvalds continues to direct the development of the kernel

Blackfin Development tools software
ADI provides its own software development toolchain, CROSSCORE® (VisualDSP++), but other options are also available, such as Green Hills Software's MULTI IDE, the GNU GCC Toolchain for the Blackfin processor family, the OpenEmbedded project, National Instruments' LabVIEW Embedded Module, or Microsoft Visual Studio through use of AxiomFount's AxiDotNet (integrated .NET Micro Framework based) solutions.

Digital Enhanced Cordless Telecommunications Technical development and adoption
The DECT standard was developed by ETSI in several phases, the first of which took place between 1988 and 1992 when the first round of standards were published. These were the ETS series in 9 parts defining the air interface, and ETS defining how the units should be type approved. A technical report, ETR-178, was also published to explain the standard. Subsequent standards were developed and published by ETSI to cover interoperability profiles and standards for testing.

Initially named "Digital European Cordless Telephone" at its launch by CEPT in November 1987, following a suggestion by Enrico Tosato of Italy, its name was soon changed to "Digital European Cordless Telecommunications" to reflect its broader range of application, including data services

DECT was developed by ETSI but has since been adopted by many countries all over the world

Blender (software) Development
Since the opening of the source, Blender has experienced significant refactoring of the initial codebase and major additions to its feature set.

Improvements include an animation system refresh; a stack-based modifier system; an updated particle system (which can also be used to simulate hair and fur); fluid dynamics; soft-body dynamics; GLSL shaders in the game engine; advanced UV unwrapping; a fully recoded render pipeline, allowing separate render passes and "render to texture"; node-based material editing and compositing; Projection painting.

Part of these developments were fostered by Google's Summer of Code program, in which the Blender Foundation has participated since 2005.

Blender has come a long way since then. The current stable release version is 2.68a (as of 24 July 2013), a bugfix release to the previous version 2.68 that was released on July 18, 2013.

Version 2.68 included many enhancements to its existing platform, but was mostly bugfixes over It was released with the addition of Texture Atlas for baking shadows and lightmaps for an entire scene, and the Edit Linked Library, for quick editing of linked assets.

The enhancements include the following but is not limited to:

Mask modifier for sequencer strips

Better key shortcuts display

Quick enabling and disabling of multiple layers

Auto indent for multi-line Python statements

Auto keyframe selection

Improved smoke simulation to avoid blockiness

Multiple modeling improvements (on existing features)

A Python Security protocol was included as well. This disabled python scripting on .blend file start-up to prevent malicious actions on load. This feature is accessible in the User Preferences and can be turned off or on.

Access Linux Platform Application development
The Access Linux Platform presents standard APIs for most common operations (as defined by the POSIX and LSB standards). Since neither POSIX nor LSB address areas such as telephony, device customization, messaging, etc., there are a number of additional frameworks and APIs defined by Access for these areas.

Applications for ALP can be developed as Linux-native code in C or C++, as legacy Palm OS applications (which run in the Garnet VM emulation environment), or in Java. Additional execution environments can be supported via the development of a "launchpad" utilized by the Application Manager (part of the Hiker framework).

The ALP SDK uses an Eclipse-based IDE, with additional plug-ins, as did its predecessor Palm OS development environment. The compilers used are EABI-enabled ARM versions of the standard gcc tool chain.

Business model Definitions of business model design or development
Zott and Amit (2009) consider business model design from the perspectives of design themes and design content. Design themes refer to the system’s dominant value creation drivers and design content examines in greater detail the activities to be performed, the linking and sequencing of the activities and who will perform the activities.

Analog television Development
The earliest mechanical television systems used spinning disks with patterns of holes punched into the disc to "scan" an image

Analog television Development
Analog television did not really begin as an industry until the development of the cathode-ray tube (CRT), which uses a steered electron beam to "write" lines of electrons across a phosphor coated surface

Yelp, Inc. 2005 to 2010: Development and expansion
In 2005, Yelp Inc. began adding social networking features to its website and formed a group of super-users called, The Yelp Elite. These elite users were rewarded by being invited to parties and other special events sponsored by Yelp. The number of reviewers grew from 12,000 in 2005, to 100,000 reviewers in 2006 and by 2007 the website had received one million user-submitted reviews of local businesses. In 2008, website traffic increased to fifteen million visitors per month.

Yelp Inc. obtained $5 million in venture funding from Bessemer Venture Partners in October 2005 to fund expansion into the New York City, Chicago and Boston markets. In October 2006, Benchmark Capital made a $10 million investment, which was followed by a $15 million investment from DAG Ventures in February In January 2010, Yelp Inc. obtained $100 million in venture capital from Elevation Partners which was used to increase their sales staff.

In 2008, Yelp Inc

That December, Google entered into negotiations with Yelp Inc. to acquire the company, but the two parties failed to reach an agreement. According to The New York Times, Google had offered "more than $500 million" but the deal was derailed after Yahoo offered $1 billion. Tech Crunch reported that Google refused to match Yahoo's offer. Then, Yelp Inc.'s management team and board of directors could not reach an agreement on the terms of the sale and both offers were abandoned.

San Francisco, where Yelp was founded, remained the most active as of 2008, though there was significant adoption in 18 metro areas including Boston, Chicago, New York, Washington, D.C., San Diego, and Los Angeles

In January 2010, Yelp Inc. instituted Internet "check in" features that put the company in competition with social networking company Foursquare. That June, Yelp incorporated OpenTable's restaurant reservation features into its website.

In September, two economists from the University of California, Berkeley surveyed 300 restaurants in San Francisco, California, and correlated their evening reservations rates with their rating on the company's website

Yelp, Inc. 2011 to present: Further development and public stock offering
Yelp Inc. began offering a service called Yelp Deals in April 2011 and the service became available to Android and iPhone apps in June. By August, Yelp Inc. had cut back on the frequency of its offering of Yelp Deals and was planning to cut its Yelp Deals sales staff in half, due to increased competition and market saturation.

That September, Yelp Inc. participated in the Federal Trade Commission's investigation of alleged anti-competition practices by Google. Yelp Inc. alleged that Google Places was using its web content without disclosing the source. It also alleged Google favored Google Places over the Yelp website in its consumer search engine.

That November, Yelp Inc

The company's website content was integrated into the mapping and directions app in Apple's September 2012 release of iOS 6. The company reported in November 2012 that 45% of its web traffic came from mobile devices. The same year Yelp Inc. made an agreement to acquire its largest European rival, Qype, for $50 million. The following year, Stoppelman reduced his CEO salary to $1, and began receiving compensation exclusively through his stock options.

In 2013 Yelp Inc. acquired the start-up, online reservation company, SeatMe, for $12.7 million in cash and company stock. That year the company began adding food ordering and delivery options and displaying restaurant hygiene inspection scores on the website. According to a September 2013 article by CNN, Yelp Inc.'s second quarter revenue "exceeded expectations" but like "many other Internet darlings, has yet to turn a profit."

Bell Labs Discoveries and developments
At its peak, Bell Laboratories was the premier facility of its type, developing a wide range of revolutionary technologies, including radio astronomy, the transistor, the laser, information theory, the UNIX operating system, the C programming language and the C++ programming language. Seven Nobel Prizes have been awarded for work completed at Bell Laboratories.

1937: Clinton J. Davisson shared the Nobel Prize in Physics for demonstrating the wave nature of matter.

1977: Philip W. Anderson shared the Nobel Prize in Physics for developing an improved understanding of the electronic structure of glass and magnetic materials.

1978: Arno A. Penzias and Robert W. Wilson shared the Nobel Prize in Physics. Penzias and Wilson were cited for their discovery of cosmic microwave background radiation, a nearly uniform glow that fills the Universe in the microwave band of the radio spectrum.

1997: Steven Chu shared the Nobel Prize in Physics for developing methods to cool and trap atoms with laser light.

1998: Horst Störmer, Robert Laughlin, and Daniel Tsui, were awarded the Nobel Prize in Physics for the discovery and explanation of the fractional quantum Hall effect.

2009: Willard S. Boyle, George E. Smith shared the Nobel Prize in Physics together with Charles K. Kao. Boyle and Smith were cited for the invention of charge-coupled device (CCD) semiconductor imaging sensors.

The Turing Award has twice been won by Bell Labs researchers:

1968: Richard Hamming for his work on numerical methods, automatic coding systems, and error-detecting and error-correcting codes.

1983: Ken Thompson and Dennis Ritchie for their work on operating systems theory, and their development of Unix.

Amazon.com Software development centers
While much of Amazon's software development occurs in Seattle, the company employs software developers in centers across the globe. Some of these sites are run by an Amazon subsidiary called A2Z Development.

USA: Cambridge, MA; Charleston, SC; Cupertino, CA; Orange County, CA; San Francisco, CA; San Luis Obispo, CA; Seattle, WA; New York, NY and Tempe, AZ

Canada: Vancouver, British Columbia, Toronto downtown and Mississauga, Ontario

UK: Slough (England), London (England) and Edinburgh (Scotland)

South Africa: Cape Town

Conventional PCI Development tools
When developing and/or troubleshooting the PCI bus, examination of hardware signals can be very important. Logic analyzers and bus analyzers are tools which collect, analyze, and decode signals for users to view in useful ways.

DVB-H Development tools
The open-source AMUSE DVB-H tools are capable of generating a DVB-H signal from one or more IP streams.

Democracy Development
Several philosophers and researchers outlined historical and social factors supporting the evolution of democracy. Cultural factors like Protestantism influenced the development of democracy, rule of law, human rights and political liberty (the faithful elected priests, religious freedom and tolerance has been practiced).

Others mentioned the influence of wealth (e.g. S. M. Lipset, 1959). In a related theory, Ronald Inglehart suggests that the increase in living standards has convinced people that they can take their basic survival for granted, and led to increased emphasis on self-expression values, which is highly correlated to democracy.

Carroll Quigley concludes that the characteristics of weapons are the main predictor of democracy: Democracy tends to emerge only when the best weapons available are easy for individuals to buy and use

Recently established theories stress the relevance of education and human capital and within them of cognitive ability to increasing tolerance, rationality, political literacy and participation. Two effects of education and cognitive ability are distinguished: a cognitive effect (competence to make rational choices, better information processing) and an ethical effect (support of democratic values, freedom, human rights etc.), which itself depends on intelligence.

Evidence that is consistent with conventional theories of why democracy emerges and is sustained has been hard to come by

In the 21st century, democracy has become such a popular method of reaching decisions that its application beyond politics to other areas such as entertainment, food and fashion, consumerism, urban planning, education, art, literature, science and theology has been criticized as "the reigning dogma of our time"

In 2010 a study by a German military think tank has analyzed how peak oil might change the global economy. The study raises fears for the survival of democracy itself. It suggests that parts of the population could perceive the upheaval triggered by peak oil as a general systemic crisis. This would create "room for ideological and extremist alternatives to existing forms of government".

Robert Michels asserts that although democracy can never be fully realized, democracy may be developed automatically in the act of striving for democracy: "The peasant in the fable, when on his death-bed, tells his sons that a treasure is buried in the field

Governmentality Further developments of the concept
Hunt and Wickham, in their work Foucault and Law [1994] begin the section on governmentality with a very basic definition derived from Foucault’s work

Kerr’s approach to the term is more complex

Dean’s understanding of the term incorporates both other forms of governance and the idea of mentalities of government, as well as Hunt and Wickham’s, and Kerr’s approaches to the term

Dean's main contribution to the definition of the term, however, comes from the way he breaks the term up into ‘govern’ ‘mentality’, or mentalities of governing—mentality being a mental disposition or outlook

On the one hand, we govern others and ourselves according to what we take to be true about who we are, what aspects of our existence should be worked upon, how, with what means, and to what ends. On the other hand, the ways in which we govern and conduct ourselves give rise to different ways of producing truth. [1999:18]

By drawing attention to the ‘how and why’, Dean connects "technologies of power" [Lemke, 2001:191] to the concept of governmentality

The semantic linking of governing and mentalities in governmentality indicates that it is not possible to study technologies of power without an analysis of the underpinning them. The practice of going to the gym, expounded below, is a useful example because it shows how our choices, desires, aspirations, needs, wants and lifestyles have been mobilised and shaped by various technologies of power.

Asia-Pacific Network Information Centre Policy development process
APNIC's policies are developed by the membership and broader Internet community. The major media for policy development are the face-to-face Open Policy Meetings, which are held twice each year, and mailing list discussions.

Everyone can discuss policy proposals.

APNIC publicly documents all policy discussions and decisions.

APNIC documents all policy discussions and decisions to provide complete transparency of the policy development process.

Management Historical development
Difficulties arise in tracing the history of management

Management Historical development
Given the scale of most commercial operations and the lack of mechanized record-keeping and recording before the industrial revolution, it made sense for most owners of enterprises in those times to carry out management functions by and for themselves. But with growing size and complexity of organizations, the split between owners (individuals, industrial dynasties or groups of shareholders) and day-to-day managers (independent specialists in planning and control) gradually became more common.

New public management Developments
Some modern authors define NPM as a combination of splitting large bureaucracies into smaller, more fragmented ones, competition between different public agencies, and between public agencies and private firms and incentivization on more economic lines. Defined in this way, NPM has been a significant driver in public management policy around the world, from the early 1980s to at least the early 2000s.

A 2003 Organisation for Economic Co-operation and Development paper described the characteristics of the new public management as decentralization, management by objectives, contracting out, competition within government and consumer orientation.

NPM, compared to other public management theories, is oriented towards outcomes and efficiency, through better management of public budget. It is considered to be achieved by applying competition, as it is known in the private sector, to organizations in the public sector, emphasizing economic and leadership principles. New public management addresses beneficiaries of public services much like customers, and conversely citizens as shareholders.

In 2007, the European Commission produced a white book on governance issues whose objective was to propose a new kind of "relationship between the state and the citizens," reform governance, improve public management and render decision-making "more flexible."

Organisation for Economic Co-operation and Development
The Organisation for Economic Co-operation and Development (OECD) (French: Organisation de coopération et de développement économiques, OCDE) is an international economic organisation of 34 countries founded in 1961 to stimulate economic progress and world trade

The OECD originated in 1948 as the Organisation for European Economic Co-operation (OEEC), led by Robert Marjolin of France, to help administer the Marshall Plan (which was rejected by the Soviet Union and its satellite states)

In 1961, the OEEC was reformed into the Organisation for Economic Co-operation and Development by the Convention on the Organisation for Economic Co-operation and Development and membership was extended to non-European states. Most OECD members are high-income economies with a very high Human Development Index (HDI) and are regarded as developed countries.

The OECD's headquarters are at the Château de la Muette in Paris, France.

Organisation for Economic Co-operation and Development Organisation for European Economic Co-operation The Organisation for European Economic Co-operation (OEEC) was formed in 1948 to administer American and Canadian aid in the framework of the Marshall Plan for the reconstruction of Europe after World War II. It started its operations on 16 April Since 1949, it was headquartered in the Chateau de la Muette in Paris, France. After the Marshall Plan ended, the OEEC focused on economic issues.

Organisation for Economic Co-operation and Development Organisation for European Economic Co-operation In the 1950s, the OEEC provided the framework for negotiations aimed at determining conditions for setting up a European Free Trade Area, to bring the European Economic Community of the six and the other OEEC members together on a multilateral basis. In 1958, a European Nuclear Energy Agency was set up under the OEEC.

Organisation for Economic Co-operation and Development Organisation for European Economic Co-operation By the end of the 1950s, with the job of rebuilding Europe effectively done, some leading countries felt that the OEEC had outlived its purpose, but could be adapted to fulfill a more global mission

Organisation for Economic Co-operation and Development Foundation of the OECD
Following the 1957 Rome Treaties to launch the European Economic Community, the Convention on the Organisation for Economic Co-operation and Development was drawn up to reform the OEEC

More than just increasing its internal structure, OECD progressively created agencies: the OECD Development Centre (1961), International Energy Agency (IEA, 1974), and Financial Action Task Force on Money Laundering.

Unlike the organizations of the United Nations system, OECD uses the spelling "organisation" with an "s" in its name rather than "organization" (see -ise/-ize).

Organisation for Economic Co-operation and Development Enlargement to Central Europe
In 1989, after the political changes in Central and Eastern Europe, the OECD started to assist these countries to prepare market economy reforms

Organisation for Economic Co-operation and Development Reform and further enlargement
In the 1990s, a number of European countries, now members of the European Union, expressed their willingness to join the organisation

In 2003, the OECD established a working group headed by Japan's Ambassador to the OECD Seiichiro Noboru to work out a strategy for the enlargement and co-operation with non-members

In 2011, President Juan Manuel Santos of Colombia expressed the country's willingness to join the organization during a speech at the OECD headquarters.

In 2013, the OECD decided to open membership talks with Colombia and Latvia. It also announced its intention to open talks with Costa Rica and Lithuania in 2015.

Other countries that have expressed interest in OECD membership are Peru and Malaysia.

Organisation for Economic Co-operation and Development Aim
The OECD defines itself as a forum of countries committed to democracy and the market economy, providing a setting to compare policy experiences, seek answers to common problems, identify good practices, and co-ordinate domestic and international policies

to achieve the highest sustainable economic growth and employment and a rising standard of living in Member countries, while maintaining financial stability, and thus to contribute to the development of the world economy;

to contribute to sound economic expansion in Member as well as nonmember countries in the process of economic development; and

to contribute to the expansion of world trade on a multilateral, nondiscriminatory basis in accordance with international obligations.

Organisation for Economic Co-operation and Development International investments and multinational enterprises Between 1995 and 1998, the OECD designed the Multilateral Agreement on Investment, which was abandoned because of a widespread criticism from civil society groups and developing countries. In 1976, the OECD adopted the Declaration on International Investment and Multinational Enterprises, which was rewritten and annexed by the OECD Guidelines for Multinational Enterprises in 2000.

Organisation for Economic Co-operation and Development International investments and multinational enterprises Among other areas, the OECD has taken a role in co-ordinating international action on corruption and bribery, creating the OECD Anti-Bribery Convention, which came into effect in February It has been ratified by thirty-eight countries.

Organisation for Economic Co-operation and Development International investments and multinational enterprises The OECD has also constituted an anti-spam task force, which submitted a detailed report, with several background papers on spam problems in developing countries, best practices for ISPs, marketers, etc., appended. It works on the information economy and the future of the Internet economy.

Organisation for Economic Co-operation and Development PISA
The OECD publishes the Programme for International Student Assessment (PISA), which is an assessment that allows educational performances to be examined on a common measure across countries.

Organisation for Economic Co-operation and Development Taxation
The OECD publishes and updates a model tax convention that serves as a template for bilateral negotiations regarding tax coordination and cooperation

Since 1998, the OECD has led a charge against harmful tax practices, principally targeting the activities of tax havens (while principally accepting the policies of its member countries, which would tend to encourage tax competition)

On 22 October 2008, at an OECD meeting in Paris, 17 countries led by France and Germany decided to draw up a new blacklist of tax havens

Organisation for Economic Co-operation and Development Publishing
The OECD publishes , reports, statistics, working papers and reference materials. All titles and databases published since 1998 can be accessed via OECD iLibrary.

Organisation for Economic Co-operation and Development Publishing
The OECD Library & Archives collection dates from 1947, including records from the Committee for European Economic Co-operation (CEEC) and the Organisation for European Economic Co-operation (OEEC), predecessors of today's OECD. External researchers can consult OECD publications and archival material on the OECD premises by appointment:

Organisation for Economic Co-operation and Development Books
The OECD releases between 300 and 500 books each year. The publications are updated accordingly to the OECD iLibrary. Most books are published in English and French. The OECD flagship[vague] titles include:

The OECD Economic Outlook, published twice a year. It contains forecast and analysis of the economic situation of the OECD member countries.

The Main Economic Indicators, published monthly. It contains a large selection of timely statistical indicators.

The OECD Factbook, published yearly and available online, as an iPhone app and in print. The Factbook contains more than 100 economic, environmental and social indicators, each presented with a clear definition, tables and graphs. The Factbook mainly focuses on the statistics of its member countries and sometimes other major additional countries. It is freely accessible online and delivers all the data in Excel format via Statlinks.

The OECD Communications Outlook and the OECD Internet Economy Outlook (formerly the Information Technology Outlook), which rotate every year. They contain forecasts and analysis of the communications and information technology industries in OECD member countries and non-member economies.

In 2007 the OECD published Human Capital: How what you know shapes your life, the first book in the OECD Insights series. This series uses OECD analysis and data to introduce important social and economic issues to non-specialist readers. Other books in the series cover sustainable development, international trade and international migration.

Organisation for Economic Co-operation and Development Magazine
OECD Observer, an award-winning magazine[n 2] launched in 1962

Organisation for Economic Co-operation and Development Statistics
The OECD is known as a statistical agency, as it publishes comparable statistics on a wide number of subjects.

as interactive databases on iLibrary together with key comparative and country tables,

as StatLinks (in most OECD books, there is a URL that links to the underlying data).

Organisation for Economic Co-operation and Development Working papers
There are 15 working papers series published by the various directorates of the OECD Secretariat. They are available on iLibrary, as well as on many specialised portals.

Organisation for Economic Co-operation and Development Reference works
The OECD is responsible for the OECD Guidelines for the Testing of Chemicals, a continuously updated document that is a de facto standard (i.e., soft law).

Organisation for Economic Co-operation and Development Reference works
It has published the OECD Environmental Outlook to 2030, which shows that tackling the key environmental problems we face today—including climate change, biodiversity loss, water scarcity, and the health impacts of pollution—is both achievable and affordable.

Organisation for Economic Co-operation and Development Structure
The OECD's structure consists of three main elements:

The OECD member countries, each represented by a delegation led by an ambassador. Together, they form the OECD Council. Member countries act collectively through Council (and its Standing Committees) to provide direction and guidance to the work of Organization.

The OECD Substantive Committees, one for each work area of the OECD, plus their variety of subsidiary bodies. Committee members are typically subject-matter experts from member and non-member governments. The Committees oversee all the work on each theme (publications, task forces, conferences, and so on). Committee members then relay the conclusions to their capitals.

The OECD Secretariat, led by the Secretary-General (currently Ángel Gurría), provides support to Standing and Substantive Committees. It is organized into Directorates, which include about 2,500 staff.

Organisation for Economic Co-operation and Development Meetings
Delegates from the member countries attend committees' and other meetings. Former Deputy-Secretary General Pierre Vinde estimated in 1997 that the cost borne by the member countries, such as sending their officials to OECD meetings and maintaining permanent delegations, is equivalent to the cost of running the . This ratio is unique among inter-governmental organisations. In other words, the OECD is more a persistent forum or network of officials and experts than an administration.

The yearly Ministerial Council Meeting, with the Ministers of Economy of all member countries and the candidates for enhanced engagement among the countries.

The annual OECD Forum, which brings together leaders from business, government, labour, civil society and international organisations. This takes the form of conferences and discussions and is open to public participation.

Thematic Ministerial Meetings, held among Ministers of a given domain (i.e. all Ministers of Labour, all Ministers of Environment, etc.).

The bi-annual World Forum on Statistics, Knowledge and Policies, which does not usually take place in the OECD. This series of meetings has the ambition to measure and foster progress in societies.

Organisation for Economic Co-operation and Development Secretariat
Exchanges between OECD governments benefit from the information, analysis, and preparation of the OECD Secretariat. The secretariat collects data, monitors trends, and analyses and forecasts economic developments. Under the direction and guidance of member governments, it also researches social changes or evolving patterns in trade, environment, education, agriculture, technology, taxation, and other areas.

Centre for Entrepreneurship, SMEs and Local Development

Directorate for Education

Directorate for Employment, Labour, and Social Affairs

Directorate for Science, Technology, and Industry

Public Governance and Territorial Development Directorate

Trade and Agriculture Directorate

Public Affairs and Communication Directorate

The work of the secretariat is financed from the OECD's annual budget, currently around US$510 million (€342.9 million)

As an international organisation the terms of employment of the OECD Secretariat staff are not governed by the laws of the country in which their offices are located

Organisation for Economic Co-operation and Development Committees
Representatives of the 34 OECD member countries and a number of observer countries meet in specialised committees on specific policy areas, such as economics, trade, science, employment, education or financial markets. There are about 200 committees, working groups and expert groups. Committees discuss policies and review progress in the given policy area.

Organisation for Economic Co-operation and Development Special bodies
Africa Partnership Forum

Business and Industry Advisory Committee (BIAC)

Institutional Management in Higher Education (IMHE)

International Transport Forum (ITF) (formally known as the European Conference of Ministers of Transport)

Trade Union Advisory Committee (TUAC)

Organisation for Economic Co-operation and Development Current members
There are currently 34 members of the OECD. The list includes all the 28 European Union member states except Bulgaria, Croatia, Cyprus, Latvia, Lithuania, Malta and Romania.

Organisation for Economic Co-operation and Development Current members
The European Commission participates in the work of the OECD alongside the EU Member States.

Organisation for Economic Co-operation and Development Former members
Free Territory of Trieste (Zone A) (member of the OEEC until 1954, where it ceased to exist as an independent territorial entity).

Organisation for Economic Co-operation and Development Currently in accession talks
Russia: In May 2007, the OECD decided to open accession negotiations with Russia.

Organisation for Economic Co-operation and Development Likely to open accession talks in 2015
Lithuania: In May 2013, the OECD declared its intention to open accession negotiations with Lithuania in 2015.

Organisation for Economic Co-operation and Development Relations with non-members
Currently, 25 non-members participate as regular observers or full participants in OECD Committees

On 16 May 2007, the OECD Ministerial Council decided to strengthen OECD's co-operation with Brazil, China, India, Indonesia and South Africa, through a process of enhanced engagement. The countries listed are key partners to the OECD. The countries contribute to the OECD's work in a sustained and comprehensive manner by direct and active participation in substantive bodies of the Organisation determined by mutual interest.

The OECD explores the possibilities for enhanced co-operation with selected countries and regions of strategic interest to the OECD, giving priority to South East Asia with a view to identifying countries for possible membership.

Organisation for Economic Co-operation and Development Criticism
The OECD has been criticised by several civil society groups and developing countries

Organisation for Economic Co-operation and Development Indicators
The following table shows various data for OECD member states, including area, population, economic output and income inequality, as well as various composite indices, including human development, viability of the state, perception of corruption, economic freedom, state of peace, freedom of the press and democratic level.

Organisation for Economic Co-operation and Development Indicators
Highest quartile Upper-mid (2nd to 3rd quartile) Lower-mid (1st to 2nd quartile) Lowest

Organisation for Economic Co-operation and Development Notes
Jump up ^ The Library and Archives' website is oecd.org/libraryandarchives.

Jump up ^ Highly Commended certificate in the annual ALPSP/Charlesworth awards from the Association of Learned and Professional Society Publishers 2002; see article .

Jump up ^ The yearbook's website is oecd.org/yearbook.

Commission on Sustainable Development
Environmental governance United Nations Commission on Sustainable Development (CSD) Commission on Sustainable Development

Environmental governance United Nations Commission on Sustainable Development (CSD)
This intergovernmental institution meets twice a year to assess follow-up on Rio Summit goals

Oracle Corporation Development software
Oracle Corporation's tools for developing applications include (amongst others):

Clinical governance Research and development
Techniques such as critical appraisal of the literature, project management and the development of guidelines, protocols and implementation strategies are all tools for promoting the implementation of research practice.

Apostrophe Historical development
The apostrophe was introduced into English in the 16th century in imitation of .

Cluster analysis Newer developments
This led to the development of pre-clustering methods such as canopy clustering, which can process huge data sets efficiently, but the resulting "clusters" are merely a rough pre-partitioning of the data set to then analyze the partitions with existing slower methods such as k-means clustering

For high-dimensional data, many of the existing methods fail due to the curse of dimensionality, which renders particular distance functions problematic in high-dimensional spaces

Ideas from density-based clustering methods (in particular the DBSCAN/OPTICS family of algorithms) have been adopted to subspace clustering (HiSC, hierarchical subspace clustering and DiSH) and correlation clustering (HiCO, hierarchical correlation clustering, 4C using "correlation connectivity" and ERiC exploring hierarchical density-based correlation clusters).

Several different clustering systems based on mutual information have been proposed. One is Marina Meilă's variation of information metric; another provides hierarchical clustering. Using genetic algorithms, a wide range of different fit-functions can be optimized, including mutual information. Also message passing algorithms, a recent development in Computer Science and Statistical Physics, has led to the creation of new types of clustering algorithms.

Adaptability Development of the use of this term
In the life sciences the term adaptability is used variously. At one end of the spectrum, the ordinary meaning of the word suffices for understanding. At the other end, there is the term as introduced by Conrad, referring to a particular information entropy measure of the biota of an ecosystem, or of any subsystem of the biota, such as a population of a single species, a single individual, cell, protein or gene.

Adaptability Development of the use of this term
In the technical research field this feature has been considered only since the late 1990s. H. P. Wiendahl first introduced adaptability as a necessary feature of a manufacturing system in The need to consider adaptability arose in the context of factory planning, where it is an objective to develop modular, adaptable systems. It has now become an important consideration for manufacturing and system engineers.

Cost accounting The development of throughput accounting
As business became more complex and began producing a greater variety of products, the use of cost accounting to make decisions to maximize profitability came into question

Agent-based model Early developments
The history of the agent-based model can be traced back to the Von Neumann machine, a theoretical machine capable of reproduction

Cranfield School of Management Centre for Customised Executive Development (CCED)
Cranfield’s Centre for Customised Executive Development (CCED) is consistently ranked amongst the top business schools worldwide for customised executive development. The Centre’s areas of expertise include: working with top teams on strategy formulation; supporting organisation development and talent management initiatives; developing functional expertise and building leadership and management capability.

The Centre offers a complete development process that includes: strategic consultancy, organisational and individual diagnostics, assessment and development centres, and programme design and delivery. Interventions are highly customised to client needs and often integrate on-line and networked learning, business simulations and real-life project work. The Centre works with more than 60 corporate and public sector clients each year.

In the Financial Times' Executive Education Custom Ranking, Cranfield is the highest ranked UK school for customised executive development over three years ( ). The School is first in Europe and second in the world for international delivery in the

Electronic business Data transmission and application development
All sensitive information being transmitted should be encrypted. Businesses can opt to refuse clients who can't accept this level of encryption. Confidential and sensitive information should also never be sent through . If it must be, then it should also be encrypted.

Transferring and displaying secure information should be kept to a minimum. This can be done by never displaying a full credit card number for example. Only a few of the numbers may be shown, and changes to this information can be done without displaying the full number. It should also be impossible to retrieve this information online.

Source code should also be kept in a secure location. It should not be visible to the public.

Applications and changes should be tested before they are placed online for reliability and compatibility.

Agile software development
It is a conceptual framework that promotes foreseen interactions throughout the development cycle

Agile software development Predecessors
Concurrently and independently the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan

So-called lightweight agile software development methods evolved in the mid-1990s as a reaction against the heavyweight waterfall-oriented methods, which were characterized by their critics as being heavily regulated, regimented, micromanaged and overly incremental approaches to development.

Proponents of lightweight agile methods contend that they are a return to development practices that were present early in the history of software development.

Early implementations of agile methods include Rational Unified Process (1994), Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development (1997), and Dynamic Systems Development Method (DSDM) (1995). These are now collectively referred to as agile methodologies, after the was published in 2001.

Agile software development Agile Manifesto
In February 2001, 17 software developers met at the Snowbird, Utah, resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development to define the approach now known as agile software development. Some of the manifesto's authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto's principles.

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

That is, while there is value in the items on the right, we value the items on the left more.

Individuals and interactions – in agile development, self-organization and motivation are important, as are interactions like co-location and pair programming.

Working software – working software will be more useful and welcome than just presenting documents to clients in meetings.

Customer collaboration – requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.

Responding to change – agile development is focused on quick responses to change and continuous development.

Customer satisfaction by rapid delivery of useful software

Welcome changing requirements, even late in development

Working software is delivered frequently (weeks rather than months)

Working software is the principal measure of progress

Sustainable development, able to maintain a constant pace

Close, daily cooperation between business people and developers

Face-to-face conversation is the best form of communication (co-location)

Projects are built around motivated individuals, who should be trusted

Continuous attention to technical excellence and good design

Simplicity—the art of maximizing the amount of work not done—is essential

Regular adaptation to changing circumstances

The well-known background picture of the Agile Manifesto website was taken by Ward Cunningham, who wanted to capture the moment during the weekend meeting at Snowbird.

In 2005, a group headed by Alistair Cockburn and Jim Highsmith wrote an addendum of project management principles, the Declaration of Interdependence, to guide software project management according to agile development methods.

In 2009, a movement spearheaded by Robert C Martin wrote an extension of software development principles, the Software Craftsmanship Manifesto, to guide agile software development according to professional conduct and mastery.

Agile software development Characteristics
There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project.

Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning

No matter what development disciplines are required, each agile team will contain a customer representative

A common characteristic of agile development are daily status meetings or "stand-ups". In a brief session, team members report to each other what they did the previous day, what they intend to do today, and what their roadblocks are.

Specific tools and techniques, such as continuous integration, automated or xUnit test, pair programming, test-driven development, design patterns, domain-driven design, code refactoring and other techniques are often used to improve quality and enhance project agility.

Light Agile Development (LAD) is a flavor of agile methodology that applies hand picked techniques from the wider range of agile practices to suit different companies, development teams, situations and environments

In agile software development, an information radiator is a (normally large) physical display located prominently in an office, where passers-by can see it. It presents an up-to-date summary of the status of a software project or other product. The name was coined by Alistair Cockburn, and described in his 2002 book Agile Software Development. A build light indicator may be used to inform a team about the current status of their project.

Agile software development Comparison with other methods
One key of adaptive development methods is a "rolling wave" approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change

In the extremes, a predictive team can report exactly what features and tasks are planned for the entire length of the development process

Formal methods, in contrast to adaptive and predictive methods, focus on computer science theory with a wide array of types of provers. A formal method attempts to prove the absence of errors with some level of determinism. Some formal methods are based on model checking and provide counter examples for code that cannot be proven. Agile teams may employ highly disciplined formal methods.

have much in common with the Rapid Application Development techniques from the 1980/90s as espoused by James Martin and others. In addition to technology-focused methods, customer- and design-centered methods, such as Visualization-Driven Rapid Prototyping developed by Brian Willison, work to engage customers and end users to facilitate agile software development.

CMMI Version 1.3 includes tips for implementing Agile and CMMI.One of the differences between agile and waterfall is that testing of the software is conducted at different points during the software development lifecycle

Agile software development Agile methods
Well-known agile software development methods include:

Agile software development Agile methods
Agile Unified Process (AUP)

Agile software development Method tailoring
In the literature, different terms refer to the notion of method adaptation, including 'method tailoring', 'method fragment adaptation' and 'situational method engineering'. Method tailoring is defined as:

A process or capability in which human agents determine a system development approach for a specific project situation through responsive changes in, and dynamic interplays between contexts, intentions, and method fragments.

Situation-appropriateness can be considered as a distinguishing characteristic between agile methods and traditional software development methods, with the latter being relatively much more rigid and prescriptive

Extreme Programming (XP) makes the need for method adaptation explicit

Agile software development Software development life cycle
The agile methods are focused on different aspects of the software development life cycle. Some focus on the practices (extreme programming, pragmatic programming, agile modeling), while others focus on managing the software projects (the scrum approach).

Yet, there are approaches providing full coverage over the development life cycle (dynamic systems development method, or DSDM, and the IBM Rational Unified Process, or RUP), while most of them are suitable from the requirements specification phase on (feature-driven development, or FDD, for example).

Thus, there is a clear difference between the various agile software development methods in this regard. Whereas DSDM and RUP do not need complementing approaches to support software development, the others do to a varying degree. DSDM can be used by anyone (although only DSDM members can offer DSDM products or services). RUP, then, is a commercially sold development environment (Abrahamsson, Salo, Rankainen, & Warsta, 2002).

Agile software development Measuring agility
The similarly named Agility Measurement Index, scores developments against five dimensions of a software project (duration, risk, novelty, effort, and interaction)

Agile software development Measuring agility
While such approaches have been proposed to measure agility, the practical application of such metrics is still debated. There is agile software development ROI data available from the CSIAC ROI Dashboard.

Agile software development Experience and reception
One of the early studies reporting gains in quality, productivity, and business satisfaction by using Agile methods was a survey conducted by Shine Technologies from November 2002 to January A similar survey conducted in 2006 by Scott Ambler, the Practice Leader for Agile Development with IBM Rational's Methods Group reported similar benefits. Others claim that agile development methods are still too young to require extensive academic proof of their success.

Agile software development Suitability
Agile development has been widely seen as being more suitable for certain types of environment, including small teams of experts.:157

Positive reception towards Agile methods has been observed in Embedded domain across Europe in recent years.

Some things that may negatively impact the success of an agile project are:

Large-scale development efforts (>20 developers), though scaling strategies and evidence of some large projects have been described.

Distributed development efforts (non-colocated teams). Strategies have been described in Bridging the Distance and Using an Agile Software Process with Offshore Development.

Mission-critical systems where failure is not an option at any cost (e.g. software for air traffic control).

The early successes, challenges and limitations encountered in the adoption of agile methods in a large organization have been documented.

In terms of outsourcing agile development, Michael Hackett, Sr. Vice President of LogiGear Corporation has stated that "the offshore team ... should have expertise, experience, good communication skills, inter-cultural understanding, trust and understanding between members and groups and with each other."

Agile methods have been extensively used for development of software products and some of them use certain characteristics of software, such as object technologies. However, these techniques can be applied to the development of non-software products, such as computers, motor vehicles, medical devices, food, and clothing; see Flexible product development.

Risk analysis can also be used to choose between adaptive (agile or value-driven) and predictive (plan-driven) methods. Barry Boehm and Richard Turner suggest that each side of the continuum has its own home ground, as follows:

Suitability of different development methods

Agile home ground Plan-driven home ground Formal methods

Requirements change often Requirements do not change often Limited requirements, limited features see Wirth's law

Small number of developers Large number of developers Requirements that can be modeled

Culture that responds to change Culture that demands order Extreme quality

Agile software development Criticism
Agile methodologies can also be inefficient in large organizations and certain types of projects (see paragraph "Suitability"). Agile methods seem best for developmental and non-sequential projects. Many organizations believe that agile methodologies are too extreme and adopt a hybrid approach that mixes elements of agile and plan-driven approaches.

Agile software development Criticism
The term "agile" has also been criticized as being a management fad that simply describes existing good practices under new jargon, promotes a "one size fits all" mindset towards development strategies, and wrongly emphasizes method over results.

Agile software development Further reading
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile Software Development Methods: Review and Analysis. VTT Publications 478.

Cohen, D., Lindvall, M., & Costa, P. (2004). An introduction to agile methods. In Advances in Computers (pp. 1–66). New York: Elsevier Science.

Dingsøyr, Torgeir, Dybå, Tore and Moe, Nils Brede (ed.): Agile Software Development: Current Research and Future Directions, Springer, Berlin Heidelberg, 2010.

Fowler, Martin. Is Design Dead?. Appeared in Extreme Programming Explained, G. Succi and M. Marchesi, ed., Addison-Wesley, Boston

Larman, Craig and Basili, Victor R. Iterative and Incremental Development: A Brief History IEEE Computer, June 2003

Riehle, Dirk. A Comparison of the Value Systems of Adaptive Software Development and Extreme Programming: How Methodologies May Learn From Each Other. Appeared in Extreme Programming Explained, G. Succi and M. Marchesi, ed., Addison-Wesley, Boston

Willison, Brian (2008). Visualization Driven Rapid Prototyping. Parsons Institute for Information Mapping.

Industry Industrial development
Factory - a traditional symbol of the industrial development (a paper mill in Georgetown, the United States).

Industry Industrial development
This process has accelerated with the development of the computer and the robot.

Big Science Development
World War II has often been called[by whom?] "the physicists' war" for the role that those scientists played in the development of new weapons and tools, notably the proximity fuze, radar, and the atomic bomb

Big Science Development
In the shadow of the first atomic weapons, the importance of a strong scientific research establishment was apparent to any country wishing to play a major role in international politics

IEC 62264 Parts under development
Part 4: Object Models and Attributes of Manufacturing Operations

Part 5: Object Models and Attributes of Manufacturing Operations Management

Part 6: Business to Manufacturing Transactions

Capability Maturity Model Integration Maturity levels in CMMI for development
There are five maturity levels. Maturity level ratings are awarded for levels 2 through 5. The process areas below and their maturity levels are listed for the CMMI for Development model:

CM - Configuration Management
Capability Maturity Model Integration Maturity levels in CMMI for development CM - Configuration Management

PPQA - Process and Product Quality Assurance
Capability Maturity Model Integration Maturity levels in CMMI for development PPQA - Process and Product Quality Assurance

DAR - Decision Analysis and Resolution
Capability Maturity Model Integration Maturity levels in CMMI for development DAR - Decision Analysis and Resolution

OPF - Organizational Process Focus
Capability Maturity Model Integration Maturity levels in CMMI for development OPF - Organizational Process Focus

PI - Product Integration
Capability Maturity Model Integration Maturity levels in CMMI for development PI - Product Integration

TS - Technical Solution
Capability Maturity Model Integration Maturity levels in CMMI for development TS - Technical Solution

QPM - Quantitative Project Management
Capability Maturity Model Integration Maturity levels in CMMI for development QPM - Quantitative Project Management

CAR - Causal Analysis and Resolution
Capability Maturity Model Integration Maturity levels in CMMI for development CAR - Causal Analysis and Resolution

Aspect-oriented software development
In computing, Aspect-oriented software development (AOSD) is an emerging software development technology that seeks new modularizations of software systems in order to isolate secondary or supporting functions from the main program's business logic. AOSD allows multiple concerns to be expressed separately and automatically unified into working systems.

These concerns span multiple primary functional units within the application, and often result in serious problems faced during application development and maintenance

Aspect-Oriented Software Development focuses on the identification, specification and representation of cross-cutting concerns and their modularization into separate functional units as well as their automated composition into a working system.

Aspect-oriented software development History
Aspect-Oriented Software Development describes a number of approaches to software modularization and composition including, in order of publication, reflection and metaobject protocols, Composition Filters, developed at the University of Twente in the Netherlands, Subject-Oriented Programming (later extended as Multidimensional Separation of Concerns) at IBM, Feature Oriented Programming at University of Texas at Austin, Adaptive Programming at Northeastern University, USA, and Aspect-Oriented Programming (AOP) at Palo Alto Research Center

Currently, several aspect-oriented programming languages are available for a variety of languages and platforms.

AOSD now refers to a wide range of software development techniques that support the modularization of crosscutting concerns in a software system, from requirement engineering to business process management, analysis and design, architecture, programming and implementation techniques, testing and software maintenance techniques.

It is a popular topic of Software Engineering research, especially in Europe, where research activities on AOSD are coordinated by the European Network of Excellence on Aspect-Oriented Software Development (AOSD-Europe), funded by the European Commission.

Aspect-oriented software development Crosscutting concerns
The motivation for aspect-oriented programming approaches stem from the problems caused by code scattering and tangling. The purpose of Aspect-Oriented Software Development is to provide systematic means to modularize crosscutting concerns.

The implementation of a concern is scattered if its code is spread out over multiple modules. The concern affects the implementation of multiple modules. Its implementation is not modular.

The implementation of a concern is tangled if its code is intermixed with code that implements other concerns. The module in which tangling occurs is not cohesive.

Scattering and tangling often go together, even though they are different concepts.

Aspect-oriented software development considers that code scattering and tangling are the symptoms of crosscutting concerns. Crosscutting concerns cannot be modularized using the decomposition mechanisms of the language (object or procedures) because they inherently follow different decomposition rules. The implementation and integration of these concerns with the primary functional decomposition of the system causes code tangling and scattering.

Aspect-oriented software development Example 1: Logging in Apache Tomcat
Figure 1 illustrates a decomposition into classes of the Apache Tomcat web container

Aspect-oriented software development Example 1: Logging in Apache Tomcat
Figure 2 represents the implementation of the logging concern in Tomcat. Logging in Tomcat is a crosscutting concern. Its implementation spreads over many classes and packages and is intermixed with the implementation of many other concerns.

Aspect-oriented software development Example 2: Coordination of components
Figure 3 represents the UML architecture diagram of a telecom component. Each box corresponds to a process that communicates with other processes through connectors.

Figure 4 illustrates the impact of a coordination concern on the architecture of the system, such as When the system starts up, all parts must initialize successfully, otherwise the system must shut down.

The highlighted box corresponds to a coordinator process. This concern has an impact on the implementation of each process in the diagram. Its implementation crosscuts the implementation of the other processes.

Aspect-oriented software development Examples of crosscutting concerns
see Cross-cutting_concern#Examples

Aspect-oriented software development Problems caused by scattering and tangling
Scattering and tangling of behavior are the symptoms that the implementation of a concern is not well modularized. A concern that is not modularized does not exhibit a well-defined interface. The interactions between the implementation of the concern and the modules of the system are not explicitly declared. They are encoded implicitly through the dependencies and interactions between fragments of code that implement the concern and the implementation of other modules.

Aspect-oriented software development Problems caused by scattering and tangling
The lack of interfaces between the implementation of crosscutting concerns and the implementation of the modules of the system impedes the development, the evolution and the maintenance of the system.

Aspect-oriented software development System development
A module is primarily a unit of independent development. It can be implemented to a large extent independently of other modules. Modularity is achieved through the definition of well-defined interfaces between segments of the system.

The lack of explicit interfaces between crosscutting concerns and the modules obtained through the functional decomposition of the system imply that the implementation of these concerns, as well as the responsibility with respect to the correct implementation of these concerns, cannot be assigned to independent development teams

Furthermore, modules whose implementation is tangled with crosscutting concerns are hard to reuse in different contexts

Finally, concerns that are not modularized are hard to test in isolation. The dependencies of the concern with respect to behavior of other modules are not declared explicitly. Hence, the implementation of unit test for such concerns requires knowledge about the implementation of many modules in the system.

Aspect-oriented software development System maintenance and evolution
The lack of support for the modular implementation of crosscutting concerns is especially problematic when the implementation of this concern needs to be modified

Aspect-oriented software development Nature of aspect-orientation
The focus of Aspect-Oriented Software Development (AOSD) is in the investigation and implementation of new structures for software modularity that provide support for explicit abstractions to modularize concerns

Aspect-oriented software development Quantification and obliviousness
The best known definition of the nature of AOSD is due to Filman and Friedman, which characterized AOSD using the equation aspect orientation = quantification + obliviousness.

AOP can be understood as the desire to make quantified statements about the behavior of programs, and to have these quantifications hold over programs written by oblivious programmers.

Obliviousness implies that a program has no knowledge of which aspects modify it where or when, whereas quantification refers to the ability of aspects to affect multiple points in the program.

The notion of non-invasiveness is often preferred to the term obliviousness. Non-invasiveness expresses that aspects can add behavior to a program without having to perform changes in that program, yet it does not assume that programs are not aware of the aspects.

Filman's definition of aspect-orientation is often considered too restrictive

The essential features of Aspect-Oriented Software Development are therefore better characterized in terms of the modularity of the implementation of crosscutting concerns, the abstractions provided by aspect-oriented languages to enable modularization and the expressiveness of the aspect-oriented composition operators.

Aspect-oriented software development Concepts and terminology
Aspect-oriented approaches provide explicit support for localizing concerns into separated modules, called aspects. An aspect is a module that encapsulates a concern. Most aspect-oriented languages support the non-invasive introduction of behavior into a code base and quantification over points in the program where this behavior should be introduced. These points are called join points.

Aspect-oriented software development Join point model
Join points are points in the execution of the system, such as method calls, where behavior supplied by aspects is combined. A join point is a point in the execution of the program, which is used to define the dynamic structure of a crosscutting concern.

The join point model of an aspect-oriented language defines the types of join points that are supported by the aspect-oriented language and the possible interaction points between aspects and base modules.

The dynamic interpretation of join points makes it possible to expose runtime information such as the caller or callee of a method from a join point to a matching pointcut. Nowadays, there are various join point models around and still more under development. They heavily depend on the underlying programming language and AO language.

exception handler execution

A method call join point covers the actions of an object receiving a method call. It includes all the actions that compose a method call, starting after all arguments are evaluated up to return.

Figure 5 illustrates possible join points in the execution of a small object-oriented program. The highlighted join points include the execution of method moveBy(int, int) on a Line object, the calls to methods moveBy(int, int) on the Point objects in the context of the Line object, the execution of these methods in the context of the Point objects and the calls and execution of the setX(int) and setY(int) methods.

Aspect-oriented software development Pointcut designators
The quantification over join points is expressed at the language level

pointcut move: call(public * Figure.* (..))

picks out each call to Figure's public methods.

cflow poincuts identify join points based on whether they occur in the dynamic context of other join points. For example, in AspectJ syntax cflow(move()) picks out each join point that occurs in the dynamic context of the join points picked out by the move pointcut.

Pointcuts can be classified in two categories:

Kinded pointcuts, such as the call pointcut, match one kind of join point using a signature.

Non-kinded pointcuts, such as the cflow pointcut match all kinds of join points using a variety of properties.

Aspect-oriented software development Advice bodies
An advice body is code that is executed when a join point is reached. Advice modularizes the functional details of a concern. The order in which the advice bodies contributed by aspects (and by the base) may be controlled in a variety of ways, including:

as a join point is reached, before the execution proceeds with the base

after the base semantics for the join point. When the join point corresponds to the execution of a method, an after advice can be executed after the method returned or after raising an exception

as the join point is reached, with explicit control over whether the base semantics is executed. Around advice can modify the control flow of the program.

When the execution of a join point satisfies a pointcut expression, the base and advice code associated with the join point are executed. The advice may interact with the rest system through a join point instance containing reflective information on the context of the event that triggered the advice, such as the arguments of a method call or the target instance of a call.

Aspect-oriented software development Inter-type declarations
Inter-type declarations allow the programmer to modify a program's static structure, such as class members and classes hierarchy. New members can be inserted and classes can be pushed down the class hierarchy.

Aspect-oriented software development Aspects
An aspect is a module that encapsulates a concern. An aspect is composed of pointcuts, advice bodies and inter-type declarations. In some approaches, an aspect may also contain classes and methods.

Aspect-oriented software development Aspect weaving
Aspect weaving is a composition mechanism that coordinates aspects with the other modules of the system. It is performed by a specialized compiler, called an aspect weaver.

Aspect-oriented software development Example
Figure 6 illustrates a classic example of a crosscutting concern in a figure editor example taken from the AOSD literature

Aspect-oriented software development Example
The move pointcut descriptor of Figure 7 captures all the executions of the moveBy methods of a subclass of Shape and invokes the display refresh functionality after the execution proceeds. The concern is modularized, which makes it easier to evolve and maintain.

Aspect-oriented software development Aspect-oriented requirement engineering
Aspect-oriented requirement Engineering (also referred to as "Early Aspects") focuses on the identification, specification and representation of crosscutting properties at the requirement level. Examples of such properties include security, mobility, availability and real-time constraints. Crosscutting properties are requirements, use cases or features that have a broadly scoped effect on other requirements or architecture components.

Aspect-oriented requirements engineering approaches are techniques that explicitly recognise the importance of clearly addressing both functional and non-functional crosscutting concerns in addition to non-crosscutting ones

Specific areas of excellence under the denominator of AO Requirements Analysis are:

the aspect-oriented requirements process itself,
Aspect-oriented software development Aspect-oriented requirement engineering the aspect-oriented requirements process itself,

adoption and integration of aspect-oriented requirements engineering, and

assessment/evaluation of aspect-oriented requirements.
Aspect-oriented software development Aspect-oriented requirement engineering assessment/evaluation of aspect-oriented requirements.

Aspect-oriented software development Aspect Oriented Business Process Management (AOBPM)
Reducing complexity is an important issue in Business Process Management (BPM) area

Aspect Oriented Business Process Management (AOBPM) tries to support separation of cross-cutting concerns from the core business concerns. It defines a set of requirements and a formal model. This model is designed using Coloured Petri Nets (CPN).

The approach is implemented as a service in YAWL based on Service Oriented Architecture.

Aspect-oriented software development Aspect-oriented system architecture
Aspect-oriented system architecture focuses on the localization and specification of crosscutting concerns in architectural designs. Crosscutting concerns that appear at the architectural level cannot be modularized by redefining the software architecture using conventional architectural abstractions. Aspect-oriented system architecture languages propose explicit mechanisms to identify, specify and evaluate aspects at the architecture design level.

Aspect-oriented software development Aspect-oriented system architecture
Aspect-oriented architecture starts from the observation that we need to identify, specify and evaluate aspects explicitly at the architecture design level. Aspectual architecture approaches describe steps for identifying architectural aspects. This information is used to redesign a given architecture in which the architectural aspects are made explicit. In this regard, specific areas of excellence are:

the aspect-oriented architecture process itself,
Aspect-oriented software development Aspect-oriented system architecture the aspect-oriented architecture process itself,

Aspect-oriented software development Aspect-oriented modeling and design
Aspect-oriented design has the same objectives as any software design activity, i.e

Aspect-oriented software development Aspect-Oriented Programming (AOP)
AOP includes programming techniques and tools that support the modularisation of concerns at the level of the source code.

Just like any other programming language, an aspect-oriented language typically consists of two parts: a language specification and an implementation. Hence, there are two corresponding areas of concern: support for language developers and support for application developers.

An aspect-oriented approach supports the implementation of concerns and how to compose those independently implemented concerns. While the specification of such a language is the primary manual for application developers, it provides obviously no guarantee that the application developer will produce high-quality aspect-oriented programs. Specific areas of excellence:

the crucial concepts of aspect-oriented programming,

programming in aspect-oriented languages,

composing software components written in any language using aspect-oriented composition mechanisms, or

Excellence on support for constructing aspect languages includes the following areas:

constructing languages or teels for specific domains and/or platforms, and

transferring implementation principles of aspect-oriented execution environments, including

Aspect-oriented software development Formal method support for aspect-orientation
Formal methods can be used both to define aspects semantically and to analyze and verify aspect-oriented systems

specially designed testing techniques to provide coverage for aspects,
Aspect-oriented software development Formal method support for aspect-orientation specially designed testing techniques to provide coverage for aspects,

program slicing and code analysis approaches to identify interactions among aspects and between aspects and underlying systems,

model checking techniques specialized for aspects, and
Aspect-oriented software development Formal method support for aspect-orientation model checking techniques specialized for aspects, and

inductive techniques to verify aspect-oriented systems.
Aspect-oriented software development Formal method support for aspect-orientation inductive techniques to verify aspect-oriented systems.

specify and analyze individual aspects relative to an existing system,
Aspect-oriented software development Formal method support for aspect-orientation specify and analyze individual aspects relative to an existing system,

define conditions for composing multiple aspects correctly, and
Aspect-oriented software development Formal method support for aspect-orientation define conditions for composing multiple aspects correctly, and

Although some approaches are already used in aspect languages, others are still subject of research and are not ready for routine industrial application. Nevertheless, awareness of these issues is essential for language designers, and for effective use of aspects, especially in safety-critical contexts.

Aspect-oriented software development Aspect-oriented middleware
support for the application developer, which includes

aspect-oriented software development using a specific middleware, involving the aspect programming model, aspect deployment model, platform infrastructure, and services of the middleware, and

Product Family Engineering (methods, architectures, techniques) in distributed and ambient computing, and

support for the middleware developer with respect to

host-infrastructure middleware,

Aspect-oriented software development Adoption
IBM Websphere Application Server (WAS) is a java application server that supports Java EE and Web Services. Websphere is distributed according to editions that support different features. Websphere uses AspectJ internally to isolate features of the different editions.

JBoss Application Server (JBoss AS) is a free, open-source java application server that supports Java EE. The core of JBoss AS is integrated with the JBoss AOP aspect-oriented programming language. The application server uses JBoss AOP to deploy services such as security and transaction management.

Oracle TopLink is a Java object-to-relational persistence framework that is integrated with the Spring Application Server. TopLink achieves high levels of persistence transparency using Spring AOP.

Sun Microsystems uses AspectJ to streamline Mobile Application development for the Java ME platform. Aspects are used to simplify the development of Mobile Applications for deployment to different operator decks and different mobile gaming community interfaces.

Siemens Soarian is a health information management system that supports seamless access to patient medical records and the definition of workflows for health provider organizations. Soarian uses AspectJ to integrate crosscutting features such as tracing, auditing and performance monitoring in the context of an agile development process.

Motorola wi4 is a cellular infrastructure system that provides support for the WiMAX wireless broadband standard. The wi4 control software is developed using an aspect-oriented extension to the UML 2.0 standard called WEAVR. WEAVR is used during the development for debugging and testing purposes.

ASML is a provider of lithography systems for the semiconductor industry. ASML uses an aspect-oriented extension to C called Mirjam to modularize tracing and profiling concerns.

Glassbox is a troubleshooting agent for Java applications that automatically diagnoses common problems. The Glassbox inspector monitors the activity of the Java virtual machine using AspectJ.

.NET 3.5 supports Aspect Oriented concepts through the Unity container.

Smartphone - Open-source development
The open-source culture has penetrated the smartphone market in several ways. There have been attempts to create open source hardware and software for smartphones.

In February 2010, Nokia made Symbian open source. Thus, most commercial smartphones were based on open-source operating systems. These include those based on Linux, such as Google's Android, Nokia's Maemo, Hewlett-Packard's webOS, and those based on BSD, such as the Darwin-based Apple iOS. Maemo was later merged with Intel's project Moblin to form MeeGo.

On the 2nd of January, Canonical, best known for its Ubuntu desktop and Smart TV operating systems, announced a mobile version of its operating system, built for both smartphones and tablets. Its design is based on the desktop equivalent and features such as gesture-based navigation.

Adolescent sexuality - Developmental feminist perspective
It is specifically interested in how society's gender norms affect adolescent development, especially for girls

Another way gender roles affect adolescent sexuality is thought the sexual double standard

O’Sullivan and her colleagues assessed 180 girls between the ages of 12 and 14 on their perceptions on what their first sexual encounters would be like; many girls reported feeling negative emotions towards sex before their first time

Researchers found that having an older sibling, especially an older brother, affected how girls viewed sex and sexuality

Appropriate technology - Appropriate technology and development
Schumacher's initial concept of intermediate technology was created as a critique of the currently prevailing development strategies which focused on maximizing aggregate economic growth through increases to overall measurements of a country's economy, such as gross domestic product (GDP)

However, by the late 1960s it was becoming clear this development method had not worked as expected and a growing number of development experts and national policy makers were recognizing it as a potential cause of increasing poverty and income inequality in developing countries

Schumacher sought to shift development efforts from a bias towards urban areas and on increasing the output per laborer to focusing on rural areas (where a majority of the population still lived) and on increasing employment.

Cross-platform - Challenges to cross-platform development
There are certain issues associated with cross-platform development. Some of these include:

Testing cross-platform applications may be considerably more complicated, since different platforms can exhibit slightly different behaviors or subtle bugs. This problem has led some developers to deride cross-platform development as "Write Once, Debug Everywhere", a take on Sun’s "Write once, run anywhere" marketing slogan.

Developers are often restricted to using the lowest common denominator subset of features which are available on all platforms. This may hinder the application's performance or prohibit developers from using platforms’ most advanced features.

Different platforms often have different user interface conventions, which cross-platform applications do not always accommodate

Scripting languages and virtual machines must be translated into native executable code each time the application is executed, imposing a performance penalty. This penalty can be alleviated using advanced techniques like just-in-time compilation; but even using such techniques, some computational overhead may be unavoidable.

Different platforms require the use of native package formats such as RPM and MSI. Multi-platform installers such as InstallAnywhere, JExpress, InstallBuilder, or IzPack address this need.

Cross-platform execution environments may suffer cross-platform security flaws, creating a fertile environment for cross-platform malware.

Capability management - Defence Lines of Development
The UK MoD uses a similar breakdown of Defence Lines of Development (DLoDs) as follows:

The acronym "Tepid oil" is used to remember these. Additionally, though not a DLoD in itself, the unifying theme of 'interoperability' is also considered to ensure a holistic approach to capability integration is adopted.

The UK MoD cites Interoperability as an overarching theme that must be considered when any DLoD is being addressed.

Automotive engineering - Development Engineer
A Development Engineer is a job function within Automotive Engineering, in which the development engineer has the responsibility for coordinating delivery of the engineering attributes of a complete automobile (bus, car, truck, van, SUV, etc.) as dictated by the automobile manufacturer, governmental regulations, and the customer who buys the product.

Much like the Systems Engineer, the Development Engineer is concerned with the interactions of all systems in the complete automobile

Another aspect of the development engineer's job is a trade-off process required to deliver all the automobile attributes at a certain acceptable level

The Development Engineer is also responsible for organising automobile level testing, validation, and certification

Binary Runtime Environment for Wireless - Brew application development
For testing applications during the development process, the SDK includes a Brew emulator, or starting with Brew version and above, the Brew Simulator

The Brew emulator, named Brew Simulator, does not emulate handset hardware. Instead, the Brew application is compiled to native code and linked with a compatible Brew runtime library. Because of this, applications cannot be tested for platform bugs related to memory alignment and various firmware related glitches without a Brew handset operating in test mode.

For testing purposes, Brew applications can be transferred using a Universal Serial Bus (USB) or serial cable to any Brew-compatible handset using Brew AppLoader from Qualcomm

Brew applications may be unloaded from a consumer handset to save handset memory space

On May 28, 2008, Qualcomm and Adobe announced a partnership to integrate Adobe Flash Lite as a supported user interface on Brew.

Binary Runtime Environment for Wireless - Development fees
Since March 2006, the least expensive digital signature package for developers costs US$400 for 100 application submissions.

Agriculture - Modern developments
After 1492, a global exchange of previously local crops and livestock breeds occurred

The developments of heat processing and refrigeration in the 19th century led to a revolution in the meat industry, as they allowed meat to be shipped long distances without spoiling

The development of agriculture into its modern form has been possible through a continuing process of mechanization, with huge advances made starting in the early 19th century

In 1909 the Haber-Bosch method to synthesize ammonium nitrate was first demonstrated; it represented a major breakthrough and allowed crop yields to overcome previous constraints

The cereals rice, corn, and wheat provide 60% of human food supply

Calculator - Development of electronic calculators
The first mainframe computers, using firstly vacuum tubes and later transistors in the logic circuits, appeared in the 1940s and 1950s. This technology was to provide a stepping stone to the development of electronic calculators.

The Casio Computer Company, in Japan, released the Model 14-A calculator in 1957, which was the world's first all-electric (relatively) "compact" calculator. It did not use electronic logic but was based on relay technology, and was built into a desk.

They employed the young graduate Norbert Kitz, who had worked on the early British Pilot ACE computer project, to lead the development

The tube technology of the ANITA was superseded in June 1963 by the U.S

There followed a series of electronic calculator models from these and other manufacturers, including Canon, Mathatronics, Olivetti, SCM (Smith-Corona-Marchant), Sony, Toshiba, and Wang

The Olivetti Programma 101 was introduced in late 1965; it was a stored program machine which could read and write magnetic cards and displayed results on its built-in printer

Another calculator introduced in 1965 was Bulgaria's ELKA 6521, developed by the Central Institute for Calculation Technologies and built at the Elektronika factory in Sofia

The Monroe Epic programmable calculator came on the market in 1967

The first handheld calculator, a prototype called "Cal Tech", was developed by Texas Instruments in It could add, multiply, subtract, and divide, and its output device was a paper tape.

Contents - Open source software development
An open source software-based strategy was adopted to accelerate the development of a Cell BE system and to provide an environment to develop Cell applications. In 2005, patches enabling Cell support in the Linux kernel were submitted for inclusion by IBM developers. Arnd Bergmann (one of the developers of the aforementioned patches) also described the Linux-based Cell architecture at LinuxTag 2005.

Both PPE and SPEs are programmable in C/C++ using a common API provided by libraries.

Terra Soft strategically partnered with Mercury to provide a Linux Board Support Package for Cell, and support and development of software applications on various other Cell platforms, including the IBM BladeCenter JS21 and Cell QS20, and Mercury Cell-based solutions

In November 2005, IBM released a "Cell Broadband Engine (CBE) Software Development Kit Version 1.0", consisting of a simulator and assorted tools, to its web site. Development versions of the latest kernel and tools for Fedora Core 4 are maintained at the Barcelona Supercomputing Center website.

In August 2007, Mercury Computer Systems released a Software Development Kit for PLAYSTATION(R)3 for High-Performance Computing.

In November 2007, Fixstars Corporation released the new "CVCell" module aiming to accelerate several important OpenCV APIs for Cell. In a series of software calculation tests, they recorded execution times on a 3.2 GHz Cell processor that were between 6x and 27x faster compared with the same software on a 2.4 GHz Intel Core 2 Duo.

With the release of kernel version on March 20, 2006, the Linux kernel officially supports the Cell processor.

Enterprise content management - ECM market development
This section has multiple issues. Please help improve it or discuss these issues on the talk page.

This article's factual accuracy may be compromised due to out-of-date information.

Prior to 2003, the ECM market was dominated by a number of medium-sized independent vendors that fell into two categories: those who had originated as Document Management companies (Advanced Processing & Imaging, Hyland Software, Documentum, Laserfiche, FileNet, OpenText, Db technology) and had begun adding on management of other enterprise content, and those who had started as Web Content Management providers (Interwoven, Vignette, Stellent) and had begun trying to branch out into managing other types of content such as business documents and rich media

In 2002, Documentum had added collaboration capabilities with its acquisition of eRoom while Interwoven and Vignette countered with their respective acquisitions of iManage and Intraspect

In April 2007, independent analyst firm CMS Watch noted that "some of the biggest names in this business are undergoing substantial transformation that will lead to shifting road maps and product sets over the next few years". In addition, 2007 saw the emergence of open-source options for ECM supplied by Nuxeo and Alfresco, along with a software-as-a-service offering from Spring CM. In 2008, Sense/Net released Sense/Net 6.0, an open source ECM and EPS solution.

There are a number of software companies that have sprung up to develop applications to complement ECM with specific functions and features. There are companies that provide third-party document and image viewers such as LEAD Technologies, Microsoft, and Accusoft. There are companies that provide workflows such as Office Gemini, SpringCM, and docAssist. There are also several companies that provide plugins for ECMs.

The Web 2.0 wave brought new players to the market with strength in web-based delivery

Gartner estimated that the ECM market was worth approximately $3.3 billion in 2008; this was expected to grow at a compound annual growth rate of 9.5 percent through After a plethora of industry consolidation, only three or four major companies are left in this space, and the industry as a whole is undergoing a significant transformation as Microsoft commoditizes content-management components.

According to Gartner's 2009 report, 75 percent of Global 2000 companies were highly likely to have a desktop-focused, process-focused content management implementation by 2008, and ECM would continue to absorb other technologies, such as digital asset management and management. Gartner also predicted that there will be further market consolidation, acquisition, and separation of vendors into platform and solution providers.[dated info]

Currently, enterprise information management (EIM) is gaining more interest from organizations trying to approach information management (whether structured or unstructured) from an enterprise perspective. EIM combines ECM and business intelligence.

Cloud content management is emerging as a web-based alternative, combining the content focus of ECM with the collaborative elements of social business software.

Capability Maturity Model - Development at Software Engineering Institute
Active development of the model by the US Department of Defense Software Engineering Institute (SEI) began in 1986 when Humphrey joined the Software Engineering Institute located at Carnegie Mellon University in Pittsburgh, Pennsylvania after retiring from IBM. At the request of the U.S. Air Force he began formalizing his Process Maturity Framework to aid the U.S. Department of Defense in evaluating the capability of software contractors as part of awarding contracts.

Humphrey based his approach on the staged evolution of a system of software development practices within an organization, rather than measuring the maturity of each separate development process independently

Watts Humphrey's Capability Maturity Model (CMM) was published in 1988 and as a book in 1989, in Managing the Software Process.

Organizations were originally assessed using a process maturity questionnaire and a Software Capability Evaluation method devised by Humphrey and his colleagues at the Software Engineering Institute

The full representation of the Capability Maturity Model as a set of defined process areas and practices at each of the five maturity levels was initiated in 1991, with Version 1.1 being completed in January The CMM was published as a book in 1995 by its primary authors, Mark C. Paulk, Charles V. Weber, Bill Curtis, and Mary Beth Chrissis.

Communication - Written communication and its historical development
Over time the forms of and ideas about communication have evolved through the continuing progression of technology. Advances include communications psychology and media psychology, an emerging field of study.

The progression of written communication can be divided into three revolutionary stages called "Information Communication Revolutions"

Communication is thus a process by which meaning is assigned and conveyed in an attempt to create shared understanding. This process, which requires a vast repertoire of skills in interpersonal processing, listening, observing, speaking, questioning, analyzing, gestures, and evaluating enables collaboration and cooperation.

Misunderstandings can be anticipated and solved through formulations, questions and answers, paraphrasing, examples, and stories of strategic talk

Operating system - Operating system development as a hobby
Operating system development is one of the most complicated activities in which a computing hobbyist may engage. A hobby operating system may be classified as one whose code has not been directly derived from an existing operating system, and has few users and active developers. [27]

Operating system development may come from entirely new concepts, or may commence by modeling an existing operating system

Examples of a hobby operating system include ReactOS and Syllable.

Android (operating system) - Development
Android is developed in private by Google until the latest changes and updates are ready to be released, at which point the source code is made available publicly. This source code will only run without modification on select devices, usually the Nexus series of devices. With others, there are proprietary binaries which have to be provided by the manufacturer in order for Android to work. The green Android logo was designed by graphic designer Irina Blok.

Open-source software - Development model
Raymond likens the development of software by traditional methodologies to building a cathedral, "carefully crafted by individual wizards or small bands of mages working in splendid isolation"

In the traditional model of development, which he called the cathedral model, development takes place in a centralized way

The bazaar model, however, is different. In this model, roles are not clearly defined. Gregorio Robles suggests that software developed using the bazaar model should exhibit the following patterns:

The users are treated like co-developers and so they should have access to the source code of the software

The first version of the software should be released as early as possible so as to increase one's chances of finding co-developers early.

Frequent integration

Code changes should be integrated (merged into a shared code base) as often as possible so as to avoid the overhead of fixing a large number of bugs at the end of the project life cycle. Some open source projects have nightly builds where integration is done automatically on a daily basis.

There should be at least two versions of the software. There should be a buggier version with more features and a more stable version with fewer features. The buggy version (also called the development version) is for users who want the immediate use of the latest features, and are willing to accept the risk of using code that is not yet thoroughly tested. The users can then act as co-developers, reporting bugs and providing bug fixes.

The general structure of the software should be modular allowing for parallel development on independent components.

Dynamic decision making structure

There is a need for a decision making structure, whether formal or informal, that makes strategic decisions depending on changing user requirements and other factors. Cf. Extreme programming.

Data suggests, however, that OSS is not quite as democratic as the bazaar model suggests. An analysis of five billion bytes of free/open source code by 31,999 developers shows that 74% of the code was written by the most active 10% of authors. The average number of authors involved in a project was 5.1, with the median at 2.

Open-source software - Development tools
In OSS development, the participants, who are mostly volunteers, are distributed among different geographic regions, so there is need for tools to aid participants to collaborate in source code development. Often, these tools are also available as OSS.

Revision control systems such as Concurrent Versions System (CVS) and later Subversion (svn) and Git are examples of tools that help centrally manage the source code files and the changes to those files for a software project.

Utilities that automate testing, compiling, and bug reporting help preserve stability and support of software projects that have numerous developers but no managers, quality controller, or technical support. Building systems that report compilation errors among different platforms include Tinderbox. Commonly used bugtrackers include Bugzilla and GNATS.

Tools such as mailing lists, IRC, and instant messaging provide means of Internet communication between developers. The Web is also a core feature of all of the above systems. Some sites centralize all the features of these tools as a software development management system, including GNU Savannah, SourceForge, and BountySource.

Diaspora (social network) - Development
Work on the Diaspora software began in May Finn Brunton, a teacher and digital media researcher at New York University, described their method as "a return of the classic geek means of production: pizza and ramen and guys sleeping under the desks because it is something that it is really exciting and challenging." A developer preview was released on September 15 and received criticism for various security bugs.

The first Diaspora "pod" was launched by the development team on November 23, 2010; as a private, invitation-only alpha.

In December 2010 ReadWriteWeb named the project as one of its Top 10 Start-Ups of 2010, saying "Diaspora certainly represents the power of crowd funding, as well as an interest in making sure the social Web is not centralized in one company". On 7 January 2011 Black Duck Software named the project one of its Open Source Rookies of 2010, for being "the privacy aware, personally controlled, do-it-all, open source social network. ",

Since its release, features of Diaspora have appeared in similar forms in other social networks

In October 2011, Diaspora announced that it was starting a fundraising campaign

The Diaspora Project website was started on September 29, Its declared mission is "to build a new and better social web, one that’s 100% owned and controlled by you and other Diasporans."

On November 12, 2011 co-founder Ilya Zhitomirskiy committed suicide, at the age of twenty-two. Reports linked pressures related to Diaspora to his death. Zhitomirskiy’s mother, Inna Zhitomirskiy, said, "I strongly believe that if Ilya did not start this project and stayed in school, he would be well and alive today."

In February 2012 the developers wrote that their own research indicated a change in the focus for the project

Olympic Stadium (London) - Redevelopment
West Ham will contribute £15 million and Newham Council £40 million for the work to be carried out with the London Legacy Development Corporation and the British Government making up the rest

PC Magazine - Development and evolution
The magazine has evolved significantly over the years

Today, the magazine runs about 150 pages an issue. It has adapted to the new realities of the 21st century by reducing its once-standard emphasis on massive comparative reviews of computer systems, hardware peripherals, and software packages to focus more on the broader consumer-electronics market (including cell phones, PDAs, MP3 players, digital cameras, and so on). Since the late 1990s, the magazine has taken to more frequently reviewing Macintosh software and hardware.

PC Magazine has consistently positioned itself as the leading source of information about personal computers (PC) and PC-related products, and its development and evolution have mirrored those of computer journalism in general. The magazine practically invented the idea of comparative hardware and software reviews in 1984 with a groundbreaking "Project Printers" issue. For many years thereafter, the blockbuster annual printer issue, featuring more than 100 reviews, was a PC Magazine tradition.

The publication also took on a series of editorial causes over the years, including copy protection (the magazine refused to grant its coveted Editors' Choice award to any product that used copy protection) and the "brain-dead" Intel (then-editor-in-chief Bill Machrone said the magazine would still review 286s but would not recommend them).

PC Magazine was a booster of early versions of the OS/2 operating system in the late 1980s, but then switched to a strong endorsement of the Microsoft Windows operating environment after the release of Windows 3.0 in May Some OS/2 users accused of the magazine of ignoring OS/2 2.x versions and later.

During the dot-com bubble, the magazine began focusing heavily on many of the new Internet businesses, prompting complaints from some readers that the magazine was abandoning its original emphasis on computer technology. After the collapse of the technology bubble in the early 2000s, the magazine returned to a more-traditional approach.

Short Message Service - Early development
The technical development of SMS was a multinational collaboration supporting the framework of standards bodies. Through these organizations the technology was made freely available to the whole world.

The first proposal which initiated the development of SMS was made by a contribution of Germany and France into the GSM group meeting in February 1985 in Oslo

SMS was considered in the main GSM group as a possible service for the new digital cellular system. In GSM document “Services and Facilities to be provided in the GSM System,” both mobile-originated and mobile-terminated short messages appear on the table of GSM teleservices.

The discussions on the GSM services were concluded in the recommendation GSM “TeleServices supported by a GSM PLMN.” Here a rudimentary description of the three services was given:

The material elaborated in GSM and its WP1 subgroup was handed over in Spring 1987 to a new GSM body called IDEG (the Implementation of Data and Telematic Services Experts Group), which had its kickoff in May 1987 under the chairmanship of Friedhelm Hillebrand (German Telecom). The technical standard known today was largely created by IDEG (later WP4) as the two recommendations GSM (the two point-to-point services merged) and GSM (cell broadcast).

WP4 created a Drafting Group Message Handling (DGMH), which was responsible for the specification of SMS

The work on the draft specification continued in the following few years, where Kevin Holley of Cellnet (now Telefónica O2 UK) played a leading role. Besides the completion of the main specification GSM 03.40, the detailed protocol specifications on the system interfaces also needed to be completed.

Patch (computing) - In software development
Patches sometimes become mandatory to fix problems with libraries or with portions of source code for programs in frequent use or in maintenance. This commonly occurs on very large-scale software projects, but rarely in small-scale development.

In open source projects, the authors commonly receive patches or many people publish patches that fix particular problems or add certain functionality, like support for local languages outside the project's locale. In an example from the early development of the Linux operating system (noted for publishing its complete source code), Linus Torvalds, the original author, received hundreds of thousands of patches from many programmers to apply against his original version.

The Apache HTTP Server originally evolved as a number of patches that Brian Behlendorf collated to improve NCSA HTTPd, hence a name that implies that it is a collection of patches ("a patchy server"). The FAQ on the project's official site states that the name 'Apache' was chosen from respect for the Native American Indian tribe of Apache. However, the 'a patchy server' explanation was initially given on the project's website.

Diaspora (software) - Development
After the project raised over $200,000 in crowdfunding via the Kickstarter website by June 1, 2010, the group began working on the software. A developer preview with a number of security holes was released on September 15, On November 23, a redesigned website was published in preparation for the alpha release, with the old site still available as a blog section. The early security holes were fixed with the alpha release.

After its foundation is completed, Diaspora's developers intend to concentrate on creating a "battery of add-on modules" in order to "facilitate any type of communication," and plan to offer a paid hosting service for Diaspora seeds.

Development was shifted to free office space provided by Pivotal Labs in San Francisco, California. The software’s alpha version was released in September The early alpha version contained many bugs and security flaws, but feedback on the free software led to quick improvements.

The software's beta release was originally scheduled for November 2011, but was postponed due to the need to add new design features and also Zhitomirskiy’s death.

In February 2012, the developers indicated that they had completed work on the software back-end to improve both pod up-time and website response time. The next phase of work involved changes to the user interface and its associated terminology to reflect the way users are actually interacting, as the software moves towards beta status, anticipated for later on in 2012.

By May 2012, development was underway to allow a high degree of customization of user posts, permitting users to post different media, such as text, photos and video with a high degree of personalization and individual expression. The developers felt that allowing individual creativity in posts will differentiate the Diaspora platform from competitors.

In June 2012, the development team was scheduled to move to Mountain View, California as part of work with startup accelerator Y Combinator. In August 2012 the developers focus changed to working on creating makr.io, as part of their yCombinator class.

In August 2012, the founders of Diaspora announced that they would let the community take over governance of the project, while they would stay involved, but take a lesser role. The project was adopted by, and became part of, the Free Software Support Network (FSSN), which is in turn run by Eben Moglen and the Software Freedom Law Center. The FSSN acts as an umbrella organization to Diaspora development and manages Diaspora's branding, finances and legal assets.

In October 2012, the project made its first community release at , dropping all references to the Alpha/Beta branding it had previously used. At the same time development was moved to a development branch, leaving the master branch for stable releases. Additionally, efforts are underway to package Diaspora for Linux distributions and other systems.

Initng - Development Despite being still considered beta, it was chosen as the default init system for Pingwinek, Enlisy, Berry Linux and Bee.

Initng - Development Also there are packages for many distributions such as Debian, Ubuntu and Fedora, as well as ebuilds for Gentoo and spells for Source Mage.

Initng - Development Contrary to other similar projects, it features a portable and flexible code base, more suited for embedded usage, and has been already ported to other operating systems like Haiku and FreeBSD.

Initng - Development It was created by Jimmy Wennlund. The current maintainer and project lead is Ismael Luceno.

dpkg - Development tools
dpkg-dev contains a series of development tools required to unpack, build and upload Debian source packages. These include:

dpkg-source packs and unpacks the source files of a Debian package.

dpkg-gencontrol reads the information from an unpacked Debian tree source and generates a binary package control package, creating an entry for this in Debian/files.

dpkg-shlibdeps calculates the dependencies of runs with respect to libraries.

dpkg-genchanges reads the information from an unpacked Debian tree source that once constructed creates a control file (.changes).

dpkg-buildpackage is a control script that can be used to construct the package automatically.

dpkg-distaddfile adds a file input to debian/files.

dpkg-parsechangelog reads the changes file (changelog) of an unpacked Debian tree source and creates a conveniently prepared output with the information for those changes.

OpenSocial - Development
OpenSocial was rumored to be part of a larger social networking initiative by Google code-named "Maka-Maka", which is defined as meaning "intimate friend with whom one is on terms of receiving and giving freely" in Hawaiian.

Linux Mint - Development
Individual users and companies using the Operating System act as donors, sponsors and partners of the distribution. Linux Mint relies on user feedback to make decisions and orient its development. The official blog often features discussions where users are asked to voice their opinion about the latest features or decisions implemented for upcoming releases. Ideas can be submitted, commented and rated by users via the Linux Mint Community Website.

The community of Linux Mint users use Launchpad to participate in the translation of the Operating System and in reporting bugs.

Most extraneous development is done in Python and organized on-line on GitHub, making it easy for developers to provide patches, to implement additional features or even to fork Linux Mint sub-projects (for example The Linux Mint menu was ported to Fedora). With each release, features are added that are developed by the community. In Linux Mint 9 for instance, the ability to edit menu items is a feature that was contributed by a Linux Mint user.

The members of the development team are spread around the world and they communicate through private forums, s and IRC.

Linux Mint reviews are tracked by the distribution and discussed by the development team and the community of users.

The overall direction of the KDE Platform is made on the KDE Core Team
KDE - Development The overall direction of the KDE Platform is made on the KDE Core Team

Commit-Digest site gives a weekly overview of the development activity
KDE - Development Commit-Digest site gives a weekly overview of the development activity

KDE - Development Season of KDE (SoK) is a program for people could not get accepted into Google Summer of Code. They will have a mentor from the KDE community to help them if any question arises or if they do not know how to continue.

KDE - Development On 20 July 2009, KDE announced that the one millionth commit has been made to its Subversion repository. On October 11, 2009, Cornelius Schumacher, a main developer within KDE, wrote about the estimated cost (using the COCOMO model with SLOCCount) to develop KDE software package with 4,273,291 LoC, which would be about US$175,364,716. This estimation does not include Qt, Calligra Suite, Amarok, Digikam, and other applications that are not part of KDE core.

The work can be measured in figures:
KDE - Development The work can be measured in figures:

KDE - Development More than 1800 contributors help develop KDE. About 20 new developers contribute their first code each month.

KDE is translated in over 108 languages.
KDE - Development KDE is translated in over 108 languages.

KDE has more than 114 official FTP mirrors in over 34 countries.
KDE - Development KDE has more than 114 official FTP mirrors in over 34 countries.

KDE - Development The KDE community is the second largest Free Software community behind the Linux kernel community.[non-primary source needed]

GNU GRUB - Development GRUB version 1 (also known as "GRUB Legacy") is no longer under development and is being phased out. The GNU GRUB developers have switched their focus to GRUB 2, a complete rewrite with goals including making GNU GRUB cleaner, more robust, more portable and more powerful. GRUB 2 started under the name PUPA. PUPA was supported by the Information-technology Promotion Agency (IPA) in Japan. PUPA was integrated into GRUB 2 development around 2002, when GRUB version 0.9x was renamed GRUB Legacy.

GNU GRUB - Development Some of the goals of the GRUB 2 project include support for non-x86 platforms, internationalization/localization, non-ASCII characters, dynamic modules, memory management, a scripting mini-language, migrating platform specific (x86) code to platform specific modules, and an object-oriented framework.

GNU GRUB - Development Three of the most widely used Linux distributions use GRUB 2 as their mainstream boot loader:

GNU GRUB - Development Ubuntu adopted GRUB 2 as the default boot loader in its 9.10 version of October 2009.

GNU GRUB - Development Fedora has been using GRUB 2 as its default boot loader since Fedora 16 released in November 2011.

GNU GRUB - Development openSUSE adopted GRUB 2 as the default boot loader with its 12.2 release of September 2012.

GNU GRUB version 2.00 was officially released on June 26, 2012.
GNU GRUB - Development GNU GRUB version 2.00 was officially released on June 26, 2012.

Mageia - Development Mageia is planned to be released on a 9-month release cycle, with each release to be supported for 2 cycles, that is 18 months.

Firefox OS - Development history
In July 2012, Boot to Gecko was rebranded as 'Firefox OS', after Mozilla's well-known desktop browser, Firefox, and screenshots began appearing in August 2012.

In September 2012, analysts Strategy Analysts forecast that Firefox OS would account for 1% of the global smartphone market in 2013 – its first year of commercial availability.

In February 2013, Mozilla announced plans for global commercial roll-out of Firefox OS. Mozilla announced at a press conference before the start of Mobile World Congress in Barcelona that the first wave of Firefox OS devices will be available to consumers in Brazil, Colombia, Hungary, Mexico, Montenegro, Poland, Serbia, Spain and Venezuela. Firefox have also announced that LG Electronics, ZTE, Huawei and TCL Corporation have committed to making Firefox OS devices.

GIMP - Development GIMP is primarily developed by volunteers as a free software project under the banner of the GNU project. Development takes place in a public git source code repository, on public mailing lists and in public chat channels on the GIMPNET IRC network.

GIMP - Development New features are held in public separate source code branches and merged into the main (or development) branch when they are able to be merged into GIMP without knowingly damaging existing functionality. Sometimes this means that features that appear complete do not get merged or take months or years before they are available in GIMP.

GIMP - Development GIMP itself is released as source code. After a source code release installers and packages are made for different operating systems by parties who may or may not be in contact with the maintainers of GIMP.

GIMP - Development The second (minor) number is incremented with each release of new features, with odd numbers reserved for in-progress development versions and even numbers assigned to stable releases; the third (micro) number is incremented before and after each release (resulting in even numbers for releases, and odd numbers for development snapshots) with any bugfixes subsequently applied and released for a stable version.

GIMP - Development Each year GIMP applies for several positions in the Google Summer of Code (GSoC); to date GIMP has participated in all years except 2007

Criticism of desktop Linux - Development platform for multimedia software
While Linux operates on the open-source philosophy, this may not benefit game development.

Criticism of desktop Linux - Audio development
The lack of strong API standards for multimedia has been criticised. For example the Adobe Systems development blog penguin.SWF discusses the complicated Linux audio infrastructure in the analysis Welcome to the jungle. The nearly one dozen actively supported systems are called an audio jungle, PulseAudio main developer Lennart Poettering stated that it is very difficult for programmers to know which audio API to use for which purpose.

Hobbyist operating system development
Hobbyist operating system is one of the more involved and technical options for a computer hobbyist

Hobbyist operating system development - Development
Elements of operating system development include:

Hobbyist operating system development - Development
Developers of hobby Operating Systems commonly use the C programming language and/or assembly language

Hobbyist operating system development - User Interface
A hobby operating system can use a Command-line Interface, a Text User Interface or a Graphical User Interface. Most hobby operating systems use a command-line interface or a simple text user interface because they are quick and easy to make and time is often a limiting factor for programmers of hobby operating systems. More advanced hobby operating system often use a graphical user interface but graphical interfaces are complicated and take a lot of time to create.

Hobbyist operating system development - Use of BIOS
BIOS interrupt call

BIOS (Basic Input/Output System) is a firmware chip designed to initialise computer hardware and load a computer's operating system

The most commonly used BIOS functions are VideoBIOS and Disk services. These are used because video cards and disk drives vary significantly on different machines and specialised drivers are often difficult to write.

The use of BIOS is uncommon in operating systems that operate in Protected mode or Long mode to use BIOS drivers, because the system must switch to real mode which BIOS drivers run in.

GNU Hurd - Development history
Richard Stallman founded the GNU project in September 1983 with an aim to create a free GNU operating system. Initially the components required for kernel and development were written: editors, shell, compiler and all the others. By 1989, GPL came into being and the only major component missing was the kernel.

Development on the Hurd began in 1990 after an abandoned kernel attempt in 1986, based on the research TRIX operating system developed by Professor Steve Ward and his group at MIT's Laboratory for Computer Science (LCS)

With the release of the Linux kernel in 1991, the primary user of GNU's userland components soon became operating systems based on the Linux kernel (Linux distributions), prompting the coining of the controversial term GNU/Linux.

In 2010, after twenty years under development, Stallman said that he was "not very optimistic about the GNU Hurd

The Debian project, among others, have worked on the Hurd project to produce binary distributions of Hurd-based GNU operating systems for IBM PC compatible systems.

The Globe and Mail - Recent developments
In recent years, the paper has made changes to its format and layout, such as the introduction of colour photographs, a separate tabloid book-review section and the creation of the Review section on arts, entertainment and culture

Other satirical nicknames for the paper include Mop and Pail or Grope and Flail, both of which were coined by longtime Globe and Mail humour columnist Richard J. Needham. The University of British Columbia's student paper, The Ubyssey published a parody issue titled Glib and Male. The spring 2008 issue of the Ryerson Review of Journalism referenced the nickname "Old and Male" for the paper's employee base and perceived target audience.

Since the launch of the National Post as another English-language national paper in 1998, some industry analysts have proclaimed a "national newspaper war" between The Globe and Mail and the National Post. Thus far, however, The Globe and Mail has continued to outsell the National Post.

On April 23, 2007, the paper introduced significant changes to its print design and also introduced a new unified navigation system to its websites. The paper added a "lifestyle" section to the Monday-Friday editions, entitled Globe Life, which has been described as an attempt to attract readers from the rival Toronto Star. Additionally, the paper followed other North American papers by dropping detailed stock listings in print and by shrinking the printed paper to a 12-inch width.

During the 2010 Winter Olympics, which were staged in Vancouver, The Globe and Mail published a Sunday edition, making it the first time that the paper has ever published on Sunday.

GNU Project - Operating system development
The first goal of the GNU project was to create a whole free-software operating system

Fork (software development)
In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct piece of software. The term often implies not merely a development branch, but a split in the developer community, a form of schism.

Fork (software development)
Free and open-source software is that which, by definition, may be forked from the original development team without prior permission without violating any copyright law. However, licensed forks of proprietary software (e.g. Unix) also happen.

Fork (software development) - Etymology
"Fork" in the meaning of "to divide in branches, go separate ways" has been used as early as the 14th century. In the software environment, the term "fork" entered computing jargon around 1969 with the Unix mechanism by which a process split in two by forming an identical copy of itself.

In the context of software development, the first documented use of the term "fork" in the sense of "branch" was by Eric Allman in 1980, to describe forming branches in SCCS:

The term was in use on Usenet by 1983 for the process of creating a subgroup to move topics of discussion to.

"Fork" is not known to have been used in the sense of a community schism during the origins of Lucid Emacs (now XEmacs) (1991) or the BSDs (1993–1994); Russ Nelson used the term "shattering" for this sort of fork in 1993, attributing it to John Gilmore. However, "fork" was in use in the present sense by 1995 to describe the XEmacs split, and was an understood usage in the GNU Project by 1996.

Fork (software development) - Forking of free and open source software
Free and open source software may be legally forked without prior approval of those currently developing, managing, or distributing the software per both The Free Software Definition and The Open Source Definition:

The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

3. Derived Works: The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

In free software, forks often result from a schism over different goals or personality clashes. In a fork, both parties assume nearly identical code bases, but typically only the larger group, or whoever controls the Web site, will retain the full original name and the associated user community. Thus, there is a reputation penalty associated with forking. The relationship between the different teams can be cordial or very bitter.

Eric S. Raymond, in his essay Homesteading the Noosphere, stated that "The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community". He notes in the Jargon File:

Forking is considered a Bad Thing—not merely because it implies a lot of wasted effort in the future, but because forks tend to be accompanied by a great deal of strife and acrimony between the successor groups over issues of legitimacy, succession, and design direction

David A. Wheeler notes four possible outcomes of a fork, with examples:

The death of the fork. This is by far the most common case. It is easy to declare a fork, but considerable effort to continue independent development and support.

The death of the original (e.g. the X.Org Server succeeding and XFree86 dying.)

Successful branching, typically with differentiation (e.g., OpenBSD and NetBSD.)

More recently, distributed revision control (DVCS) tools have popularised a less emotive use of the term "fork", blurring the distinction with "branch"

Forks often restart version numbering from 0.1 or 1.0 even if the original software was at version 3.0, 4.0, or 5.0. An exception is when the forked software is designed to be a drop-in replacement for the original project, e.g. MariaDB for MySQL or LibreOffice for OpenOffice.org.

Fork (software development) - Forking proprietary software
This is almost always an economic decision to generate a greater market share and thus pay back the associated extra development costs created by the fork.

A notable proprietary fork not of this kind is the many varieties of proprietary Unix—almost all derived from AT&T Unix and all called "Unix", but increasingly mutually incompatible. See UNIX wars.

The BSD licenses permit forks to become proprietary software, and some say that commercial incentives thus make proprietisation almost inevitable

FreeBSD - Development As of March 2010 FreeBSD had more than 400 active developers and thousands of contributors.

FreeBASIC - Future development
Using the GCC as a back-end remains on the FreeBASIC TODO list. However, since 2008, official updates to the compiler have been anywhere from six months to years apart.

MeeGo - Software development
The officially endorsed way to develop MeeGo applications is to use the Qt framework and Qt Creator as the development environment, but writing GTK applications is also supported.

MeeGo - Software development
openSUSE’s Build Service is used to compile the applications.

illumos - Development Its primary development project, illumos-gate, derives from OS/Net (aka ON), which is a Solaris kernel with the bulk of the drivers, core libraries, and basic utilities, similar to what is delivered by a BSD "src" tree. It was originally dependent on OpenSolaris OS/Net, but a fork was made after Oracle decided to close development of Solaris and unofficially killed the OpenSolaris project.

Mobile Web - Development
The first access to the mobile web was commercially offered in Finland in 1996 on the Nokia 9000 Communicator phone via the TeliaSonera|Sonera and Radiolinja networks. This was access to the real internet. The first commercial launch of a mobile-specific browser-based web service was in 1999 in Japan when i-mode was launched by NTT DoCoMo.

Mobile Web - Development
The mobile Web primarily utilises lightweight pages like [ this one] written in XHTML|Extensible Hypertext Markup Language (XHTML) or Wireless Markup Language (WML) to deliver content to mobile devices. Many new mobile browsers are moving beyond these limits by supporting a wider range of Web formats, including variants of HTML commonly found on the desktop Web.

Maemo - Software development
Software can be developed in C using the Maemo SDK, Java (which is supported by the Jalimo JVM), Python, Ruby, Mono, Vala, Perl and Pascal.

The Maemo SDK is based around the Debian-oriented Scratchbox Cross Compilation Toolkit, which provides a sandbox environment in which development may take place. Scratchbox uses Qemu to emulate an ARM processor or sbrsh to remotely execute instructions. Scratchbox-compatible rootstraps are available for both x86 and ARM, so the majority of development and debugging takes place on x86, with final packaging being for ARM.

As a new feature of the Maemo operating system, Maemo 5 offers the Qt library as a community-supported component, alongside the officially supported GTK+ backend. This will change with the Harmattan release, which will add the Qt library as the default, with GTK+ becoming community-supported. The programming languages Python, C and C++ will also be supported.

The Nokia Developer Wiki community has articles about Qt development, and includes tutorials and articles about development for the Maemo operating system.

Mandriva Linux - Development version
The development tree of Mandriva Linux has always been known as Cooker. This tree is directly released as a new stable version.

Nexenta OS - Development
Since Nexenta OS does not use the Linux kernel, and Sun only recently began releasing the code of their Solaris operating system as free and open source software, it supports less diverse hardware than other Debian variants.

Nexenta OS - Development
The Nexenta OS team has decided to focus on a minimal GNU/OpenSolaris effort called the Nexenta Core Platform (NCP) which forms the basis of the NexentaStor NAS storage solution. Version 1.0 of Nexenta Core Platform was released on February 10, 2008.

History of free and open-source software - Recent developments
While copyright is the primary legal mechanism that FOSS authors use to ensure license compliance for their software, other mechanisms such as legislation, patents, and trademarks have implications as well. In response to legal issues with patents and the DMCA, the Free Software Foundation released version 3 of its GNU Public License in 2007 that explicitly addressed the DMCA's DRM provisions and patent rights.

After the development of the GNU GPLv3, as copyright holder of many pieces of the GNU system, such as the GCC compiler software, the FSF updated most of the GNU programs' licenses from GPLv2 to GPLv3

Recent mergers have affected major open-source software. Sun Microsystems (Sun) acquired MySQL AB, owner of the popular open-source MySQL database, in 2008.

Oracle in turn purchased Sun in January, 2010, acquiring their copyrights, patents, and trademarks

Python (programming language) - Development environments
Most Python (including CPython) can function as a command line interpreter, for which the user enters statements sequentially and receives the results immediately. In short, Python acts as a shell.

Python (programming language) - Development environments
Other shells add capabilities beyond those in the basic interpreter, including IDLE and IPython. While generally following the visual style of the Python shell, they implement features like auto-completion, retention of session state, and syntax highlighting.

Python (programming language) - Development
Python's development is conducted largely through the Python Enhancement Proposal (PEP) process. The PEP process is the primary mechanism for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. Outstanding PEPs are reviewed and commented upon by the Python community and by Van Rossum, the Python project's Benevolent Dictator for Life (leader / language architect).

Enhancement of the language goes along with development of the CPython reference implementation. The mailing list python-dev is the primary forum for discussion about the language's development; specific issues are discussed in the Roundup bug tracker maintained at python.org. Development takes place on a self-hosted source code repository running Mercurial.

CPython's public releases come in three types, distinguished by which part of the version number is incremented:

Backwards-incompatible versions, where code is expected to break and must be manually ported. The first part of the version number is incremented. These releases happen infrequently—for example, version 3.0 was released 8 years after 2.0.

Major or "feature" releases, which are largely compatible but introduce new features. The second part of the version number is incremented. These releases are scheduled to occur roughly every 18 months, and each major version is supported by bugfixes for several years after its release.

Bugfix releases, which introduce no new features but fix bugs. The third and final part of the version number is incremented. These releases are made whenever a sufficient number of bugs have been fixed upstream since the last release, or roughly every 3 months. Security vulnerabilities are also patched in bugfix releases.

A number of alpha, beta, and release-candidates are also released as previews and for testing before the final release is made. Although there is a rough schedule for each release, this is often pushed back if the code is not ready. The development team monitor the state of the code by running the large unit test suite during development, and using the BuildBot continuous integration system.

The community of Python developers has also contributed over 25,000 software modules to the Python Package Index (called pypi), the official repository of third-party libraries for python.

Macintosh - Development and introduction
Over the years, Raskin assembled a large development team that designed and built the original Macintosh hardware and the original version of the Mac OS operating system that the computer ran

Smith's first Macintosh board was built to Raskin's design specifications: it had 64 kilobytes (kB) of RAM, used the Motorola 6809E microprocessor, and was capable of supporting a 256×256-pixel black-and-white bitmap display

After hearing of the pioneering GUI technology being developed at Xerox PARC, Jobs had negotiated a visit to see the Xerox Alto computer and its Smalltalk development tools in exchange for Apple stock options

The Macintosh 128K was announced to the press in October 1983, followed by an 18-page brochure included with various magazines in December

Two days after "1984" aired, the Macintosh went on sale, and came bundled with two applications designed to show off its interface: MacWrite and MacPaint

Apple spent upwards of $2.5 million purchasing all 39 advertising pages in a special, post-election issue of Newsweek Apple also ran a "Test Drive a Macintosh" promotion, in which potential buyers with a credit card could take home a Macintosh for 24 hours and return it to a dealer afterwards

GENIVI Alliance - Development baseline
to verify the GENIVI software architecture buildability

to verify the impact of the GENIVI software architecture on software dependencies and platform licenses

The GENIVI software baselines are compatible with both ARM and X86 architectures.

Friendster - Development
Friendster has been an open site since August 2006 when it first began allowing widgets and content to be embedded in user profile pages through its developer program. Roughly 39 percent of Friendster's users have widgets on their profile.

Friendster gives software developers access to APIs that utilize content and data within the Friendster network to build and deploy customizable applications on and off Friendster. Friendster's Developer Program is an open, non-proprietary platform with an open revenue model.

Friendster was the first social network to support both the OpenSocial and the Facebook Platform.

History of Linux - Open Source Development Lab and Linux Foundation
The Open Source Development Lab (OSDL) was created in the year 2000, and is an independent nonprofit organization which pursues the goal of optimizing Linux for employment in data centers and in the carrier range. It served as sponsored working premises for Linus Torvalds and also for Andrew Morton (until the middle of 2006 when Morton transferred to Google). Torvalds works full-time on behalf of OSDL, developing the Linux Kernels.

History of Linux - Open Source Development Lab and Linux Foundation
On January 22, 2007, OSDL and the Free Standards Group merged to form The Linux Foundation, narrowing their respective focuses to that of promoting GNU/Linux in competition with Microsoft Windows.

GNU Compiler Collection - Development
The current stable version of GCC is 4.8.2, which was released on October 16, GCC now C++ as its implementation language.

GCC 4.6 supports many new Objective-C features, such as declared and synthesized properties, dot syntax, fast enumeration, optional protocol methods, method/protocol/class attributes, class extensions and a new GNU Objective-C runtime API

GCC many standard tools in its build, including Perl, Flex, Bison, and other common tools. In addition it currently requires three additional libraries to be present in order to build: GMP, MPC, and MPFR.

GCC 4.5, initially released on April 14, 2010, included several minor new features (new targets, new language dialects) and a couple of major new features:

Link-time optimization optimizes across object file boundaries to directly improve the linked binary

Plugins can extend the GCC compiler directly

The trunk concentrates the major part of the development efforts, where new features are implemented and tested. Eventually, the code from the trunk will become the next major release of GCC.

Linux kernel - Development
“ People like Linus Torvalds and I don’t plan the kernel evolution. We don’t sit there and think up the roadmap for the next two years, then assign resources to the various new features. That’s because we don’t have any resources. The resources are all owned by the various corporations who use and contribute to Linux, as well as by the various independent contributors out there. It’s those people who own the resources who decide... ”

Linux kernel - Development
The fact is, evolution often does odd (and "sub-optimal") things exactly because it does incremental changes that DO NOT BREAK at any point. The kernel changes made in year 2007 have been submitted by not less than 1900 developers—but they may be a lot more because developers working in teams usually count as one. It is generally assumed that the community of Linux kernel developers is composed by or members.

Linux kernel - Development model
The current development model of the Linux kernel is such that Linus Torvalds makes the releases of new versions, also called the "vanilla" or "mainline" kernels, meaning that they contain the main, generic branch of development. This branch is officially released as a new version approximately every three months, after Torvalds does an initial round of integrating major changes made by all other programmers, and several rounds of bug-fix pre-releases.

In the current scheme, the main branch of development is not a traditional "stable" branch, instead it incorporates all kinds of changes, both the latest features as well as security and bug fixes

Most Linux users use a kernel supplied by their Linux distribution

The development model for Linux 2.6 was a significant change from the development model for Linux 2.5

As a response to the lack of a stable kernel tree where people could coordinate the collection of bug fixes as such, in December 2005 Adrian Bunk announced that he would keep releasing y kernels when the stable team moved on to

In February 2008, Stephen Rothwell created the linux-next tree to serve as a place where patches aimed to be merged during the next development cycle are gathered

Free Pascal - Integrated development environments (IDEs)
Like most modern compilers, Free Pascal can be used with an integrated development environment (IDE).

Free Pascal - Development tools
FPS Complete Win32 based IDE for FPC, including debugger (trace, breakpoint and watch windows).

MSEide+MSEgui - a RAD/Cross Platform GUI Development System for FPC.

Morfik Win32 based IDE for build Ajax-based web applications that uses FPC for compiling back-end server side logic.

For More Information, Visit:
The Art of Service

Development https://store.theartofservice.com/the-development-toolkit.html.

Similar presentations

Presentation on theme: "Development https://store.theartofservice.com/the-development-toolkit.html."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Development https://store.theartofservice.com/the-development-toolkit.html.

Similar presentations

Presentation on theme: "Development https://store.theartofservice.com/the-development-toolkit.html."— Presentation transcript:

Similar presentations

About project

Feedback