Dr. Rob Hasker. Logistics Class roster, attendance policy Book, Schedule, policies, grading Course web site Prereq check: SE 2800, Software.

SE 3800SOFTWARE ENGINEERING PROCESS II

Dr. Rob Hasker

Logistics

Class roster, attendance policy Book, Schedule, policies,

grading Course web site Prereq check:

SE 2800, Software Process I SE 2832, Verification

Curricular ContextSenior Design

SE 3800 Process II

SE 2800 Process I

SE 2832 Verification

Software Development Lab

SE 3821 Requirements

SE 2800 Review

What do you remember from SE 2800? Process models? Software development activities? Scrum process? Teamwork issues?

What is unclear?Pair

Exercise

Practice vs. Process

Practice = “what we do” Analyze requirements, create

architectural/design solutions, implement, verify

Process = “how and when we do it” Plan, organize, measure, make/meet

commitments, ensure quality, control, improve, adapt

Activities

Planning & tracking Risk assessment and

mitigation Requirements

analysis & specification

Architecture and high-level design

High level design review

Detailed design

Detailed design review

Implementation (coding)

Code review/inspection

Unit testing Integration testing System testing Acceptance testing DeploymentThere are many different ways to

organize these activities, but all must be included.

Process Models

Frameworks for organizing development activities

One pass, sequential – waterfall Iterative/incremental

Agile: XP, Scrum, Feature-driven development

Personal Software Process/Team Software Process (SEI)

Highly prescriptive Cleanroom, formal

Course Goals

Build on SE 2800: increase knowledge and skill in following software process

Tailor software process (especially Scrum) to project needs

Add continuous integration, verification, software quality components

Industrial strength tool use

Textbooks

Essential Scrum: A Practical Guide to the Most Popular Agile Process Kenneth S. Rubin, Addison Wesley, 2013 Plan: cover rest of this book

Continuous Integration: Improving Software Quality and Reducing Risk Paul M. Duvall et. Al, Addison Wesley, 2007 Historically: software quality achieved

through process alone CI: automate much of this process

Tools

Atlassian JIRA/Agile

planning & tracking

Confluence (wiki) Bitbucket

Git repository Sourcetree

JUnit Test automation

Jenkins/Teamcity Continuous build

The big picture

1st year: implementation 2nd year: basic elements of SE

process 3rd year: project experience

This course: software quality goals and tools, tailoring process to project

Scrum Refresher

Who are these people? Product owner ScrumMaster Development team

Scrum Refresher

Who are these people? Product owner ScrumMaster Development team

What will be developed, and in what order

Guiding team on creating, following process; removing impediments

5-9 people: determines how to deliver what product owner requests.

Scrum Refresher

Who are these people? Product owner ScrumMaster Development team

Is the product owner the only interface to the customer?

How to qualify as ScrumMaster? How to approach being ScrumMaster?

Reviewing Scrum Activities The Scrum process cycle

Pair Exercise

Reviewing Scrum Activities The Scrum activity cycle

Sprintplanning

Sprint executio

n

Sprint review

Sprint retro-

spective

Daily scrum

Product Backlog

Product backlog items (PBIs)

What qualifies as a PBI? Who manages these? What is “grooming”? How are PBIs ordered? How are PBIs estimated?

Scrum review

Product roles Scrum activities Product backlog Read: Ch. 2, 3

At start of Wed. class, submit hard copy, typed report on assigned Ch. 3 principle

Heading: student named, assigned principle Definition: what assigned component means

with examples Assess: reasoned opinion of value &

correctness of each component; exceptions?