Theoretical Foundation Quiz Review

Question 1

What is legacy code?

Answer 1

code that continues to meet the customers’ needs but is difficult to evolve and maintain

Question 2

What is beautiful code?

Answer 2

long-lasting code that is easy to evolve and meets the customers’ needs.

Question 3

Why is it important to learn to deal with legacy code?

Answer 3

It might be difficult to rewrite old software

Question 4

What is quality assurance?

Answer 4

It is the process or standards that result in high quality products and improve the manufacturing process

Question 5

What is quality software?

Answer 5

It is software that meets the customers’ needs and is easy to evolve. Quality means “fitness for use.”

Question 6

What does verification mean?

Answer 6

Did you build the thing right? Did you meet the specification?

Question 7

What do we do to assure software quality?

Answer 7

Tests!

Question 8

What is the approach that makes exhaustive testing feasible? Divide and ?

Answer 8

Divide and Conquer. We can significantly cut down the number of test cases by approaching the problem hierarchically.

Question 9

What are the different types of tests: unit, …?

Answer 9

Unit Testing: makes sure a single procedure does what was expected
Module Testing: tests across individual units
Integration Testing: ensures that the interfaces between the units have consistent assumptions and communicate correctly,
System/Acceptance Testing: test to see if the integrated program meets its specifications
Widget Tests

Question 10

What is test coverage?

Answer 10

It is the percentage of lines of code that were run by the test suite.

Question 11

What does regression testing mean?

Answer 11

It means automatically rerunning old tests so new changes don’t break old code.

Question 12

What is continuous integration testing?

Answer 12

It is regression testing every time new code is added.

Question 13

How software engineering originated?

Answer 13

Margaret Hamilton used the term to distinguish it from hardware and other kinds of engineering

Question 14

What does Plan-and-Document mean?

Answer 14

Extensive Planning Up Front

Question 15

The concept behind the P and D models. Why don’t P and D models work well?

Answer 15

The concept is extensive planning before you ever start coding and write detailed documentation.
The P&D models don’t work well because any changes require changes in the documentation, which means going over deadlines. Changes are inevitable in production.

Question 16

What was a model that tried to fix it by prototypes?(Spiral) What is the bad part of Spiral?

Answer 16

The model was Spiral. The bad part was that it used iterations that were too long apart from each other.

Question 17

Make sure you have read the Agile Manifesto

Answer 17

-Individuals and Interactions over Processes and Tools
-Working Software over Comprehensive Documentation
-Customer Collaboration over Contract Negotiation
-Responding to Change over Following Plans

Question 18

Who created the concept of Extreme Programming?

Answer 18

Kent Beck

Question 19

Does Extreme Programming advocate shorter or larger iterations?

Answer 19

Shorter iterations

Question 20

Does XP advocate writing tests before code or tests after code?

Answer 20

Writing tests before writing code, either using BDD or TDD

Question 21

Does XP advocate working alone or working in pairs?

Answer 21

Working in pairs

Question 22

What doe Agile emphasize to reduce mistakes?

Answer 22

Test-Driven Development

Question 23

What does Agile emphasize to validate customer requirements?

Answer 23

User Stories

Question 24

What does Agile emphasize to measure progress?

Answer 24

Velocity

Question 25

Does Agile emphasize refining a working but incomplete prototype?

Answer 25

Yes.

Question 26

How often in Agile do you get feedback from the customer/boss? Is Agile an accepted practice?

Answer 26

You get feedback from each iteration, which is 1-2 weeks long. Now, Agile is an accepted practice, but it wasn't before.

Question 27

What are the difference between software as a product and software as a service?

Answer 27

SaaP: one physical copy of the software that works in one hw/os environment; slow upgrade cycles; if computer died, you lost your data; SaaS: distributing software in which the distributor hosts the application and makes it available to customers of the internet, client-server pattern in which a client makes a request and a server responds to the requests of many clients; one version of the application and it runs in the cloud; data stored in cloud; groups can easily share/collaborate; no compatibility for developers, users; upgrading means deploying the version in cloud; continuous customer feedback

Question 28

How do App Stores make it easier to employ Agile Processes?

Answer 28

App stores continuously deliver value to the end users which makes this model of distribution perfect for Agile

Question 29

Why is Flutter a good fit for learning Software as a Product development?

Answer 29

It's a complete SDK, software development kit

Question 30

What is refactoring?

Answer 30

refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior

Question 31

What are some of the benefits of working in Flutter in regards to refactoring?

Answer 31

-all refactoring techniques used in Dart code can also be applied to the UI; -functions can return UI; -you can create widget classes that can wrap and organize UI elements and encapsulate functionality; -you can specify your UI in different files and import them; -separate UI from logic and data (models & views)

Question 32

Why do software projects fail?

Answer 32

-they don't do what the customers really want, -they are late, -they are over-budget, -they are hard to maintain and evolve

Question 33

Why are some codebases hard to maintain and evolve?

Answer 33

-inelegant design -old tech(COBOL, Fortran) -lack of testing or insufficient test coverage

Question 34

What is Agile?

Answer 34

-working closely, continuously with the customer to develop requirements and tests -maintaining a working prototype while deploying new features -checking with the customer on what's next to validate building the right thing

Question 35

What is Behavior-Driven Design?

Answer 35

act of asking questions about the desired behavior in the application before and after the development to reduce miscommunication

Question 36

What are user stories?

Answer 36

requirements written down from the perspective of the user, that user story eventually becomes an automated/acceptance test

Question 37

When a test verifies the presence of a user story in the software, what type of test is it?

Answer 37

acceptance test

Question 38

What are the benefits of using sketching to validate user stories?

Answer 38

-see if you interpreted what they wanted correctly and if that is indeed what they want

Question 39

What are the benefits of creating high-fidelity user interfaces for your user stories?

Answer 39

it will give the customer an exact idea of how the application would look like

Question 40

Creating high-fidelity user interface designs helps you do outside-in development or inside-out development?

Answer 40

outside in development

Question 41

What are some tools you can use for low-fidelity prototypes?

Answer 41

drawings, sketches, index cards

Question 42

What are some tools you can use for high-fidelity prototypes?

Answer 42

software such as figma and adobe xd

Question 43

What is it called when new code breaks old code?

Answer 43

Regression

Question 44

What is the problem with manual testing?

Answer 44

it's exhaustive, we cannot find all the errors in our code alone

Question 45

What is a test suite?

Answer 45

It is a set of tests that we write for our application to ensure it works.

Question 46

What are some of the benefits of automated testing?

Answer 46

-Catch bugs sooner and prevents them from being deployed -Reduces manpower to test an entire system -Doesn't require you leave your editor for testing

Question 47

Why is relying on a QA team to find and catch bugs an expensive mistake?

Answer 47

Humans will never be as effective or scalable as automated tests at catching regressions.

Question 48

What are the two major types of conceptual tests?

Answer 48

-Unit -Integration

Question 49

How does testing enable confidence?

Answer 49

A good test suite allows you to make large, sweeping changes in your codebase without fearing you will break something. Confidence allows you to move faster.

Question 50

If you are unsure of how an application is supposed to work, what is the best option?

Answer 50

Look at the test suite.

Question 51

What are the three steps to Test-Driven Development?

Answer 51

Red, Green, Refactor

Question 52

What is outside-in development? When should you use it?

Answer 52

Starts from the highest level of abstraction. From the perspective of the user walking through the application on their device, conceptually called an acceptance test, from a technical standpoint this is an integration test. As a feature is developed, you may need more lower level tests like unit test. Ensures no unnecessary code is written. I should use it when I have an understanding of how the user-interface will look and how the code will work ahead of time. The high-level test will guide the design of the feature all the way to completion.

Question 53

What is inside-out development? When should you use it?

Answer 53

I should use it when I don't know what my user interface will look like. This helps build up the code component by component.

Question 54

What are some of the benefits of Test-Driven Development?

Answer 54

-Confidence -Time Savings -Flow -Improved Design

Question 55

When should you not use TDD?

Answer 55

-When you don't know what you are doing yet and you want to explore options with a quick implementation. This is called a spike. -The program is small and easy to test manually -The program will only be used for a short time then be thrown away -You don't care if the program works.

Question 56

What are the three types of tests in Flutter?

Answer 56

Integration Tests Widget Tests Unit Tests

Question 57

Why are integration tests in Flutter slow?

Answer 57

These open an emulator.

Question 58

What can unit testing be used for?

Answer 58

-Check that we are able to create instances of the class when provided valid constructor - check that we are not able to create instances of the class when provided an invalid constructor -Does the function perform as expected under certain input/output combinations?