ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ١٣٨٥ ﺍﺳﻔﻨﺪ۳ ﺗﺎ۱ ، ﺍﻳﺮﺍﻥ،ﺗﻬﺮﺍﻥ، ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ،ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ﻣﻌﻤﺎﺭﻱﻫﺎ ﻭ ﺭﻭﺵ ﻫﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ¥ ﭘﻴﻤﺎﻥ ﻋﻤﺎﺩﻱ، ﺍﻳﻤﺎﻥ ﻗﺰﻟﺒﺎﺵ، ﺳﺎﻧﺎﺯ ﺣﻴﺪﺭﻱ، ﻋﻠﻲ ﺍﻳﺰﺩﻱ،* ﺍﺳﻼﻡ ﻧﺎﻇﻤﻲ ﭼﻜﻴﺪﻩ ﺩﺭ ﺍﻳـﻦ. ﭘﻴﭽﻴﺪﮔﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻫﺎ ﺭﻭﺯ ﺑﺮﻭﺯ ﺑﻴﺸﺘﺮ ﺷﺪﻩ ﻭ ﺗﻘﺎﺿﺎ ﺑﺮﺍﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻫﺎﻱ ﻗﺪﺭﺗﻤﻨﺪﺗﺮ ﺍﻓﺰﺍﻳﺶ ﻳﺎﻓﺘـﻪ ﺍﺳـﺖ، ﺩﺭ ﭼﻬﺎﺭ ﺩﻫﻪ ﺍﺧﻴﺮ ﺑﻪ ﻧﻈﺮ ﻣﻲﺭﺳﺪ ﮐﻪ ﺭﻭﺷﻬﺎﻱ ﻗﺪﻳﻤﻲ ﺟﻮﺍﺑﮕﻮﻱ ﻧﻴﺎﺯﻫﺎﻱ ﺩﺭ ﺣﺎﻝ ﺭﺷﺪ ﮐﻨﻮﻧﻲ ﻧﻴﺴﺘﻨﺪ ﻭ ﻧﻴﺎﺯ ﺑﻪ ﺍﻳﺠﺎﺩ ﻭ ﺑﮑﺎﺭﮔﻴﺮﻱ ﺭﻭﺷﻬﺎﻳﻲ ﺍﺳـﺖ، ﻣﻴﺎﻥ ﺍﺯ ﻃﺮﻓﻲ ﺍﻣﻜﺎﻥ ﻛﻨـﺎﺭ ﮔﺬﺍﺷـﺘﻦ ﺳﻴـﺴﺘﻤﻬﺎﻱ ﻧـﺮﻡ ﺍﻓـﺰﺍﺭﻱ.ﮐﻪ ﺑﻮﺳﻴﻠﻪ ﺁﻧﻬﺎ ﺑﺘﻮﺍﻥ ﺑﺮ ﺍﻳﻦ ﭘﻴﭽﻴﺪﮔﻲ ﻫﺎ ﺩﺭ ﺯﻣﺎﻧﻬﺎﻳﻲ ﮐﻮﺗﺎﻫﺘﺮ ﻏﻠﺒﻪ ﮐﺮﺩ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﻭ ﻣﻲ ﺑﺎﻳﺴﺖ ﺳﻴﺴﺘﻤﻬﺎﻱ ﺟﺪﻳﺪ ﺭﺍ ﺑﺼﻮﺭﺕ ﻳﮑﭙﺎﺭﭼـﻪ ﻭ، ﻣﻮﺟﻮﺩ ﮐﻪ ﺗﺎ ﺑﻪ ﺣﺎﻝ ﻣﺸﻐﻮﻝ ﺳﺮﻭﻳﺲ ﺩﻫﻲ ﺑﻪ ﻣﺸﺘﺮﻳﺎﻥ ﺑﻮﺩﻩ ﺍﻧﺪ ﺑﻪ ﻳﮑﻲ ﺍﺯ ﻣﺒﺎﺣﺚ ﻣﻬﻢ ﺩﺭ ﺣﻮﺯﻩ ﻣﻬﻨﺪﺳـﻲ، ﺗﺤﻘﻴﻘﺎﺕ ﺩﺭﺑﺎﺭﻩ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ، ﺩﺭ ﺳﺎﻟﻬﺎﻱ ﺍﺧﻴﺮ.ﺩﺭ ﮐﻨﺎﺭ ﻫﻤﻴﻦ ﺳﻴﺴﺘﻤﻬﺎ ﺑﻮﺟﻮﺩ ﺁﻭﺭﺩ . ﻳﮑﻲ ﺍﺯ ﻣﻮﺿﻮﻋﺎﺕ ﺍﺻﻠﻲ ﺩﺭ ﺍﻳﻦ ﺣﻮﺯﻩ ﻣﻲﺑﺎﺷﺪ،ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺗﺒﺪﻳﻞ ﺷﺪﻩ ﺍﺳﺖ ﻭ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﻫﺪﻑ ﺍﺯ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻳﮏ ﺳﻴﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﺟﻬﺖ ﻣﺸﺨﺺ ﮐﺮﺩﻥ ﭘﺘﺎﻧـﺴﻴﻞ ﺭﻳـﺴﮏﻫـﺎ ﻭ ﺗـﺼﺪﻳﻖ ﮐﻴﻔﻴـﺖ ﻧﻘﺶ ﺍﻳﻦ ﺑﺤﺚ ﺍﻳﻨﺴﺖ ﮐﻪ ﺭﻫﻨﻤﻮﺩﻱ ﺭﺍ ﺩﺭ ﺭﺍﺑﻄﻪ ﺑﺎ ﺑﮑﺎﺭﮔﻴﺮﻱ ﻣﻨﺎﺳﺐﺗﺮﻳﻦ ﺭﻭﺵ ﺑـﺮﺍﻱ.ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎﻱ ﺍﺷﺎﺭﻩ ﺷﺪﻩ ﺩﺭ ﻃﺮﺍﺣﻲ ﻣﻲ ﺑﺎﺷﺪ ﺗﻤﺮﮐﺰ ﺍﻳﻦ ﺗﺤﻘﻴﻖ ﺭﻭﻱ ﮐﺸﻒ ﺷﺒﺎﻫﺘﻬﺎ ﻭ ﺍﺧﺘﻼﻓﺎﺕ ﺑﻴﻦ ﭘﺎﻧﺰﺩﻩ ﺭﻭﺵ ﺩﺭ ﺩﺳﺘﺮﺱ ﺧﻮﺍﻫﺪ ﺑـﻮﺩ ﻭ.ﻓﺮﺁﻳﻨﺪ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﭘﻴﺸﻨﻬﺎﺩ ﺩﻫﺪ .ﺍﻳﻦ ﮐﺎﺭ ﺍﺯ ﻃﺮﻳﻖ ﺟﺪﻭﻝ ﺍﺭﺯﻳﺎﺑﻲ ﺻﻮﺭﺕ ﺧﻮﺍﻫﺪ ﮔﺮﻓﺖ ﮐﻪ ﺍﻳﻦ ﺟﺪﻭﻝ ﺷﺎﻣﻞ ﺷﺎﻧﺰﺩﻩ ﭘﺎﺭﺍﻣﺘﺮ ﺟﻬﺖ ﺍﺭﺯﻳﺎﺑﻲ ﺭﻭﺷﻬﺎ ﻣﻲﺑﺎﺷﺪ ﻛﻠﻤﺎﺕ ﻛﻠﻴﺪﻱ . ﮐﻴﻔﻴﺖ ﻧﺮﻡﺍﻓﺰﺍﺭ، ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ،ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ Architectures and Software Architecture Evaluation Methods Eslam Nazemi, Ali Izadi, Sanaz Heidari, Iman Ghezelbash, Peyman Emadi Abstract In the recent four, the complexity of the software has increased and there for the demand and request for powerful software all increasing they by they too. Mean will it seem, that the old methods and softwares doesn't respond the modern days demands and needs, and the need to develop and utilize new approaches that can over come these complications in the shortest time is felt. On the other hand it is not possible to leave behind the current software and stop using them witch servicing the clients so for, are so we should develop and create new systems and softwares that are able operate along the old systems and softwares. Recently researches about software architectures significant is becoming one off the most subject in the software engineering domain and the analysis of software architecture is also one of the main topics of discussion these days. The purpose of the architecture evaluation of a software system is to analyze the architecture to identify potential risks and to verify that the quality requirements have been addressed in the design. The role of the discussion is to offer guidelines related to the use of the most suitable method for an architecture assessment process. We will concentrate on discovering similarities and differences between these fifteen available methods. We compare SA evaluation methods using a comparison framework with sixteen elements. Keywords Software architecture, evaluation method, software quality. * ﺍﺳﺘﺎﺩﻳﺎﺭ ﻭ ﻫﻴﺎﺕ ﻋﻠﻤﯽ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﻲ ﺩﺍﻧﺸﺠﻮﻳﺎﻥ ﮐﺎﺭﺷﻨﺎﺳﻲ ﺍﺭﺷﺪ ﻣﻬﻨﺪﺳﻲ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺩﺍﻧﺸﮕﺎﻩ ﺁﺯﺍﺩ ﺍﺳﻼﻣﯽ ﻗﺰﻭﻳﻦ¥ 2159 ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ -۲-۲ﻣﻌﻤﺎﺭﻱ File Server -۱ﻣﻘﺪﻣﻪ ﻳﮑﻲ ﺍﺯ ﻣﻮﺿﻮﻋﺎﺕ ﺍﺻﻠﻲ ﺩﺭ ﺗﻮﺳﻌﻪ ﺳﻴـﺴﺘﻢﻫـﺎﻱ ﻧـﺮﻡ ﺍﻓـﺰﺍﺭﻱ ﺍﻣـﺮﻭﺯﻱ ﮐﻴﻔﻴﺖ ﺁﻧﻬﺎ ﻣﻲ ﺑﺎﺷﺪ .ﺍﻳﺪﻩ ﭘﻴﺶ ﺑﻴﻨﻲ ﮐﻴﻔﻴﺖ ﻳﮏ ﻣﺤﺼﻮﻝ ﻧﺮﻡ ﺍﻓـﺰﺍﺭﻱ ﺍﺯ ﺑﺎﻻﺗﺮﻳﻦ ﺳﻄﺢ ﻃﺮﺍﺣﻲ ,ﻣﻮﺿـﻮﻉ ﺟﺪﻳـﺪﻱ ﻧﻴـﺴﺖ .ﺩﺭ ﺳـﺎﻝ ،۱۹۷۲ Parnasﭘﻴﻤﺎﻧﻪﺍﯼ ﮐﺮﺩﻥ ﻭ ﭘﻨﻬﺎﻥﺳﺎﺯﻱ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳـﮏ ﺍﺑـﺰﺍﺭ ﺗﺠﺰﻳﻪ ﺳﻄﺢ ﺑﺎﻻﻱ ﺳﻴﺴﺘﻢ ﺟﻬﺖ ﺍﺻﻼﺡ ﺍﻧﻌﻄﺎﻑﭘـﺬﻳﺮﻱ ﻭ ﻗﺎﺑﻠﻴـﺖ ﺩﺭﮎ ﺗﻮﺻﻴﻒ ﮐـﺮﺩ .ﺩﺭ ﺳـﺎﻝ Stevens et al. ،۱۹۷۴ﻧـﺸﺎﻥﮔـﺬﺍﺭﻱ ﺍﺗـﺼﺎﻝ ﭘﻴﻤﺎﻧﻪ ﻭ ﺍﻧﺴﺠﺎﻡ ﭘﻴﻤﺎﻧﻪ ﺭﺍ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﮔﺰﻳﻨﻪ ﻫﺎﻱ ﺗﺠﺰﻳﻪ ﺑﺮﻧﺎﻣﻪ ﻣﻌﺮﻓـﻲ ﮐﺮﺩ .ﺍﺧﻴﺮﺍ ،ﻧﺸﺎﻥ ﮔـﺬﺍﺭﻱ ﻣﻌﻤـﺎﺭﯼ ﻧـﺮﻡ ﺍﻓـﺰﺍﺭ ١SAﺑـﻪ ﻋﻨـﻮﺍﻥ ﺳـﻄﺢ ﻣﻨﺎﺳﺒﻲ ﺩﺭ ﺧﺼﻮﺹ ﮐﻴﻔﻴﺖ ﻧﺮﻡﺍﻓﺰﺍﺭ ﭘﺪﻳﺪﺍﺭ ﺷﺪﻩ ﺍﺳﺖ ].[12 ﺗﺎﮐﻨﻮﻥ ،ﻣﻌﻤﺎﺭﻱﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺑﻤﻨﻈﻮﺭ ﻃﺮﺍﺣﻲ ﻭ ﭘﻴﺎﺩﻩﺳﺎﺯﻱ ﻧـﺮﻡ- ﺍﻓﺰﺍﺭ ،ﻣﺘﻨﺎﺳﺐ ﺑﺎ ﺭﺷﺪ ﻓﻨﺎﻭﺭﻱ ﺩﺭ ﺑﺨﺶ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺍﺭﺍﺋﻪ ﺷـﺪﻩ ﺍﺳـﺖ .ﺍﻳـﻦ ﻣﻌﻤﺎﺭﻱﻫﺎ ﺍﺯ ﻳﮏ ﻃﺮﻑ ﺑﺮﺧﺎﺳﺘﻪ ﺍﺯ ﺍﻣﮑﺎﻧﺎﺕ ﻭ ﻣﺎﻫﻴﺖ ﻣﻌﻤﺎﺭﻱ ﺳـﺨﺖ- ﺍﻓﺰﺍﺭﻫﺎﻱ ﺯﻣﺎﻥ ﺧﻮﺩ ﻭ ﺍﺯ ﻃﺮﻑ ﺩﻳﮕﺮ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﻭ ﻧﮕﺮﺵ ﺩﺭ ﺗﮑﻨﻮﻟﻮﮊﻱ- ﻫﺎﻱ ﺳﺎﺧﺖ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺍﻧﺘﻈﺎﺭﺍﺕ ﻃﺮﺡ ﺷﺪﻩ ﺗﻮﺳﻂ ﮐﺎﺭﺑﺮﺍﻥ ﻣﻲﺑﺎﺷـﻨﺪ. ﻫﺮ ﻣﻌﻤﺎﺭﻱ ﺩﺍﺭﺍﻱ ﺷﺎﺧﺺﻫﺎ ﻭ ﻭﻳﮋﮔﻲﻫﺎﻱ ﻣﻨﺤـﺼﺮ ﺑﻔـﺮﺩ ﺑـﻮﺩﻩ ﻭ ﻧـﺮﻡ- ﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﮐﻪ ﺑﺎ ﺍﺗﮑﺎﺀ ﺑﺮ ﻫﺮ ﻳﮏ ﺍﺯ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱﻫﺎ ﭘﻴﺎﺩﻩﺳﺎﺯﻱ ﻣﻲﮔﺮﺩﻧﺪ، ﺧﺼﺎﻳﺺ ﺧﻮﺩ ﺭﺍ ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﺑﮑﺎﺭﮔﺮﻓﺘﻪ ﺷﺪﻩ ﺑﻪ ﺍﺭﺙ ﺧﻮﺍﻫﻨﺪ ﺑﺮﺩ .ﻣـﺴﻠﻤﺎ ﻣﻌﻤﺎﺭﻱﻫﺎ ﻭ ﭼﺎﺭﭼﻮﺏﻫﺎﻱ ﺟﺪﻳﺪ ﻣﺒﺘﻨﻲ ﺑﺮ ﺑﺮﻧﺎﻣـﻪ ﻧﻮﻳـﺴﻲ ﺗﺤـﺖ ﻭﺏ ﻭ ﺍﻳﻨﺘﺮﻧﺖ ﻧﻈﻴﺮ J2EE , .Netﻗﺎﺑﻠﻴﺖ ﻭ ﻟـﺰﻭﻡ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ ﻣﻌﻤـﺎﺭﻱﻫـﺎﻱ ﭼﻨﺪ ﻻﻳﻪ ﺍﻱ ﺭﺍ ﺗﻮﺻﻴﻪ ﻣﻲﻧﻤﺎﻳﻨﺪ .ﻣﻌﻤﺎﺭﻱﻫﺎﻱ ﻣﺨﺘﻠـﻒ ﺍﺭﺍﺋـﻪ ﺷـﺪﻩ(۱ : ﻣﻌﻤﺎﺭﻱ (۲ ،MainFrameﻣﻌﻤﺎﺭﻱ (۳ ،File Serverﻣﻌﻤﺎﺭﻱ Client (۴ ،Serverﻣﻌﻤﺎﺭﻱ ﺩﻭ ﻻﻳﻪ ﺍﻱ(۵ ،ﻣﻌﻤﺎﺭﻱ ﭼﻨﺪ ﻻﻳـﻪ ﺍﻱ(۶ ،ﻣﻌﻤـﺎﺭﻱ ﺳﺮﻭﻳﺲ ﮔﺮﺍ ﻭ (۷ﻣﻌﻤﺎﺭﻱ ﺩﺍﺩﻩ ﮔﺮﺍﺀ ﻣﻲ ﺑﺎﺷﻨﺪ ﮐﻪ ﺩﺭ ﺑﺨـﺶ ﺑﻌـﺪﻱ ﺑـﻪ ﺷﺮﺡ ﻣﺨﺘﺼﺮﻱ ﺍﺯ ﻫﺮ ﻳﮏ ﺍﺯ ﻣﻌﻤﺎﺭﻱﻫﺎ ﺧﻮﺍﻫﻴﻢ ﭘﺮﺩﺍﺧﺖ. ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﭘﺲ ﺍﺯ ﺑﻮﺟﻮﺩ ﺁﻣﺪﻥ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺷﺨﺼﻲ ﻭ ﭘﺎﻳﻴﻦ ﺁﻣﺪﻥ ﻗﻴﻤﺖ ﺁﻧﻬﺎ ﻣﻄﺮﺡ ﺷﺪ ﮐﻪ ﺩﺍﺩﻩﻫﺎ ﺭﺍ ﺭﻭﻱ ﺳﺮﻭﺭ ﺫﺧﻴﺮﻩ ﻣﻲﮐﻨﺪ ﻭ ﭘـﺮﺩﺍﺯﺵﻫـﺎ ﺭﺍ ﺭﻭﻱ Clientﻫﺎ ﺍﻧﺠﺎﻡ ﻣﻲﺩﻫﺪ .ﺩﺭ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﺍﺯ ﺳﺮﻭﻳﺲﺩﻫﻨﺪﻩ)ﻫﺎﻱ( ﻣﺘﻌﺪﺩ ،ﺑﺼﻮﺭﺕ ﻣﺘﻤﺮﮐﺰ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﮔﺮﺩﺩ ،ﻭ ﻧﻴﺰ ﻣﻨـﺎﺑﻊ ﻣﺘﻔـﺎﻭﺗﻲ ﻧﻈﻴـﺮ ﭼﺎﭘﮕﺮ ﻭ ﻳﺎ ﻓﻀﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺑﻪ ﺍﺷﺘﺮﺍﮎ ﮔﺬﺍﺷﺘﻪ ﻣﻲﺷﻮﻧﺪ[22]. -۳-۲ﻣﻌﻤﺎﺭﻱ Client/Server ﭘﺲ ﺍﺯ ﺗﻘﻮﻳﺖ ﺗﮑﻨﻴﮏﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻭ ﺑﻬﺒﻮﺩ ﻣﺸﮑﻼﺕ ﺷﺒﮑﻪﻫـﺎﻱ ﮐﺎﻣﭙﻴﻮﺗﺮﻱ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﻣﻄﺮﺡ ﺷﺪ ﻭ ﻫﻨﻮﺯ ﺑﻪ ﺻﻮﺭﺕ ﮔـﺴﺘﺮﺩﻩ ﺩﺭ ﺣـﺎﻝ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺑﺎﺷﺪ .ﺩﺭ ﻣﻌﻤـﺎﺭﻱ ﻓـﻮﻕ ﺍﺯ ﺳـﺮﻭﻳﺲﺩﻫﻨـﺪﮔﺎﻥ ﻭ ﺳـﺮﻭﻳﺲ- ﮔﻴﺮﻧﺪﮔﺎﻥ ﺑﺎ ﺧﺼﺎﻳﺺ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﺩ ].[4 -۴-۲ﻣﻌﻤﺎﺭﻱ Client Server : Two Tier ﺑﺎ ﺑﻮﺟﻮﺩ ﺁﻣﺪﻥ ﺑﺎﻧﮏﻫـﺎﻱ ﺍﻃﻼﻋـﺎﺗﻲ ،ﻃﺮﺍﺣـﺎﻥ ﻣﻌﻤـﺎﺭﻱ ﺍﺣـﺴﺎﺱ ﻧﻴـﺎﺯ ﮐﺮﺩﻧﺪ ﮐﻪ ﭘﺮﺩﺍﺯﺵﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﺩﺍﺩﻩﻫـﺎ ﺭﺍ ﺩﺭ ﻻﻳـﻪﺍﻱ ﻣـﺴﺘﻘﻞ ﭘﻴـﺎﺩﻩ ﮐﻨﻨﺪ ﺗﺎ ﺑﺘﻮﺍﻧﻨﺪ ﺍﺯ ﻣﺰﺍﻳﺎﻱ ﭘﻴﻤﺎﻧﻪ ﺍﯼ ﺍﺳﺘﻔﺎﺩﻩ ﮐﻨﻨﺪ .ﺍﻳﻦ ﻣﺪﻝ ﻣﺸﺎﺑﻪ ﻣﺪﻝ Client/Serverﺍﺳﺖ ﮐﻪ ﺩﺭ ﺑﺨﺶ ﻗﺒﻞ ﺑﻪ ﺁﻥ ﺍﺷﺎﺭﻩ ﺷﺪ].[21,22 -۵-۲ﻣﻌﻤﺎﺭﻱ Multi Tier, Three Tier ﺍﻳﻦ ﻣﺪﻝ ﻣﺎﻧﻨﺪ ﻣﺪﻝ ﺩﻭ ﻻﻳﻪﺍﻱ ﺍﺳﺖ ﺑﺎ ﺍﻳـﻦ ﺗﻔـﺎﻭﺕ ﮐـﻪ ﺭﺍﺑـﻂ ﮐـﺎﺭﺑﺮ ﺭﺍ ﺑﺼﻮﺭﺕ ﻻﻳﻪﺍﻱ ﻣﺠﺰﺍ ﭘﻴﺎﺩﻩ ﻣﻲﮐﻨﺪ] .[21ﺍﻳﻦ ﻋﻤﻞ ﻣﺰﺍﻳﺎﻳﻲ ﺍﺯ ﻗﺒﻴﻞ ﺟﺪﺍ- ﺳﺎﺯﻱ ﻣﻨﻄﻖ ﺑﺮﻧﺎﻣﻪ ﺍﺯ ﺭﺍﺑﻂ ﮐﺎﺭﺑﺮ ﻭ ﺳـﻬﻮﻟﺖ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ ﺍﺟـﺰﺍﻱ ﺁﻣـﺎﺩﻩ ﺑﺮﺍﻱ ﺍﻳﻦ ﺑﺨﺶ ﺭﺍ ﺩﺍﺭﺩ .ﺩﺭ ﺍﻳـﻦ ﻣـﺪﻝ ﺍﺯ ﻳـﮏ ﻻﻳـﻪ ﻣﻴـﺎﻧﻲ ﺩﻳﮕـﺮ ﺑـﻴﻦ ﺳﺮﻭﻳﺲﮔﻴﺮﻧﺪﻩ ﻭ ﺳﺮﻭﻳﺲﺩﻫﻨﺪﻩ ﺑﺎﻧﮏ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﺩ. -۶-۲ﻣﻌﻤﺎﺭﻱ ﺳﺮﻭﻳﺲ ﮔﺮﺍ -۲ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻳﮏ ﺳﻴﺴﺘﻢ ﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﺗﻌﺮﻳﻒ ﻣﻲ ﺷﻮﺩ "ﺳـﺎﺧﺘﺎﺭ ﻳﺎ ﺳﺎﺧﺘﺎﺭﻫﺎﻱ ﺳﻴﺴﺘﻢ ،ﮐﻪ ﺍﺟﺰﺍﺀ ﻧﺮﻡﺍﻓﺰﺍﺭ ،ﺧﺼﻮﺻﻴﺎﺕ ﺑﺴﻴﺎﺭ ﻭﺍﺿﺢ ﺍﻳـﻦ ﺍﺟﺰﺍﺀ ﻭ ﺍﺭﺗﺒﺎﻁ ﻣﻴﺎﻥ ﺁﻧﻬﺎ ﺭﺍ ﺩﺭ ﺑﺮﺩﺍﺭﺩ" ] .[23ﺍﻳﻦ ﺗﻌﺮﻳﻒ ﻓﻘـﻂ ﺑـﺮ ﺭﻭﻱ ﺟﻨﺒﻪ ﻫﺎﻱ ﺩﺍﺧﻠﻲ ﻳﮏ ﺳﻴﺴﺘﻢ ﺗﻤﺮﮐﺰ ﺩﺍﺭﺩ ﻭ ﺑﻴﺸﺘﺮ ﺭﻭﺷﻬﺎﻱ ﺗﺤﻠﻴﻞ ﻧﻴﺰ ﺑﺮ ﭘﺎﻳﻪ ﺁﻥ ﻣﻲﺑﺎﺷﻨﺪ .ﺗﻌﺮﻳﻒ ﮐﻮﺗﺎﻩ ﺩﻳﮕـﺮﻱ ﻧﻴـﺰ ﮐـﻪ ﺑﻮﺳـﻴﻠﻪ Garlanﻭ Perryﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ SAﺭﺍ ﺑﻪ ﺍﻳﻦ ﺻـﻮﺭﺕ ﺑﻴـﺎﻥ ﻣـﻲ ﮐﻨـﺪ "ﺳـﺎﺧﺘﺎﺭ ﺍﺟﺰﺍﺀ ﺩﺭ ﻳﮏ ﺑﺮﻧﺎﻣﻪ ﻳﺎ ﺳﻴﺴﺘﻢ ،ﺍﺭﺗﺒﺎﻁ ﺑـﻴﻦ ﺁﻧﻬـﺎ ﻭ ﻗﻮﺍﻋـﺪ ﻭ ﺭﺍﻫﻨﻤـﺎﻳﻲ ﻫﺎﻳﻲ ﮐﻪ ﻃﺮﺍﺣﻲ ﻭ ﺗﻮﺳﻌﻪ ﺭﺍ ﺩﺭ ﺯﻣﺎﻥ ﻣﻘﺮﺭ ﮐﻨﺘﺮﻝ ﻣﻲﮐﻨﻨﺪ". -۱-۲ﻣﻌﻤﺎﺭﻱ MainFrame ﺍﻳﻦ ﻣﻌﻤـﺎﺭﻱ ﺑـﻪ ﺯﻣـﺎﻥ ﮐﺎﻣﭙﻴﻮﺗﺮﻫـﺎﻱ MainFrameﺩﺭ ﺩﻫـﻪ -۱۹۶۰ ۱۹۷۰ﺑﺎﺯ ﻣﻲﮔﺮﺩﺩ] .[22ﺩﺭ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ،ﮐـﺎﻣﭙﻴﻮﺗﺮ Hostﻣـﺴﺌﻮﻟﻴﺖ ﺍﻧﺠﺎﻡ ﺗﻤﺎﻣﻲ ﭘﺮﺩﺍﺯﺵﻫﺎ ﺭﺍ ﺑﺮﻋﻬﺪﻩ ﺩﺍﺭﺩ ﻭ ﮐﺎﺭﺑﺮﺍﻥ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﺮﻣﻴﻨﺎﻝ- ﻫﺎ ،ﻗﺎﺩﺭ ﺑﻪ ﺍﻳﺠﺎﺩ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ﺳﻴﺴﺘﻢ ﺍﺻﻠﻲ ) (Hostﻣﻲﺑﺎﺷﻨﺪ. ﻣﻌﻤﺎﺭﻱ ﺳﺮﻭﻳﺲﮔﺮﺍ ،ﺑﺎ ﺗﮑﻴﻪ ﺑﺮ ﻣﺤﺎﺳﺒﺎﺕ ﺗﻮﺯﻳﻊ ﺷﺪﻩ ﻭ ﺑﺮ ﭘﺎﻳﻪ ﺷﺒﮑﻪ- ﻫﺎ ﻭ ﻻﻳﻪﻫﺎﻱ ﻣﻴﺎﻧﻲ ﻭ ﻫﻤﭽﻨﻴﻦ ﺯﺑﺎﻥﻫﺎﻳﻲ ﮐﻪ ﺗﻮﻟﻴﺪ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻱ ﺗﻮﺯﻳـﻊ ﺷﺪﻩ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﻨﺪ ،ﺑﻌﻨﻮﺍﻥ ﺭﺍﻩﺣﻠﻲ ﻣﻨﺎﺳﺐ ﺟﻬﺖ ﺍﺯ ﻣﻴﺎﻥ ﺑﺮﺩﺍﺷـﺘﻦ ﻣﺸﮑﻼﺕ ﺭﻭﺵﻫﺎﻱ ﻗـﺪﻳﻤﻲﺗـﺮ ﻣﻄـﺮﺡ ﮔﺮﺩﻳـﺪﻩ ﺍﺳـﺖ] . [3, 4ﺗﻌـﺎﺭﻳﻒ ﮔﻮﻧﺎﮔﻮﻧﻲ ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﺳﺮﻭﻳﺲﮔﺮﺍ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﺳﺖ ﻛﻪ ﻧﻤﻮﻧـﻪﺍﻱ ﺭﺍ ﻋﻨـﻮﺍﻥ ﻣﻲﮐﻨﻴﻢ" :ﻣﻌﻤﺎﺭﻱ ﺳﺮﻭﻳﺲﮔﺮﺍ ﺭﻭﺷﻲ ﺑﺮﺍﻱ ﺳﺎﺧﺖ ﺳﻴﺴﺘﻢﻫـﺎﻱ ﺗﻮﺯﻳـﻊ ﺷﺪﻩﺍﻱ ﺍﺳﺖ ﮐﻪ ﺩﺭ ﺁﻧﻬﺎ ﻋﻤﻠﮑﺮﺩ ﺳﻴـﺴﺘﻢ ﺑـﺼﻮﺭﺕ ﺳـﺮﻭﻳﺲ ﺩﺭ ﺍﺧﺘﻴـﺎﺭ ﮐﺎﺭﺑﺮﺍﻥ ﻭ ﻳﺎ ﺳﺎﻳﺮ ﺳﺮﻭﻳﺲﻫﺎ ﻗـﺮﺍﺭ ﻣـﻲﮔﻴـﺮﺩ" .ﻣﺤﺎﺳـﺒﺎﺕ ﺳـﺮﻭﻳﺲﮔـﺮﺍ ) ، ( ٢SOCﻧﻤﻮﻧﻪﺍﻱ ﺍﺯ ﻣﺤﺎﺳـﺒﺎﺕ ﺍﺳـﺖ ﮐـﻪ ﺩﺭ ﺁﻥ ﻃﺮﺍﺣـﻲ ﻭ ﺗﻮﺳـﻌﻪ ﺳﻴﺴﺘﻢﻫﺎﻱ ﮐﺎﺭﺑﺮﺩﻱ ﺑﺮ ﭘﺎﻳﻪ ﺳﺮﻭﻳﺲ ﺍﻧﺠﺎﻡ ﻣﻲﮔﻴﺮﺩ ]. [20 -۷-۲ﻣﻌﻤﺎﺭﻱ ﺩﺍﺩﻩﮔﺮﺍ ﺩﺍﺩﻩﻫﺎ ﺩﺭ ﺑﺮﻧﺎﻣﻪﻫﺎﻱ ﮐﺎﻣﭙﻴﻮﺗﺮﻱ ﺩﺍﺭﺍﻱ ﻧﻘﺸﻲ ﺑﺴﻴﺎﺭ ﻣﻬﻢ ﺑﻮﺩﻩ ﻭ ﻫﻤﻮﺍﺭﻩ ﻧﺤﻮﻩ ﺫﺧﻴﺮﻩ ﻭ ﺑﺎﺯﻳﺎﺑﻲ ﺁﻧﺎﻥ ﺍﺯ ﻣﻬﻤﺘﺮﻳﻦ ﻣﺒﺎﺣﺚ ﺩﺭ ﺩﻧﻴﺎﻱ ﮔﺴﺘﺮﺩﻩ ﻧﺮﻡ- 2160 ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ ﺍﻓﺰﺍﺭ ﺑﻮﺩ ] .[20ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﺩﺍﺭﺍﻱ ﻭﻳﮋﮔﻲﻫﺎﻱ ﺧـﺎﺹ ﺧـﻮﺩ ﻣـﻲﺑﺎﺷـﺪ: )(۱ﻟﺰﻭﻡ ﻳﮏ ﺍﺗﺼﺎﻝ ﭘﻴﻮﺳﺘﻪ ﺑﺎ ﺷﺒﮑﻪ؛ )(۲ﻗﺎﺑﻠﻴﺖ ﺍﻧﺠﺎﻡ ﻋﻤﻠﻴﺎﺕ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺩﺭ ﺯﻣﺎﻥ ﺩﻟﺨﻮﺍﻩ ﻭ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ﻣﻨﺒﻊ ﺩﺍﺩﻩ ﺩﺭ ﺯﻣﺎﻧﻲ ﺩﻳﮕﺮ ﺑﻤﻨﻈﻮﺭ ﭘﺮﺩﺍﺭﺵ؛ )(۳ﺍﺳﺘﻔﺎﺩﻩ ﺳﺎﻳﺮ ﮐﺎﺭﺑﺮﺍﻥ ﺍﺯ ﺍﺭﺗﺒﺎﻁ؛ )(۴ﺑﻬﺒﻮﺩ ﺩﺭ ﮐﺎﺭﺁﺋﻲ ﻭ ﺗﻮﺳﻌﻪ ﺑﺮﻧﺎﻣﻪ؛ )(۵ﺑﺮﻭﺯ ﺗﻨـﺎﻗﺺ ﺍﻃﻼﻋـﺎﺗﻲ ﺩﺭ ﺻـﻮﺭﺕ ﺍﻋﻤـﺎﻝ ﺗﻐﻴﻴـﺮﺍﺕ ﻭ ﻟـﺰﻭﻡ ﺍﻧﺠـﺎﻡ ﺍﻗﺪﺍﻣﺎﺕ ﻻﺯﻡ ﺩﺭ ﺍﻳﻦ ﺧﺼﻮﺹ. ﮐﻴﻔﻴﺖ ﮐﻪ ﻳﮏ ﺻﻔﺖ ﺧﺎﺻﻪ ﺍﺳﺖ ،ﻳﮏ ﻣﺸﺨﺼﻪ ﻏﻴﺮ ﺗﺎﺑﻌﻲ ﺍﺯ ﻳـﮏ ﻣﻮﻟﻔﻪ ﻳﺎ ﻳﮏ ﺳﻴﺴﺘﻢ ﻣﻲﺑﺎﺷﺪ .ﮐﻴﻔﻴﺖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺩﺭ [25] IEEE 1061 ﺗﻌﺮﻳﻒ ﻣﻲﺷﻮﺩ ﻭ ﺩﺭﺟﻪﺍﻱ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲﮐﻨﺪ ﮐﻪ ﺑﻴﺎﻧﮕﺮ ﺩﺍﺭﺍ ﺑـﻮﺩﻥ ﺗﺮﮐﻴـﺐ ﻣﻄﻠﻮﺏ ﺻﻔﺎﺕ ﺧﺎﺻﻪ ﻧﺮﻡﺍﻓـﺰﺍﺭ ﻣـﻲﺑﺎﺷـﺪ .ﺍﺳـﺘﺎﻧﺪﺍﺭﺩ ﺩﻳﮕـﺮISO/IEC ، ،[26] Draft 9126-1ﻣﻲﺑﺎﺷﺪ ﮐﻪ ﻣﺪﻝ ﮐﻴﻔﻴﺘﻲ ﻧﺮﻡﺍﻓـﺰﺍﺭ ﺭﺍ ﻣـﺸﺨﺺ ﻣﻲﮐﻨﺪ .ﺑﺮ ﺍﻳﻦ ﺍﺳﺎﺱ ﺷﺶ ﻃﺒﻘﻪﺑﻨﺪﻱ ﺍﺯ ﻣﺸﺨﺼﻪﻫﺎ (functionality, reliability, usability, efficiency, maintainability, and -۳ﺭﻭﺷﻬﺎﻱ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺍﺧﻴﺮﺍ ﺗﻼﺵﻫﺎﻳﻲ ﺩﺭ ﺟﻬﺖ ﻧﻈﺎﻡﺩﻫـﻲ ﺍﻟﮕﻮﻫـﺎﻱ ﻃﺮﺍﺣـﻲ ﻭ ﺳـﺒﮏﻫـﺎﻱ ﻣﻌﻤﺎﺭﻱ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﺩﺭ ﺍﻳﻦ ﺣﻮﺯﻩ ،ﺻﻮﺭﺕ ﮔﺮﻓﺘﻪ ﺍﺳﺖ ،ﮐﻪ ﺍﻏﻠﺐ ﺍﻳـﻦ ﻓﻌﺎﻟﻴﺖﻫﺎ ﺑﺎ ﺭﻭﺵﻫﺎﻱ ﻏﻴﺮ ﺭﺳﻤﻲ ﺑﻮﺩﻩ ﻭ ﻫـﺪﻑ ﺁﻧﻬـﺎ ﺗـﻀﻤﻴﻦ ﮐﻴﻔﻴـﺖ ﻃﺮﺡ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺑﻮﺩﻩ ﺍﺳﺖ .ﻣﺸﺨﺺ ﺷﺪﻩ ﺍﺳﺖ ﮐﻪ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﮐﻴﻔﻴـﺖ ﺧﺼﻮﺻﻴﺎﺕ ﺳﻴﺴﺘﻢ ﻧﻬﺎﻳﻲ ﺑﺮ ﺍﺳﺎﺱ ﻃﺮﺡ SAﺍﻣﮑﺎﻥ ﭘـﺬﻳﺮ ﻧﻤـﻲ ﺑﺎﺷـﺪ. ﺍﻳﻦ ﺍﻣﺮ ﺩﻻﻟﺖ ﺑﺮ ﺍﻳﻦ ﺩﺍﺭﺩ ﮐـﻪ ﻃﺮﺍﺣـﻲ ﺩﺍﺭﺍﻱ ﺟﺰﺋﻴـﺎﺕ ﻭ ﭘﻴـﺎﺩﻩﺳـﺎﺯﻱ، ﺗﺼﻮﺭ ﺳﺨﺘﻲ ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﻣﻲﺑﺎﺷﺪ .ﻫﺪﻑ ﺍﺯ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﻳﮏ ﺳﻴـﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﭘﻴﺶ ﺑﻴﻨﻲ ﮐﻴﻔﻴﺖ ﺳﻴﺴﺘﻢ ﻗﺒﻞ ﺍﺯ ﺳﺎﺧﺘﻪ ﺷـﺪﻥ ﺁﻥ ﺍﺳـﺖ ﻭ ﻫﺪﻑ ،ﺑﺮﺁﻭﺭﺩ ﺧﻴﻠﻲ ﺩﻗﻴﻖ ﺁﻥ ﻧﻴﺴﺖ .ﻫـﺪﻑ ﺍﺭﺯﻳـﺎﺑﻲ ،ﺁﻧـﺎﻟﻴﺰ SAﺑـﺮﺍﻱ ﻣﺸﺨﺺ ﮐـﺮﺩﻥ ﭘﺘﺎﻧـﺴﻴﻞ ﺭﻳـﺴﮏ ﻭ ﺗـﺼﺪﻳﻖ ﮐﻴﻔﻴـﺖ ﻧﻴﺎﺯﻣﻨـﺪﻱﻫـﺎﻱ ﻣﺸﺨﺺ ﺷﺪﻩ ﺩﺭ ﻃﺮﺍﺣﻲ ﺍﺳﺖ ].[24 ﮔﺮﻭﻩﻫـﺎﻱ ﻧـﺮﻡﺍﻓـﺰﺍﺭﯼ ﻣﺨﺘﻠـﻒ ﺗﮑﻨﻴﮑﻬـﺎﻱ ﻣﺨـﺘﺺ ﺧﻮﺩﺷـﺎﻥ ﺭﺍ ﺑﺮﻣﺒﻨﺎﻱ ﻣﺘﺮﻳﮏ ﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ،ﺳﻨﺎﺭﻳﻮ ﻭ ﻣﺪﻝ ﺻﻔﺖ ﺗﻮﺳـﻌﻪ ﺩﺍﺩﻩﺍﻧـﺪ. ﮔﺮﻭﻩﻫﺎﻳﻲ ﮐـﻪ ﺍﺯ ﻣﺘﺮﻳـﮏﻫـﺎﻱ ﻧـﺮﻡﺍﻓـﺰﺍﺭﻱ ﺑﻬـﺮﻩ ﻣـﻲﮔﻴﺮﻧـﺪ ﺍﺯ ﻧـﺸﺎﻥ ﮔﺬﺍﺭﻳﻬﺎﻱ module couplingﻭ module cohesionﺑﺮﺍﻱ ﭘﻴـﺸﮕﻮﻳﻲ ﮐﻴﻔﻴﺖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﺳﺘﻔﺎﺩﻩ ﮐﺮﺩﻩﺍﻧﺪ .ﺭﻭﺵﻫﺎﻱ ﺑﺮ ﭘﺎﻳﻪ ﺳﻨﺎﺭﻳﻮ ﺩﺭ ﺳـﺎﻟﻬﺎﻱ ﺍﺧﻴﺮ ﺑﻪ ﺍﻧﺪﺍﺯﻩ ﻛﺎﻓﻲ ﻣـﻮﺭﺩ ﺑﺮﺭﺳـﻲ ﻗـﺮﺍﺭ ﺩﺍﺩﻩ ﺷـﺪﻩﺍﻧـﺪ ،ﺍﻣـﺎ ﺭﻭﺵﻫـﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﺑﺮﻣﺒﻨﺎﻱ ﻣﺪﻝ ﺻﻔﺖ ﻫﻨﻮﺯ ﺩﺭ ﺣﺎﻝ ﭘﻴﺸﺮﻓﺖ ﻫﺴﺘﻨﺪ. ) portabilityﻭﺟﻮﺩ ﺩﺍﺭﺩ ،ﮐﻪ ﻫﺮ ﮐﺪﺍﻡ ﺑﻪ ﺯﻳﺮ ﻣﺸﺨﺼﻪﻫﺎﻳﻲ ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﻧﺪ .ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﺑﻮﺳﻴﻠﻪ ﺍﺑﺰﺍﺭ ﺧﺼﻮﺻﻴﺎﺕ ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺧﺎﺭﺟﻲ ﺑﺮﺍﻱ ﻫﺮ ﺳﻴﺴﺘﻢ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﻣﻌﻴﻦ ﻣﻲﺷﻮﻧﺪ. ﺑﺮﺍﻱ ﻳﮏ ﺗﺤﻠﻴﻞ ﺍﻧﻌﻄﺎﻑﭘﺬﻳﺮ ،ﻣﺤـﻴﻂ ﺑﻴﺮﻭﻧـﻲ ﻣﻬـﻢﺗـﺮ ﺍﺯ ﻣﺤـﻴﻂ ﺩﺍﺧﻠﻲ ﺳﻴﺴﺘﻢ ﻣﻲﺑﺎﺷﺪ .ﺗﻌﺮﻳﻒ SAﺑﺎﻳﺪ ﺗﺮﮐﻴﺒﻲ ﺍﺯ ﺩﻭ ﺑﺨﺶ ﺑﺎﺷﺪ ،ﻳﮏ ﺑﺨﺶ ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﻌﻤﺎﺭﻱ ﮐﻼﻥ ﮐﻪ ﺑﺮ ﺭﻭﻱ ﻣﺤﻴﻂ ﺳﻴﺴﺘﻢ ﺗﻤﺮﮐﺰ ﺩﺍﺭﺩ ﻭ ﺩﻳﮕﺮﻱ ﻣﻌﻤﺎﺭﻱ ﺟﺰﺀ ﮐﻪ ﺳﺎﺧﺘﺎﺭ ﺩﺍﺧﻠﻲ ﺳﻴﺴﺘﻢ ﺭﺍ ﭘﻮﺷﺶ ﻣﻲﺩﻫﺪ. ﺩﺭ ] [10,11ﭼﻬﺎﺭﭼﻮﺑﻲ ﺑﺮﺍﻱ ﻣﻘﺎﻳـﺴﻪ ﺭﻭﺷـﻬﺎﻱ ﻣﺨﺘﻠـﻒ ﺍﺭﺯﻳـﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﺳﺖ )ﺟﺪﻭﻝ ) .((۱ﺩﺭ ﺍﺩﺍﻣﻪ ﺭﻭﺷﻬﺎﻳﻲ ﻣﻌﺮﻓـﻲ ﺷـﺪﻩ ﮐﻪ ﺩﺭ ﻧﻬﺎﻳﺖ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻫﻤﻴﻦ ﭼﻬﺎﺭﭼﻮﺏ ﻣﻮﺭﺩ ﺍﺭﺯﻳﺎﺑﻲ ﻭ ﻣﻘﺎﻳﺴﻪ ﻗﺮﺍﺭ ﺧﻮﺍﻫﻨﺪ ﮔﺮﻓـﺖ .ﭼﻨـﺪﻳﻦ ﮔـﺮﻭﻩ ﺗﺤﻘﻴﻘـﺎﺗﻲ ] [10-14ﺗـﻼﺵ ﮐـﺮﺩﻩﺍﻧـﺪ ﭼﻬﺎﺭﭼﻮﺏﻫﺎﻳﻲ ﺟﻬﺖ ﻣﻘﺎﻳﺴﻪ ﺭﻭﺷﻬﺎﻱ ﻣﻮﺟﻮﺩ ﺍﺭﺍﺋﻪ ﮐﻨﻨﺪ ،ﻫـﺮ ﮐـﺪﺍﻡ ﺍﺯ ﺍﻳﻦ ﺗﻼﺵﻫﺎ ﻣﻮﺟﺐ ﺍﻓﺰﺍﻳﺶ ﻓﻬﻢ ﻣﺎ ﺍﺯ ﺭﻭﺷﻬﺎﻱ ﻣﻮﺟﻮﺩ ﻣﻲﺷﻮﺩ. FAAM -۱-۳ ٣ ﺍﻳﻦ ﺭﻭﺵ ﻋﻤﺪﺗﺎ ﺑﺮﺍﯼ ﺍﺭﺯﻳﺎﺑﻲ ﺧﺎﻧﻮﺍﺩﻩ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﮐﺎﺭﺑﺮﺩ ﺩﺍﺭﺩ ] ، [۲ﻭ ﻋﻤﺪﻩ ﺗﻮﺟﻪ ﺁﻥ ﺑﺮ ﺭﻭﻱ ﺩﻭ ﺻﻔﺖ ﺗﻌﺎﻣﻞ ﻭ ﻗﺎﺑﻠﻴﺖ ﮔﺴﺘﺮﺵ ﻣﻲ- ﺑﺎﺷﺪ .ﮔﺎﻡﻫﺎﻱ ﺍﺻﻠﻲ ﺍﻳـﻦ ﺭﻭﺵ ﻋﺒﺎﺭﺗﻨـﺪﺍﺯ(۱) :ﺗﻌﺮﻳـﻒ ﻫـﺪﻑ ﺍﺭﺯﻳـﺎﺑﻲ؛ )(۲ﻣﻬﻴﺎﺳﺎﺯﻱ ﻧﻴﺎﺯﻫﺎﻱ ﮐﻴﻔﻲ ﺳﻴﺴﺘﻢ؛ )(۳ﺁﻣﺎﺩﻩﺳﺎﺯﻱ ﻣﻌﻤﺎﺭﻱ؛ )(۴ﻣﺮﻭﺭ ﻭ ﭘﺎﻻﻳﺶ ﺩﺳﺘﺎﻭﺭﺩﻫﺎ؛ )(۵ﺑﺮﺭﺳﻲ ﻣﻌﻤﺎﺭﻱ؛ )(۶ﺍﻋﻼﻡ ﻧﺘﺎﻳﺞ. ﺟﺪﻭﻝ ) :(۱ﺟﺪﻭﻝ ﺍﺭﺯﻳﺎﺑﻲ ﺟﻬﺖ ﻣﻘﺎﻳﺴﻪ ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﺍﺟﺰﺍﺀ ﻣﺘﻦ ﻋﻨﺎﺻﺮ ﺗﻌﺮﻳﻒ SA ﻫﺪﻑ ﻭﻳﮋﻩ ﻫﺪﻑ ﺍﺻﻠﻲ ﺭﻭﺵ ﭼﻴﺴﺖ؟ ﺧﺼﻮﺻﻴﺎﺕ ﮐﻴﻔﻲ ﭼﻪ ﺗﻌﺪﺍﺩ ﻭ ﮐﺪﺍﻡ ﺧﺼﻮﺻﻴﺎﺕ ﮐﻴﻔﻲ ﺑﻮﺳﻴﻠﻪ ﺭﻭﺵ ﻣﻮﺭﺩ ﻧﻈﺮ ﭘﻮﺷﺶ ﺩﺍﺩﻩ ﻣﻲﺷﻮﺩ؟ ﻣﺮﺣﻠﻪ ﺍﻋﻤﺎﻝ ﺭﻭﺵ ﻣﻨﺎﺳﺐﺗﺮﻳﻦ ﻓﺎﺯ ﺍﻋﻤﺎﻝ ﺭﻭﺵ ﺩﺭ ﭼﺮﺧﻪ ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﮐﺪﺍﻡ ﺍﺳﺖ؟ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻭﺭﻭﺩﻳﻬﺎﻱ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻭ ﺧﺮﻭﺟﻲﻫﺎﻱ ﺗﻮﻟﻴﺪ ﺷﺪﻩ ﺗﻮﺳﻂ ﺭﻭﺵ ﮐﺪﺍﻡﻫﺎ ﻫﺴﺘﻨﺪ؟ ﺣﻮﺯﻩ ﮐﺎﺭﺑﺮﺩ ﻣﺰﻳﺖ ﺭﻭﺵ ﺍﻓﺮﺍﺩ ﺩﺭﮔﻴﺮ ﺩﺭ ﺍﺭﺯﻳﺎﺑﻲ ﺫﻳﻨﻔﻌﺎﻥ ﻣﺰﺍﻳﺎﻱ ﺭﻭﺵ ﺑﺮﺍﻱ ﺫﻳﻨﻔﻌﺎﻥ ﮐﺪﺍﻡﻫﺎ ﻫﺴﺘﻨﺪ؟ ﮐﺪﺍﻡ ﮔﺮﻭﻩ ﺍﺯ ﺫﻳﻨﻔﻌﺎﻥ ﺩﺭ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻫﺴﺘﻨﺪ؟ ﻣﻴﺰﺍﻥ ﺣﻤﺎﻳﺖ ﺭﻭﺵ ﺍﺯ ﻣﺮﺍﺣﻞ ﻣﻮﺿﻮﻋﻬﺎﻱ ﺗﮑﻨﻴﮑﻲ-ﺍﺟﺘﻤﺎﻋﻲ ﺁﻳﺎ ﺭﻭﺵ ﻫﻴﭻ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻳﺎ ﺭﺍﻫﻨﻤﺎﻳﻲ ﺭﻭﻱ ﻣﻮﺍﺭﺩ ﻏﻴﺮﺗﮑﻨﻴﮑﻲ )ﻣﺎﻧﻨﺪ ﺍﺟﺘﻤﺎﻋﻲ ،ﺳﺎﺯﻣﺎﻧﻲ ،ﻣﺪﻳﺮﻳﺘﻲ ،ﻳﺎ ﺗﺠﺎﺭﻱ( ﺍﺭﺍﺋﻪ ﻣﻲﮐﻨﺪ؟ ﻣﺮﺍﺣﻞ ﺭﻭﺵ ﺗﻮﺻﻴﻒ ﺭﻭﺵ ﺗﮑﻨﻴﮏ ﺍﺭﺯﻳﺎﺑﻲ ﺣﻤﺎﻳﺖ ﺍﺑﺰﺍﺭ ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺭﻭﺵ ﺩﺭ ﭼﻪ ﺩﺍﻣﻨﻪﻫﺎﻳﻲ ﺑﻴﺸﺘﺮﻳﻦ ﮐﺎﺭﺑﺮﺩ ﺭﺍ ﺩﺍﺷﺘﻪ ﺍﺳﺖ؟ ﭼﻪ ﻣﻴﺰﺍﻥ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺑﻮﺳﻴﻠﻪ ﺭﻭﺵ ﺑﺮﺍﻱ ﺍﻧﺠﺎﻡ ﻣﺮﺍﺣﻞ ﻣﺨﺘﻠﻒ ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ؟ ﻣﻨﺎﺑﻊ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻣﺤﺘﻮﻳﺎﺕ ﺗﻮﺿﻴﺢ ﺁﻳﺎ ﺭﻭﺵ ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﻳﮏ ﺗﻌﺮﻳﻒ ﻋﻤﻠﻲ ﺍﺯ SAﺭﺍ ﻣﻮﺭﺩ ﺭﺳﻴﺪﮔﻲ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ؟ ﺳﻄﺢ ﺭﺷﺪ ﺭﻭﺵ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺭﻭﺵ ﭼﻪ ﺗﻌﺪﺍﺩ ﺭﻭﺯ ﮐﺎﺭﻱ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺍﺳﺖ؟ ﺗﻴﻢ ﺍﺭﺯﻳﺎﺑﻲ ﭼﻨﺪ ﻧﻔﺮﻩ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺍﺳﺖ؟ ﭼﻪ ﻣﺮﺍﺣﻠﻲ ﺍﻧﺠﺎﻡ ﻣﻲﺷﻮﻧﺪ ﻭ ﺑﺎ ﭼﻪ ﺗﺮﺗﻴﺒﻲ ﺑﻪ ﻫﺪﻑ ﻣﻲﺭﺳﻨﺪ؟ ﭼﻪ ﻓﺮﻣﻲ ﺍﺯ ﺗﻮﺻﻴﻒ SAﺗﻮﺻﻴﻪ ﻣﻲﺷﻮﺩ )ﻣﺎﻧﻨﺪ ﺭﺳﻤﻲ ،ﻏﻴﺮ ﺭﺳﻤﻲ view ،ﻫﺎ ﻭ ﻏﻴﺮﻩ(؟ ﭼﻪ ﻧﻮﻉ ﺍﺯ ﺗﮑﻨﻴﮏ ﺍﺭﺯﻳﺎﺑﻲ ﺑﻮﺳﻴﻠﻪ ﺭﻭﺵ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﺩ؟ ﺁﻳﺎ ﺍﺑﺰﺍﺭﻱ ﺟﻬﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺭﻭﺵ ﻣﻮﺟﻮﺩ ﺍﺳﺖ؟ ﺳﻄﺢ ﺭﺷﺪ ﺭﻭﺵ ﺑﻪ ﭼﻪ ﻣﻴﺰﺍﻥ ﺍﺳﺖ )ﺁﻏﺎﺯ ،ﺗﻮﺳﻌﻪ ،ﭘﺎﻻﻳﺶ ،ﺳﺎﮐﺖ(؟ ﺁﻳﺎ ﺭﻭﺵ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺷﺪﻩ ﺍﺳﺖ؟ ﭼﻄﻮﺭ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺷﺪﻩ ﺍﺳﺖ؟ 2161 ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ SAAM -۵-۳ﭘﺎﻳﻪﮔﺬﺍﺭﻱ ﺷﺪﻩ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮﻫﺎﻱ -۲-۳ﺭﻭﺵ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ(SAAM) ٤ ﺭﻭﺵ SAAMﺩﺭ ﺳﺎﻝ ۱۹۹۳ﭘﺪﻳﺪﺍﺭ ﺷﺪ ،ﻛﻪ ﺍﻳﻦ ﺳـﺎﻝﻫـﺎ ﻣﻘـﺎﺭﻥ ﺑـﺎ ﺗﻤﺎﻳﻞ ﺑﺮﺍﻱ ﻓﻬﻢ ﺑﻬﺘﺮ ﻣﻔﺎﻫﻴﻢ ﮐﻠﻲ ﻣﻌﻤﺎﺭﻱ ﺑﻮﺩ].[27 ﻫﺪﻑ ﺍﺻﻠﻲ :ﺑﺮﺭﺳﻲ ﺻﺤﺖ ﻓﺮﺿﻴﺎﺕ ﻭ ﻗﻮﺍﻋـﺪ ﭘﺎﻳـﻪﺍﻱ ﻣﻌﻤـﺎﺭﻱ ﺩﺭ ﺑﺮﺍﺑﺮ ﺍﺳﻨﺎﺩﻱ ﮐﻪ ﺧﺼﻮﺻﻴﺎﺕ ﻣﻄﻠﻮﺏ ﻳـﮏ ﺑﺮﻧﺎﻣـﻪ ﮐـﺎﺭﺑﺮﺩﻱ ﺭﺍ ﺗﻮﺻـﻴﻒ ﻣﻲﮐﻨﻨﺪ .ﺑﻌﻼﻭﻩ ،ﺍﺭﺯﻳﺎﺑﻲ ﺭﻳﺴﻚﻫﺎﻱ ﻣﻌﻤـﺎﺭﻱ ﻭ ﺗﻤﺮﮐـﺰ ﺑـﺮ ﺭﻭﻱ ﻧﻘـﺎﻁ ﺑﺤﺮﺍﻧﻲ ﻛﻪ ﺍﺯﺟﻤﻠﻪ ﺍﻳﻦ ﻧﻘﺎﻁ ﺑﺤﺮﺍﻧﻲ ﺗﻀﺎﺩ ٥ﺑﻴﻦ ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎ ﻳـﺎ ﺗﻨـﺎﻗﺾ ﻣﺸﺨﺼﻪﻫﺎﻱ ﻃﺮﺍﺣـﻲ ﺍﺯ ﺩﻳـﺪ ﻳـﮏ ﺫﻳﻨﻔـﻊ ﻣـﻲﺑﺎﺷـﻨﺪ .ﺭﻭﺵ SAAM ﻫﻤﭽﻨﻴﻦ ﺑﺮﺍﻱ ﻣﻘﺎﻳﺴﻪ ﻣﻌﻤﺎﺭﻱﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ )ﺷﻜﻞ ).((۱ ﺗﻮﺳﻌﻪ ﺳﻨﺎﺭﻳﻮ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺍﺭﺯﻳﺎﺑﻲ ﮐﻠﻲ ﻣﻘﺎﻳﺴﻪ ﭼﻨﺪ ﻣﻌﻤﺎﺭﻱ ﺭﻭﺵ [28] SAAMCSﭘﻴﭽﻴﺪﮔﻲ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ﻓﺎﮐﺘﻮﺭ ﺑـﺴﻴﺎﺭ ﻣﻬﻤﻲ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﺭﻳﺴﮏ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ .ﺍﺭﺯﻳـﺎﺑﻲ ﺭﻳـﺴﮏ ﻫﺪﻑ ﺍﺻﻠﻲ ﺍﻳﻦ ﺭﻭﺵ ﻣﻲﺑﺎﺷﺪ .ﺍﻳﻦ ﺭﻭﺵ ﺑﻪ ﺩﻧﺒﺎﻝ ﺳﻨﺎﺭﻳﻮﻫﺎﻳﻲ ﺍﺳﺖ ﮐﻪ ﺗﺤﻘﻖ ﺁﻧﻬﺎ ﭘﻴﭽﻴﺪﻩ ﺍﺳﺖ .ﺩﺭ ﺗﻮﺳﻌﻪ ﺳﻨﺎﺭﻳﻮ ،ﻳﮏ ﺩﻳﺎﮔﺮﺍﻡ ﺩﻭ ﺑﻌﺪﻱ )ﭘـﻨﺞ ﮔﺮﻭﻩ ﺍﺯ ﻧﻮﻉ ﭘﻴﭽﻴﺪﮔﻲ ﺳﻨﺎﺭﻳﻮﻫﺎ ،ﭼﻬﺎﺭ ﻣﻨﺒﻊ ﺗﻐﻴﻴﺮﺍﺕ( ﺗﻌﺮﻳﻒ ﻣـﻲﺷـﻮﺩ ﮐﻪ ﻣﻤﮑﻦ ﺍﺳﺖ ﺑﺮﺍﻱ ﭘﻮﺷـﺶ ﺩﺍﺩﻥ ﺳـﻨﺎﺭﻳﻮﻫﺎﻱ ﭘﻴﭽﻴـﺪﻩ ﮐﻤـﮏ ﮐﻨـﺪ. ﻣﻨﺎﺑﻊ ﺗﻐﻴﻴﺮﺍﺕ ،ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎﻱ ﭘﺎﻳﻪ ،ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎﻱ ﮐﻴﻔﻴﺘﻲ ،ﻣﻮﻟﻔﻪ ﻫـﺎﻱ ﺧﺎﺭﺟﻲ ﻭ ﻣﺤﻴﻂ ﻓﻨﻲ ﻫﺴﺘﻨﺪ )ﺷﮑﻞ ).((۲ ﺗﻮﺻﻴﻒ AND ﺍﺭﺯﻳﺎﺑﻲ ﺳﻨﺎﺭﻳﻮ ﺑﻪ ﺗﻔﮑﻴﮏ ﭘﻴﭽﻴﺪﻩ(SAAMCS) ٨ ﺗﻮﺻﻴﻒ ﺳﻨﺎﺭﻳﻮ ﺗﺤﻠﻴﻞ ﻧﻴﺎﺯﻫﺎ SAAM ﺗﻌﺎﻣﻞ ﺳﻨﺎﺭﻳﻮ ﺗﻮﺳﻌﻪ ﺳﻨﺎﺭﻳﻮ ﺳﻨﺎﺭﻳﻮﻫﺎﯼ ﭘﻴﭽﻴﺪﻩ AND ﺑﹺﻴﺎﻥ ﻧﻴﺎﺯﻫﺎ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺗﺤﻠﻴﻞ ﻣﺠﺮﺩ ﻣﻌﻤﺎﺭﻱ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﺍﺭﺯﻳﺎﺑﻲ ﺍﺛﺮ ﺳﻨﺎﺭﻳﻮ ﺗﻮﺻﻴﻒ SAAMCS ﺗﺤﻠﻴﻞ ﻣﺠﺮﺩ ﻣﻌﻤﺎﺭﻱ ﺷﻜﻞ) :(۱ﻭﺭﻭﺩﻳﻬﺎ ﻭ ﻣﺮﺍﺣﻞ ﺭﻭﺵ SAAM ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺧﺮﺩ ﻭ ﮐﻼﻥ ﻭﺳﺎﻳﻞ ﺍﻧﺪﺍﺯﻩﮔﻴﺮﻱ ﺷﮑﻞ ) :(۲ﻭﺭﻭﺩﻱﻫﺎ ﻭ ﻓﻌﺎﻟﻴﺖﻫﺎﻱ SAAMCS -۳-۳ﺭﻭﺵ ﺗﺤﻠﻴﻞ ﻧﻘﺎﻁ ﺗﻌﺎﺩﻟﻲ ﻣﻌﻤﺎﺭﻱ(ATAM) ٦ -۶-۳ﻣﺮﻭﺭﻫﺎﻱ ﻓﻌﺎﻝ ﺑﺮﺍﻱ ﻃﺮﺍﺣﻲ ﻣﻴﺎﻧﻲ(ARID) ٩ ﺭﻭﺵ ATAMﺑﺮﻣﺒﻨﺎﻱ SAAMﺑﺮﺍﻱ ﺗﺤﻠﻴﻞ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ،ﮐـﺎﺭﺍﻳﻲ، ﺩﺭ ﺩﺳﺘﺮﺱ ﺑﻮﺩﻥ ﻭ ﺍﻣﻨﻴﺖ ﻣﻲﺑﺎﺷﺪ] ATAM .[12ﺩﺭ ۱۹۹۸ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﮏ ﻣﺪﻝ ﻣﺎﺭﭘﻴﭽﻲ ﺍﺯ ﻃﺮﺍﺣﻲﻫﺎ ﻭ ﺩﺭ ۱۹۹۹ Mayﺑﻪ ﻋﻨﻮﺍﻥ ﻳـﮏ ﻣـﺪﻝ ﻣﺎﺭﭘﻴﭽﻲ ﺍﺯ ﺗﺤﻠﻴﻞ ﻭ ﻃﺮﺍﺣﻲ ﻣﻄﺮﺡ ﺷﺪ .ﻫﺪﻑ ATAMﺍﺭﺍﺋﻪ ﻳﮏ ﺭﻭﺵ ﺍﺻﻮﻟﻲ ﺟﻬﺖ ﻓﻬﻢ ﺗﻮﺍﻧﺎﻳﻲ SAﺩﺭ ﻣﻘﺎﻳـﺴﻪ ﭼﻨـﺪﻳﻦ ﻣﺸﺨـﺼﻪ ﮐﻴﻔﻴﺘـﻲ ﻣﻲﺑﺎﺷﺪ ATAM .ﺿـﺮﻭﺭﺕ ﺑﺮﻗـﺮﺍﺭﻱ ﺗﻌـﺎﺩﻝ ﻣﻴـﺎﻥ ﭼﻨـﺪﻳﻦ ﻣﺸﺨـﺼﻪ ﮐﻴﻔﻴﺘﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺭﺍ ﺩﺭ ﺯﻣﺎﻥ ﻣﺸﺨﺺ ﮐـﺮﺩﻥ SAﻭ ﻗﺒـﻞ ﺍﺯ ﺗﻮﺳـﻌﻪ ﺁﻥ ﺗﻌﻴﻴﻦ ﻣﻲﮐﻨﺪ .ﺍﻳﻦ ﺭﻭﺵ ﺍﺯ ﭼﻬﺎﺭ ﻓﺎﺯ ﻓﻌﺎﻟﻴﺘﻲ ﺍﺻﻠﻲ ﺷـﺎﻣﻞ ﺟﻤـﻊﺁﻭﺭﻱ ﻧﻴﺎﺯﻫﺎ ﻭ ﺳﻨﺎﺭﻳﻮﻫﺎ ،ﻣﺤﻘﻖﺳﺎﺯﻱ ﺳﻨﺎﺭﻳﻮﻫﺎ ﻭ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺑﺎ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ ﺩﻳﺪﻫﺎ ،ﻣﺪﻝﺳﺎﺯﻱ ﻭ ﺗﺤﻠﻴﻞ ﻭ ﺗﻌﺎﺩﻝ ﺑﻴﻦ ﺻﻔﺎﺕ ﺗﺸﮑﻴﻞ ﻣﻲﺷﻮﺩ. ﺭﻭﺵ ، ARIDﺍﻳﺪﻩ ﺭﻭﺵﻫﺎﻱ ﻣﺒﺘﻨـﻲ ﺑـﺮ ﺳـﻨﺎﺭﻳﻮ ﻣﺎﻧﻨـﺪ ATAMﻳـﺎ SAAMﺭﺍ ﺑﺎ ﺟﻠﺴﺎﺕ ﻣﮑﺮﺭ ﻣﺮﻭﺭ ﻣﻌﻤﺎﺭﻱ ﻭ ﻃﺮﺍﺣﻲ ﺗﻠﻔﻴـﻖ ﻣـﻲﮐﻨـﺪ ﻭ ﺗﻤﺮﮐﺰ ﺍﺻﻠﻲ ﺁﻥ ﺑﺮ ﻃﺮﺍﺣﻲﻫﺎﻱ ﺟﺰﺋﻲ ﺑﺨﺶﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﺳﺖ ،ﺑـﺎ ﺍﻳـﻦ ﺍﺳﺘﺪﻻﻝ ﮐﻪ ﺍﮔﺮ ﻃﺮﺍﺣﻲﻫـﺎﻱ ﺟﺰﺋـﻲ ﺩﺭﺳـﺖ ﺍﻧﺠـﺎﻡ ﻧـﺸﺪﻩ ﺑﺎﺷـﺪ ،ﮐـﻞ ﻣﻌﻤﺎﺭﻱ ﻧﺎﺩﺭﺳﺖ ﺧﻮﺍﻫﺪ ﺑﻮﺩ .ﻫﺪﻑ ﺍﻳﻦ ﺭﻭﺵ ﺍﻳﻦ ﺍﺳﺖ ﮐﻪ ﺍﺯ ﺳـﺎﺯﮔﺎﺭﻱ ﻃﺮﺍﺣﻲﻫﺎﻱ ﺟﺰﺋﻲ ﺑﺎ ﺳﺎﻳﺮ ﺑﺨﺶﻫﺎ ﺍﻃﻤﻴﻨﺎﻥ ﺣﺎﺻﻞ ﮐﻨﺪ ].[۲ -۴-۳ﺭﻭﺵ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺑﺮﺍﻱ ﺗﮑﺎﻣﻞ ﻭ ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ:(SAAMER) ٧ ﺩﺭ ﺗﻮﺳﻌﻪ ﺭﻭﺵ SAAMﺑﻪ SAAMERﺩﻭ ﺧﺼﻮﺻﻴﺖ ﮐﻴﻔﻴﺘﻲ ﻳﻌﻨـﻲ ﺗﮑﺎﻣﻞ ﻭ ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ،ﻣﻮﺭﺩ ﺗﺎﮐﻴﺪ ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳـﺖ ].[19 ﺭﻭﺵ SAAMERﭘﻴﺸﻨﻬﺎﺩﺍﺕ ﺧﻮﺑﻲ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲﮐﻨـﺪ ﮐـﻪ ﭼﻄـﻮﺭ ﻳـﮏ ﺳﻴﺴﺘﻢ ﻣﻲﺗﻮﺍﻧـﺪ ﻫـﺮ ﮐـﺪﺍﻡ ﺍﺯ ﺍﻫـﺪﺍﻑ ﮐﻴﻔﻴﺘـﻲ ﻳـﺎ ﺳـﻄﻮﺡ ﺭﻳـﺴﮏ ﺭﺍ ﭘﺸﺘﻴﺒﺎﻧﻲ ﮐﻨﺪ ،ﻭ ﻳﺎ ﺍﻳﻨﮑﻪ ﭼﻄﻮﺭ ﺁﻥ ﺭﺍ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﮐﻨﺪ. SAAMERﻳﮏ ﭼﻬﺎﺭﭼﻮﺏ ﺍﺯ ﻓﻌﺎﻟﻴﺖﻫﺎ ﺭﺍ ﺍﺭﺍﺋـﻪ ﻣـﻲﮐﻨـﺪ ﮐـﻪ ﺑـﺮﺍﻱ ﻓﺮﺁﻳﻨﺪ ﺗﺤﻠﻴﻞ ﺳﻮﺩﻣﻨﺪ ﻣﻲﺑﺎﺷﻨﺪ .ﺍﻳﻦ ﭼﻬﺎﺭﭼﻮﺏ ﺗﺮﮐﻴﺒﻲ ﺍﺳﺖ ﺍﺯ ﭼﻬـﺎﺭ ﻓﻌﺎﻟﻴﺖ ﮐﻪ ﻋﺒﺎﺭﺗﻨﺪﺍﺯ :ﮔﺮﺩﺁﻭﺭﻱ ﺍﻃﻼﻋﺎﺕ ﺩﺭﺑﺎﺭﻩ ﺫﻳﻨﻔﻌﺎﻥ ،SA ،ﮐﻴﻔﻴﺖ، ﺳﻨﺎﺭﻳﻮﻫﺎ ،ﻣﺪﻝ ﮐﺮﺩﻥ ﻣﺼﻨﻮﻋﺎﺕ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ،ﺗﺤﻠﻴﻞ ﻭ ﺍﺭﺯﻳﺎﺑﻲ. -۷-۳ﺭﻭﺵ ﺗﺤﻠﻴﻞ ﻫﺰﻳﻨﻪ ﺳﻮﺩ(CBAM) ١٠ ﺍﻳﻦ ﺭﻭﺵ ﺑﺮﻣﺒﻨﺎﻱ ATAMﺑﻮﺩﻩ ﻭ ﺗﺤﻠﻴﻞ ﺭﺍ ﺍﺯ ﺟﺎﻳﻲ ﺑـﻪ ﭘﺎﻳـﺎﻥ ﻣـﻲ- ﺭﺳﺎﻧﺪ ﮐﻪ ATAMﺗﻤﺎﻡ ﺷﺪﻩ ﺍﺳﺖ .ﻋﻤﺪﺗﺎ ﺑﻪ ﻫﺰﻳﻨﻪ ،ﺯﻣﺎﻥﺑﻨﺪﻱ ﻭ ﻓﻮﺍﺋﺪ ﭘﺮﻭﮊﻩ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺗﻮﺟﻪ ﺩﺍﺭﺩ ﻭ ﻫﺰﻳﻨﻪ ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳـﮏ ﺻـﻔﺖ ﮐﻴﻔـﻲ ﺩﺭ ﻧﻈﺮ ﻣﻲﮔﻴﺮﺩ ﻭ ﺍﺯ ﺁﻧﺠﺎﺋﻴﮑﻪ ﺭﻭﻱ ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻋﻤﻮﻣﻲ ﻣﺜـﻞ SAAMﻭ ATAMﺳﺎﺧﺘﻪ ﺷﺪﻩ ﺍﺳﺖ ،ﺩﺭ ﻧﺘﻴﺠﻪ ﺭﻭﺵ ﮐـﺎﺭﺍﺋﻲ ﺁﻧﻬـﺎ ﺭﺍ ﺑﻪ ﺍﺭﺙ ﺑﺮﺩﻩ ﺍﺳﺖ] . [13ﻣﺮﺍﺣﻞ ﺭﻭﺵ ﻋﺒﺎﺭﺗﻨﺪﺍﺯ(۱) :ﺍﺭﺯﻳﺎﺑﻲ ﻓﻮﺍﺋﺪ ﺻﻔﺎﺕ ﮐﻴﻔــﻲ؛ )(۲ﺗﻌﻴــﻴﻦ ﻓﻮﺍﺋــﺪ ﺍﺳــﺘﺮﺍﺗﮋﻳﻬﺎﻱ ﻣﻌﻤــﺎﺭﻱ؛ )(۳ﺑــﺮﺁﻭﺭﺩ ﻫﺰﻳﻨــﻪ ﻭ ﺯﻣﺎﻧﺒﻨﺪﻱ؛ )(۴ﻣﺤﺎﺳﺒﻪ ﻣﻄﻠﻮﺑﻴﺖ؛ )(۵ﺗﺼﻤﻴﻢﮔﻴﺮﻱ. -۸-۳ﻣﺪﻟﻲ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ(SAEM) ١١ ﻓﺮﺁﻳﻨﺪ ﺍﺭﺯﻳﺎﺑﻲ ﻧﻴﺎﺯﻣﻨﺪﻳﻬﺎﻱ ﮐﻴﻔﻴﺘـﻲ SAﺩﺭ ﺍﻳـﻦ ﺭﻭﺵ ﮐـﺎﻣﻼ ﻓﺮﻣﻮﻟـﻪ ﺷﺪﻩ ﺍﺳﺖ ،ﺑﻮﻳﮋﻩ ﺩﺭ ﻣﻮﺭﺩ ﻣﺘﺮﻳﮏﻫﺎﻳﻲ ﮐﻪ ﺩﺭ ﻣـﺪﻝ ] [15ﺗﻮﺿـﻴﺢ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ .ﻳﮏ ﻣﺪﻝ ﮐﻴﻔﻴﺘﻲ ﺑﺮ ﻣﺒﻨﺎﻱ ﻓﺮﺁﻳﻨﺪ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺍﺭﺯﻳﺎﺑﻲ ﮐﻴﻔﻴﺖ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺍﻧﺘﺨﺎﺏ ﻣﻲﺷﻮﺩ ﻭ ﻳﮏ ﭼﻬﺎﺭﭼﻮﺏ ﻣﻔﻬﻮﻣﻲ ﮐـﻪ ﻧﻴﺎﺯﻣﻨـﺪﻱﻫـﺎﻱ 2162 ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ ﮐﻴﻔﻴﺘﻲ ،ﻣﺘﺮﻳﮏﻫﺎ ﻭ ﺧﺼﻮﺻﻴﺎﺕ ﺩﺍﺧﻠﻲ SAﻭ ﺳﻴﺴﺘﻢ ﻧﻬﺎﻳﻲ ﺭﺍ ﻣﺮﺑـﻮﻁ ﻣﻲﮐﻨﺪ ،ﭘﻴﺸﻨﻬﺎﺩ ﻣﻲﺷﻮﺩ .ﻋﻨﺎﺻﺮﻱ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﮐﻴﻔﻴﺖ ﻳـﮏ ﺳﻴـﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺑﺮﻣﺒﻨﺎﻱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺧﺎﺻﻲ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺍﺳﺖ ﮐﻪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ :ﻳـﮏ ﻣﺪﻝ ﮐﻴﻔﻴﺘﻲ ،ﻳﮏ ﺭﻭﺵ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻭ ﺍﺑﺰﺍﺭ ﭘﺸﺘﻴﺒﺎﻧﻲ. ASAAM -۹-۳ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺍﺭﺯﻳﺎﺑﻲ ﺻﻔﺖ ﮐﻴﻔﻲ OK ١٢ ﺍﻳﻦ ﺭﻭﺵ ﻧﻴﺰ ﺑﻪ ﻧﻮﻋﻲ ﺗﻮﺳﻌﻪﻳﺎﻓﺘﻪ ﺭﻭﺵ SAAMﻣﻲﺑﺎﺷﺪ] .[18ﻣﺸﺎﺑﻪ ﺑﺎ ﺁﻥ ﺑﻪ ﻋﻨﻮﺍﻥ ﻭﺭﻭﺩﻱ ﺗﻮﺻﻴﻒ ﻣﺴﺎﻟﻪ ،ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﻭ ﺗﻮﺻﻴﻒ ﻧﻴﺎﺯﻫﺎ ﺭﺍ ﺩﺭﻳﺎﻓﺖ ﻣﻲﮐﻨﺪ .ﻣﺮﺍﺣﻞ ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺷﮑﻞ ) (۳ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ. ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺗﻮﺳﻌﻪ ﺳﻨﺎﺭﻳﻮ ﺑﺎﺯﺳﺎﺯﯼ ﻣﻌﻤﺎﺭﻱ ﺍﺯ ﻟﺤﺎﻅ aspectﻫﺎ ﺑﺎﺯﺳﺎﺯﻱ ﻣﻌﻤﺎﺭﻱ ﺷﮑﻞ ) :(۳ﻣﺮﺍﺣﻞ ASAAM -۱۰-۳ﮔﺴﺘﺮﺵ SAAMﺑﻮﺳﻴﻠﻪ ﻳﮑﭙﺎﺭﭼﻪﺳﺎﺯﻱ ﺩﺭ ﺩﺍﻣﻨﻪ(ESAAMI) ١٣ ﺍﻳﻦ ﺭﻭﺵ ﺗﻌﻤﻴﻤﻲ ﺍﺯ SAAMﺍﺳﺖ ﮐﻪ ﺑﺎ ﺗﻤﺮﮐﺰ ﺩﺭ ﺣﻮﺯﻩﻫـﺎﻱ ﺧـﺎﺹ ﺳﻌﻲ ﺩﺭ ﺍﻓﺰﺍﻳﺶ ﻣﻴﺰﺍﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺩﺍﺭﺩ] .[12ﺷﮑﻞ ) (۴ﻭﺭﻭﺩﻱﻫﺎﻱ ﺍﺻﻠﻲ ESAAMIﻭ ﺭﻭﺍﺑﻂ ﺑﻴﻦ ﺁﻧﻬﺎ ﺭﺍ ﺷﺮﺡ ﻣﻲﺩﻫﺪ. ﻃﺮﺍﺣﻲ ﺑﻴﺎﻥ ﻧﻴﺎﺯﻫﺎ ﺗﺤﻠﻴﻞ Not OK ﺍﺻﻼﺣﺎﺕ ﻣﻌﻤﺎﺭﻱ ﺍﺻﻼﺡ ﺻﻔﺖ ﮐﻴﻔﻲ ﭘﻴﺎﺩﻩﺳﺎﺯﻱ ﺷﮑﻞ ) :(۵ﻣﺮﺍﺣﻞ . SBARﻃﺮﺍﺣﻲ ﻭ ﺗﺤﻠﻴﻞ SA -۱۲-۳ﭘﻴﺶﺑﻴﻨﻲ ﻧﮕﻬﺪﺍﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺩﺭ ﺳﻄﺢ ﻣﻌﻤﺎﺭﻱ(ALPSM) ١٦ ﺍﺭﺯﻳﺎﺑﻲ ﺳﻨﺎﺭﻳﻮﻫﺎ ﻭ ﺷﻨﺎﺳﺎﻳﻲ aspectﻫﺎ ﺍﺭﺯﻳﺎﺑﻲ ﺗﻌﺎﻣﻞ ﺑﻴﻦ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺗﻌﻴﻴﻦ ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎ ﻃﺮﺍﺣﻲ ﻣﺠﺪﺩ ﻣﻌﻤﺎﺭﻱ ﺑﺮﻣﺒﻨﺎﻱ ﻋﻤﻠﮑﺮﺩ ، ALPSMﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ ﻳﮏ ﺳﻴﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺭﺍ ﺑﻮﺳـﻴﻠﻪ ﺑﺮﺭﺳـﻲ ﺗﺎﺛﻴﺮ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺩﺭ ﺳﻄﺢ SAﺗﺤﻠﻴﻞ ﻣﻲﮐﻨﺪ ] ALPSM .[16ﺍﺯ ﻣﻴـﺰﺍﻥ ﺗﻐﻴﻴﺮﺍﺕ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﮏ ﻋﺎﻣﻞ ﭘﻴﺸﮕﻮﻳﻲﮐﻨﻨـﺪﻩ ﺑـﺮﺍﻱ ﺗـﻼﺵ ﻣـﻮﺭﺩ ﻧﻴـﺎﺯ ﺟﻬﺖ ﺳﺎﺯﮔﺎﺭﻱ ﺳﻴﺴﺘﻢ ﺩﺭ ﺩﺍﺧﻞ ﻳﮏ ﺳﻨﺎﺭﻳﻮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﮐﻨﺪ ].[17 ﺍﻳﻦ ﺭﻭﺵ )ﺷﮑﻞ ) ((۶ﺗﻌﺪﺍﺩﻱ ﻭﺭﻭﺩﻱ ﺩﺍﺭﺩ ﻭ ﺗﺮﮐﻴﺒﻲ ﺍﺳﺖ ﺍﺯ ﺷﺶ ﮔﺎﻡ ﮐﻪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ(۱) :ﺷﻨﺎﺳﺎﻳﻲ ﻃﺒﻘﻪ ﺑﻨـﺪﻱﻫـﺎﻱ ﻭﻇـﺎﻳﻒ ﻣﺮﺑـﻮﻁ ﺑـﻪ ﭘﺸﺘﻴﺒﺎﻧﻲ؛ )(۲ﺗﺮﮐﻴﺐ ﺳﻨﺎﺭﻳﻮﻫﺎ١٧؛ )(۳ﻧﺴﺒﺖ ﺩﺍﺩﻥ ﻭﺯﻥ ﺑﻪ ﻫـﺮ ﺳـﻨﺎﺭﻳﻮ؛ )(۴ﺗﺨﻤﻴﻦ ﺍﻧﺪﺍﺯﻩ ﻫﻤﻪ ﻋﻨﺎﺻﺮ؛ )(۵ﺗﻬﻴـﻪ ﻣـﺘﻦ ﺳـﻨﺎﺭﻳﻮﻫﺎﻭ )(۶ﻣﺤﺎﺳـﺒﻪ ﺗﻼﺵ ﭘﻴﺶﺑﻴﻨﻲ ﺷﺪﻩ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ. ﺑﻴﺎﻥ ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﺗﺨﻤﻴﻦ ﻧﮕﻬﺪﺍﺭﻱ ﺗﻮﺻﻴﻒ ﻣﺴﺎﻟﻪ ﺭﻭﺵ ( ALPSM )ﭘﻴﺶﺑﻴﻨﻲ ﻧﮕﻬﺪﺍﺭﻱ ﺍﻇﻬﺎﺭ ﻧﻈﺮ ﻓﻨﻲ ﻣﻬﻨﺪﺱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺑﻴﺎﻥ ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎ ESAAMI ﺍﻟﮕﻮﻱ ﺗﺤﻠﻴﻞ ﺑﺎ ﺩﺍﻣﻨﻪ ﻣﺤﺪﻭﺩ ﻣﻌﻤﺎﺭﻱ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ+ﺍﻟﮕﻮﻱ ﺗﺤﻠﻴﻞ ﺍﻧﺘﺨﺎﺏ ﺷﮑﻞ ) :(۶ﻭﺭﻭﺩﻱﻫﺎ ﻭ ﻧﺘﺎﻳﺞ ALPSM ﻣﻌﻤﺎﺭﻱ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ+ﺍﻟﮕﻮﻱ ﺗﺤﻠﻴﻞ -۱۳-۳ﺗﺤﻠﻴﻞ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ﺩﺭ ﺳﻄﺢ ﻣﻌﻤﺎﺭﻱ ﺷﮑﻞ ) :(۴ﻭﺭﻭﺩﻱﻫﺎﻱ ﺭﻭﺵ ESAAMI -۱۱-۳ﻣﻬﻨﺪﺳﻲ ﻣﺠﺪﺩ ﻣﻌﻤﺎﺭﻱ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ ١٨ )(ALMA ١٤ )(SBAR ﭼﻬﺎﺭ ﺗﮑﻨﻴﮏ ﻣﺨﺘﻠﻒ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﺸﺨﺼﻪﻫﺎﻱ ﮐﻴﻔﻴﺘﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣـﻲ- ﺷﻮﺩ :ﺳﻨﺎﺭﻳﻮﻫﺎ ،ﺷﺒﻴﻪ ﺳﺎﺯﻱ ،ﻣﺪﻝ ﺳﺎﺯﻱ ﺭﻳﺎﺿﻲ ﻭ ﺍﺳﺘﺪﻻﻝ ﺑﺮ ﻣﺒﻨـﺎﻱ ﺗﺠﺮﺑﻪ . ١٥ﺑﺮﺍﻱ ﻫﺮ ﻣﺸﺨﺼﻪ ﮐﻴﻔﻴﺘﻲ ,ﺗﮑﻨﻴﮏ ﻣﻨﺎﺳﺐ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﺷـﻮﺩ. ﻳﮏ ﺧﺼﻮﺻﻴﺖ ﺑﺮﺟﺴﺘﻪ ﺍﻳﻦ ﺭﻭﺵ ﺁﻥ ﺍﺳﺖ ﮐﻪ ﺑـﺮﺍﻱ ﺍﺭﺯﻳـﺎﺑﻲ ﻣﻌﻤـﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻣﻮﺟﻮﺩ ،ﺧﻮﺩ ﺳﻴﺴﺘﻢ ﻣﻲﺗﻮﺍﻧﺪ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ ].[29 ﻓﺮﺁﻳﻨﺪ ﺍﺭﺯﻳﺎﺑﻲ )ﺷﮑﻞ ) ((۵ﻣﻲﺗﻮﺍﻧﺪ ﺑﻪ ﺭﻭﺵ ﮐﺎﻣﻞ ﻳﺎ ﺁﻣﺎﺭﻱ ﺍﻧﺠـﺎﻡ ﺷﻮﺩ .ﺩﺭ ﺭﻭﺵ ﺍﻭﻝ ،ﻣﺠﻤﻮﻋﻪﺍﻱ ﺍﺯ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺗﻌﺮﻳﻒ ﻭ ﺑﺎ ﻫﻢ ﺗﺮﮐﻴﺐ ﻣﻲ- ﺷﻮﻧﺪ .ﺩﻭﻣﻴﻦ ﺭﻭﺵ ﺗﻌﺮﻳﻒ ﮐﺮﺩﻥ ﻣﺠﻤﻮﻋﻪﺍﻱ ﺍﺯ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺍﺳﺖ ﮐﻪ ﻳـﮏ ﻧﻤﻮﻧﻪ ﺳﺎﺩﻩ ﺑﺪﻭﻥ ﻫﻤﻪ ﻣﻮﺍﺭﺩ ﺭﺍ ﻣﻲﺳﺎﺯﺩ SBAR .ﺑﻪ ﻋﻨﻮﺍﻥ ﺭﻭﺷﻲ ﺑـﺮﺍﻱ ﺍﻧﺪﺍﺯﻩﮔﻴﺮﻱ ﺳﻴﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺷﻨﺎﺧﺘﻪ ﺷﺪﻩ ﺍﺳﺖ. ﺍﻳﻦ ﺭﻭﺵ ﺑﺮﻣﺒﻨﺎﻱ SAAMﺑﻨﺎ ﺷﺪﻩ ﺍﺳﺖ ﻭ ﺩﺭ ﺍﺑﺘﺪﺍ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺗﺠﺎﺭﻱ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﮔﺮﻓﺖ] .[5,6ﻫﺪﻑ ﺍﺻﻠﻲ ﺍﻳﻦ ﺭﻭﺵ ﺍﺭﺯﻳﺎﺑﻲ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ﺩﺭ ﺟﻬﺖ ﭘﻴﺶﺑﻴﻨﻲ ﻫﺰﻳﻨﻪ ﺍﺻﻼﺡ ،ﺷﻨﺎﺳﺎﻳﻲ ﻋـﺪﻡ ﺍﻧﻌﻄﺎﻑﭘﺬﻳﺮﻱ ﺳﻴﺴﺘﻢ ﻭ ﻣﻘﺎﻳﺴﻪ ﺩﻭ ﻳﺎ ﭼﻨﺪ ﻣﻌﻤﺎﺭﻱ ﻣﻲﺑﺎﺷﺪ. ﻣﺮﺍﺣﻞ ﺍﻧﺠﺎﻡ ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺷﮑﻞ ) (۷ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ. 2163 ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺍﺳﺘﺨﺮﺍﺝ ﺳﻨﺎﺭﻳﻮﻫﺎﻱ ﺗﻐﻴﻴﺮﺍﺕ ﻣﺠﻤﻮﻋﻪ ﺍﻫﺪﺍﻑ ﺍﺭﺯﻳﺎﺑﻲ ﺳﻨﺎﺭﻳﻮﻱ ﺗﻐﻴﻴﺮﺍﺕ ﺗﻔﺴﻴﺮ ﻧﺘﺎﻳﺞ ﻭ ﺍﺭﺍﺋﻪ ﻧﺘﻴﺠﻪﮔﻴﺮﻱ ﺷﮑﻞ) :(۷ﻣﺪﻝ ﻓﺮﺁﻳﻨﺪ [16] ALMA ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ -۱۴-۳ﺍﺭﺯﻳﺎﺑﻲ ﮐﺎﺭﺍﻳﻲ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ(PASA) ١٩ Williamsﻭ Smithﺭﻭﺷﻲ ﺭﺍ ﺍﺭﺍﺋﻪ ﺩﺍﺩﻧﺪ ﺗـﺎ ﻣﻮﺿـﻮﻉﻫـﺎﻱ ﻣـﺮﺗﺒﻂ ﺑـﺎ ﮐﺎﺭﺍﻳﻲ ﺭﺍ ﺩﺭ ﺳﻄﺢ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻣﻮﺭﺩ ﺍﺭﺯﻳﺎﺑﻲ ﻗﺮﺍﺭ ﺩﻫﻨﺪ ﮐـﻪ ﺍﻳـﻦ ﺭﻭﺵ ﺍﺭﺯﻳﺎﺑﻲ ﮐﺎﺭﺍﻳﻲ ﻣﻌﻤﺎﺭﻱ ﻧـﺮﻡﺍﻓـﺰﺍﺭﻱ ) (PASAﻧﺎﻣﻴـﺪﻩ ﻣـﻲﺷـﻮﺩ )ﺷﮑﻞ ) .، [7]((۸ﺍﻳﻦ ﺭﻭﺵ ﺑﺮﺍﻱ ﺍﺭﺯﻳﺎﺑﻲ ﮐﺎﺭﺍﻳﻲ SAﻣﺒﺘﻨﻲ ﺑﺮ ﺍﺑﺰﺍﺭﻫﺎ ﻭ ﺗﮑﻨﻴﮏﻫﺎﻳﻲ ﺍﺳﺖ ﮐﻪ ﺍﻳﻦ ﺩﻭ ﺩﺭ ﮐﺎﺭﺷﺎﻥ ﺑﻪ ﮐـﺎﺭ ﮔﺮﻓﺘـﻪﺍﻧـﺪ ﻭ ﺩﺭ ][7,9 ﮔﺰﺍﺭﺵ ﺷﺪﻩ ﺍﺳﺖ. ﻣﺸﺨﺺ ﮐﺮﺩﻥ use- ﺩﻳﺪﮔﺎﻩ ﮐﻠﻲ ﻣﻌﻤﺎﺭﻱ ﺩﻳﺪﮔﺎﻩ ﮐﻠﻲ ﻓﺮﺁﻳﻨﺪ ﺍﻧﺘﺨﺎﺏ ﺳﻨﺎﺭﻳﻮﻫﺎﯼ ﮐﻠﻴﺪﻱ ﻣﺸﺨﺺ ﮐﺮﺩﻥ ﺍﻫﺪﺍﻑ ﺗﻮﺿﻴﺢ ﻭ ﺑﺤﺚ ﺩﺭ ﻣﻮﺭﺩ ﻣﻌﻤﺎﺭﻱ caseﻫﺎﻱ ﺑﺤﺮﺍﻧﻲ ﺍﺭﺍﺋﻪ ﻧﺘﺎﻳﺞ ﺗﺤﻠﻴﻞ ﺍﻗﺘﺼﺎﺩﻱ ﻣﺸﺨﺺ ﮐﺮﺩﻥ ﮔﺰﻳﻨﻪ ﻫﺎ ﻣﺮﺍﺟﻊ ] [۱ﺟﻠﻴﻠﻲ ،ﺳﻌﻴﺪ ،ﮐﻴﻮﺍﻥﭘﻮﺭ ﻣﺤﻤﺪﺭﺿﺎ" ،ﻃﺒﻘﻪﺑﻨﺪﻱ ﻭ ﺍﺭﺯﻳﺎﺑﻲ ﺭﻭﺵﻫﺎﻱ ﻣﺒﺘﻨﻲ ﺑﺮ ﺳﻨﺎﺭﻳﻮ ﺩﺭ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ" ] [۲ﺟﻠﻴﻠﻲ ،ﺳﻌﻴﺪ ،ﺷﺎﻩﻣﺤﻤﺪﻱ ،ﻏﻼﻣﺮﺿﺎ ،ﮐﻤﻨﺪﻱ ،ﻋﻠﻲ" ،ﺍﺭﺯﻳﺎﺑﻲ ﺭﻭﺵﻫﺎﻱ ﺗﺤﻠﻴﻞ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ" ،ﺩﻭﻣﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﻲ ﻓﻨﺎﻭﺭﻱ ﺍﻃﻼﻋﺎﺕ ﻭ ﺩﺍﻧﺶ ،ﺗﻬﺮﺍﻥ، ﺩﺍﻧﺸﮕﺎﻩ ﺻﻨﻌﺘﻲ ﺍﻣﻴﺮ ﮐﺒﻴﺮ۱۳۸۴ ، [3] Channabasavaiah, K., et al., Migrating to a service-oriented ﺷﮑﻞ) :(۸ﻓﺮﺁﻳﻨﺪ ﻣﺪﻝ .PASA B&B -۱۵-۳ ﻣﻌﺮﻓﻲ ﺷﺪﻩ ﺩﺭ ﺍﻳﻦ ﻣﻘﺎﻟﻪ ﺭﺍ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﻣﻲﺩﻫﻴﻢ .ﺩﺭ ﺟـﺪﻭﻝ )(۲ ﺟﺎﻫﺎﻳﻲ ﮐﻪ ﻋﻼﻣـﺖ ) (-ﺑﮑـﺎﺭ ﺭﻓﺘـﻪ ﺍﺳـﺖ ﺑـﺪﻳﻦ ﻣﻌﻨـﻲ ﺍﺳـﺖ ﮐـﻪ ﺩﺭ ﻣﺴﺘﻨﺪﺍﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﺭﻭﺵ ﮔﺰﺍﺭﺷـﻲ ﺩﺭﺑـﺎﺭﻩ ﺁﻥ ﺧـﺼﻮﺻﻴﺖ ﺩﺍﺩﻩ ﻧـﺸﺪﻩ ﺍﺳﺖ ﻭ ﻳﺎ ﺑﺮﺍﻱ ﻧﻮﻳﺴﻨﺪﻩ ﻣﻘﺎﻟﻪ ﻗﺎﺑﻞ ﺩﺳﺘﺮﺱ ﻧﺒﻮﺩﻩ ﺍﺳﺖ .ﺑﻪ ﻧﻈـﺮ ﻧﻤـﻲ- ﺭﺳﺪ ﮐﻪ ﺍﻣﮑﺎﻥ ﺍﺳﺘﺎﻧﺪﺍﺭﺩﺳﺎﺯﻱ ﺩﻗﻴﻖ ﻣﺮﺍﺣﻞ ﺗﺤﻠﻴﻞ ﻣﻌﻤـﺎﺭﻱ ﻧـﺮﻡﺍﻓـﺰﺍﺭ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻭ ﺗﺤﻘﻴﻘﺎﺗﻲ ﻧﻈﻴﺮ ﺍﻳﻦ ﻣﻘﺎﻟﻪ ﺩﺭ ﻭﺍﻗﻊ ﺗﻼﺵ ﺩﺭ ﺟﻬـﺖ ﺳﺎﻣﺎﻧﺪﻫﻲ ﻣﺴﺎﻟﻪ ﺗﺤﻠﻴﻞ ﺩﺭ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻧﺮﻡﺍﻓـﺰﺍﺭﻱ ﺑـﻪ ﺷـﻤﺎﺭ ﻣﻲﺭﻭﺩ. architecture, Part 1, IBM official web site, 16 December 2003. ٢٠ [4] Bieber, G. , Carpenter J. , Introduction to Service-Oriented ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺳﺎﻝ ۱۹۹۹ﺑﺎ ﻫﺪﻑ ﺗﺨﻤﻴﻦ ﻫﺰﻳﻨﻪ ﻧﮕﻬـﺪﺍﺭﻱ ﺑـﺮﺍﻱ ﻳـﮏ ﺳﻴﺴﺘﻢ ﺑﺮﻣﺒﻨﺎﻱ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺁﻥ ﺳﻴﺴﺘﻢ ﺍﺭﺍﺋﻪ ﺷـﺪ] .[۱ﻋﻤﻠﻴـﺎﺕ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﺑﺮﺍﺳﺎﺱ ﺍﻳـﻦ ﺭﻭﺵ ﺩﺭ ﺷـﺶ ﻣﺮﺣﻠـﻪ ﺍﻧﺠـﺎﻡ ﻣـﻲﺷـﻮﺩ: )(۱ﮔﺮﻭﻫﺒﻨﺪﻱ ﮐﺎﺭﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻧﮕﻬـﺪﺍﺭﻱ؛ )(۲ﺗﻌﻴـﻴﻦ ﻳـﮏ ﻣﺠﻤﻮﻋـﻪ ﻣﺸﺨﺺ ﺍﺯ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺑﻪ ﺍﺯﺍﻱ ﻫﺮ ﻳﮏ ﺍﺯ ﮔﺮﻭﻫﻬﺎﻱ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺩﺭ ﻣﺮﺣﻠﻪ ﻗﺒﻞ؛ )(۳ﺗﺨﻤﻴﻦ ﻳﮏ ﻭﺯﻥ ﺑﻪ ﻫﺮ ﻳﮏ ﺍﺯ ﺳﻨﺎﺭﻳﻮﻫﺎ؛ )(۴ﺍﻋﻤـﺎﻝ ﺳـﻨﺎﺭﻳﻮﻫﺎ؛ )(۵ﻣﺤﺎﺳﺒﻪ ﻫﺰﻳﻨﻪ ﻧﮕﻬـﺪﺍﺭﻱ ﻣـﻮﺭﺩ ﺍﻧﺘﻈـﺎﺭ ،ﻫﺰﻳﻨـﻪ ﻧﮕﻬـﺪﺍﺭﻱ ﺳﻴـﺴﺘﻢ ﺑﺮﺍﺳﺎﺱ ﺭﺍﺑﻄﻪ ) (۱ﺑﺪﺳﺖ ﻣﻲﺁﻳﺪ. n )(۱ ) c m = å p( sci ).c ( sci ﺍﺣﺘﻤﺎﻝ ﺭﺧﺪﺍﺩ ﺳﻨﺎﺭﻳﻮﻱ i ﻫﺰﻳﻨﻪ ﺳﻨﺎﺭﻳﻮﻱ i ﻫﺰﻳﻨﻪ ﻧﮕﻬﺪﺍﺭﻱ ) p( sci i =0 ) c ( sci cm ﻣﻲﺗﻮﺍﻥ ﮔﻔﺖ ﮐﻪ ﺍﻳﻦ ﺭﻭﺵ ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ ﺳﻴـﺴﺘﻢ ﺭﺍ ﺑـﺎ ﺑﺮﺭﺳـﻲ ﺣﻮﺯﻩ ﺗﺎﺛﻴﺮ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺗﺤﻠﻴﻞ ﻣﻲﮐﻨﺪ. -۴ﻧﺘﻴﺠﻪ ﺩﺭ ﺍﻳﻦ ﻣﻘﺎﻟﻪ ﺑﻪ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﮑﻲ ﺍﺯ ﺟﺪﻳﺪﺗﺮﻳﻦ ﻣﺤﻮﺭﻫﺎﻱ ﺗﺤﻘﻴﻘﺎﺗﻲ ﺩﺭ ﺣﻮﺯﻩ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡﺍﻓﺰﺍﺭ ﭘﺮﺩﺍﺧﺘﻪ ﺷﺪﻩﺍﺳﺖ .ﺩﺭ ﺍﺑﺘﺪﺍ ﺍﻧـﻮﺍﻉ ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻣﻮﺟﻮﺩ ﻣﻌﺮﻓﻲ ﺷﺪﻩ ﻭ ﺳﭙﺲ ﺑﺎ ﺑﻴـﺎﻥ ﺟﺎﻳﮕـﺎﻩ ﻭ ﺩﻻﻳﻞ ﺗﺤﻠﻴﻞ ﻭ ﺍﺭﺯﻳﺎﺑﻲ ﺩﺭ ﺣﻮﺯﻩ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻫـﺎﻱ ﻧـﺮﻡﺍﻓـﺰﺍﺭﻱ ﺑـﻪ ﻣﻌﺮﻓﻲ ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻣﻮﺟﻮﺩ ﭘﺮﺩﺍﺧﺘﻪ ﺷﺪﻩ ﺍﺳﺖ. ﺟﺪﺍﻭﻝ ﺍﺭﺯﻳﺎﺑﻲ ﻣﺨﺘﻠﻔﻲ ﺩﺭ ﻣﻘﺎﻻﺕ ﻣﺘﻌﺪﺩ ﺟﻬﺖ ﻣﻘﺎﻳﺴﻪ ﺭﻭﺷـﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻣﻌﺮﻓـﻲ ﺷـﺪﻩ ﺍﺳـﺖ .ﺑﺮﺍﺳـﺎﺱ ﻳﮑـﻲ ﺍﺯ ﺍﻳـﻦ ﭼﻬﺎﺭﭼﻮﺏﻫﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ،ﺩﺭ ﭘﻴﻮﺳﺖ ﻣﻘﺎﻟﻪ )ﺟﺪﻭﻝ ) ((۲ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳـﺎﺑﻲ Programming , Motorola ISD , 2003. Lassing, N., Ph.D. Thesis, Architecture-Level Modifiability Analysis, Free University Amesterdam, February 2002. Bengtsson, P. Architecture-Level Modifiability Analysis, Ph.D. Thesis, Blekinge Institute of Technology, Sweden 2002. Williams, L.G.; and C.U. Smith,; "PASA: A Method for the Performance Assessment of Software Architecture", Proc. of the 3rd Workshop on Software Performance. Rome, Italy. 2002. Williams, L.G.; and C.U. Smith,; "Performance Evaluation of Software Architectures", proc. of the Workshop on Software and Performance. Santa Fe, USA, 1998. Smith, C.U.; "Performance Engineering for Software Architectures", Proc. of the 21th Computer and Software Applications. Washington, DC, USA. 1997. Ali Babar, M.; and Gorton, I.; "Comparison of Scenario-Based Software Architecture Evaluation Methods", First Asia-Pacific Workshop on Software Architecture and Component Technology, Appears in proceedings of the 11th Asia-Pacific Software Engineering Conference, Busan, Korea, 2004. Ali-Babar, M.; et al.; "A Framework for Classifying and Comparing Software Architecture Evaluation Methods", Proc. of the Australian Software Engineering Conference, Melbourne, Australia. 2004. Dobrica, L.; and E. Niemela,; "A Survey on Software Architecture Analysis Methods", IEEE Transactions on Software Engineering, 2002. Ionita, M.T.; Hammer, D.K.; and Obbink, H.; “Scenario-Based Software Architecture Evaluation Methods: An Overview”, Proc. Int. Conf. on SW Engineering, Orlando (FA), May 2002. Clements, P.; Kazman, R.; and Klein, M.; "Evaluating Software Architectures: Methods and Case Studies", Addison-Wesley, 2002. Duenas, J.C. Oliveira, W.L. de and Puente, J.A. de la "A Software Architecture Evaluation Model", Proc. Second Int'l ESPRIT ARES Workshop, pp. 148-157, Feb. 1998. Bengtsson, P.O. and Bosch, J. "Architecture Level Prediction of Software Maintenance", Proc. Third European Conf. Software Maintenance and Reeng ,.pp. 139-147, Mar. 1999. ][5 ][6 ][7 ][8 ][9 ][10 ][11 ][12 ][13 ][14 ][15 ][16 [17] Arnold, R.S. and Bohner, S.A. "Software Change Impact Analysis . Los Alamitos ", Calif.: IEEE Computer Society , 1996. [18] Tekinerdoğan B. "ASAAM Aspectual Software Architecture 2164 "Analysis Method ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ [19] Lung, C. Bot, S. Kalaichelvan, K. and Kazman R. "An Approach [26] ISO/IEC91ÐInt'l Organization of Standardisation and Int'l to Software Architecture Analysis for Evolution and Reusability", Proc. CASCON '97 ,Nov. 1997. Electrotechnical Commission, Information TechnologyÐSoftware Product Evaluation of Quality Characteristics and Guidelines for Their Use, ISO/IEC 9216: 1991(E), 1991. Kazman, R. , Abowd, G. , Bass, L. and Clements, P. , "ScenarioBased Analysis of Software Architecture", IEEE software, pp. 4755, Nov. 1996. N. Lassing, D. Rijsenbrij, and H. van Vliet "On Software Architecture Analysis of Flexibility, Complexity of Changes: Size Isn't Everything", Proc. Second Nordic Software Architecture Workshop )NOSA '99 ,(pp. 1103-1581, 1999. [20] Alonso, G. "Myths Around Web Services", IEEE Data Engineering Bulletin, Vol. 25 No. 4, IEEE, 2002. [21] Sang-woo H. "Three-Tier Architecture for Sentinel Applications and Tools", Separating Presentation from Functionality University of Florid, 1997. Barroca, L., Hall, J., Hall, P.A. "Software Architecture: Advances and Application", Springer-Verlag, 1999. Bass, L. Clements, P. and Kazman, R. "Software Architecture in Practice. Reading", Mass.: Addison-Wesley, 1998. Li, W. and Henry, S. "Object-Oriented Metrics that Predict Maintainability", J. Systems and Software, vol. 23, no. 2, pp. 111122, 1993. IEEE Standard 1061-1992, Standard for Software Quality Metrics Methodology, New York: Institute of Electrical and Electronics Engineers, 1992. ][22 ][23 ][24 ][27 ][28 [29] Bengtsson, P.O. and Bosch, J. "Scenario-Based Architecture Reengineering", Proc. Fifth Int'l Conf. Software Reuse (ICSR 51998). ][25 ﭘﻴﻮﺳﺖ ﺟﺪﻭﻝ ) :(۲ﻣﻘﺎﻳﺴﻪ ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ SBAR ALMA SAAMER ARID ATAM SAAM ﺗﻌﺮﻳﻒ SA ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ SAAMCS ﻫﺪﻑ ﻭﻳﮋﻩ ﭘﻴﺶ ﺑﻴﻨﻲ ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ ﻭ ﺗﺤﻠﻴﻞ ﺗﺨﻤﻴﻦ ﭘﺘﺎﻧﺴﻴﻞ SAﺩﺭ ﺩﺳﺘﻴﺎﺑﻲ ﺑﻪ ﺻﻔﺎﺕ ﭘﻴﺶ ﺑﻴﻨﻲ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ﺭﻳﺴﮏ ﮐﻴﻔﻲ ﺻﻔﺎﺕ ﮐﻴﻔﻲ ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ، ﺍﺭﺯﻳﺎﺑﻲ SAﺑﺮﺍﻱ ﺗﮑﺎﻣﻞ ﻭ ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﻣﺘﻨﻮﻉ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ﺩﺭ ﮔﺎﻡ ﻣﻬﻨﺪﺳﻲ ﻣﺠﺪﺩ ﺩﺭ ﻃﻮﻝ ﻓﺎﺯ ﻃﺮﺍﺣﻲ ﺣﻮﺯﻩ ﮐﺎﺭﺑﺮﺩ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺳﻨﺠﻴﺪﻥ ﺳﻴﺴﺘﻢ ﻣﻮﻓﻖ ﺩﺭ ﺳﻴﺴﺘﻤﻬﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺗﺠﺎﺭﻱ ﻣﺰﻳﺖ ﺭﻭﺵ ﺑﺮﺭﺳﻲ ﮐﺮﺩﻥ SA ﺩﺭﻭﻥ ﻣﻌﻤﺎﺭﻱ ﺧﺮﺩ ﻭ ﻫﻤﮑﺎﺭﻱ ﺩﺭ ﻃﺮﺍﺣﻲ ﻣﻌﻤﺎﺭﻱ ﻭ ﺍﺭﺯﻳﺎﺑﻲ ﮐﻼﻥ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ ﺩﺭﮔﻴﺮﻱ ﺫﻳﻨﻔﻌﺎﻥ ﺍﺻﻠﻲ ﻃﺮﺍﺡ ﻣﻌﻤﺎﺭﻱ ﻣﺮﺣﻠﻪ ﺍﻋﻤﺎﻝ ﺭﻭﺵ ﺍﻓﺮﺍﺩ ﺩﺭﮔﻴﺮ ﺩﺭ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻴﺰﺍﻥ ﺣﻤﺎﻳﺖ ﺭﻭﺵ ﺍﺯ ﻣﺮﺍﺣﻞ ﻗﺎﺑﻠﻴﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻗﺒﻞ ﺍﺯ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻃﺮﺡ ﻣﻌﻤﺎﺭﻱ ﮔﺎﻣﻬﺎ ﺑﻴﺎﻥ ﺷﺪﻩ ﻭﻟﻲ ﺭﺍﻫﻨﻤﺎﻳﻲ ﻣﻨﺎﺳﺐ ﻧﻴﺴﺖ ﻣﻮﺿﻮﻋﻬﺎﻱ ﺗﮑﻨﻴﮑﻲ -ﺷﻨﺎﺧﺖ ﺿﻤﻨﻲ ﻣﺴﺎﺋﻞ ﻣﺎﻟﮑﻴﺖ ﺍﺟﺘﻤﺎﻋﻲ ﺟﺎﺳﺎﺯﻱ ﺷﺪﻩ ﺩﺭ ﺗﻮﺻﻴﻒ ﺭﻭﺵ ﺗﻌﻴﻴﻦ ﺭﻳﺴﮑﻬﺎﻱ ، SAﺗﺨﻤﻴﻦ ﺗﻼﺵ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺑﺮﺍﻱ ﻫﻤﺴﺎﻥ ﮐﺮﺩﻥ ﺗﻐﻴﻴﺮﺍﺕ ،ﻳﺎ ﺍﻧﺘﺨﺎﺏ ﻳﮏ SAﺑﻬﻴﻨﻪ ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﻣﺘﻨﻮﻉ ﺩﺭ ﺟﻬﺖ ﻣﻨﺎﺳﺐ ﻭ ﺗﮑﺎﻣﻞ ﺑﻮﺩﻥ ﻃﺮﺡ ﻣﻌﻤﺎﺭﻱ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺩﺭ ﻃﻮﻝ ﻣﺪﺕ ﻃﺮﺍﺣﻲ ﻓﺮﺁﻳﻨﺪﻱ ﺗﮑﺮﺍﺭﻱ ﻗﺒﻞ ﺍﺯ ﺷﺪﻩ ﺍﺟﺰﺍﺀ ﻣﻌﻤﺎﺭﻱ ﺍﺭﺍﺋﻪ SA ﺳﻴﺴﺘﻤﻬﺎﻱ ﺍﺭﺗﺒﺎﻁ ﺍﺯ ﺭﺍﻩ ﺩﻭﺭ ﻃﺮﺍﺣﻲ ﺍﺟﺰﺍﺀ ﻋﺎﻡ ﺍﺭﺍﺋﻪ ﻳﮏ ﭼﻬﺎﺭﭼﻮﺏ ﺩﺭ ﻓﻌﺎﻟﻴﺘﻬﺎﻱ ﻣﺨﺘﻠﻒ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ﺩﺭ ﺣﺎﻝ ﺍﺻﻼﺡ ﺑﺮﺭﺳﻲ ﺻﺤﺖ ﻭ ﺳﻘﻢ ﻃﺮﺍﺣﻲ ﺗﺤﻠﻴﻞ ﻧﻘﺎﻁ ﺣﺴﺎﺱ ﻭ ﻧﻘﺎﻁ ﺗﻌﺎﺩﻟﻲ ﮐﺸﻒ ﺻﻼﺣﻴﺖ ﺳﺮﻭﻳﺴﻬﺎﻱ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺑﻮﺳﻴﻠﻪ ﻃﺮﺡ ﻭ ﮐﻴﻔﻴﺖ ﻭ ﺗﻤﺎﻣﻴﺖ ﻣﺴﺘﻨﺪﺍﺕ ﻣﺘﻨﻮﻉ ﺍﺳﺎﺳﺎ ﻗﺎﺑﻠﻴﺖ ﺗﻐﻴﻴﺮ ﺑﻌﺪ ﺍﺯ ﺍﺭﺍﺋﻪ ﻣﻌﻤﺎﺭﻱ ﻭ ﻗﺒﻞ ﺍﺯ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻋﺎﻡ ﭼﻨﺪﻳﻦ ﻣﺰﻳﺖ ﺗﮑﻨﻴﮑﻲ ﻃﺮﺍﺡ ،ﻣﺪﻳﺮ، ﮐﺎﺭﺑﺮﻧﻬﺎﻳﻲ ﻃﺮﺍﺡ ،ﻣﻌﻤﺎﺭ ﻭ ﻫﺮ ﻓﺮﺩﻱ ﮐﻪ ﻧﻔﻌﻲ ﺩﺍﺭﺩ ﻫﻤﻪ ﺍﻓﺮﺍﺩ ﺫﻳﻨﻔﻊ ﭼﻬﺎﺭﭼﻮﺑﻲ ﺟﻬﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺷﺎﻳﺴﺘﻪ ﺍﺯ ﺑﻄﻮﺭ ﺟﺎﻣﻊ ﭘﻮﺷﺶ ﺩﺍﺩﻩ ﺣﻤﺎﻳﺖ ﺍﺯ ﺍﺭﺯﻳﺎﺑﻲ ﻓﺮﺁﻳﻨﺪ ﺷﺪﻩ ﻣﻮﺭﺩ ﺭﺳﻴﺪﮔﻲ ﻗﺮﺍﺭ ﻧﮕﺮﻓﺘﻪ - ﺧﻴﻠﻲ ﮐﻢ ﺑﺮﺭﺳﻲ ﺷﺪﻩ ﻣﻨﺎﺑﻊ ﻣﻮﺭﺩ ﻧﻴﺎﺯ - - - - ﻣﺮﺍﺣﻞ ﺭﻭﺵ ۳ﻣﺮﺣﻠﻪ ،ﻧﻴﺎﺯﻣﻨﺪ ۲ ﺍﺟﺮﺍﻱ ﻣﻮﺍﺯﻱ ﺍﻧﺠﺎﻡ ۳ﻣﺮﺣﻠﻪ ﺑﻄﻮﺭ ﺗﮑﺮﺍﺭﻱ ۵ﻣﺮﺣﻠﻪ ﺑﻄﻮﺭ ﭘﺸﺖ ﺳﺮ ﻫﻢ ۴ﻣﺮﺣﻠﻪ ﺑﻄﻮﺭ ﺗﮑﺮﺍﺭﻱ ﺗﻮﺻﻴﻒ SA ﻃﺮﺣﻬﺎﻱ ﻣﻌﻤﺎﺭﻱ ﺧﺮﺩ ﻭ ﮐﻼﻥ ﻳﮏ ﻣﻌﻤﺎﺭﻱ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺷﺪﻩ ﻣﺴﺘﻘﻞ ﺍﺯ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﻭ ﮔﺮﺍﻣﺮ ﺍﺳﺘﻔﺎﺩﻩ ﺷﺪﻩ ﺍﻳﺴﺘﺎ ،ﻧﻘﺸﻪ ، ﺩﻳﻨﺎﻣﻴﮏ ﺗﮑﻨﻴﮏ ﺍﺭﺯﻳﺎﺑﻲ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ )ﺳﻨﺎﺭﻳﻮﻫﺎﻱ ﭘﻴﭽﻴﺪﻩ( ﭼﻨﺪﻳﻦ ﺗﮑﻨﻴﮏ )ﺳﻨﺎﺭﻳﻮ ،ﻣﺪﻟﺴﺎﺯﻱ ﺭﻳﺎﺿﻲ ، ﺍﻳﻦ ﻣﺴﺎﺋﻞ ﺩﺭ ADR ﭘﺸﺘﻴﺒﺎﻧﻲ ﺷﺪﻩ ﺗﺤﻠﻴﻞ ﺭﻳﺴﮏ ﺑﻘﺪﺭ ﮐﺎﻓﻲ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﮐﺸﻒ ﺁﺳﺎﻥ ﻣﺸﮑﻼﺕ، ﺍﺻﻼﺡ ﻣﺴﺘﻨﺪﺍﺕ ، SAﻭ ﺍﻓﺰﺍﻳﺶ ﻓﻬﻢ ﻣﺎ ﺍﺯ ﻣﺴﺎﺋﻞ ﻣﺮﺑﻮﻁ ﺑﻪ SA ﻫﻤﻪ ﺍﻓﺮﺍﺩ ﺫﻳﻨﻔﻊ ﻣﺮﺍﺣﻞ ﺗﻮﺻﻴﻒ ﺷﺪﻩ ﭼﻨﻴﻦ ﻣﺴﺎﺋﻠﻲ ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﺫﮐﺮ ﺷﺪﻩ ﻋﻼﻭﻩ ﺑﺮ ﺗﻤﻬﻴﺪﺍﺕ ﺷﺮﻭﻉ ﻭ ﻋﻼﻭﻩ ﺑﺮ ﺗﻤﻬﻴﺪﺍﺕ ﺷﺮﻭﻉ ﻭ ﻋﻼﻭﻩ ﺑﺮ ﺗﻤﻬﻴﺪﺍﺕ ﺷﺮﻭﻉ ﻭ ﭘﺎﻳﺎﻥ ۳ ،ﺭﻭﺯ ﻭ ۴ﻓﺮﺩ ﭘﺎﻳﺎﻥ ۲ ،ﺭﻭﺯ ﻭ ۳ﻓﺮﺩ ﺩﺭ ﭘﺎﻳﺎﻥ ۲ ،ﺭﻭﺯ ﻭ ۲ﻓﺮﺩ ﺩﺭ ﺩﺭ ﺗﻴﻢ ﺍﺭﺯﻳﺎﺑﻲ ﻭ ﺫﻳﻨﻔﻌﺎﻥ ﺗﻴﻢ ﺍﺭﺯﻳﺎﺑﻲ ﻭ ﺫﻳﻨﻔﻌﺎﻥ ﺗﻴﻢ ﺍﺭﺯﻳﺎﺑﻲ ﻭ ﺫﻳﻨﻔﻌﺎﻥ ۹ﻣﺮﺣﻠﻪ ﺩﺭ ۲ﻓﺎﺯ ۹ﻣﺮﺣﻠﻪ ﺩﺭ ۲ﻓﺎﺯ ﻃﺮﺡ ﺍﻭﻟﻴﻪ ﺑﺎ ﺟﺰﺋﻴﺎﺕ ﻣﻨﺎﺳﺐ ﺑﻪ ﻫﻤﺮﺍﻩ ﻓﺮﺁﻳﻨﺪ ،ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ، ﮐﺎﺭﺑﺮﺩﻫﺎview ،ﻫﺎﻱ viewﻫﺎﻱ ﺷﺎﻳﺴﺘﻪ ﻓﻴﺰﻳﮑﻲ ﻭ ﻣﺎﺟﻮﻟﻪ ﻭﺍﺑﺴﺘﻪ ﺑﻪ ﻫﺪﻑ ﺗﺤﻠﻴﻞ ﻣﺪﻝ ﮐﺮﺩﻥ ﺍﻃﻼﻋﺎﺕ & ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ ﺗﺮﮐﻴﺐ ﺗﮑﻨﻴﮏ ﺑﺮ ﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ & ADR ﺗﮑﻨﻴﮏ ﺗﺮﮐﻴﺒﻲ: & questioning measuring ﺣﻤﺎﻳﺖ ﺍﺑﺰﺍﺭ - - - - - - ﺳﻄﺢ ﺭﺷﺪ ﺭﻭﺵ Dormant or merged Dormant or merged Refinement/Development Dormant Development Refinement Refinement/Dormant ﺭﻭﻱ ﺳﻴﺴﺘﻤﻬﺎﻱ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺷﺪﻩ ﺭﻭﻱ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺷﺪﻩ ﺩﺭ ﺩﺍﻣﻨﻪ ﻫﻨﻮﺯ ﺑﺎ ﻭﺳﻌﺖ ﺯﻳﺎﺩ ﺑﻄﻮﺭ ﺍﺩﺍﻣﻪ ﺩﺍﺭ ﺩﺭ ﺣﺎﻝ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺷﺪﻩ ﺭﻭﻱ ﺍﻃﻼﻋﺎﺕ ﺗﺠﺎﺭﻱ ﻳﮏ ﺳﻴﺴﺘﻢ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﻧﺸﺪﻩ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺍﺳﺖ ﺩﺍﻣﻨﻪ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺭﻭﺵ ﺷﺒﻴﻪ ﺳﺎﺯﻱ ،ﺍﺳﺘﺪﻻﻝ( ﻳﮏ ﺳﻴﺴﺘﻢ ﺳﻮﺋﻴﭽﻴﻨﮓ ﻭ ﺍﺭﺗﺒﺎﻁ ﺍﺯ ﺭﺍﻩ ﺩﻭﺭ 2165 ۶ﻣﺮﺣﻠﻪ Viewﻫﺎﻱ ﻣﻨﻄﻘﻲ ﻭ ﻣﺎﺟﻮﻟﻪ ﺑﺮﻣﺒﻨﺎﻱ ﺳﻨﺎﺭﻳﻮ ﺣﻤﺎﻳﺖ ﺟﺰﺋﻲ )(SAAMTOOL ﺩﻭﺍﺯﺩﻫﻤﻴﻦ ﮐﻨﻔﺮﺍﻧﺲ ﺑﻴﻦﺍﻟﻤﻠﻠﯽ ﺍﻧﺠﻤﻦ ﮐﺎﻣﭙﻴﻮﺗﺮ ﺍﻳﺮﺍﻥ ﺩﺍﻧﺸﮕﺎﻩ ﺷﻬﻴﺪ ﺑﻬﺸﺘﯽ ،ﺩﺍﻧﺸﮑﺪﻩ ﻣﻬﻨﺪﺳﯽ ﺑﺮﻕ ﻭ ﮐﺎﻣﭙﻴﻮﺗﺮ ،ﺗﻬﺮﺍﻥ ،ﺍﻳﺮﺍﻥ ۱ ،ﺗﺎ ۳ﺍﺳﻔﻨﺪ ١٣٨٥ ﺍﺩﺍﻣﻪ ﺟﺪﻭﻝ ) :(۲ﻣﻘﺎﻳﺴﻪ ﺭﻭﺷﻬﺎﻱ ﺍﺭﺯﻳﺎﺑﻲ ﺗﻌﺮﻳﻒ SA PASA ASAAM ISAAMCR CBAM ESAAMI ALPSM SAEM FAAM ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ - ﺑﻪ ﻋﻬﺪﻩ ﮐﺎﺭﺑﺮ - - ﺍﺭﺍﺋﻪ ﻧﺸﺪﻩ ﻣﺮﺗﺒﻂ ﮐﺮﺩﻥ ﺍﺭﺯﻳﺎﺑﻲ ﺗﻮﺍﻧﺎﻳﻲ -SA ﺗﻌﺮﻳﻒ aspectﻫﺎﻱ ﺗﺤﻠﻴﻞ ﺍﻧﻌﻄﺎﻑﭘﺬﻳﺮﻱ ﺩﺭ ﻓﺮﺁﻳﻨﺪ ﻣﻌﻤﺎﺭﯼ ﻭ ﺑﻬﺒﻮﺩ ﺑﺨﺸﻴﺪﻥ ﺑﻪ ﺩﺭﺟﻪ ﻫﺎﻱ ﭘﻴﺸﻨﻬﺎﺩ ﺷﺪﻩ ﺩﺭ ﻣﻌﻤﺎﺭﻱ ﻭ ﺷﻔﺎﻑ ﺳﺎﺯﻱ ﺩﺭ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﻋﻠﻢ ﺍﻗﺘﺼﺎﺩ ﺩﺭ ﺟﻬﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺭﺍﺑﻄﻪ ﺑﺎ ﺍﻫﺪﺍﻑ ﮐﺎﺭﺍﻳﻲ ﭼﺮﺧﻪ ﺗﻮﺳﻌﻪ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺗﻮﺳﻌﻪ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ﻫﺪﻑ ﻭﻳﮋﻩ ﺗﺤﻠﻴﻞ ﻗﺎﺑﻠﻴﺖ ﺍﺻﻼﺡ ﺍﺭﺍﺋﻪ ﻣﺒﺘﺎﻳﻲ ﺟﻬﺖ ﺍﺭﺯﻳﺎﺑﻲ ﮐﻴﻔﻴﺖ ﻭ ﭘﻴﺶ ﺑﻴﻨﻲ ﮐﻴﻔﻴﺖ ﺳﻴﺴﺘﻢ ﻧﻬﺎﻳﻲ ﺟﻬﺖ ﺍﺭﺯﻳﺎﺑﻲ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻤﻬﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺎﺳﺎ ﮐﺎﺭﺍﻳﻲ )ﺑﻌﻼﻭﻩ ﺧﺼﻮﺻﻴﺎﺕ ﮐﻴﻔﻲ ﺩﻳﮕﺮ ﻣﺎﻧﻨﺪ ﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ( ﺻﻔﺎﺕ ﮐﻴﻔﻲ ﺩﺭ ﭼﺮﺧﻪ ﺗﻮﺳﻌﻪ ،ﻗﺒﻞ ﺍﺯ ﺗﻮﺳﻌﻪ ﻳﺎ ﺩﺭ ﺑﺮﻭﺯ ﻣﺮﺣﻠﻪ ﺍﻋﻤﺎﻝ ﺭﻭﺵ ﻣﺘﻨﻮﻉ )ﻣﺎﻧﻨﺪ (SAAM ﻣﺸﺎﺑﻪ SAAM ﺭﺳﺎﻧﻲ ﺳﻴﺴﺘﻢ ﻗﺪﻳﻤﻲ ﺍﻧﻌﻄﺎﻑﭘﺬﻳﺮﻱ ﻗﺎﺑﻠﻴﺖ ﻫﺰﻳﻨﻪ ،ﻓﺎﻳﺪﻩ ، ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺯﻣﺎﻧﺒﻨﺪﻱ ﻣﺸﺎﺑﻪ ﺑﺎ SAAMﺭﻭﻱ ﻧﺴﺨﻪ ﻧﻬﺎﻳﻲ SA ﺍﺩﺍﻣﻪ ﺍﺭﺯﻳﺎﺑﻲ ﺍﺯ ﻣﺤﻞ ﺗﺮﮎ ﻗﺎﺑﻠﻴﺖ ﺗﻐﻴﻴﺮ ﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ ﻳﮏ ﻣﺪﻝ ﮐﻴﻔﻲ ﺭﻭﻱ ﻧﺴﺨﻪ ﻧﻬﺎﻳﻲ SA ﺩﺭ ﻃﻮﻝ ﻃﺮﺍﺣﻲ ﺟﻬﺖ ﭘﻴﺶﺑﻴﻨﻲ ﻗﺎﺑﻠﻴﺖ ﺭﻭﻱ ﻧﺴﺨﻪ ﻧﻬﺎﻳﻲ SA ﻧﮕﻬﺪﺍﺭﻱ ﻧﺮﻡﺍﻓﺰﺍﺭ ATAM ،Embedded ﺣﻮﺯﻩ ﮐﺎﺭﺑﺮﺩ ﺳﻴﺴﺘﻤﻬﺎﻱ Real - - - - ﻋﺎﻡ ﮔﺴﺘﺮﺵ ﺿﺮﻭﺭﺕ ﻭﺟﻮﺩ ﺗﻮﺻﻴﻒ ﻣﻌﻤﺎﺭﻱ ﻳﺎ ﺗﻌﻤﻴﺮ ﺷﺪﻥ ﺁﻥ ﻗﺒﻞ ﺍﻋﻤﺎﻝ FAAM ﺳﻴﺴﺘﻤﻬﺎﻱ ﺑﺮﻣﺒﻨﺎﻱ ،Webﺳﻴﺴﺘﻤﻬﺎﻱ ﻳﮏ ﺳﻴﺴﺘﻢ ﺩﻳﺎﻟﻴﺰ ﺧﻮﻥ ﺗﻌﺎﻣﻞ ﻭ ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻧﺸﺪﻩ ﺧﺎﻧﻮﺍﺩﻩ ﺳﻴﺴﺘﻤﻬﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ،timeﻭ ﺩﺭ ﺩﺍﻣﻨﻪ financial ﺩﺍﺭﺍﻱ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﺑﺮﺍﻱ ﻣﺰﻳﺖ ﺭﻭﺵ ﻓﺮﻣﻮﻟﻪ ﮐﺮﺩﻥ ﻣﺮﺍﺣﻞ ﺭﻭﺵ ﺗﺎﮐﻴﺪ ﺑﻴﺸﺘﺮ ﺭﻭﻱ ﺗﻮﺳﻌﻪ ﮔﺮﺍﻥ /ﻧﻴﺰ ﺍﻓﺮﺍﺩ ﺩﺭﮔﻴﺮ ﺩﺭ ﺍﺭﺯﻳﺎﺑﻲ ﺍﻣﮑﺎﻥ ﺩﺭﮔﻴﺮﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﮐﻨﻨﺪﮔﺎﻥ ﻣﻴﺰﺍﻥ ﺣﻤﺎﻳﺖ ﺭﻭﺵ ﮐﻢ ﺍﺯ ﻣﺮﺍﺣﻞ ﻣﻮﺿﻮﻋﻬﺎﻱ ﺗﮑﻨﻴﮑﻲ- ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﺍﺷﺎﺭﻩ ﺍﺟﺘﻤﺎﻋﻲ ﻧﺸﺪﻩ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺳﻴﺴﺘﻤﺎﺗﻴﮏ ﻣﺪﻳﺮﻳﺖ aspectﻫﺎﻱ ﻣﻌﻤﺎﺭﻱ ﺑﺎ ﻳﮏ ﺭﻭﺵ ﻓﺮﺁﻳﻨﺪ ﺍﺭﺯﻳﺎﺑﻲ ﮐﺎﻣﻼ ﺍﺭﺍﺋﻪ ﺍﻧﺪﺍﺯﻩﮔﻴﺮﻱ - ﭘﻴﺸﻨﻬﺎﺩ ﺑﺴﺘﻪﻫﺎﻱ ﺍﻟﮕﻮﻱ ﺗﺤﻠﻴﻞ - ﺿﻤﻨﻲ ﻓﺮﻣﻮﻟﻪ ﻭ ﺑﺮﺭﺳﻲ SAﺍﺯ ﺩﻭ ﺑﮑﺎﺭﮔﻴﺮﯼ ﺭﻭﺵ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺗﻴﻢ ﺩﻳﺪﮔﺎﻩ )ﮐﺎﺭﺑﺮ ﻭ ﺗﻮﺳﻌﻪ ﮔﺮ( ﻣﺸﺎﺑﻪ SAAM ﻫﻤﻪ ﺍﻓﺮﺍﺩ ﺫﻳﻨﻔﻊ ﻣﺸﺎﺑﻪ SAAM ﮐﻢ ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﺍﺷﺎﺭﻩ ﻧﺸﺪﻩ ﻣﺸﺎﺑﻪ SAAM ﻣﻨﺎﺑﻊ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻣﺸﺨﺺ ﻧﺸﺪﻩ ﻣﺸﺨﺺ ﻧﺸﺪﻩ ﻣﺸﺨﺺ ﻧﺸﺪﻩ ﻣﺮﺍﺣﻞ ﺭﻭﺵ ۱۰ﻣﺮﺣﻠﻪ ۵ﻣﺮﺣﻠﻪ ۶ﻣﺮﺣﻠﻪ ﺗﻮﺻﻴﻒ SA ﭼﻨﺪﻳﻦ ﺩﻳﺪﮔﺎﻩ ﻣﺸﺎﺑﻪ SAAM ﺍﻟﮕﻮﻫﺎﻱ ﺗﺤﻠﻴﻞ ﻣﻌﻤﺎﺭﻱ ﺳﻪ ﺩﺳﺘﻪ ﺍﺯ ﺫﻳﻨﻔﻌﺎﻥ ﻫﻤﻪ ﺍﻓﺮﺍﺩ ﺫﻳﻨﻔﻊ ﻃﺮﺍﺡ ﻣﻌﻤﺎﺭﻱ ﻣﻌﻘﻮﻝ ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﺍﺷﺎﺭﻩ ﻧﺸﺪﻩ ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﺍﺷﺎﺭﻩ ﻧﺸﺪﻩ - ﺩﺭ ﮐﻤﺘﺮ ﺍﺯ ۴ﺭﻭﺯ - - ﺳﻪ ﺩﺳﺘﻪ ﺍﺯ ﺫﻳﻨﻔﻌﺎﻥ ﺑﻄﻮﺭ ﻭﺍﺿﺢ ﺍﺷﺎﺭﻩ ﻧﺸﺪﻩ ﺗﻮﺻﻴﻒ ﺑﺴﻴﺎﺭ ﺟﺰﺋﻲ - - ﻣﺸﺨﺺ ﻧﺸﺪﻩ ﻣﺸﺨﺺ ﻧﺸﺪﻩ ﻣﺸﺨﺺ ﻧﺸﺪﻩ ۳ﺭﻭﺯ ﮐﺎﺭﻱ - ۶ﻣﺮﺣﻠﻪ ﺗﻘﺴﻴﻢ ﺑﻪ ﻓﺮﺁﻳﻨﺪ ﺩﺍﺧﻠﻲ ﻭ ﺧﺎﺭﺟﻲ ۶ﻣﺮﺣﻠﻪ ﻣﺸﺎﺑﻪ SAAM - ﺩﻳﺪﮔﺎﻩ ﮐﺎﺭﺑﺮ ﻭ ﺩﻳﺪﮔﺎﻩ ﺗﻮﺳﻌﻪ ﮔﺮ ﺗﺎﮐﻴﻴﺪ ﺭﻭﻱ ﺩﻳﺪ ﻣﻨﻄﻘﻲ ﺗﮑﻨﻴﮏ ﺍﺭﺯﻳﺎﺑﻲ ﺗﺮﮐﻴﺒﻲ ﺍﺯ ﺗﮑﻨﻴﮑﻬﺎﻱ ﮐﻤﻲ ﻭ ﮐﻴﻔﻲ ﺳﻨﺎﺭﻳﻮ ﺳﻨﺎﺭﻳﻮ ﺳﻨﺎﺭﻳﻮ ﻭ ﻣﺪﻝ ﺻﻔﺖ ﺳﻨﺎﺭﻳﻮ ﺳﻨﺎﺭﻳﻮ GSMﻭ ﺳﻨﺠﺶ ﺳﻨﺎﺭﻳﻮ ﻭ ﻣﻌﻴﺎﺭ ﺣﻤﺎﻳﺖ ﺍﺑﺰﺍﺭ - - - - - - - - ﺳﻄﺢ ﺭﺷﺪ ﺭﻭﺵ Development Refinement Dormant or merged - Development - - - ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺭﻭﺵ ﺑﺎ ﻣﻮﺍﺭﺩ ﻣﺨﺘﻠﻒ - ﮔﺰﺍﺭﺵ ﻣﻨﺘﺸﺮ ﻧﺸﺪﻩ - + ﺳﻴﺴﺘﻢ ﺩﻳﺎﻟﻴﺰ ﺧﻮﻥ - - ﮐﺎﺭﻱ ۶ﻣﺮﺣﻠﻪ ﺩﺭ ۲ﻓﺎﺯ ﺷﺮﻭﻉ ﺍﺯ ﻣﺤﻞ ﺍﺗﻤﺎﻡ ATAM ﺯﻳﺮﻧﻮﻳﺲﻫﺎ 9 Active Reviews for Intermediate Design Cost-Benefit Analysis Method 11 A Software Architecture Evaluation Model 12 The Aspectual Software Architecture Analysis Method 13 Extending SAAM by Integration in the Domain 14 Scenario-Based Architecture Reengineering 15 Experience-based reasoning 16 Architecture Level Prediction of Software Maintenance 17 Synthesis scenarios 18 Architecture Level Modifiability Analysis 19 Performance Assessment of Software Architecture 20 Bengtsson & Bosch 10 Software Architecture Service-Oriented Computing Family-Architecture Assessment Method Scenario-Based Architecture Analysis Method Conflict The Architecture Trade-off Analysis Method Software Architecture Analysis for Evolution and Reusability SAAM Founded on Complex Scenario 1 2 3 4 5 6 7 8 2166
© Copyright 2025 Paperzz