Figure 8.1 The eight phases of Sun’s structured process. © 2003 Crnkovic, Asklund, Persson...
-
Upload
avis-francis -
Category
Documents
-
view
215 -
download
1
Transcript of Figure 8.1 The eight phases of Sun’s structured process. © 2003 Crnkovic, Asklund, Persson...
Figure 8.1 The eight phases of Sun’s structured process.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
P6Deploy
P7Sustain
P8Retire
P5Customer
Acceptance
P4System
test
P3Develop
ImplementTest
P2Plan
P1Concept
Figure 8.2 Product approval committees.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Product Approval Committee Chair
Marketing Sales FinanceDev.Eng. Operations
Service/Support CTO CA
Figure 8.3 Phase completion reviews.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Review
no
gord.
Review
no
gord.
Review
no
gord.
Review
no
gord.
Review
no
gord.
Review
no
gord.
Review
no
gord.
P6Deploy
P7Sustain
P8Retire
P5Customer
Acceptance
P4System
test
P3Develop
ImplementTest
P2Plan
P1Concept
Figure 8.4 A transparent interface to SCM tools.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
SNIFF+
RCS commands
RCSrepository
ClearCase
ClearCaserepository
User
Transparent access
Conversion from RCS to ClearCase
Figure 8.5 The PPDC network architecture.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
PPDC Network Architecture
PSTNISDNPSTNISDNPSTNISDN
HLR
VMSC
GMSC
BS
SMS -C
BackboneIP Network
ApplicationServers
BillingSystem
PMSC
NOCOSSHLR
VMSC
GMSC
BS
SMS -C
T1
Existing functionality
New functionality
Interface
Figure 8.6 Example of an Ericsson product structure.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
system
subsystem
function block
function unit
subfunction
hardware units
Functional structure
software units
Realization structure
Delivery structure
Delivery unit
parts
parts
Project structure
Project
Project struct.
Documents
Commercial structure
Product
Product packages
Figure 8.7 Generic project organization and roles in a large project.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
SubprojectManager
ProjectManager
ProjectStaff
Total Project Manager
ProjectSteering Group
ProjectSponsor
Reference Group
Reference Group
ProjectManager
ProjectManager
SubprojectManager
SubprojectManager
SteeringFunctions
ManagingFunctions
ExecutingFunctions
People responsible for carrying out the activities
Figure 8.8 Example of project organization from the PPDC product line.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
TCM – Program Production FENIX – Project for Packet data for PDC MS Lab – Mobile Test Lab RNA – Radio Network Applications OSS – Operating Support System SS – Switching SIT – System Integration and Test BSP – Base Station Products BSA – Base Station Applications SPP – Packet Data on TRAU-96 and C-TRA FOA – First Office Application
System
ProjectStaff
Project Manager 1 & 2
FENIX TCM
Requirement Coordinator Technical Coordinator Test Coordinator Configuration Manager Quality Coordinator Acceptance Coordinator Hardware Coordinator Librarian Project Administrator
MS Lab RNA
System Test
SPP BSA BSP
SIT SS
Customer Services
OSS
FOA
SubprojectManagers
ManagingFunctions
Figure 8.9 Time-to-market flow for PDC systems.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Marketing
DesignProductmanagement
specify
product
design &test
verifyDefine business
opportunity
Define prod.con.
Time to marketflow
Time to customerflow
Maintenance &support
Customer
Time to market
Figure 8.10 The four different subsystems in PRIM.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Product Document
PRIM
PS
Product Structure
IS
Information structure
Document Data
DDPD
Product Data
Figure 8.11 The baseline content.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Baselines
DELTA
DataServer
GASK
PRIM
DataServer
Testreport
Auditreport
CRs
TroubleReports
MoMs
Baseline report
ConfigurationQualityDeviationsDecisions
Time
Figure 8.12 The CR flow.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Delta
CR
CR
User
LocalCCB
Product managerProject Members
CCBMailbox
CRLog
MaintenanceCCB
MainCCB
UpdateCR log
Figure 8.13 Overview PPDC information flow.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Customer
PEACE
Req.
DOORS
Req.Prod. mgmtProj. members
DELTA
MRSMRS
GASK
Design
SWAXE
deliveries
PRIM
Product str.
Localfile server
Program prod.
Production design when ready for function test
FOA/Roll Out
When test performed
ALEX
Customerproduct info
Customer
CR
Different archives for sw or hw
REQUIREMENT
DEVELOPMENT
BUILD &RELEASE
DWAXE
Design and deliveries
Figure 8.14 The requirement flow in the product specification phase.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
To DesignMRS
Delta
CR
PEACE
Customer
DOORSNew req.
Figure 8.15 Information flow for software and hardware development.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Delta
SwaxeGASK
Local Archives
PRIM
ClearCase
Productspecification
SW-design
Figure 8.16 Information flow for hardware design.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Delta LocalDatabase
CADdesign
GASK PRIM
GOLF Otherdb
HW development
Functional test System test FOA Rolling product
TTC
Figure 8.17 Software program and document library production.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Delta
GASK Dwaxe PRIM
LocalDB
ClearCase
Golf
MSH
Prog.
ALEX
Functional test System test FOA Rolling product
Swaxe
Hardware
Faults
Programs
Documents
Figure 8.18 Information flow and tools used in the design and manufacturing processes. The following abbreviations are used: Design status (DS), production ready status (PR), design just started (DS-/PR-), ready for preproduction (PR1/DS1), product test doc (PRA/DS4), ready to be sold (PRA), and product revision information (PRI).
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Design phase
Design EngineeringPrototype
FactoryPrototype Mass ProductionPre series
Production phase
BOMmanagement
Engineeringchanges,Customisations
Engineeringdata flow.
Excelsheet PRIM
PRIMstatus
PCPProcess
EDA
CASE
LocalArchivePRIM Copy
Process
MDA
PRIMCOM
PIMAdmin
BAAN
SAP R/3
Zebra
Other
PIMAdmin
GASK
PIMAdmin
Excelsheet
Zebra
PIMAdmin
PRIPRB
PR-/DS- PR1/DS1 PRA/DS4
PRIM
PRIM
GASK
Web/FTP
Ester
<No PRIM>
PASK
PRI
Manufacturing
Figure 8.19 PDM tool architecture.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Metaphase
Oracle DB
CDM – Collaborative Data Management
metaDoc UnigraphicsOtherinterfaces
Figure 8.20 Modeling the products by rules describing the products.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
‘Super BOM’
Family A
1.1 BKB (prod no)
1.2 BKB (prod no)
2. Family Antennas
1. Family batteries
……
2.1 ……
2.2 ……
1.1 and 2.1 or 2.3 …
1.3 and 2.1 and 3.1 …
……
Product Engine
BOM
1.1
2.1
……
Figure 8.21 Tools supporting product and document management.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Documentum
Product documentsComponents documentsProject documents
Document templatesGuidelines
Outsourcing:Development
TemplatesGuidelines
SAP R/3
Product and productiondocuments
Develop.doc.
Outsourcing:Production
Productiondocument
Productrelease doc.
VSS
Software codeSoftware specificationSoftware
Spec.
Binary codeProduction doc.
PVCS Tracker
CRsDefects
Customer
ProductUser doc.
Figure 8.22 Example of a product structure: (a) product structure, (b) product low volume, and (c) product high volume.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Product low volume
FW
The product
SW
HW
HW SW
c)
B
A
C
D E G
F
I
K L
Product high volume
The product
SW
HW
HW SW
FW
b)
A
C
D E G
F
H
I
K L
J
Product structure
FW ManualsThe product
SW
HW
HW SW needed for HW logic
High volume. FW loaded earlier in the process
High volumeDelivered bymanufacturer
Low volumeDelivered bymanufacturer
Low volume.FW loaded late in theprocess
FW
a)
A
C
D E
F
G H
I J
K L
B
Figure 8.23 An example of an article and its constituent parts.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
<article no> Product <article no> Circuit Board <article no> label <article no> packaging <article no> Firmware version x.y
Figure 8.24 CAS system functions.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
VAX DBMS
Data transfer• Prima• REM• DOKREG• PREDICTOR
CASL• listings and reports
CASF• searching for information
CASP• information used by production
CASR• update and registration
Data about• articles• structures• lists• suppliers
Figure 8.25 CAS II system architecture.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
The main PDM system
Archive
Local PDM Local PDM CM
Development ILS Production
Local PDM Local PDM
Figure 8.26 Life cycle model.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
Marketing Sales Production Delivery Product Management
Project Management
Develop-ment
Figure 8.27 Overall system architecture and its relationship to the development phase during the product development process.
© 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”
The main PDM system
DocumentArticles &structures
Mec-CADElec-CAD
SWDocument Requirements ILS
Customerdocuements
MPS
Dokreg CAS Unigraphics VeriBest CVS MS Office Requisite-Pro
Reliability Frame-Maker
PRIMA
LocalPDM
LocalPDM
LocalPDM
ManualCM
LocalSCM
ManualCM
LocalPDM
LocalPDM
LocalPDM
LocalPDM
Archive Development ILS Production
Development Production Delivery