Difference between revisions of "What the DevOps Is"

From CNM Wiki
Jump to: navigation, search
(Lectio 2 quiz questions)
 
(74 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[CNM DevOps Support]]
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[What the DevOps Is]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of the '''[[Digital Transformations]]''' [[lesson]] that introduces its participants to [[CNM Lab]]. This ''lesson'' belongs to the [[CNMC for Experience]] session of [[EmployableU Concepts]].
  
[[CNM Lab Essentials]]''
 
  
 +
==Content==
 +
The predecessor [[lectio]] is [[What CNM Agile Is]].
  
|2||'''[[DevOps]]''', [[project management system]], [[version control system]]
+
[[File:Devops.png|400px|thumb|right|[[DevOps process]]]]
  
:'''[[DevOps]]'''. An engineering practice and a set of [[concept]]s based on that practice that aim at unifying [[new product development]] (the '''Dev''' part) and [[operations]] (the '''Ops''' part). The primary feature of ''DevOps'' is to strongly advocate [[automation]] and [[monitoring]] at all steps of the [[project]] such as [[integration]], [[testing]], releasing to deployment, and infrastructure management. DevOps aims at shorter development cycles, increased deployment frequency, more dependable releases, in close alignment with business objectives. Functions of ''DevOps'' office staffers can be compared with those of [[project management office]] ([[project management office|PMO]]) in a traditional [[project management]] framework.
+
===Script===
<div style="background-color:#efefef; padding: 5px; margin: 15px;">
+
:Many [[enterprise]]s distinguish [[ongoing operation]]s or so-called ''old businesses'' and [[project]]s or so-called ''new businesses''. [[DevOps]] is an engineering practice that merges both.
:*'''[[Project management system]]'''. Any [[system]] for [[project management]]. Usually, the ''System'' is built using [[project management software]], which tends to be a combination of [[end-user application]]s specifically designed to aid with planning and controlling project costs and schedules.
 
:*[[File:Fixett-vs-wiki.png|400px|thumb|[[CNM Lab]] vs [[CNM Wiki]]]]'''[[Version control system]]'''. The [[system]] that is set for [[version control]]. The ''system'' controls versions or revisions of [[document]]s, [[source code]]s, files, groups of files, collections of data, and/or other resources.</div>
 
  
==Systems of CNM Lab==
+
:In ''DevOps'', [[new product development]] or the '''Dev''' part organically feeds [[operations]] or the '''Ops''' part and, vice versa, the ''operations'' feed their further development. A framework that represents a chain of phases of ''DevOps'' is called [[DevOps process]].
''Systems of CNM Lab'' is the first [[lectio]] out of five ones that make up the ''Lesson''.
 
  
===Lectio 2 presentation===
+
:Depending on [[organizational culture]], technology, and other factors, these phases may vary. In the development loop, they may include planning, building, and verifying. In the operations loop, the phases may include deploying, using, and monitoring in order to start planning a new development.
:Four [[software system]]s support [[CNM Lab]]. They are [[document collaboration system|document collaboration]], [[project management system|project management]], [[version control system|version control]], and [[file-sharing system|file-sharing one]]s.
 
  
:[[CNM Lab]]'s [[file-sharing system]] contains all the [[web document]]s, [[source code]] and other files that have been used in [[CNM Cyber]]'s development.
+
:[[CNMCyber Team]] has developed its [[CNMCT DevOps process]]. In its ''observe and envision'' phase, [[product epic]]s are drafted on [[CNM Wiki]]. In its ''define'' phase, [[product owner]]s shall publish on [[CNM Page]] those ''epics'' that they approve. In its outline phase, [[CNMCyber Coordinator]]s draft [[user story|user stori]]es on [[talk page]]s of [[CNM Wiki]]. In the ''prioritize'' phase, [[product owner]]s include select ''stories'' in the [[sprint backlog]]. If needed, mock-ups emerge as deliverables from the prototype phase. In the ''create and test'' phase, the ''Team'' build [[minimum viable product]]s ([[MVP]]s). [[Marketable product]]s emerge as deliverables from the release and deploy phase to be observed and re-envisioned. In this way, the loops re-start again.
  
:[[CNM Lab]]'s [[version control system]] allows for the management of all the changes to every of them.
+
:The [[CNMCN DevOps process]] is built with a chain of tools that [[CNM Page]], [[CNM Wiki]], and [[CNM Lab]] offer. This chain is called [[CNMCT DevOps toolchain]]. Each of any [[DevOps toolchain]] shall fit one of the phases of a [[DevOps process]]. So does [[CNM DevOps toolchain]].
  
:[[CNM Lab]]'s [[project management system]] is in the heard of this service. [[CNM Lab]] treats every development as a [[project]]. For instance, only those developers who actively work on [[CNM Cert]]'s development can assign, re-assign, or report on the project tasks, as well as can access, modify, and update its private details and get the update notifications.
+
:The bulk of development of [[CNMCT DevOps process]] occurs in two [[development hub]]s. The ''hub'' is a center of development in which two or more developing parties work on one or more [[deliverable]]s.
  
:The project's private details are published by the secure [[wiki engine]] of [[CNM Lab]]'s [[document collaboration system]]. Its [[wikipage]]s are tightened to the projects, so a particular project team can collaborate on the content for its project.
+
:At [[CNM Wiki]], [[CNMCyber Team]] creates the [[requirement]]s that reflect what needs to be developed. These ''requirements'' include [[product epic]]s, [[epic story|epic stori]]es, [[user story|user stori]]es, and [[requirements specification]]s. This ''hub'' is open to the general public 24/7.
  
===Lectio 2 quiz questions===
+
:At [[CNM Lab]], the [[Friends Of CNM]] leads implementations of those ''requirements'' that [[CNMCyber Team]] created. This private ''hub'' is used to develop viable [[computer file]]s, [[software]], as well as security-sensitive documentation.
:Which statement below is correct:<ol type="a"><li>A user of [[CNM Cyber]] should not necessarily be in a good standing in order to utilize services of [[CNM Lab]].</li><li>Every [[source code]] file must be uploaded to [[CNM Lab]] in order to be deployed within [[CNM Cyber]].</li><li>Authorized users of [[CNM Lab]] can identify which image file was last edited.</li><li>All of the other substantive answers are correct.</li><li>None of the other answers is correct.</li></ol>
+
 
:''-- (wlcm--prvw)''
+
===Key terms===
 +
:[[DevOps]], [[DevOps process]], [[CNMCT DevOps process]], [[DevOps toolchain]], [[CNMCT DevOps toolchain]], [[development hub]], [[computer file]] ([[digital file]])
 +
 
 +
===Closing===
 +
:Is the concept of [[CNMCT DevOps process]] explained well?---Yes/No/I'm not sure
 +
 
 +
 
 +
'''[[What Requirements Are]]''' is the successor [[lectio]].
 +
 
 +
==Questions==
 +
 
 +
===Placement entrance exam===

Latest revision as of 22:13, 29 October 2023

What the DevOps Is (hereinafter, the Lectio) is the lesson part of the Digital Transformations lesson that introduces its participants to CNM Lab. This lesson belongs to the CNMC for Experience session of EmployableU Concepts.


Content

The predecessor lectio is What CNM Agile Is.

Script

Many enterprises distinguish ongoing operations or so-called old businesses and projects or so-called new businesses. DevOps is an engineering practice that merges both.
In DevOps, new product development or the Dev part organically feeds operations or the Ops part and, vice versa, the operations feed their further development. A framework that represents a chain of phases of DevOps is called DevOps process.
Depending on organizational culture, technology, and other factors, these phases may vary. In the development loop, they may include planning, building, and verifying. In the operations loop, the phases may include deploying, using, and monitoring in order to start planning a new development.
CNMCyber Team has developed its CNMCT DevOps process. In its observe and envision phase, product epics are drafted on CNM Wiki. In its define phase, product owners shall publish on CNM Page those epics that they approve. In its outline phase, CNMCyber Coordinators draft user stories on talk pages of CNM Wiki. In the prioritize phase, product owners include select stories in the sprint backlog. If needed, mock-ups emerge as deliverables from the prototype phase. In the create and test phase, the Team build minimum viable products (MVPs). Marketable products emerge as deliverables from the release and deploy phase to be observed and re-envisioned. In this way, the loops re-start again.
The CNMCN DevOps process is built with a chain of tools that CNM Page, CNM Wiki, and CNM Lab offer. This chain is called CNMCT DevOps toolchain. Each of any DevOps toolchain shall fit one of the phases of a DevOps process. So does CNM DevOps toolchain.
The bulk of development of CNMCT DevOps process occurs in two development hubs. The hub is a center of development in which two or more developing parties work on one or more deliverables.
At CNM Wiki, CNMCyber Team creates the requirements that reflect what needs to be developed. These requirements include product epics, epic stories, user stories, and requirements specifications. This hub is open to the general public 24/7.
At CNM Lab, the Friends Of CNM leads implementations of those requirements that CNMCyber Team created. This private hub is used to develop viable computer files, software, as well as security-sensitive documentation.

Key terms

DevOps, DevOps process, CNMCT DevOps process, DevOps toolchain, CNMCT DevOps toolchain, development hub, computer file (digital file)

Closing

Is the concept of CNMCT DevOps process explained well?---Yes/No/I'm not sure


What Requirements Are is the successor lectio.

Questions

Placement entrance exam