|
Development Environment (software Development Process)
In software deployment, an environment or tier is a computer system or set of systems in which a computer program or software component is deployed and executed. In simple cases, such as developing and immediately executing a program on the same machine, there may be a single environment, but in industrial use, the ''development'' environment (where changes are originally made) and ''production'' environment (what end users use) are separated, often with several stages in between. This structured release management process allows phased deployment (rollout), testing, and rollback in case of problems. Environments may vary significantly in size: the development environment is typically an individual developer's workstation, while the production environment may be a network of many geographically distributed machines in data centers, or virtual machines in cloud computing. Code, data, and configuration may be deployed in parallel, and need not connect to the corresponding tier—for ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Deployment
Software deployment is all of the activities that make a software system available for use. Deployment can involve activities on the producer (software developer) side or on the consumer ( user) side or both. Deployment to consumers is a hard task because the target systems are diverse and unpredictable. Software as a service avoids these difficulties by deploying only to dedicated servers that are typically under the producer's control. Because every software system is unique, the precise processes or procedures within each activity can hardly be defined. Therefore, "deployment" should be interpreted as a ''general process'' that has to be customized according to specific requirements or characteristics. History When computers were extremely large, expensive, and bulky (mainframes and minicomputers), the software was often bundled together with the hardware by manufacturers. If business software needed to be installed on an existing computer, this might require an expens ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Continuous Integration
Continuous integration (CI) is the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state. Typically, developers Merge (version control), merge changes to an Branching (revision control), integration branch, and an automated system Software build, builds and software testing, tests the software system. Often, the automated process runs on each Commit (version control), commit or runs on a schedule such as once a day. Grady Booch first proposed the term CI in Booch method, 1991, although he did not advocate integrating multiple times a day, but later, CI came to include that aspect. History The earliest known work (1989) on continuous integration was the Infuse environment developed by G. E. Kaiser, D. E. Perry, and W. M. Schell. In 1994, Grady Booch used the phrase continuous integration in ''Object-Oriented Analysis and Design with Applications'' (2nd edition) to explain how, when developing using micro ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
High Availability
High availability (HA) is a characteristic of a system that aims to ensure an agreed level of operational performance, usually uptime, for a higher than normal period. There is now more dependence on these systems as a result of modernization. For example, to carry out their regular daily tasks, hospitals and data centers need their systems to be highly available. Availability refers to the ability of the user to access a service or system, whether to submit new work, update or modify existing work, or retrieve the results of previous work. If a user cannot access the system, it is considered ''unavailable from the user's perspective''. The term '' downtime'' is generally used to refer to describe periods when a system is unavailable. Resilience High availability is a property of network resilience, the ability to "provide and maintain an acceptable level of service in the face of faults and challenges to normal operation." Threats and challenges for services can range from ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Downtime
In computing and telecommunications, downtime (also (system) outage or (system) drought colloquially) is a period when a system is unavailable. The unavailability is the proportion of a time-span that a system is unavailable or offline. This is usually a result of the system failing to function because of an unplanned event, or because of routine maintenance (a planned event). The terms are commonly applied to networks and servers. The common reasons for unplanned outages are system failures (such as a crash) or communications failures (commonly known as network outage or network drought colloquially). For outages due to issues with general computer systems, the term computer outage (also IT outage or IT drought) can be used. The term is also commonly applied in industrial environments in relation to failures in industrial production equipment. Some facilities measure the downtime incurred during a work shift, or during a 12- or 24-hour period. Another common practice is to ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Development
Software development is the process of designing and Implementation, implementing a software solution to Computer user satisfaction, satisfy a User (computing), user. The process is more encompassing than Computer programming, programming, writing source code, code, in that it includes conceiving the goal, evaluating feasibility, analyzing software requirements, requirements, software design, design, software testing, testing and software release life cycle, release. The process is part of software engineering which also includes management, organizational management, Software project management, project management, configuration management and other aspects. Software development involves many skills and job specializations including software programmer, programming, software test, testing, Technical writing, documentation, graphic design, user support, marketing, and fundraising. Software development involves many software tools, tools including: compiler, integrated develo ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Integrated Development Environment
An integrated development environment (IDE) is a Application software, software application that provides comprehensive facilities for software development. An IDE normally consists of at least a source-code editor, build automation tools, and a debugger. Some IDEs, such as IntelliJ IDEA, Eclipse (software), Eclipse and Lazarus (software), Lazarus contain the necessary compiler, interpreter (computing), interpreter or both; others, such as SharpDevelop and NetBeans, do not. The boundary between an IDE and other parts of the broader software development environment is not well-defined; sometimes a version control system or various tools to simplify the construction of a graphical user interface (GUI) are integrated. Many modern IDEs also have a class browser, an object browser, and a class diagram, class hierarchy diagram for use in object-oriented programming, object-oriented software development. Overview Integrated development environments are designed to maximize progra ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Development, Testing, Acceptance And Production
Development, testing, acceptance and production (DTAP) is a phased approach to software testing and deployment. The four letters in DTAP denote the following common steps: # Development: The program or component is developed on a development system. This development environment might have no testing capabilities. # Testing: Once the software developer thinks it is ready, the product is copied to a test environment, to verify it works as expected. This test environment is supposedly standardized and in close alignment with the target environment. # Acceptance: If the test is successful, the product is copied to an acceptance test environment. During the acceptance test, the customer will test the product in this environment to verify whether it meets their expectations. # Production: If the customer accepts the product, it is deployed to a production environment, making it available to all users of the system. The set of environments used for a DTAP cycle is often called a DTAP str ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Application Lifecycle Management
Application lifecycle management (ALM) is the product lifecycle management (governance, development, and maintenance) of computer programs. It encompasses requirements management, software architecture, computer programming, software testing, software maintenance, change management, continuous integration, project management, and release management. ALM vs. Software Development Life Cycle ALM is a broader perspective than the Software Development Life Cycle (SDLC), which is limited to the phases of software development such as requirements, design, coding, testing, configuration, project management, and change management. ALM continues after development until the application is no longer used, and may span many SDLCs. Integrated ALM Modern software development processes are not restricted to the discrete ALM/ SDLC steps managed by different teams using multiple tools from different locations. Real-time collaboration, access to the centralized data repository, cross-t ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Blue–green Deployment
In software engineering, blue–green deployment is a method of installing changes to a web, app, or database server by swapping alternating production and staging servers. Overview In blue–green deployments, two servers are maintained: a "blue" server and a "green" server. At any given time, only one server is handling requests (e.g., being pointed to by the DNS). For example, public requests may be routed to the blue server, making it the production server and the green server the staging server, which can only be accessed on a private network. Changes are installed on the non-live server, which is then tested through the private network to verify the changes work as expected. Once verified, the non-live server is swapped with the live server, effectively making the deployed changes live. Using this method of software deployment offers the ability to quickly roll back to a previous state if anything goes wrong. This rollback is achieved by simply routing traffic back to the ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Domestic Canary
The domestic canary (''Serinus canaria'' forma ''domestica''), often simply known as the canary, is a domesticated form of the wild canary, a small songbird in the finch family originating in the Macaronesian Islands. Over the past 500 years of captivity, a wide variety of coloured, decorative and singing canaries have been bred through selection. The canary has been kept as a pet for centuries, which began after the European conquests of the islands inhabited by its wild ancestor. They were domesticated and became prized possessions in 17th century Europe, eventually becoming popular even amongst poorer households, largely due to its melodious song and flexibility in breeding. They were also a highly popular pet in the United States from the 19th century until the mid 20th century. Canaries have also been used in the coal mining industry to detect carbon monoxide, a practice that has since been ceased. Domestic canaries come in a wide variety of different plumage colours, un ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Hot Swapping
Hot swapping is the replacement or addition of components to a computer system without stopping, shutting down, or rebooting the system. Hot plugging describes only the addition of components to a running computer system. Components which have such functionality are said to be ''hot-swappable'' or ''hot-pluggable''; likewise, components which do not are ''cold-swappable'' or ''cold-pluggable''. Although the broader concept of hot swapping can apply to electrical or mechanical systems, it is usually mentioned in the context of computer systems. An example of hot swapping is the express ability to pull a Universal Serial Bus (USB) peripheral device, such as a thumb drive, mouse, keyboard, or printer out of a computer's USB slot without powering down the computer first. Most desktop computer hardware, such as CPUs and memory, are only cold-pluggable. However, it is common for mid to high-end servers and mainframes to feature hot-swappable capability for hardware componen ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Feature Flag
A feature toggle in software development provides an alternative to maintaining multiple feature branches in source code. A condition within the code enables or disables a feature during runtime. In agile settings the toggle is used in production, to switch on the feature on demand, for some or all the users. Thus, feature toggles do make it easier to release often. Advanced roll out strategies such as canary roll out and A/B testing are easier to handle. Continuous delivery is supported by feature toggles, even if new releases are not deployed to production continuously. The feature is integrated into the main branch even before it is completed. The version is deployed into a test environment once, the toggle allows to turn the feature on, and test it. Software integration cycles get shorter, and a version ready to go to production can be provided. The third use of the technique is to allow developers to release a version of a product that has unfinished features. These un ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
