Koondkonspekt (Tarkvaratehnika)

Waterfall

• Requirements building blocks: analyze (analysis), design, build (development), test, deploy (täpsemalt alates slaid 26)

• More risky and costly than iterative method

• Design errors are captured before any software is written saving time during the implementation phase.

• Excellent technical documentation is part of the deliverables and it is easier for new programmers to get up to speed during the maintenance phase

• The approach is very structured and it is easier to measure progress by reference to clearly defined milestones

• The total cost of the project can be accurately estimated after the requirements have been defined (via the functional and user interface specifications)

• Testing is easier as it can be done by reference to the scenarios defined in the functional specification

• Clients will often find it difficult to state their requirements at the abstract level of a functional specification and will only fully appreciate what is needed when the application is delivered

• It then becomes very difficult (and expensive) to re-engineer the application

• The model does not cater for the possibility of requirements changing during the development cycle

• A project can often take substantially longer to deliver than planned

Iterative development

• We do risky things at first

• we might build more than needed

• Defects are more likely to be detected earlier than in waterfall → overall project time and cost is reduced

Use case and story

• Larger than user story

• User story is similar to one scenario of a use case (üks mullike koos aktoriga).

• Use cases are permanent artifacts, story cards are torn up

• use case is a document agreement between customer and developers

• Story is written to facilitate release and iteration planning

• Split- A large story can be split into two or more smaller ones of different sizes; useful for breaking up epics

• Combined- Two or more small stories can be combined into one

• Added- New stories can be added to an existing backlog

• Deleted- Existing stories can be deleted from a backlog

• Epic- Large initiatives delivering new products, solutions, or services to customers. Comprised of a large collection of features

• Feature- Provides values to users. Realized by some number of user stories

• User Story- Represents a user’s need. Planning ítem

Confirmation

5 principles of lean

1. Value- define value precisely from the perspective of the end customer

2. Value stream- identify the entire value stream for each service, product or product family and eliminate waste

3. Flow- make the remaining value-creating steps flow

4. Pull- as flow is introduced, let the customer pull (i.e., provide what the customer wants only when the customer wants it)

5. Perfection- pursue perfection

LEAN

• First Lean system was applied in Toyota (1953) to:
• reduce inventory and production cycle time
• improve productivity

Toyota production system (TPS)

• product

• process

• rapid product flow

• built-in quality

• just-in-time (JIT)

• automation

Muda, mura, muri

8 wastes in production (WIP) (täpsemalt alates slaid 260):

• in team potential (slaid 534)

• in code development (slaid 535)

• in project management (slaid 536)

Lean production house:

Scrum (al slaid 352)

• Manages product backlog

• Optimizes the value of the product

• Represents the customer

• is accountable for maximizing the value of the product resulting from the work of the Scrum Team

• Developing and explicitly communicating the Product Goal

• Creating and clearly communicating Product Backlog items

• Ordering Product Backlog items

• Ensuring that the Product Backlog is transparent, visible and understood

• manages the scrum process

• Removes impediments

• team protector

• troubleshooter

• scrum guide

• is accountable for establishing Scrum as defined in the Scrum Guide

• Cross-functional

• Self-managed

• Create a plan for the Sprint, the Sprint backlog

• Instilling quality by adhering to a Definition of Done

• Adapting their plan each day toward the Sprint Goal

• Holding each other accountable as professionals

• No one (not even the Scrum Master) tells the Developers how to turn Product Backlog into usable Increment

Events (al slaid 383):

Artifacts:

Extreme programming (XP)

Kanban

Lean startup

1. Entrepreneurs are everywhere- You don't have to work in a garage to be in a startup

2. Entrepreneurship is management- A startup is an institution, not just a product, so it requires management, a new kind of management specifically geared to its context

3. Validated learning- Startups exist not to make stuff, make money, or serve customers. They exist to learn how to build a sustainable business. This learning can be validated scientifically, by running experiments that allow us to test each element of our vision

4. Set up build - measure - learn process- The "Build-Measure-Learn feedback loop is at the core of the Lean Startup model

5. Use innovation accounting- To improve entrepreneurial outcomes, and to hold entrepreneurs accountable, we need to focus on the boring stuff: how to measure progress, how to setup milestones, how to prioritize work. This requires a new kind of accounting, specific to startups

1. Ideas

2. Build

3. Product

4. Measure

5. Data

6. Learn

waterfall vs scrum vs kanban

Lean vs traditional aka waterfall

RUP phases (al slaid 810):

Testing

1. Complete testing is impossible

2. Software testing is not simple activity

3. Testing is risk-based

4. Testing must be planned

5. Testing requires independence (SQA team).

6. Quality software testing depends on:
1. Good understanding of software products and related domain application
2. Cost-effective testing methodology, coverage, test methods, and tools
3. Good engineers with creativity, and solid software testing experience

1. Unit testing (slaid 975)
• –Purpose: to verify that the component/module functions properly
• Normally white box oriented

2. Integration test (slaid 976)
• Normally black box oriented

3. System test (slaid 977)
• Normally black box oriented

4. Acceptance test (slaid 978)
• Normally black box oriented