Intro to DevOps

Credits to @chesteralvarez
Image Link



What is DevOps?
  • Is the blending of the roles of developers and operations support. 
Example:In application service, developers write the code that is deployed* into application service. Operations team maintains the application server. If the application fails to work on deployment there is a knowledge gap. People with knowledge of both software development and operations are required to bridge this gap, this is where DevOps practitioners are required.


deployed*: Software deployment includes all the process required for preparing a software application to run and operate in a specific environment. It involves installation, configuration, testing and making changes to optimize the performance of the software. It can either be carried out manually or through automated systems.


How it is important to the software engineering process?
The software development lifecycle is complex and has a number of important phases which include:
  1. Requirements Gathering 
  2. Design 
  3. Software Development 
  4. Testing 
  5. Deployment 
  6. Production Support 



Traditionally the phases have been performed by individuals and teams who have very little interaction with each other.

A key DevOps role is: Bridging the division of teams and improving communication between the phases.


How it is important to quality and testing?
Deploying an updated production application is a very tedious task to be performed manually, this is very time consuming and error prone. There are now a wide range of tools that allow these tests to be automated.

An important DevOps role is to: make the best use of tools and to ensure that they ar integrated to achieve a high level of automation.

Comments

Post a Comment

Popular posts from this blog

Chapters 6.1 & 6.2

Image
Credits to @4vid Image Link 1. What two properties must be satisfied for an input domain to be properly partitioned?  Completeness: The partition must cover all of the domain. Disjoint: blocks should not overlap 2. What is an Input Domain Model (IDM)? Two Approaches to Input Domain Modeling: A. Interface-based approach. 􏰀 Develop characteristics directly from individual input parameters. 􏰀 Just use properties of the domains without considering the actual function under test. B. Functionality-based approach 􏰀 Develop characteristics from a behavioral view of the program under test. 􏰀 Use your understanding of what the system should do. 3. What gives more tests, each choice coverage or pair-wise coverage? Each Choice Coverage (ECC) states that one value from each block for each characteristic must be used in at least one test case. For example, for partitions [A, B] [1, 2] we can get [A, A], [B, B], [1, 1] and [2, 2] which are clearly redundant. Pair-
Read more

Course evaluation

Image
Credits to @rossf Image Link ECOA Evidence  I've been Ken Bauer's student for almost four years in several different courses, and his teaching method has always been a breath of fresh air. From flip learning to almost conventional teaching (since you grade your own exam) he's not afraid to make changes and give students the chance to explore self learning and to take responsibility on when and how they learn the content of the course. This is a skill that is very important acquire and that is needed on a daily basis in every job in the tech field. Personally i enjoyed the Software Quality and Testing course. There are many students that might not like this method of teaching applied on this course because it requires them to take responsibilities on their own learning and some students can't handle this type of control over their own learning. No negative feedback for this course, only that maybe some classes should be online.
Read more

Final Exam Questions

1. Software fault: static error in the code. Software error: internal, not a normal behavior of the program due to a fault. Software failure: external, visible failure of the program. That it doesn't work basically. 2. Beizer discussed the goals of testing in terms of the “test process maturity levels” of an organization, where the levels are characterized by the testers’ goals. Level 0: Testing and debugging are the same. (Worst level) Level 1: Testing is only to find that your code doesn't work. Level 2: Get defensive or make an issue personal with testers because they broke your code. Level 3: Understand the job of a tester and take feedback as constructive criticism. Level 4: Become an expert software tester and make extreme good quality software. Work in harmony with testers. 3. Static Code Analysis is usually performed as part of a Code Review (also known as white-box testing). is a method of debugging by examining source code before a program is run . It’s done by ana
Read more