Chapter 7: Software Engineering

Question 1

The software engineering discipline

• Distinct from other engineering fields:
• CASE (Computer Aided Software Engineering) tools:

Answer 1

• Distinct from other engineering fields:
  
  • Prefabricated components
  • Metrics
• CASE (Computer Aided Software Engineering) tools:
  
  • Project planning
  • Project management
  • Documentation
  • Prototyping and simulation
  • Interface design
  • Programming

Question 2

The Software lifecycle

Answer 2

Development, Deploy, Maintenance and repeat!

Question 3

The development phase

Answer 3

Requirement analysis
Design
Implementation
Testing

Question 4

Software engineering methodologies

Answer 4

• Waterfall model
• Incremental model (extending repeatedly)
• Iterative model (refining repeatedly)
• Agile methods

Question 5

Scrum (1)
It’s the most popular agile development method

Different roles:

Answer 5

• Product Owner maintains a product backlog
• Development team 3-9 people
• Scrum master (not a traditional project manager)

Question 6

Scrum (2)
Workflow:

• Sprint:
• Sprint planning:
• Daily scrum:
• Sprint review:
• Sprint retrospective:

Answer 6

• Sprint: is an iteration of 2-4 weeks and should have some deliveries
• Sprint planning: planning the upcoming sprint
• Daily scrum: daily morning meeting (stand-up)
• Sprint review: the work of the sprint is presented and reviewed
• Sprint retrospective: continuous process improvements

Question 7

Modularity (1)

Answer 7

• Module: a manageable unit of software
• Modules vs
  Procedures (imperative programming)
  Functions (functional programming)
  Objects (object-oriented programming)
  Components (component architecture)

Question 8

• Coupling:
• Cohesion:
• Information hiding:

Answer 8

• Coupling: the linkage between modules (should be minimized):
  control coupling
  data coupling
• Cohesion: the internal binding within a module (should be maximized)
  Logical cohesion
  Functional cohesion
• Information hiding: restricting information to a module (should be achieved)

Question 9

Structure chart

Answer 9

• A structure chart shows the breakdown of a system to its lowest manageable levels. They are used in structured programming to arrange program modules into a tree.

Question 10

Data Flow diagram

Answer 10

• Data flow diagrams provide a graphical representation of how information moves between processes in a system. Data flow diagrams follow a hierarchy; that is, a diagram may consist of several layers, each unique to a specific process or data function

Question 11

Use Case diagram (UML)

Answer 11

• A UML is a way to summarize details of a system and the users within that system.

Question 12

Class diagram (UML) - relationships

Answer 12

• Class diagram describes the structure of classes and the relationships between classes.
• Entity relationship diagram describes entities and relationships between entities

Question 13

Design patterns

Answer 13

• Design patterns are “templates” for solving recurring problems
• Examples:
  adapter pattern (adapts the interface)
  decorator pattern (extends the interface)

Question 14

Software testing strategies

Answer 14

• Glass box testing (white box testing):
  The tester is aware of the internal structure of the software (the source code)
  Pareto principle: focus on the modules where the problems seem to be
  basis path testing: each instruction in the software is executed at least once
• Black box testing:
  Tests that do not rely on knowledge about the internal structure of the software (tests from the user’s point of view)
  Boundary value analysis
  Beta testing (tested by external users)