OSD PROCESS

TRAINING

DATE: 12/ Mar/ 2009

TRAINER: HOA TRAN
Purpose

Prepare the knowledge for the detail process

training by:
 Explaining the Abbreviations used in Process
 Explaining the general concepts used in Process
 Introduce the relationship between OSD’s
processes
 Overall about the OSD’s process
Some definitions
 Work Breakdown Structure (WBS) : An arrangement of work
elements and their relationship to each other and to the end
product.
 Entry Criteria: States of being that must be present before an
effort can begin successfully
 Exit Criteria: States of being that must be present before an
effort can end successfully.
 Stakeholder : A group or individual that is affected by or is in
some way accountable for the outcome of an undertaking.
Stakeholders may include project members, suppliers,
customers, end users, and others.
 Relevant Stakeholder: A stakeholder that is identified for
involvement in specified activities and is included in a plan.
Some definitions
 Requirement:
 A condition or capability needed by a user to solve a problem or achieve an objective (1).
 A condition or capability that must be met or possessed by a product or product component to satisfy a contract,
standard, specification, or other formally imposed documents (2).
 A documented representation of a condition or capability as in (1) or (2).
 Customer Requirement : The result of eliciting, consolidating, and resolving conflicts among the needs,
expectations, constraints, and interfaces of the product's relevant stakeholders in a way that is acceptable
to the customer.
 Product Requirement:
 A refinement of the customer requirements into the developers’ language, making implicit requirements into explicit
derived requirements. (See also “derived requirements” and “product component requirements.”)
 The developer uses the product requirements to guide the design and building of the product .
 Product Component Requirements: A complete specification of a product component, including form,
function, and any other requirements
 Product Component: a work product that is a lower level component of the product. Product
components are integrated to produce the product. There may be multiple levels of product components.
 Work product: A useful result of a process. This can include files, documents, products, parts of a
product, services, process descriptions, specifications, and invoices.
 A key distinction between a work product and a product component is that a work product is not necessarily part of the
product. (See also “product” and “product component.”)
 Technical Requirement: Properties (attributes) of products or services to be acquired or developed.
 Nontechnical Requirement: Contractual provisions, commitments, conditions, and terms that affect how
products or services are to be acquired.
Some definitions
 Quality: The ability of a set of inherent characteristics of a product, product
component, or process to fulfill requirements of customers.
 Quality Assurance: A planned and systematic means for assuring
management that the defined standards, practices, procedures, and methods of
the process are applied
 Root Cause: A source of a defect such that if it is removed, the defect is
decreased or removed.
 Root Cause Analysis: The analysis of defects to determine their root cause.
 Quality Control: The operational techniques and activities that are used to fulfill
requirements for quality.
 Verification: Confirmation that work products properly reflect the requirements
specified for them. In other words, verification ensures that “you built it right.”.
 Validation: Confirmation that the product, as provided (or as it will be provided),
will fulfill its intended use. In other words, validation ensures that “you built the
right thing.”.
 Peer review: The review of work products performed by peers during
development of the work products to identify defects for removal.
Some definitions
 Process Owner: The person (or team) responsible for defining and
maintaining a process.
 Baseline: A set of specifications or work products that has been
formally reviewed and agreed on, which thereafter serves as the basis
for further development, and which can be changed only through
change control procedures.
 Tailoring: Tailoring a process makes, alters, or adapts the process
description for a particular end. For example, a project establishes its
defined process by tailoring from the organization’s set of standard
processes to meet the objectives, constraints, and environment of the
project.
 Version Control : The establishment and maintenance of baselines
and the identification of changes to baselines that make it possible to
return to the previous baseline.
Some Abbreviations
 MD: Managing Director
 PM: Project Manager
 TL: Team Leader
 BA: Business Analyst
 DEV: Developer
 QA: Quality Assurance
 QC: Quality Control
 CUS: Customer
 HR: Human Resource
 NA: Network Admin
 TM: Team member
OSD Process

 OSD have 6 Processes

 Sales
 Requirement Development and Management
 Technical
 Quality Control
 Project Management
 Project Working Environment Management
Relationship between 6
processes
Prj Management
-provide fw for mag prj;
-provide practical gls
for planning, executing
&monitoring prj

Sales Req Dev& Technical Quality Control

Define the process Management define the technical Test & fix bug to
for conducting some process for OSD’s ensure the quality
works when starting Dev & manage the software dev process before delivering to
a project in OSD. cus, product& product the customer
component reqs

Prj Working
Env Magt
manage the nw to
support the prj from
the begin to finish
Sales
S
tart

Rec
eiveaLe a
d ’s -B
usinessBro
chure
M
D R
eques
tforane w -Qu
o ta
tio
nT e
m p
late
Projec
t

{Optio n
al }:
-Con trac
tT em p
late
M
D E
valu
ateth
eLe
ad -ND A Templa
te
-In
vo iceT e
m pla
te

P
ass
ed ?
- S
ig
nedN
D A
- Q&A Lis
t

Y
es

N
o - Custo
m e
r
D
eve
lopL ea
d’s Req
uirementSurv
ey
B
A , M
D , L
ead -UserRequire
m e
ntLis
t
Require
m e
nts

W
orko
nth
ePro
ject -P
roje
ctE
stim
atio
n
D
EV , P
M ,M
D
Quote

M
D

R
eje
ctth
ePro
jec
t N
o O
k ?

Y
es

-Contra
ct / A
gre
eme
nt
S
ig
nac o
ntra
ct / -In
voice
M
D , L
ead -SOW
a
greement

M
D , S
ale
s -In
voic
e
F
ollo
w u
pIn
voic
e

E
nd
Requirement Development and
Management
Start

- Customer
Requirement Survey
DeveloptheCustomer -Q&AList
BA
Requirement - User Requirement List

DevelopProduct &
BA Product Component PL , BA , MD , TMs ManageRequirement
Requirement

- ChangeRequest
- SRS
Registry
BA , TL , TMs ValidateRequirement - UseCaseScenarios
-TraceabilityMatrix

End
Technical
- User Requirement List
Start - SRS
- UseCaseScenarios
- Codingconvention

- HighLevel Design
BA , TL , CUS , - Unit / Functional
Design Specifications
DEV , TMs

DEV , TL
- HighLevel Design
- Unit / Functional
Implement CodeTask Specifications
No -CodingConvention

Designok ?

Yes

End
Quality Control
Start

- Detail Schedule
- User Requirement List

- Detail Schedule
(Including Test
QC, TL Plan for Testing
Schedule)

- User Requirement List

-Use Case Scenarios
QC/ CUS, all TMs, - SRS
Prepare for Testing
NA - High/ Low level design

QC/ CUS, TL, - Test Case

Execute Test& Fix Bug
DEV

- Bug Report
QC Report

End
Project Management
S
tart - K
ic
k - o
ffP
res
e n
tatio
n

- Re
sourc
eRe
port

- Custo
m e
r
MD , PM , T L , HR , Requ
irementS urv
e y
TMs , A llrelev
a n
t K
ic
k -o
ffP
rojec
t - UserRequire
m e ntL
ist
sta
keh
olde rs

- Te c
h nic
alPropos
a l (If
any )
TL, P
M , TMs P
roje
ctP
Lan
nin
g -DetailSchedule
-ProjectPlan

- P
rojectPla
n
- De
tailSc
h edu
le

TL, TMs TL TM , TL

E
xec
uteP
roje
ct M
onito
r & Co
ntro
l
M
ana
geis
sue
P
roje
ct

- ProjectPla
n
- Projec
tScheduleW
ith - Is
sueLog
-ProjectWe eklyR e
p o
rt
Pro
g res
sR ep
ort
-DetailSchedu le

TL , All
S
tak
ehold
ers
- Proje ctPla
n
-Projec tWe ek
lyR ep
ort
-D e
tail Schedu le
- Proje ctSche duleW ith - P
rojec
tClo
sureRe
port
Clo
se -o
utP
rojec
t
Progres sRe port
- Is
s ueL o
g

E
nd
Project Working Environment
Management
Start

Set upaproject working

NA
environment

Troubleshoot the
NA , TM
workingenvironment

Withdrawtheworking
NA
environment

End
Q&A
END

 Thank you!