|
Software Engineering. DOI
|
Pdf ko'rish
bet | 154/584 | Sana | 08.01.2022 | Hajmi | 11,97 Mb. | | #331302 |
| Bog'liq Software Engineering Architecture-driven Software Development ( PDFDrive )
79
Software Engineering. DOI:
©
2012
Published by Elsevier Inc. All rights reserved.
2013
http://dx.doi.org/10.1016/B978-0-12-407768-3.00005-7
Software Integrated Product
and Process Development
5
CHAPTER
CHAPTER OUTLINE
5.1 Application of IPPD to software ............................................................................ 82
5.1.1
Customer focus .............................................................................. 84
5.1.2
Concurrent development of products and processes ........................... 84
5.1.3
Early and continuous life-cycle planning .......................................... 86
5.1.4
Maximize flexibility for optimization and use of contractor unique
approaches ................................................................................... 87
5.1.5
Encourage robust design and improved process capability .................. 88
5.1.6
Event-driven scheduling ................................................................. 88
5.1.7
Multidisciplinary teamwork ............................................................. 88
5.1.8
Empowerment ............................................................................... 88
5.1.9
Seamless management tools ........................................................... 89
5.1.10
Proactive identification and management of risk ............................... 89
5.2 Software engineering and development ................................................................ 89
Integrated product and process development (IPPD) is a central theme of software
engineering that affects the software product architecture and sustainment processes.
The object of IPPD is to control the product definition in a manner that reduces
complexity and life-cycle support costs. IPPD addresses two prevalent concerns
within the system development community: first, concurrent engineering, which is
to ensure that the entire product’’s life cycle is taken into consideration during the
design process; and second, that all product disciplines, including all implementa-
tion, assembly, test and evaluation, maintenance, and support, should be involved in
the early design phases. This chapter will discuss how IPPD should be adapted for
software engineering efforts. Successful implementation of IPPD can result in:
●
Reduced time-to-market.
●
Reduced product development costs.
●
Reduced development risk.
●
Improved product quality.
●
Reduced sustainment costs.
Traditional IPPD addressed the tight relationships between product design engi-
neering and production capabilities. Products that involve hardware elements must
Do'stlaringiz bilan baham: |
|
|