Software Deployment Task
A Software Deployment Task is a software engineering process that make a software system available for use.
- AKA: Software Delivery Process.
- Context:
- It can (typically) be within an SDLC Deployment Stage.
- It can range from being a Manual Software Deployment Process to being an Automated Software Deployment Process.
- It can be associated to a Software Upgrade Task.
- ...
- Example(s):
- Counter-Example(s):
- See: Integration Test, Smoke Test, Acceptance Test, Software System, Software Developer.
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/software_deployment Retrieved:2020-8-26.
- Software deployment is all of the activities that make a software system available for use. [1] The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer side or at the consumer side or both. 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.
2013
- https://puppet.com/blog/continuous-delivery-vs-continuous-deployment-what-s-diff
- QUOTE: Continuous delivery is a series of practices designed to ensure that code can be rapidly and safely deployed to production by delivering every change to a production-like environment and ensuring business applications and services function as expected through rigorous automated testing. Since every change is delivered to a staging environment using complete automation, you can have confidence the application can be deployed to production with a push of a button when the business is ready.
Continuous deployment is the next step of continuous delivery: Every change that passes the automated tests is deployed to production automatically. Continuous deployment should be the goal of most companies that are not constrained by regulatory or other requirements.
There are business cases in which IT must wait for a feature to go live, making continuous deployment impractical. While application feature toggles solve many of those cases, they don’t work in every case. The point is to decide whether continuous deployment is right for your company based on business needs — not on IT limitations.
- QUOTE: Continuous delivery is a series of practices designed to ensure that code can be rapidly and safely deployed to production by delivering every change to a production-like environment and ensuring business applications and services function as expected through rigorous automated testing. Since every change is delivered to a staging environment using complete automation, you can have confidence the application can be deployed to production with a push of a button when the business is ready.
- ↑ Roger S. Pressman Software engineering: a practitioner's approach (eighth edition)