several factors should be
taken into account, such as the development goals, the communication goals, the
concerns, personal goals, abilities, and attitudes of the actors involved, etc.
take place between different stakeholders of that system.
In this book, the primary focus is on architectural models of a graphical (as
opposed to textual or verbal) nature. One may refer to these as architectural models
‘in the narrow sense’. In this chapter, however, we are concerned with architecture
descriptions in ‘the broader sense’. In other words, textual, verbal, or any other
types of architecture descriptions are included.
At present, many description languages are already available to architects, while
many more are being created by both academia and industry. Why all these
languages? How does one select the language that is most apt in a given situation?
Such questions beg for a well-conceived answer. In line with the old adage ‘practice
what you preach’, we argue that just as proper requirements engineering is needed
for the development of systems, proper requirements should also be formulated for
languages and approaches that are to used as vehicles for communication during
system development. In formulating these requirements,
several factors should betaken into account, such as the development goals, the communication goals, theconcerns, personal goals, abilities, and attitudes of the actors involved, etc.take place between different stakeholders of that system.In this book, the primary focus is on architectural models of a graphical (asopposed to textual or verbal) nature. One may refer to these as architectural models‘in the narrow sense’. In this chapter, however, we are concerned with architecturedescriptions in ‘the broader sense’. In other words, textual, verbal, or any othertypes of architecture descriptions are included.At present, many description languages are already available to architects, whilemany more are being created by both academia and industry. Why all theselanguages? How does one select the language that is most apt in a given situation?Such questions beg for a well-conceived answer. In line with the old adage ‘practicewhat you preach’, we argue that just as proper requirements engineering is neededfor the development of systems, proper requirements should also be formulated forlanguages and approaches that are to used as vehicles for communication duringsystem development. In formulating these requirements,
การแปล กรุณารอสักครู่..
