Midterm

Question 1

What does bad Software engineer procatices create?

Answer 1

• failed projects
• lost money
• stressed employees
• poor customer value

Question 2

Name 5 items of a user story.

Answer 2

1) Role-Goal-Benefit
2) Notes
3) Definitions of Done
4) Tasks
5) Effort Estimate

Question 3

Name 6 properties of a good user story.

Answer 3

Independent
Negotiable
Valuable to users or customers
Estimable
Small
Testable

Question 4

What does it mean for a user story to be independent?

Answer 4

• Little dependence between stories
• Keeps development flexible
• Makes estimation easier

Question 5

What does it mean for a user story to be negotiable?

Answer 5

• Details are negotiated between developers and users

- Stories become reminders of what has been negotiated

Question 6

What does it mean for a user story to be valuable to user/customer?

Answer 6

• Make sure customer can estimate value of a story

- Not intended to be valuable only yo developers

Question 7

Who is a customer?

Answer 7

Purchaser: person who pays for the software.
User: person who uses the software.

Question 8

What does it mean for a user story to be estimable?

Answer 8

• a developer should be able to estimate how lind a story should take to complete
• helps in planning
• problems:
  lack of domain knowledge -> ask customer
  lack of technocal knowledge -> burst up on tech
  story is too big -> break it up

Question 9

What does it mean for a user story to be small?

Answer 9

• stories should be “just the right size”
• rule-of-thumb: half a day to several days to implement
• too big:
• > estimate inacccurate + no value delivered until story is complete
• > compound suggests break it up
• too small:
• > writing down the story may take longer than implementing it
• > combine if too small

Question 10

What does it mean for a user story to be testable?

Answer 10

• the story should have a test that goes with it to demonstrate that the story is implemented
• two types:
  1) Automated
  2) Manual

Question 11

Describe the process of decomposing a user story.

Answer 11

• Look for “entities” and “responsibilities”.
• Relate the entities
• Identify veebs
• Build a diagram

Question 12

Name and describe two common phases of Software Design.

Answer 12

1) Architectural Design
- determining which sub-system you need
2) Detailed design
- looking at the statistics and dynamic of your system

Question 13

What is a aequence diagram?

Answer 13

Sequenced diagram is a diagram used to describe sequences of invocations between the objects that comprise the system.

Question 14

Name 6 steps of refactoring.

Answer 14

1) Make sure all your tests pass
2) Identify the code smell
3) Determine how to refactor this code
4) Apply the refactoring
5) Run tests to make sure you didn’t break anything
6) Repeat until the smell gone

Question 15

How to refactor magic numbers?

Answer 15

To refactor magic numbers replace it with a symbolic constant.

Question 16

How to refactor repeated lines of code?

Answer 16

To refactor repeated lines of code extract method.

Question 17

How to refactor same method in two classes?

Answer 17

To refactor same method in two classes, pull up method.

Question 18

How to refactor almost duplicated code?

Answer 18

To refactor almost duplicated code, move to template method.

Question 19

How to refactor long method?

Answer 19

To refactor ling method, do one of :
Extract Method
Replace Temp with Query
Replace Method with Method Object
Decompose Conditional
Consolidate Conditional Expression

Question 20

How to refactor complicated conditionals?

Answer 20

To refactor complicated conditionals, decompose conditional.

Question 21

How to refactor switch statement/typed conditional?

Answer 21

To refactor switch statement/typed conditional, replace conditional with polymorphism.

Question 22

How to refactor one class doing the work of two?

Answer 22

To refactor one class doing the work of two, extract class.

Question 23

How to refactor data clump?

Answer 23

To refactor data clump, introduce parameter object.

Question 24

How to refactor divergent changes?

Answer 24

To extract divergent changes, extract class.

Question 25

How to refactor shotgun surgery?

Answer 25

To refactor shotgun surgery, move method/field.

Question 26

How to refactor needing comments to explain the code?

Answer 26

To refactor needing comments to explain the code, extract functionality/introduce assertion. When you feel the need to write a comment first try to refactor the code so that any comment becomes superfluous.

Question 27

Define broken code.

Answer 27

If module doesn't not have one of the following three functions it is broken: 1) To execute according to its purpose 2) To afford change 3) To communicate to its readers

Question 28

Name 3 cases when you don't need to refactor code.

Answer 28

1) When the tests are failing 2) When you should just rewrite the code 3) When you have impending deadlines

Question 29

Name commons code smells.

Answer 29

- Magic Numbers - Duplicated Code - Long Method - Complicated Conditionals - Switch Statements/Type Conditionals - Large class (doing the work of two) - Divergent Change - Shotgun Surgery - Comments

Question 30

Name 6 project risks.

Answer 30

1) User 2) Requirements: continually changing, inadequately identified; unclear, incorrect 3) Project Complexity - new technology, high technical complexity, immature technology, first use of technology 4) Planning and Control - poor process oversight 5) Team - lack of experience 6) Organizational environment - unstable organisation

Question 31

What is a software process?

Answer 31

A software process is a structured set of activities to develop a software system.

Question 32

Name and describe software process models.

Answer 32

1) Waterfall model - separate and distinct phases of specification and development 2) Spiral - incremental prototyping with risk management 3) Agile models/principles - iterative approach with high customer communication

Question 33

Name steps of waterfall software process model and tell what benefits and drawbacks it has.

Answer 33

Waterfall Model: requirements design coding testing maintenance Benefits: - Good for well-understood, complex projects (tackles all planning up front, no midstream changes = efficient process) - Provides support for an inexperienced team (easy-to-follow model, slow progress, reviews at each step) Drawbacks: - Getting requirements right up front - Hard to manage risks - Reactive to errors but not to changing requirements.

Question 34

What are the benefits and drawbacks of spiral model?

Answer 34

Benefits: - Manages risk by repeated prototyping - Requirements changes incorporated iteratively Drawbacks: - High administrative overhead - Can be overly conservative if you have high confidence in the project outcome

Question 35

What is the goal of agility?

Answer 35

To develop software in the face of changing environment and constrained resources.

Question 36

What are advantages and disadvantages of Agile models?

Answer 36

``` Advantages: - Lower risk - Close customer involvement - Better visibility - Compliant with changes Disadvantages: - Harder to enforce with inexperienced programmers - Close customer involvement - Hard to estimate completion schedule - Increases the risk of feature creep - Can be inefficient ```

Question 37

What are advantages and disadvantages of Test-Driven Development?

Answer 37

``` Advantages: - Maintainable, Flexible, Easily Extensible - Clean Interface Disadvantages: - Big time investment - Additional Complexity - Design Impacts - Continuous Tweaking ```

Question 38

Name roles, ceremonies and artifacts of scrum framework.

Answer 38

``` Roles: - Product Owner - Scrum Master - Team Ceremonies: - Sprint Planning - Daily Scrum Meet - Sprint Review - Sprint Retrospective Artifacts: - Product Backlog - Sprint Backlog - Burndown Charts ```

Question 39

What is the role of product owner in scrum process?

Answer 39

- Defines the features of the product - Prioritizes features according to market value - Adjusts features and priority every iteration, as needed

Question 40

What is the role of Scrum Master in scrum process?

Answer 40

- Facilitates Scrum process - Helps resolve impediments - Shields team from external interferences - Not a “real manager”, he serves the team