Software process and artifacts

Содержание

Слайд 2

OBJECTIVES Software process phases. Software process artifacts. Sets of artifacts. SPMP and SRS like leading artifacts.

OBJECTIVES

Software process phases.
Software process artifacts. Sets of artifacts.
SPMP and SRS like

leading artifacts.
Слайд 3

OUTCOMES FOR LESSON Students will: Know what are artifacts of software

OUTCOMES FOR LESSON

Students will:
Know what are artifacts of software development process
Distinguish

sets of artifacts
Understand which artifacts are primary for projects of any size
Be able to write SPMP
Be able to write SRS
Слайд 4

SOFTWARE PROCESS PHASES

SOFTWARE PROCESS PHASES

Слайд 5

Formulating the scope of the project Synthesizing the architecture Planning and

Formulating the scope of the project
Synthesizing the architecture
Planning and preparing the

business case

SOFTWARE PROCESS PHASES: INCEPTION

Слайд 6

Elaborating the vision Elaborating the process and infrastructure Elaborating the architecture

Elaborating the vision
Elaborating the process and infrastructure
Elaborating the architecture and selecting

the components

SOFTWARE PROCESS PHASES: ELABORATION

Слайд 7

Resource management, control and process optimization Complete component development and testing

Resource management, control and process optimization
Complete component development and testing against

evaluation criteria
Assessments of product releases against acceptance criteria of the vision

SOFTWARE PROCESS PHASES: CONSTRUCTION

Слайд 8

Beta testing to validate the new system Conversations of operational databases

Beta testing to validate the new system
Conversations of operational databases
Training of

users and maintainers

SOFTWARE PROCESS PHASES: TRANSITION

Слайд 9

What is it artifact in general meaning? What is it artifact

What is it artifact in general meaning?
What is it artifact in

context of software development process?

SOFTWARE PROCESS PHASES: Artifacts

Слайд 10

Deliverables Non-deliverables SOFTWARE PROCESS PHASES: Artifacts

Deliverables
Non-deliverables

SOFTWARE PROCESS PHASES: Artifacts

Слайд 11

SOFTWARE PROCESS ARTIFACTS: FOCUSED GROUPS. For Developers For Users For Customers

SOFTWARE PROCESS ARTIFACTS: FOCUSED GROUPS.

For Developers
For Users
For Customers

Слайд 12

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS.

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS.

Слайд 13

Work breakdown structure Business case Release specifications Software development plan Release

Work breakdown structure
Business case
Release specifications
Software development plan
Release description
Status assessments
Software change order
Deployment

document

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Management Set

Слайд 14

Vision statement Software Requirement Specification User mockups Prototypes UML diagrams (USE

Vision statement
Software Requirement Specification
User mockups
Prototypes
UML diagrams (USE CASE)

SOFTWARE PROCESS ARTIFACTS. SETS

OF ARTIFACTS: Requirement Set
Слайд 15

Design model Test model Software architecture description SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Design Set

Design model
Test model
Software architecture description

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Design

Set
Слайд 16

Source code Custom components APIes of commercial components SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Implementation Set

Source code
Custom components
APIes of commercial components

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS:

Implementation Set
Слайд 17

Executable run-time files User manuals SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Deployment Set

Executable run-time files
User manuals

SOFTWARE PROCESS ARTIFACTS. SETS OF ARTIFACTS: Deployment Set

Слайд 18

Overview. Scope and goals. Organization. Schedule and Budget. Risk management. Sub-contract

Overview.
Scope and goals.
Organization.
Schedule and Budget.
Risk management.
Sub-contract management.
Communications and reporting.
Delivery plan.
Quality

assurance.
Configuration and change management.
Security aspects.
Definitions, abbreviations, references, revision.

SOFTWARE PROJECT MANAGEMENT PLAN

Слайд 19

What the motivation for this project is Who the customer is

What the motivation for this project is
Who the customer is
What

the project will deliver. Is it a new product or an extension of an existing one?
What it will cost
How long it will take
Which organizations are involved
Which other projects depend on the project result
Which other projects contribute with their results

SPMP: Overview

Слайд 20

Functional goals Strategic goals Business goals (e.g.: time-to-market, cost) Technological goals

Functional goals
Strategic goals
Business goals (e.g.: time-to-market, cost)
Technological goals
Quality goals
Organizational goals
Other

goals, e.g.: usability, portability, etc.
Constraints

SPMP: Scope and goals

Слайд 21

Functional goals Strategic goals Business goals (e.g.: time-to-market, cost) Technological goals

Functional goals
Strategic goals
Business goals (e.g.: time-to-market, cost)
Technological goals
Quality goals
Organizational goals
Other

goals, e.g.: usability, portability, etc.
Constraints
Scope: Clarify what the project will (and will not) deliver, in order to avoid future shifts in the level of ambition. List of deliverables & corresp. receivers.

SPMP: Scope and goals

Слайд 22

Boundaries & interfaces Owners Receivers Sub-contractors Suppliers Cross Functions Other projects

Boundaries & interfaces
Owners
Receivers
Sub-contractors
Suppliers
Cross Functions
Other projects
Project responsibilities
Project management
Projects teams

SPMP: Organization

Слайд 23

WBS Schedule and Milestones Budget Development Process Development Environment Measurements Program SPMP: Schedule & Budget

WBS
Schedule and Milestones
Budget
Development Process
Development Environment
Measurements Program

SPMP: Schedule & Budget

Слайд 24

Слайд 25

Describe the procedure to be used for managing risks in the

Describe the procedure to be used for managing risks in the

project. The procedure should specify who is responsible for risk management, when risk situation is regularly considered (e.g. at each project status meeting), and which roles risks are communicated to, etc.

SPMP: Risk Management

Слайд 26

List which part of work is out-sourced to which sub-contractor. Refer

List which part of work is out-sourced to which sub-contractor.
Refer to

the sub-contractor’s agreement that should include or refer to the statement of work, the execution process, milestones, quality assurance, configuration management, communication structure, hand-over procedure, acceptance criteria, and quality audits.

SPMP: Sub-contract management (if any)

Слайд 27

State the principles for reporting and distributing information within the project

State the principles for reporting and distributing information within the project

for the different groups of internal and external stakeholders. Include, for example, how often the reporting will take place, the type of reports or information, the type of media in which it is presented, and the type of meetings that will take place.

SPMP: Communication and Reporting

Слайд 28

List here all deliverables from the project and who the receivers

List here all deliverables from the project and who the receivers

of the deliverables are. Indicate also the planned delivery date. Take in consideration both strategic and technical aspects

SPMP: Delivery Plan