Software Engineering


   Software engineering integrated product team (detailed



Download 11,97 Mb.
Pdf ko'rish
bet538/584
Sana08.01.2022
Hajmi11,97 Mb.
#331302
1   ...   534   535   536   537   538   539   540   541   ...   584
Bog'liq
Software Engineering Architecture-driven Software Development ( PDFDrive )

18.2.2 
 Software engineering integrated product team (detailed 
architecture definition stage)
1. 
Synthesize structural unit alternatives.
 The SWE-IPT should conduct software 
design synthesis to identify and group common functions and allocate them to 
identified structural units. This includes determining the physical unit inherit-
ance and physical unit user interface hierarchies. Structural unit block diagrams 
should be develop to identify how the structural units will need to interface. 
Alternative structural unit configurations should be identified and evaluated to 
narrow the solution space to the preferred physical design solution.
2. 
Develop the software integration hierarchy.
 The software integration hierarchy 
should be developed to depict the software integration strategy. This hierarchy 
depicts how structural elements will be assembled, integrated, and tested to 
form a single integrated structural configuration item.
3. 
Analyze structural configuration alternatives, conflicts, and trade-offs.
 The 
SWE-IPT should analyze structural design alternatives to identify the preferred 
architectural solution. Trade-off studies should be conducted for structural 
design alternatives, as necessary. The risks for structural design alternatives 
must be identified and assessed to ensure the resulting structural configura-
tion can be implemented within program cost and schedule constraints. The 
preferred structural design solution should be selected that achieves a balance 
among performance characteristics, reduced physical architecture complexity, 
architectural stability, and the satisfaction of stakeholder needs and expecta-
tions. The SWE-IPT should evaluate identified conflicts between the functional 
and physical architectures to determine potential courses of corrective action. 
Viable approaches to resolving architectural conflict should be explored and 
evaluated against program objectives and stakeholder needs. The software 
implementation and test challenges and risks associated with each approach 
must be identified. The alternative approaches should be prioritized to facilitate 
architectural decision making.



Download 11,97 Mb.

Do'stlaringiz bilan baham:
1   ...   534   535   536   537   538   539   540   541   ...   584




Ma'lumotlar bazasi mualliflik huquqi bilan himoyalangan ©hozir.org 2024
ma'muriyatiga murojaat qiling

kiriting | ro'yxatdan o'tish
    Bosh sahifa
юртда тантана
Боғда битган
Бугун юртда
Эшитганлар жилманглар
Эшитмадим деманглар
битган бодомлар
Yangiariq tumani
qitish marakazi
Raqamli texnologiyalar
ilishida muhokamadan
tasdiqqa tavsiya
tavsiya etilgan
iqtisodiyot kafedrasi
steiermarkischen landesregierung
asarlaringizni yuboring
o'zingizning asarlaringizni
Iltimos faqat
faqat o'zingizning
steierm rkischen
landesregierung fachabteilung
rkischen landesregierung
hamshira loyihasi
loyihasi mavsum
faolyatining oqibatlari
asosiy adabiyotlar
fakulteti ahborot
ahborot havfsizligi
havfsizligi kafedrasi
fanidan bo’yicha
fakulteti iqtisodiyot
boshqaruv fakulteti
chiqarishda boshqaruv
ishlab chiqarishda
iqtisodiyot fakultet
multiservis tarmoqlari
fanidan asosiy
Uzbek fanidan
mavzulari potok
asosidagi multiservis
'aliyyil a'ziym
billahil 'aliyyil
illaa billahil
quvvata illaa
falah' deganida
Kompyuter savodxonligi
bo’yicha mustaqil
'alal falah'
Hayya 'alal
'alas soloh
Hayya 'alas
mavsum boyicha


yuklab olish