Software Development

Front 1

What is Software Engineering?

Back 1

Software Engineering is the “systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.”

Front 2

What are the goals (4) of Software Engineering?

Back 2

Economical
On-Time
High Quality
Meets Needs

Front 3

How does Software Engineering relates to CS as a whole?

Back 3

We can apply CS theories and functions, to the tools and techniques of problem solving to get solutions!

Front 4

What are the different parts of Software Engineering?

Back 4

Project Management, Software Design, Hardware Considerations, Programming, Software Specification, User Interface Design, User Documentation, Maintenance, Testing.

Front 5

Why is Software Engineering needed?

Back 5

Software engineering is necessary to become able to build software on time, on budget, within specification while minimizing defects, managing quality, cost, time, complexity, verifiable, maintainability, availability, reliability, dependability, performance, security, usability, and other attributes of software.

Front 6

Myths about Software Engineering

Back 6

MYTHS:
1) More developers = more work done
2) Deliverables ONLY include working project (screw documentation!)
3) More features = better!
4) Once it works, you're done!!!!
5) Quality can only be determined at run-time.
6) outsourcing means you're all done!
7) Software is flexible

Front 7

What is Version Control?

Back 7

Managing the change of documents.

Front 8

Uses for Version Control

Back 8

Backup & Restore, synchronizing work, track changes, track ownership, sandboxing, branching & merging, short/long-term undo.

Front 9

Distributed vs Central Version Control

Back 9

Distributed is faster (other than push/pull), can use without internet (other than push/pull), committing is local, every person has own personal copy, could be sucky for large projects or long history (YuUUUuuGe files).

Front 10

Mercurial Commands (hg)

Back 10

init : make repository
add : add files
commit : commit change // -u user, -m message
log : see history
status : current state of files (M, A, C, ?, !, I)
diff : see differences
update : change to specific version/recent
revert : go back to last commit
clone : make local copy
push : put commit into remote repository
pull : get changes

Front 11

Bill needs to pull the new changes into his repository, merge the changes, commit them and push the changes:

Back 11

•hg pull

•hg merge

•hg commit

•hg push

Front 12

What is Issue Tracking?

Back 12

A database for tracking work that needs to be done on the software

–Text file (2 person)

–Spreadsheet (small team)

–Database-backed system (small to large teams)

Front 13

What is Issue Tracking used for?

Back 13

Bug Reports

Front 14

What are bug reports and who uses them?

Back 14

A bug report is way to convince a developer to spend time and energy on your problem or feature idea.

Used by: Testers, Managers, Users, Developers, and those mysterious others...

Front 15

Bug Report Lifecycle

Back 15

Tester identifies a bug ->

files a bug report ->

Triager prioritize bug ->

developer fixes ->

Tester tests to see if fix worked ->

Bug report updated ->?

Front 16

Team Roles in Handling Bug Reports

Back 16

Tester: finds, investigates & reports
Developer: examine & either fixes, estimates, recommends deferring, argues its not a defect
Project Manager: prioritize and reassign
Project Team: reviews deferred defects & re prioritizes
Test Group: retests defects and either closes or sends new info to developers

Front 17

Ways motivate developers and overcome their objections?

Back 17

BEER... stroke ego, looks bad, interesting puzzle, affects a lot of users, trivial fix, embarrassment, management says so!

Front 18

Principles of writing a good bug report

Back 18

1. Clearly describe steps to reproduce the problem
2. Expected behaviours
3. Actual behaviours

Front 19

What is Software Testing?

Back 19

The dynamic verification of the behavior of a program on a finite set of test cases, suitably selected from the usually infinite executions domain, against the expected behavior.

Front 20

Types of testing

Back 20

Black-box, white-box, gray-box

Front 21

What is Black-Box Testing?

Back 21

Testing of a system without understanding the implementation.

Front 22

What are black-box testing techniques?

Back 22

Robustness Testing (values outside of domain) and Ad hoc/Exploratory (based on tester's skills, intuition and experience), equivalence partitioning (selecting the RIGHT test cases to cover all possible scenarios), Boundary value Analysis (choose cases at boundaries).

Front 23

What is Gray-box Testing?

Back 23

Testing of functionality, but also looking at how it is done to make sure that is correct also.

Front 24

What is White-box Testing?

Back 24

Testing software that tests internal structures or workings of an application, as opposed to its functionality.

Front 25

What is Unit Testing?

Back 25

A ‘unit’ is the smallest possible testable item.

Front 26

What is Test Fixture?

Back 26

Class containing one or more test methods

Front 27

What is Test Method?

Back 27

Method that executes a specific test

Front 28

What is Test Runner?

Back 28

Application that finds and executed test methods on

Front 29

What is Assertion?

Back 29

A Boolean expressions that describes what must be true when an action execute.

Front 30

What is UML?

Back 30

Unified Modelling Language

Front 31

Visibility Symbols:
+
-
#

~

Back 31

+ -> Public
- -> Private
# -> Protected
~ -> Package

Front 32

Three main components of the class in a UML diagram?

Back 32

Name of the class, attributes, and methods.

Front 33

What is the difference between “composition” and “aggregation”?

Back 33

The distinction is subtle, and has to do with if the object would exist after the containing object is destroyed. Composition wouldn't exist, and Aggregation would still exist.

Front 34

Italics means...?
Arrow means...?

Back 34

Italics: Abstract class
Arrows: Generalization

Front 35

What are exceptions?

Back 35

A situation where something ‘unexpected’ happened during normal execution of program

Front 36

Examples of Exceptions?

Back 36

Index out of bounds

Divide by 0

Unexpected input

Front 37

What are the two types of errors?

Back 37

Logic errors: internal logic; length, domain, invalid-argument, out_of_range.
Runtime: detected at runtime; range, overflow/underflow, system

Front 38

When you detect an error.... what you have to do?

Back 38

THROW AN EXCEPTION!
throw domain_error{“Divisor is 0 in function f()”}

Front 39

When do exceptions stop being 'thrown up the chain'?

Back 39

Exception is ‘thrown up the chain’ until either:

Exception is handled

Entire program terminates

Front 40

Try Catch Block...
Write general case!

Back 40

try{

}

catch () {

}

Front 41

Which catch does it go to?

Back 41

When an exception occurs in a try block, the first catch that matches the exception type is executed.

Front 42

What is the key idea of inheritance?undefined

Back 42

You get it from your parents!

Front 43

Design Principles (5)

Back 43

•Form consistent abstraction in same class

•Encapsulate implementation details

•Use inheritance to simplify design and reuse code

•Information hiding (complexity hiding)

•Keep coupling loose

Front 44

What is coupling?

Back 44

Coupling is the degree of interdependence between software modules; a measure of how closely connected two routines or modules are; the strength of the relationships between modules. Coupling is usually contrasted with cohesion.

Front 45

ADT and used for?

Back 45

Abstract Data Types: a collection of data and operations that work on that data (i.e. vector), hides implementation details, easy to change implementation, and works with ABSTRACTION! (not details)

Front 46

What is Inheritance good for?

Back 46

Avoiding duplication of code, model relationships, easily extend functionality.

Front 47

"Has a" ?
"Is a" ?

Back 47

“Has a”: use containment (i.e. data members)

“Is a”: use inheritance

Front 48

A is a B...
Who inherits from who?
Who is a subclass, super class, derived class, base class?

Back 48

A inherits the properties of B.
A is a subclass of B, B is a superclass of A, A is a derived class of B, B is a base class of A.

Front 49

Chain of calls...

Constructors call Base or Derived first...?
Destructors call Base or Derived first...?

Back 49

Constructor goes from the Base and goes down to the actual class. Destructors are the opposite.

Front 50

Employees and Persons have writeInfo();
Employees is a Person.
What do we use to call the Person version and how?

Back 50

Use SCOPING!!!
Inside the Employee class member function, we can write
Person::writeInfo();

Front 51

All data members and member functions are automatically inherited by a derived class except for....

Back 51

Functions which are overriden, constructors, destructors, assignment operators, and friends!

Front 52

Employee is a subclass of Person. How do we convert?
Person p{"John Doe"};

Employee e{"Joe Blow", 30000};

p = e; OR e = p; ?

Back 52

p = e; // legal, but you lose information

e = p; // illegal

SoooOOOo, use first one.

Front 53

Differences between Public, Private, and Protected?

Back 53

Public: All can use.
Private: Only the class can get access to it.
Protected: Stays in the family.

Front 54

3 Forms of inheritance?

Back 54

Specialization: uses public inheritance, adds new specialized attributes and behaviours.

Specification: uses public inheritance, base class specifies some behaviours but does not implement.

Restriction: Only subset of methods in base class used by client, private or protected, least common form.

Front 55

What is polymorphism?

Back 55

Means that a call to a member function will cause a different function to be executed depending on the type of object that invokes the function.

Front 56

Function overloading (static or dynamic)?

Back 56

STATIC!
Means determined at compile time.

Front 57

Binding the meaning to the form when the program is run (static or dynamic)?

Back 57

DYNAMIC BINDING!!!

Front 58

How is dynamic binding achieved in C++?

Back 58

Virtual functions

Front 59

How is a member declared as virtual?

Back 59

Writing virtual in front of its prototype.

Front 60

Why polymorphism for functions of same name?

Back 60

Avoid unnecessary if-thens or switches. Makes the code cleaner and easier to extend! Smells better ;)

Front 61

True or False: To be safe, destructors of any base class should NOT be called virtual! Only do this when you know what you are doing.

Back 61

FALSE!
Declaring a destructor virtual makes it possible for the correct destructor to be called by delete. If a class needs to have a destructor, the destructor should probably be a virtual one. To be safe, declare destructors in any base class virtual.

Front 62

How do we make something an abstract class?

Back 62

Give it a pure virtual function!

Front 63

How do we declare a pure virtual function?
Make one for a function draw that is a void type.
Can we implement it in this class?

Back 63

virtual void draw() = 0;

Technically yes, but for the purpose of this class, NO, the function is not implemented in this class.

Front 64

Can one declare objects of an abstract class?

Back 64

NO! One cannot do this. So stop trying!

Front 65

If a base class is abstract, how can its derived class be normal?

Back 65

All pure virtual functions must be override!

Front 66

What is typeid() ?
What do we need to include?

Back 66

The typeid() operator allows us to get a unique value for each type.

So you can do:

if (typeid(*p1) == typeid(Employee)) { ... }

#include

Front 67

Dynamic vs Static Casting

Back 67

Static_cast is used for cases where you basically want to reverse an implicit conversion, with a few restrictions and additions and performs no runtime checks.
Dynamic_cast is used for cases where you don't know what the dynamic type of the object is. You cannot use dynamic_cast if you downcast and the argument type is not polymorphic. If wrong, returns null pointer.

Front 68

Multiple Inheritance. Does C++ have this?
What does

class A : public B, public C { ... };

really mean?

Back 68

YES!

class A inherits all members from classes B and C.

Front 69

A is a B and is a C. B and C have printInfo() .

Let 'a' be of type A.

How do I call B's printInfo?

Back 69

a.B::printInfo();

Front 70

SOLID?

Back 70

S: Single Responsibility Principle
O: Open/Closed Principle
L: Liskov Substitution Principle
I: Interface Segregation Principle
D: Dependency Inversion Principle

Front 71

What is encapsulation?

Back 71

Information hiding. The less you know, the better!

Front 72

What is Single Responsibility Principle

Back 72

A class should have only a SINGLE responsibility (i.e. ONLY ONE potential change in the software's specification should be able to affect the specification of the class). Delegate!

Front 73

What is Open/closed principle?

Back 73

Software entities … should be open for extension, but closed for modification!

Front 74

What is Liskov substitution principle?

Back 74

Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program

Front 75

What is Interface segregation principle?

Back 75

Many client-specific interfaces are better than one general-purpose interface.

Front 76

What is Dependency inversion principle?

Back 76

One should “depend upon abstractions, [not] concretions".

Front 77

What's the best way to test a design?

Back 77

Try to change something!!!

Front 78

Three OO Design Principles?

Back 78

1. Code to interface, not implementation
2. Encapsulate what varies
3. Each class should only have one reason to change

Front 79

What is a cohesive class? What's it do?

Back 79

A cohesive class does one thing really well and does not try to do or be anything else. It has only one reason to change.

Front 80

What is leading cause of project failure?

Back 80

Teamwork Problems!

Front 81

Team Structures

Back 81

Hierarchical: chief exec -> team leaders -> project members (pyramid!).
Democratic/Open Structured: (whatever)

Front 82

Phases of Team Development?

Back 82

Forming: team comes together

Storming: disagreements (teams fail if stuck)

Norming: offering ideas, preferences, contributions

Performing: ideal phase, work hard & play hard

Front 83

What are these?

Back 83

Aggregation Association.
Aggregation shows a “part of” relationship.

Front 84

What is this?

Back 84

Composition Association.
Composition also shows a “part of” relationship.

Front 85

Fill in the blank.

Back 85

Generalization

Front 86

Fill in the blanks.

Back 86

Front 87

Whats wrong?

Back 87

Front 88

What is this?!

Back 88

Tight coupling with concrete instruments.

Front 89

What type of version control is this?

Back 89

Centralized.

Front 90

What type of version control is this?

Back 90

Distributed.