‫ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪1‬‬

‫‪Softw are Engineering-I‬‬

‫ﻣﻨﺒﻊ ‪ :‬ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫ﻣﻮﻟﻒ‪ :‬ﺳﺎﻣﺮﻭﻳﻞ‬
‫ﻣﺪﺭﺱ ‪ :‬ﺩﻛﺘﺮ ﺭﺿﺎ ﻗﺎﺋﻤﻲ‬
 ‫ﺑﺨﺶ ﺍﻭﻝ‬

‫ﻣﻘﺪﻣﻪ ﺍﻱ ﺑﺮ ﺁﻧﺎﻟﻴﺰ ﻭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‬

 ‫ﻓﺼﻞ‪1‬‬

‫ﺳﻴﺴﺘﻢ ﻭ ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢ ﻫﺎ‬

 ‫ﺳﻴﺴﺘﻢ ﭼﻴﺴﺖ ؟‬
‫ﺳﻴﺴﺘﻢ ﻋﺒﺎﺭﺗﺴﺖ ﺍﺯ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻗﻄﻌﺎﺕ‪ ،‬ﻋﻨﺎﺻﺮ‪ ،‬ﻓﺮﺁﻳﻨﺪﻫﺎ‪ ،‬ﺍﺟﺰﺍء‪،‬‬
‫ﻭﻇﺎﻳﻒ‪ ،‬ﻭ ‪ ...‬ﻛﻪ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﺩﺭﺗﻌﺎﻣﻞ ﺑﺎﺷﻨﺪ ﻭﻫﺪﻑ ﺧﺎﺹ ﻭ ﻣﺸﺘﺮﻛﻲ ﺭﺍ‬
‫`ﺩﻧﺒﺎﻝ ﻛﻨﻨﺪ‪.‬‬
‫ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺳﻴﺴﺘﻢ ﺑﺎ ﻣﺠﻤﻮﻋﻪ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ‪.‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺑﺎﺯ ﻭ ﺑﺴﺘﻪ ‪ :‬ﺩﺭﻳﺎﻓﺖ ﺍﻃﻼﻋﺎﺕ ﺍﺯﺑﻴﺮﻭﻥ ﺳﻴﺴﺘﻢ ﻭ ﻋﺪﻡ ﺩﺭﻳﺎﻓﺖ‪.‬‬

‫‪Control‬‬

‫‪Input‬‬ ‫‪Process‬‬ ‫‪Output‬‬

‫‪Feedback‬‬
 ‫ﺁﻧﺎﻟﻴﺰ ﻭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﭼﻴﺴﺖ ؟‬
‫ﺗﺠﺰﻳﻪ ﻭ ﺗﺤﻠﻴﻞ ﺳﻴﺴﺘﻢ ﻋﺒﺎﺭﺗﺴﺖ ﺍﺯ ﺍﻣﺘﺤﺎﻥ ﻗﻄﻌﺎﺕ‪،‬‬
‫ﻋﻨﺎﺻﺮ‪ ،‬ﻓﺮﺁﻳﻨﺪﻫﺎ‪ ،‬ﺍﺟﺰﺍء‪ ،‬ﻭﻇﺎﻳﻒ‪ ،‬ﻭ ‪ ...‬ﻛﻪ ﻳﻚ ﺳﻴﺴﺘﻢ‬
‫ﺭﺍ ﺗﺸﻜﻴﻞ ﻣﻴﺪﻫﻨﺪ‪ ،‬ﺗﺎ ﺭﻭﺍﺑﻂ ﺁﻧﻬﺎ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﻭﭼﮕﻮﻧﮕﻲ‬
‫ﻧﻘﺶ ﻫﺮﻳﻚ ﺭﺍ ﺩﺭ ﺑﻪ ﺍﻧﺠﺎﻡ ﺭﺳﺎﻧﻴﺪﻥ ﻫﺪﻑ ﺳﻴﺴﺘﻢ ﺗﻌﻴﻴﻦ‬
‫ﻧﻤﺎﻳﺪ‪.‬‬
‫ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﻋﺒﺎﺭﺗﺴﺖ ﺍﺯ ﻋﻤﻞ ﺑﻬﺴﺎﺯﻱ ﻳﻚ‬
‫ﺳﻴﺴﺘﻢ‪ ،‬ﻳﺎ ﺩﺭﻣﻮﺭﺩ ﻳﻚ ﺳﻴﺴﺘﻢ ﺟﺪﻳﺪ‪ ،‬ﺷﺮﺡ ﻣﺸﺨﺼﺎﺕ‬
‫ﻗﻄﻌﺎﺗﻲ ﺍﺳﺖ ﻛﻪ ﺳﻴﺴﺘﻢ ﺭﺍ ﺗﺸﻜﻴﻞ ﺧﻮﺍﻫﻨﺪ ﺩﺍﺩ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ‬
‫‪P arallel Processing‬‬‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻣﻮﺍﺯﻱ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻫﻤﺰﻣﺎﻥ ﺍﺯﭼﻨﺪﻳﻦ ﭘﺮﺩﺍﺯﺷﮕﺮ‪.‬‬
‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺍﺯﻱ ‪SISD, SIMD, MISD, MIMD‬‬

‫ﻋﺒﺎﺭﺗﺴﺖ ﺍﺯ‬
‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﺩﺳﺘﻪ ﺍﻱ‬
‫‪Batch P rocessing‬‬

‫ﮔﺮﻭﻩ ﺑﻨﺪﻱ ﺩﺍﺩﻩ ﻫﺎﻱ ﻭﺭﻭﺩﻱ ﺩﺭﻳﻚ ﻣﺪﺕ ﺯﻣﺎﻥ ﺧﺎﺹ ﻭ ﭘﺮﺩﺍﺯﺵ‬
‫ﺩﺳﺘﻪ ﺍﻱ ﻛﻞ‬
‫ﺩﺍﺩﻩ ﻫﺎ ﻣﺎﻧﻨﺪ ﻗﺒﻮﺽ ﺁﺏ ﺑﺮﻕ ﺗﻠﻔﻦ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ‬
‫‪I nteractive P rocessing‬‬ ‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻣﺤﺎﻭﺭﻩ ﺍﻱ‬
‫ﻋﻜﺲ ﺍﻟﻌﻤﻞ ﺳﻴﺴﺘﻢ ﺩﺭﻗﺒﺎﻝ ﻫﺮﻋﻤﻞ ﺗﻮﺳﻂ ﻛﺎﺭﺑﺮ ﺑﺎ ﻓﺮﺽ ﺍﻫﻤﻴﺖ ﻧﺪﺍﺷﺘﻦ‬
‫ﺯﻣﺎﻥ ﭘﺎﺳﺦ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﻣﺎﻧﻨﺪ ﺩﺳﺘﮕﺎﻩ ﻋﺎﺑﺮﺑﺎﻧﻚ‪.‬‬

‫‪I ntegrated P rocessing‬‬ ‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻣﺠﺘﻤﻊ‬

‫ﺍﺟﺮﺍﻱ ﻣﺪﺍﻭﻡ ﺑﺮﻧﺎﻣﻪ ﻫﺎ‪ ،‬ﻣﺮﺍﺣﻞ‪ ،‬ﻛﺎﺭﻫﺎ‪ ،‬ﻭﭘﺮﺩﺍﺯﺵ ﻣﺪﺍﻭﻡ ﻭﺭﻭﺩﻱ ﻭﺧﺮﻭﺟﻲ‬
‫ﻫﺎﺳﺖ ﻛﻪ‬
‫‪ Job Stream‬ﻧﺎﻣﻴﺪﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ‬
‫‪Real-tim e Processing‬‬ ‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﺑﻼﺩﺭﻧﮓ‬
‫ﻋﻜﺲ ﺍﻟﻌﻤﻞ ﺁﻧﻲ ﻭ ﻣﻨﺎﺳﺐ ﺳﻴﺴﺘﻢ ﺩﺭﻗﺒﺎﻝ ﻭﺭﻭﺩﻱ ﺩﺭﻳﺎﻓﺖ ﺷﺪﻩ ﺑﺎ ﻓﺮﺽ‬
‫ﺍﻫﻤﻴﺖ ﺩﺍﺷﺘﻦ ﺯﻣﺎﻥ ﭘﺎﺳﺦ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻫﻮﺍﻳﻲ ﻭﻓﻀﺎﻳﻲ‪.‬‬
‫ﻫﺮﭘﺮﺩﺍﺯﺵ ﺑﻼﺩﺭﻧﮕﻲ ﻣﺤﺎﻭﺭﻩ ﺍﻱ ﺍﺳﺖ ﻭﻟﻲ ﻫﺮﭘﺮﺩﺍﺯﺵ ﻣﺤﺎﻭﺭﻩ ﺍﻱ‬
‫ﺑﻼﺩﺭﻧﮓ ﻧﻴﺴﺖ‪.‬‬
‫‪ Netw ork P rocessing‬ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻱ‬
‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻛﻞ ﻛﻪ ﺩﺭﺷﺒﻜﻪ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﻣﻮﺭﺩﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﻧﺪ‬
‫ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ﺍﻃﻼﻋﺎﺕ ﻣﺪﻳﺮﻳﺖ ﺗﺤﺖ ﺷﺒﻜﻪ ﺳﺮﺍﺳﺮﻱ ﺩﺭﻳﻚ ﺳﺎﺯﻣﺎﻥ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ‬
‫‪Ex pert P rocessing‬‬‫ﭘﺮﺩﺍﺯﺵ ﻫﺎﻱ ﺧﺒﺮﻩ‬
‫ﺍﺳﺘﻨﺘﺎﺝ ﻣﻨﻄﻘﻲ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﺑﺎ ﺩﺭﺍﺧﺘﻴﺎﺭﺩﺍﺷﺘﻦ ﻳﻚ ﭘﺎﻳﮕﺎﻩ ﺩﺍﻧﺶ ﻭ ﺑﺎ‬
‫ﺩﺭﻳﺎﻓﺖ ﻭﻗﺎﻳﻊ ﻣﺤﻴﻂ ﺍﻃﺮﺍﻑ‪.‬‬
‫ﺗﻮﺍﻧﺎﻳﻲ ﺗﻜﻤﻴﻞ ﻛﺮﺩﻥ ﺗﺪﺭﻳﺠﻲ ﻗﻮﺍﻋﺪ ﻣﻮﺟﻮﺩ ﺩﺭﭘﺎﻳﮕﺎﻩ ﺩﺍﻧﺶ ﻭ ﺍﺿﺎﻓﻪ‬
‫) ‪(Learning‬ﻛﺮﺩﻥ ﺍﺳﺘﻨﺘﺎﺝ ﻫﺎﻱ ﺟﺪﻳﺪ ﺑﻪ ﺁﻥ‬
‫ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ‪.MyCin‬‬
 ‫ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺕ ﻣﺪﻳﺮﻳﺘﻲ‬
‫‪M anagem ent I nform ation System‬‬

‫ﺷﺎﻣﻞ ﺍﻃﻼﻋﺎﺕ ﻭ ﮔﺰﺍﺭﺷﺎﺕ ﻣﻮﺭﺩﻧﻴﺎﺯ ﻣﺪﻳﺮﺍﻥ ﺩﺭﺳﻄﻮﺡ ﺍﺳﺘﺮﺗﮋﻳﻚ‪،‬‬

‫ﻣﻴﺎﻧﻲ‪ ،‬ﻭ ﻋﻤﻠﻴﺎﺗﻲ ﺟﻬﺖ ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﻛﻨﺘﺮﻝ ﻭ ﻫﺪﺍﻳﺖ ﺳﺎﺯﻣﺎﻥ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬
‫ﺑﺪﻳﻬﻲ ﺍﺳﺖ ‪ MIS‬ﺑﺎ ‪ IMS‬ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ‪.‬‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﭘﺸﺘﻴﺒﺎﻥ ﺗﺼﻤﻴﻢ ﮔﻴﺮﻱ‬

‫‪Decision Support System‬‬

‫ﺷﺎﻣﻞ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺭﺩﻧﻴﺎﺯ ﻣﺪﻳﺮ ﺑﺼﻮﺭﺕ ﺍﺭﻗﺎﻡ ﻳﺎ ﻧﻤﻮﺩﺍﺭ ﻭﭼﺎﺭﺕ ﺟﻬﺖ‬

‫ﺗﺼﻤﻴﻢ ﮔﻴﺮﻱ ﺗﻮﺳﻂ ﻣﺪﻳﺮ ﺩﺭﻳﻚ ﺳﺎﺯﻣﺎﻥ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬
‫‪ DSS‬ﻗﺎﺩﺭ ﺑﻪ ﺗﺼﻤﻴﻢ ﮔﻴﺮﻱ ﻧﻴﺴﺖ ﻭ ﻋﻤﻠﻲ ﺍﻧﺠﺎﻡ ﻧﻤﻲ ﺩﻫﺪ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺧﺒﺮﻩ‬
‫‪Ex pert System‬‬

‫ﺗﺼﻤﻴﻢ ﮔﻴﺮﻱ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﺑﺎ ﺳﺮﻋﺖ ﺑﺎﻻ‪ .‬ﻗﺎﺑﻠﻴﺖ ﻳﺎﺩﮔﻴﺮﻱ ‪. Learning‬‬

‫ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ﺗﺸﺨﻴﺺ ﺑﻴﻤﺎﺭﻱ‪ ،‬ﺗﺸﺨﻴﺺ ﻫﻮﻳﺖ‪ ،‬ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻫﻮﺍﻳﻲ‪،‬‬

‫ﻭ ﺑﺎﺯﻱ ﺷﻄﺮﻧﺞ‪.‬‬
‫‪ Engineer,‬ﺍﺟﺰﺍﻱ ‪Knowledge Base, Search Engine, User Interface, Knowledge : ES‬‬
‫‪Expert person‬‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺍﺩﺍﺭﻱ‬

‫‪Virtual Office System‬‬

‫ﻣﻜﺎﻧﻴﺰﻩ ﺳﺎﺯﻱ ﺩﻓﺘﺮ ﻳﻚ ﺳﺎﺯﻣﺎﻥ ) ‪.(Paperless‬‬

‫ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ﺗﻨﻈﻴﻢ ﺟﻠﺴﺎﺕ ﻣﺪﻳﺮﺍﻥ ‪ ،‬ﺑﺎﻳﮕﺎﻧﻲ ﻭ ﻛﻨﻔﺮﺍﻧﺲ ﻭﻳﺪﺋﻮﻳﻲ‪.‬‬
 ‫ﻓﺼﻞ‪2‬‬

‫ﺁﻧﺎﻟﻴﺰ ﻭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﻫﺎ‬

 ‫ﺳﻪ ﻧﺴﻞ ﻣﺘﺪﻫﺎﻱ ﺁﻧﺎﻟﻴﺰ ﻭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‬
‫‪Function Oriented‬‬ ‫ﻣﺘﺪﻫﺎﻱ ﻧﺴﻞ ﺍﻭﻝ‬
‫‪Structured Analysis & Designing M ethod‬‬

‫‪Data Driven‬‬ ‫ﻣﺘﺪﻫﺎﻱ ﻧﺴﻞ ﺩﻭﻡ‬

‫‪Object-oriented Analysis & Designing M ethod‬‬

‫‪I ntegrated‬‬ ‫ﻣﺘﺪﻫﺎﻱ ﻧﺴﻞ ﺳﻮﻡ‬

‫‪Softw are Life Cycle‬‬ ‫ﭼﺮﺧﻪ ﺣﻴﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻣﺠﻤﻮﻋﻪ ﻣﺮﺍﺣﻞ ﺁﻧﺎﻟﻴﺰ ﻭ ﻃﺮﺍﺣﻲ ﻳﻚ ﺳﻴﺴﺘﻢ ﺍﺯ ﺩﺭﺧﻮﺍﺳﺖ ﺳﻴﺴﺘﻢ‬
‫ﺗﺎ ﺍﺳﺘﻘﺮﺍﺭﻭﻧﮕﻬﺪﺍﺭﻱ ﺳﻴﺴﺘﻢ‪.‬‬
 ‫ﺑﺨﺶ ﺩﻭﻡ‬

‫ﻣﺮﻭﺭ ﻛﻠﻲ ﺑﺮ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

 ‫ﻓﺼﻞ‪3‬‬

‫ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

 ‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭼﻴﺴﺖ ؟‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺷﺎﻣﻞ ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﻫﻤﺮﺍﻩ ﺑﺎ ﻣﺴﺘﻨﺪﺍﺕ ﻭ‬
‫ﺩﺍﺩﻩ ﻫﺎﻱ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﺩﺭﺳﺖ ﻛﺎﺭﻛﺮﺩﻥ ﺑﺮﻧﺎﻣﻪ‬
‫ﺿﺮﻭﺭﻱ ﺍﺳﺖ ‪.‬‬
‫ﺩﻭ ﻧﻮﻉ ﻣﺤﺼﻮﻝ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ‪:‬‬
‫‪ -1‬ﻣﺤﺼﻮﻻﺕ ﻛﻠﻲ‬
‫‪ -2‬ﻣﺤﺼﻮﻻﺕ ﺳﻔﺎﺭﺷﻲ‬
 ‫ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭼﻴﺴﺖ؟‬
‫ﻳﻚ ﻧﻈﺎﻡ ﻣﻬﻨﺪﺳﻲ ﺍﺳﺖ ﻛﻪ ﺑﺎ ﺟﻨﺒﻪ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ‬
‫ﻣﺤﺼﻮﻝ ‪ ،‬ﺍﺯ ﻣﺮﺍﺣﻞ ﺍﻭﻟﻴﻪ ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﺳﻴﺴﺘﻢ ﺗﺎ‬
‫ﻧﮕﻬﺪﺍﺭﻱ ﺳﻴﺴﺘﻢ ‪ ،‬ﺳﺮﻭﻛﺎﺭ ﺩﺍﺭﺩ ‪.‬‬
‫ﺷﺎﻣﻞ ﻣﺮﺍﺣﻞ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﻧﻈﺎﻡ ﻣﻬﻨﺪﺳﻲ ‪.‬‬
‫‪ -2‬ﺗﻤﺎﻡ ﺟﻨﺒﻪ ﻫﺎﻱ ﻣﺤﺼﻮﻝ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ‪.‬‬
 ‫ﺗﻔﺎﻭﺕ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭ ﻋﻠﻢ ﻛﺎﻣﭙﻴﻮﺗﺮ ﭼﻴﺴﺖ ؟‬

‫ﻋﻠﻢ ﻛﺎﻣﭙﻴﻮﺗﺮ ﺑﺎ ﺗﺌﻮﺭﻱ ﻭ ﺍﺻﻮﻝ ﺳﺮﻭﻛﺎﺭ ﺩﺍﺭﺩ ‪ .‬ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﺎ ﻓﻌﺎﻟﻴﺖ‬
‫ﻫﺎﻱ ﺗﻮﺳﻌﻪ ﻭ ﺗﺤﻮﻳﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺳﺮﻭﻛﺎﺭﺩﺍﺭﺩ ‪.‬‬

‫ﺗﻔﺎﻭﺕ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭ ﻣﻬﻨﺪﺳﻲ ﺳﻴﺴﺘﻢ ﭼﻴﺴﺖ ؟‬

‫ﻣﻬﻨﺪﺳﻲ ﺳﻴﺴﺘﻢ ﺑﺎ ﺗﻤﺎﻡ ﺟﻨﺒﻪ ﻫﺎﻱ ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺒﺘﻨﻲ ﺑﺮ ﻛﺎﻣﭙﻴﻮﺗﺮ ﺍﺯ‬
‫ﺟﻤﻠﻪ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ‪ ،‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭ ﻣﻬﻨﺪﺳﻲ ﻓﺮﺍﻳﻨﺪ ﺳﺮﻭﻛﺎﺭ ﺩﺍﺭﺩ ‪ .‬ﻣﻬﻨﺪﺳﻲ‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﺨﺸﻲ ﺍﺯ ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺍﺳﺖ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭼﻴﺴﺖ ؟‬
‫ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻓﻌﺎﻟﻴﺖ ﻫﺎ ﺍﺳﺖ ﻛﻪ ﻫﺪﻑ ﺁﻥ ﻫﺎ ﺗﻮﺳﻌﻪ ﻳﺎ‬
‫ﺗﻜﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﺳﺖ‪.‬‬

‫ﺷﺎﻣﻞ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺍﺳﺎﺳﻲ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬

‫)‪(Requirment Specification‬‬ ‫‪ -1‬ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫)‪(Developing‬‬ ‫‪ -2‬ﺗﻮﺳﻌﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫)‪(Validation‬‬ ‫‪ -3‬ﺍﻋﺘﺒﺎﺭ ﺳﻨﺠﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫)‪(Evolution‬‬ ‫‪ -4‬ﺗﻜﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
 ‫ﻣﺪﻝ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭼﻴﺴﺖ ؟‬
‫ﻧﻤﺎﻳﺶ ﺳﺎﺩﻩ ﺍﻱ ﺍﺯ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﺳﺖ ﻛﻪ ﺍﺯ ﺟﻨﺒﻪ ﺧﺎﺻﻲ ﺍﺭﺍﺋﻪ ﺷﺪﻩ‬
‫ﺍﺳﺖ ‪.‬‬
‫ﻧﻤﻮﻧﻪ ﻫﺎﻳﻲ ﺍﺯ ﺍﻧﻮﺍﻉ ﻣﺪﻝ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪:‬‬
‫)‪(Flowchart‬‬ ‫‪ -1‬ﻣﺪﻝ ﺟﺮﻳﺎﻥ ﻛﺎﺭ ‪.‬‬
‫)‪(Data Flow Diagram‬‬ ‫‪ -2‬ﻣﺪﻝ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ﻳﺎ ﻓﻌﺎﻟﻴﺖ ‪.‬‬
‫)‪(Use Case‬‬ ‫‪ -3‬ﻣﺪﻝ ﻧﻘﺶ‪ /‬ﻓﻌﺎﻟﻴﺖ ‪.‬‬
‫ﻣﺪﻝ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﻛﻪ ﺑﺮﺍﻱ ﺗﻮﺳﻌﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭﺟﻮﺩ‬
‫ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﺭﻫﻴﺎﻓﺖ ﺁﺑﺸﺎﺭﻱ ‪.‬‬
‫‪ -2‬ﺗﻮﺳﻌﻪ ﺗﻜﺎﻣﻠﻲ ‪.‬‬
‫‪ -3‬ﺗﺒﺪﻳﻞ ﺭﺳﻤﻲ ‪.‬‬
‫‪ -4‬ﻣﻮﻧﺘﺎژ ﺳﻴﺴﺘﻢ ﺑﺎ ﻗﻄﻌﺎﺕ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ‪.‬‬
‫ﻣﺪﻝ ﺁﺑﺸﺎﺭﻱ ‪:‬‬
‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﻜﺎﻣﻠﻲ ‪:‬‬
‫ﻣﺪﻝ ﺗﺒﺪﻳﻞ ﺭﺳﻤﻲ ‪:‬‬
‫ﻣﺪﻝ ﻣﻮﻧﺘﺎژ ﺳﻴﺴﺘﻢ ﺑﺎ ﻗﻄﻌﺎﺕ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ‪:‬‬
 ‫ﻛﻴﺲ ﭼﻴﺴﺖ ؟‬
‫)‪(CASE:Computer Aided Software Engineering‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺍﻧﺪ ﻛﻪ ﺍﺯ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﺑﻄﻮﺭ ﺧﻮﺩﻛﺎﺭ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲ ﻛﻨﻨﺪ ‪.‬‬
‫‪High Level CASE & Low Level CASE‬‬

‫ﻫﺰﻳﻨﻪ ﻫﺎﻱ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻛﺪﺍﻣﻨﺪ ؟‬

‫ﺗﻘﺮﻳﺒﺎً ‪ 60‬ﺩﺭﺻﺪ ﻫﺰﻳﻨﻪ ﻫﺎ ﻣﺮﺑﻮﻁ ﺑﻪ ﺗﻮﺳﻌﻪ ‪ ،‬ﻭ ‪ 40‬ﺩﺭﺻﺪ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﺗﺴﺖ ﺍﺳﺖ ‪.‬‬
 ‫ﺗﻮﺯﻳﻊ ﻫﺰﻳﻨﻪ ﻓﻌﺎﻟﻴﺖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻣﺪﻝ ﺁﺑﺸﺎﺭﻱ‬
‫‪0‬‬ ‫‪25‬‬ ‫‪50‬‬ ‫‪75‬‬ ‫‪100‬‬

‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬ ‫ﻃﺮﺍﺣﻲ‬ ‫ﺗﻮﺳﻌﻪ‬ ‫ﺟﺎﻣﻌﻴﺖ ﻭﺗﺴﺖ‬

‫ﺗﻮﺳﻌﻪ ﺗﻜﺮﺍﺭﻱ‬
‫‪0‬‬ ‫‪25‬‬ ‫‪50‬‬ ‫‪75‬‬ ‫‪100‬‬

‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬ ‫ﺗﻮﺳﻌﻪ ﺗﻜﺮﺍﺭﻱ‬ ‫ﺗﺴﺖ ﺳﻴﺴﺘﻢ‬

 ‫ﺗﻮﺯﻳﻊ ﻫﺰﻳﻨﻪ ﻓﻌﺎﻟﻴﺖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﺒﺘﻨﻲ ﺑﺮ ﻗﻄﻌﻪ‬
‫‪0‬‬ ‫‪25‬‬ ‫‪50‬‬ ‫‪75‬‬ ‫‪100‬‬

‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬ ‫ﺗﻮﺳﻌﻪ‬ ‫ﺟﺎﻣﻌﻴﺖ ﻭﺗﺴﺖ‬

‫ﻫﺰﻳﻨﻪ ﻫﺎﻱ ﺗﻮﺳﻌﻪ ﻭ ﺗﻜﺎﻣﻞ ﺩﺭﺍﺯ ﻣﺪﺕ‬

‫‪0‬‬ ‫‪100‬‬ ‫‪200‬‬ ‫‪300‬‬ ‫‪400‬‬

‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ‬ ‫ﺗﻜﺎﻣﻞ ﺳﻴﺴﺘﻢ‬

 ‫ﺭﻭﺵ ﻫﺎﻱ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻛﺪﺍﻣﻨﺪ ؟‬
‫ﺭﻫﻴﺎﻓﺖ ﻫﺎﻱ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ﺗﻮﺳﻌﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻛﻪ ﺣﺎﻭﻱ ﻣﺪﻝ ﻫﺎﻱ‬
‫ﺳﻴﺴﺘﻢ‪ ،‬ﻧﺸﺎﻧﻪ ﮔﺬﺍﺭﻱ ﻫﺎ ‪ ،‬ﻗﻮﺍﻋﺪ ‪ ،‬ﺗﻮﺻﻴﻪ ﻃﺮﺍﺣﻲ ﻭ ﺭﺍﻫﻨﻤﺎﻱ‬
‫ﻓﺮﺍﻳﻨﺪ ﺍﺳﺖ ‪.‬‬
‫‪JSD, SSADM, Operation-Oriented, Object-Oriented, UML‬‬

‫ﺍﻳﻦ ﺭﻭﺵ ﻫﺎ ﺑﺎﻳﺪ ﺗﻌﺪﺍﺩﻱ ﻣﻮﻟﻔﻪ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ‪:‬‬

‫‪ -1‬ﺗﻮﺻﻴﻒ ﻫﺎﻱ ﻣﺪﻝ ﺳﻴﺴﺘﻢ‬
‫‪ -2‬ﻗﻮﺍﻧﻴﻦ‬
‫‪ -3‬ﭘﻴﺸﻨﻬﺎﺩﺍﺕ‬
‫‪ -4‬ﺭﺍﻫﻨﻤﺎﻱ ﻓﺮﺍﻳﻨﺪ‬
 ‫ﺻﻔﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺧﻮﺏ ﻛﺪﺍﻣﻨﺪ ؟‬
‫‪ -1‬ﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ‬
‫)‪(Dependability‬‬ ‫‪ -2‬ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ‬
‫‪ -3‬ﻛﺎﺭ ﺁﻣﺪﻱ‬
‫)‪(Usability‬‬ ‫‪ -4‬ﻗﺎﺑﻠﻴﺖ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻣﺴﺌﻮﻟﻴﺖ ﺗﺨﺼﺼﻲ ﻭ ﺍﺧﻼﻗﻲ‬
‫‪ -1‬ﻣﺤﺮﻣﺎﻧﮕﻲ‪.‬‬
‫‪ -2‬ﺻﻼﺣﻴﺖ‪.‬‬
‫‪ -3‬ﺣﻘﻮﻕ ﻣﻌﻨﻮﻱ‪.‬‬
‫‪ -4‬ﺳﻮء ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻛﺎﻣﭙﻴﻮﺗﺮ‪.‬‬
 ‫ﻓﺼﻞ‪4‬‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺟﺘﻤﺎﻋﻲ ‪ -‬ﺗﻜﻨﻴﻜﻲ‬

 ‫ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﻳﻚ ﻣﺠﻤﻮﻋﻪ ﻫﺪﻓﻤﻨﺪ ﺍﺯ ﻣﻮﻟﻔﻪ ﻫﺎﻱ ﻣﺮﺗﺒﻂ ﺑﻪ ﻫﻢ ﺍﺳﺖ‬
‫ﻛﻪ ﺑﺎ ﻫﻢ ﻛﺎﺭ ﻣﻲ ﻛﻨﻨﺪ ﺗﺎ ﻫﺪﻓﻲ ﺭﺍ ﺑﺮ ﺁﻭﺭﺩﻩ ﻧﻤﺎﻳﻨﺪ ‪.‬‬
‫‪System  Subsystems‬‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺷﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻫﺴﺘﻨﺪ ‪:‬‬

‫‪ -1‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺗﻜﻨﻴﻜﻲ ‪.‬‬
‫‪ -2‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺟﺘﻤﺎﻋﻲ‪ -‬ﺗﻜﻨﻴﻜﻲ ‪.‬‬
 ‫ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺍﺻﻠﻲ ﺳﻴﺴﺘﻢ ﻫﺎﻱ‬
‫ﺍﺟﺘﻤﺎﻋﻲ‪ -‬ﺗﻜﻨﻴﻜﻲ ‪:‬‬
‫‪ -1‬ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺟﺪﻳﺪﻱ ﻛﻪ ﺑﻪ ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﺑﻪ‬
‫ﻋﻨﻮﺍﻥ ﻳﻚ ﻛﻞ ﻣﺮﺑﻮﻁ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫‪ -2‬ﺍﻏﻠﺐ ﻏﻴﺮ ﻗﻄﻌﻲ ﺍﻧﺪ ‪.‬‬
‫‪ -3‬ﺑﺴﻂ ﺳﻴﺴﺘﻢ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺍﻫﺪﺍﻑ ﺳﻴﺴﺘﻢ ﻓﻘﻂ ﺑﻪ‬
‫ﺧﻮﺩ ﺳﻴﺴﺘﻢ ﺑﺴﺘﮕﻲ ﻧﺪﺍﺭﺩ ‪.‬‬
 ‫ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺟﺪﻳﺪ ﺳﻴﺴﺘﻢ ‪:‬‬
‫‪ -1‬ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ‬
‫ﻭﻳﮋﮔﻴﻬﺎﻱ ﻛﻠﻴﻪ ﻣﻮﻟﻔﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻛﻪ ﺑﺎ ﻫﻢ ﻛﺎﺭ ﻣﻲ ﻛﻨﻨﺪ ﺗﺎ ﻫﺪﻑ‬
‫ﺧﺎﺻﻲ ﺭﺍ ﺑﺮﺁﻭﺭﺩﻩ ﻛﻨﻨﺪ‪.‬‬
‫‪ -2‬ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﻏﻴﺮ ﻋﻤﻠﻜﺮﺩﻱ‬
‫ﻭﻳﮋﮔﻴﻬﺎﻱ ﻣﺜﻞ ﻗﺎﺑﻠﻴﺖ‪ ،‬ﺍﻋﺘﻤﺎﺩ‪ ،‬ﻛﺎﺭﺍﻳﻲ‪ ،‬ﺍﻣﻨﻴﺖ‪ ،‬ﻭ ﺣﻔﺎﻇﺖ‪.‬‬
 ‫ﻣﺜﺎﻝ ﻫﺎﻳﻲ ﺍﺯ ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺟﺪﻳﺪ ‪:‬‬
‫)‪(Volume‬‬ ‫‪ -1‬ﺣﺠﻢ ‪.‬‬
‫)‪(Relability‬‬ ‫‪ -2‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪.‬‬
‫)‪(Security‬‬ ‫‪ -3‬ﺍﻣﻨﻴﺖ‪.‬‬
‫)‪(Recovery‬‬ ‫‪ -4‬ﻗﺎﺑﻠﻴﺖ ﺗﺮﻣﻴﻢ ﻭ ﺑﻜﺎﺭﮔﻴﺮﻱ‪.‬‬
‫ﻋﻮﺍﻣﻞ ﻣﻮﺛﺮ ﺩﺭ ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ﺳﻴﺴﺘﻢ ‪:‬‬
‫‪ -1‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ‪.‬‬
‫‪ -2‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
‫‪ -3‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ﺍﭘﺮﺍﺗﻮﺭ ‪.‬‬
 ‫ﻣﻬﻨﺪﺳﻲ ﺳﻴﺴﺘﻢ ﻫﺎ ‪:‬‬
‫ﻓﻌﺎﻟﻴــﺖ ﺗﻌﻴــﻴﻦ ﻣﺸﺨﺼــﺎﺕ‪ ،‬ﻃﺮﺍﺣــﻲ‪ ،‬ﭘﻴــﺎﺩﻩ ﺳــﺎﺯﻱ‪ ،‬ﺍﻋﺘﺒــﺎﺭ‬
‫ﺳﻨﺠﻲ‪ ،‬ﺍﺳﺘﻘﺮﺍﺭ ﻭﻧﮕﻬﺪﺍﺭﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺟﺘﻤـﺎﻋﻲ‪ -‬ﺗﻜﻨﻴﻜـﻲ‬
‫ﻣﻲ ﺑﺎﺷﺪ ‪.‬‬
‫ﺗﻔﺎﻭﺕ ﻫﺎﻱ ﺑﻴﻦ ﻓﺮﺍﻳﻨﺪ ﻣﻬﻨﺪﺳﻲ ﺳﻴﺴﺘﻢ ﻭ ﻓﺮﺍﻳﻨﺪ ﺗﻮﺳﻌﻪ‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪:‬‬
‫‪ -1‬ﻭﺟﻮﺩ ﺣﻮﺯﻩ ﻣﺤﺪﻭﺩ ﺑﺮﺍﻱ ﻛﺎﺭ ﻣﺠﺪﺩ ﺩﺭ ﺍﺛﻨﺎﻱ ﺗﻮﺳﻌﻪ‬
‫ﺳﻴﺴﺘﻢ‪.‬‬
‫‪ -2‬ﭘﻴﭽﻴﺪﮔﻲ ﻧﻈﺎﻡ ﻫﺎﻱ ﺩﺍﺧﻠﻲ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﻣﻬﻨﺪﺳﻲ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﺗﺠﺰﻳﻪ ﺳﻴﺴﺘﻢ‬

‫ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‬ ‫ﺗﻜﺎﻣﻞ ﺳﻴﺴﺘﻢ‬

‫ﺗﻮﺳﻌﻪ ﺯﻳﺮﺳﻴﺴﺘﻢ‬ ‫ﻧﺼﺐ ﺳﻴﺴﺘﻢ‬

‫ﺟﺎﻣﻌﻴﺖ ﺳﻴﺴﺘﻢ‬
 ‫ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺍﻳﻦ ﻓﻌﺎﻟﻴﺖ‪ ،‬ﻋﻤﻠﻜﺮﺩ ﻭ ﺧﻮﺍﺹ ﺍﺳﺎﺳﻲ ﻭ ﻣﻄﻠﻮﺏ ﺳﻴﺴﺘﻢ ﺭﺍ‬
‫ﻣﺸﺨﺺ ﻣﻲ ﻛﻨﺪ ‪.‬‬

‫ﺍﻧﻮﺍﻉ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪:‬‬

‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ ﺍﻧﺘﺰﺍﻋﻲ ‪.‬‬
‫‪ -2‬ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -3‬ﺧﻮﺍﺻﻲ ﻛﻪ ﺳﻴﺴﺘﻢ ﻧﺒﺎﻳﺪ ﺍﺯ ﺧﻮﺩ ﻧﺸﺎﻥ ﺩﻫﺪ‪.‬‬
 ‫ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﻣﺸﺨﺺ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﻋﻤﻠﻜﺮﺩ ﺳﻴﺴﺘﻢ ﭼﮕﻮﻧﻪ ﺑﺎﻳﺪ‬
‫ﺗﻮﺳﻂ ﻣﻮﻟﻔﻪ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺳﻴﺴﺘﻢ ﺍﻧﺠﺎﻡ ﺷﻮﺩ ‪.‬‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ‪:‬‬
‫‪ -1‬ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -2‬ﺷﻨﺎﺳﺎﻳﻲ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ‪.‬‬
‫‪ -3‬ﺍﻧﺘﺴﺎﺏ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺑﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ‪.‬‬
‫‪ -4‬ﺗﻌﻴﻴﻦ ﻋﻤﻠﻜﺮﺩ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ‪.‬‬
‫‪ -5‬ﺗﻌﺮﻳﻒ ﻭﺍﺳﻂ ﻫﺎﻱ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ‬ ‫ﺗﻌﺮﻳﻒ ﻭﺍﺳﻂ ﻫﺎﻱ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﺯﻳﺮ ﺳﻴﺴﺘﻢ‬

‫ﺗﺸﺨﻴﺺ‬ ‫ﻣﺸﺨﺺ ﻛﺮﺩﻥ‬

‫ﺯﻳﺮﺳﻴﺴﺘﻢ‬ ‫ﻋﻤﻠﻜﺮﺩ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‬

‫ﺍﻧﺘﺴﺎﺏ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﺑﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‬
 ‫ﻣﺪﻝ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺩﺭ ﺍﺛﻨﺎﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﻭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ‪ ،‬ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﺑﺼﻮﺭﺕ‬
‫ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻣﻮﻟﻔﻪ ﻫﺎ ﻭ ﺭﻭﺍﺑﻂ ﺑﻴﻦ ﺁﻧﻬﺎ ﻣﺪﻝ ﺳﺎﺯﻱ ﺷﻮﺩ ‪.‬‬

‫ﺳﻴﺴﺘﻢ ﺑﻪ ﭼﻨﺪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﺗﺠﺰﻳﻪ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﻫﺮ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‬

‫ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﺗﺠﺰﻳﻪ ﺷﻮﺩ ﺗﺎ ﻣﻮﻟﻔﻪ‬
‫ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ ﺑﻪ ﺩﺳﺖ ﺁﻳﻨﺪ ‪.‬‬
 ‫ﺗﻮﺳﻌﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺩﺭ ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ‪ ،‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ﺍﺛﻨﺎﻱ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‬
‫ﺷﻨﺎﺳﺎﻳﻲ ﺷﺪﻧﺪ‪ ،‬ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬

‫)‪(Parallel Developing‬‬

‫ﺟﺎﻣﻌﻴﺖ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ‪:‬‬

‫ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﻣﺴﺘﻘﻞ ﺍﺯ ﻫﻢ ﺗﻮﺳﻌﻪ ﺩﺍﺩﻩ ﺷﺪﻧﺪ‪ ،‬ﺩﺭ ﻛﻨﺎﺭ‬
‫ﻫﻢ ﻗﺮﺍﺭ‬
‫ﻣﻲ ﮔﻴﺮﻧﺪ ﺗﺎ ﺳﻴﺴﺘﻢ ﻛﺎﻣﻞ ﺍﻳﺠﺎﺩ ﻛﻨﻨﺪ ‪.‬‬
‫) ‪(Big Bang Strategy & Incremental Strategy‬‬
 ‫ﻧﺼﺐ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﻭﺟﻮﺩﻣﺸﻜﻼﺕ ‪ :‬ﻣﺤﻴﻂ ‪ ،‬ﺍﺟﺮﺍﻱ ﻣﻮﺍﺯﻱ ‪ ،‬ﻛﺎﻫﺶ‬
‫ﻣﺴﺌﻮﻟﻴﺖ ‪ ،‬ﻣﺸﻜﻼﺕ ﻓﻴﺰﻳﻜﻲ‬

‫ﻋﻤﻠﻴﺎ ﺕ ﺳﻴﺴﺘﻢ ‪:‬‬

‫ﺁﻣﻮﺯﺵ ﺍﭘﺮﺍﺗﻮﺭ ‪ ،‬ﻧﺎﺳﺎﺯﮔﺎﺭﻱ ﻓﻴﺰﻳﻜﻲ‬
 ‫ﺗﻜﺎﻣﻞ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺑﺰﺭگ ‪ ،‬ﺩﺭ ﺍﺛﻨﺎﻱ ﺯﻧﺪﮔﻲ ﺷﺎﻥ‪ ،‬ﺑﺎﻳﺪ ﺗﻜﺎﻣﻞ‬
‫ﻳﺎﺑﻨﺪ ﺗﺎ ﺧﻄﺎﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺍﺻﻠﻲ ﺳﻴﺴﺘﻢ ﺭﺍ‬
‫ﺍﺻﻼﺡ ﻛﻨﻨﺪ ﻭ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺟﺪﻳﺪ ﺭﺍ ﺑﺮﺁﻭﺭﺩﻩ ﻧﻤﺎﻳﻨﺪ ‪.‬‬

‫ﺗﺠﺰﻳﻪ ﺳﻴﺴﺘﻢ ‪:‬‬

‫ﺳﻴﺴﺘﻢ ﭘﺲ ﺍﺯ ﻃﻮﻝ ﻋﻤﺮ ﻣﻔﻴﺪ ﻋﻤﻠﻴﺎﺗﻲ ﺁﻥ‪ ،‬ﻛﻨﺎﺭ ﮔﺬﺍﺷﺘﻪ‬
‫ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫ﺳﺎﺯﻣﺎﻥ ﻫﺎ ‪ ،‬ﺍﻓﺮﺍﺩ ﻭ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ‬
‫ﻋﻮﺍﻣﻞ ﺳﺎﺯﻣﺎﻧﻲ ﻭ ﺍﻧﺴﺎﻧﻲ ﺩﺭ ﻣﺤﻴﻂ ﺳﻴﺴﺘﻢ ﻛﻪ‬
‫ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﺭﺍ ﺗﺤﺖ ﺗﺎﺛﻴﺮ ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﻨﺪ ‪:‬‬

‫‪ -1‬ﺗﻐﻴﻴﺮﺍﺕ ﻓﺮﺍﻳﻨﺪ ‪.‬‬

‫‪ -2‬ﺗﻐﻴﻴﺮﺍﺕ ﺷﻐﻞ ‪.‬‬
‫‪ -3‬ﺗﻐﻴﻴﺮﺍﺕ ﺳﺎﺯﻣﺎﻧﻲ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﺗﻬﻴﻪ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﻣﺤﺼﻮﻻﺕ ﻛﻠﻲ‬

‫ﺗﻌﺪﻳﻞ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﺍﻧﺘﺨﺎﺏ ﺳﻴﺴﺘﻢ‬ ‫ﺩﺭﺧﻮﺍﺳﺖ ﺍﺭﺍﺋﻪ ﻗﻴﻤﺖ‬ ‫ﺍﻧﺘﺨﺎﺏ ﻋﺮﺿﻪ ﻛﻨﻨﺪﻩ‬

‫ﺑﺮﺭﺳﻲ ﺑﺎﺯﺍﺭ ﺑﺮﺍﻱ‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺟﻮﺩ‬

‫ﭘﻴﺸﻨﻬﺎﺩ ﻣﻨﺎﻗﺼﻪ‬ ‫ﺍﻧﺘﺨﺎﺏ ﻣﻨﺎﻗﺼﻪ‬ ‫ﻣﺬﺍﻛﺮﻩ ﺑﺮﺍﻱ ﻗﺮﺍﺭ ﺩﺍﺩ‬ ‫ﻋﻘﺪ ﻗﺮﺍﺭ ﺩﺍﺩ‬

‫ﻣﺤﺼﻮﻻﺕ ﺳﻔﺎﺭﺷﻲ‬
‫ﻓﺮﺍﻳﻨﺪ ﻫﺎی ﺗﻬﻴﻪ‪ ،‬ﺗﻮﺳﻌﻪ ﻭ ﻋﻤﻠﻴﺎﺗﯽ‬
‫‪:‬‬

‫ﻓﺮﺍﻳﻨﺪ ﺗﻬﻴﻪ‬

‫ﻓﺮﺍﻳﻨﺪ ﺗﻮﺳﻌﻪ‬

‫ﻓﺮﺍﻳﻨﺪ ﻋﻤﻠﻴﺎﺗﻲ‬
 ‫ﻓﺮﺍﻳﻨﺪ ﺗﻬﻴﻪ ‪:‬‬
‫ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺑﻪ ﺗﺼﻤﻴﻢ ﮔﻴﺮﻱ ﺩﺭ ﻣﻮﺭﺩ ﺑﻬﺘﺮﻳﻦ ﺭﻭﺵ ﺩﺳﺘﻴﺎﺑﻲ ﻳﻚ‬
‫ﺳﺎﺯﻣﺎﻥ ﺑﻪ ﺳﻴﺴﺘﻢ ﻭ ﺑﻬﺘﺮﻳﻦ ﺗﻬﻴﻪ ﻛﻨﻨﺪﻩ ﺳﻴﺴﺘﻢ ﻣﺮﺑﻮﻁ ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫ﻓﺮﺍﻳﻨﺪﻫﺎﻱ ﻋﻤﻠﻴﺎﺗﻲ ‪:‬‬

‫ﻓﺮﺍﻳﻨﺪ ﻫﺎﻳﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺩﺭ ﺑﻜﺎﺭﮔﻴﺮﻱ ﺍﺯ ﺳﻴﺴﺘﻢ ﺑﺮﺍﻱ ﺭﺳﻴﺪﻥ ﺑﻪ‬
‫ﺍﻫﺪﺍﻓﺶ ﻧﻘﺶ ﺩﺍﺭﺩ ‪.‬‬
 ‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻬﻨﻪ ‪:‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺍﺟﺘﻤﺎﻋﻲ – ﺗﻜﻨﻴﻜﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺩﺭ ﮔﺬﺷﺘﻪ ﺍﻳﺠﺎﺩ‬
‫ﺷﺪﻧﺪ ﻭ ﻣﻌﻤﻮﻻً ﺍﺯ ﻓﻦ ﺁﻭﺭﻱ ﻗﺪﻳﻤﻲ ﺗﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻧﻤﺎﻳﻨﺪ ‪.‬‬
‫ﻗﻄﻌﺎﺕ ﺳﻴﺴﺘﻢ ﻛﻬﻨﻪ ‪:‬‬
‫‪ -1‬ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ‬
‫‪ -2‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭘﺸﺘﻴﺒﺎﻥ ‪.‬‬
‫‪ -3‬ﻧﺮﻡ ﺍﻓﺰﺍﺭﻫﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ‪.‬‬
‫‪ -4‬ﺩﺍﺩﻩ ﻫﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ‪.‬‬
‫‪ -5‬ﻓﺮﺍﻳﻨﺪ ﺗﺠﺎﺭﻱ ‪.‬‬
‫‪ -6‬ﻗﻮﺍﻧﻴﻦ ﻭ ﺳﻴﺎﺳﺘﻬﺎﻱ ﺗﺠﺎﺭﻱ ‪.‬‬
‫ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻗﺪﻳﻤﻲ‬

‫ﻓﺮﺍﻳﻨﺪ ﻫﺎی ﺗﺠﺎﺭی‬

‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﮐﺎﺭﺑﺮﺩی‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﭘﺸﺘﻴﺒﺎﻥ‬
‫ﺳﺨﺖ ﺍﻓﺰﺍﺭ‬
 ‫ﻓﺼﻞ‪5‬‬

‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ‬

 ‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ‪:‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺷﻜﺴﺖ ﻣﻲ ﺗﻮﺍﻧﺪ ﻣﻨﺠﺮ ﺑﻪ ﺿﺮﺭﻫﺎﻱ ﺍﻗﺘﺼﺎﺩﻱ ‪،‬‬
‫ﺧﺮﺍﺑﻲ ﻓﻴﺰﻳﻜﻲ ﻳﺎ ﺁﺳﻴﺐ ﺭﺳﺎﻧﻲ ﺑﻪ ﺍﻧﺴﺎﻥ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫ﺳﻪ ﻧﻮﻉ ﺳﻴﺴﺘﻢ ﺣﻴﺎﺗﻲ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ﺍﻣﻨﻴﺘﻲ ‪.‬‬
‫‪ -2‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ﻣﺄﻣﻮﺭﻳﺘﻲ ‪.‬‬
‫‪ -3‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ﺗﺠﺎﺭﻱ ‪.‬‬
 ‫ﻣﻬﻢ ﺗﺮﻳﻦ ﻭﻳﮋﮔﻲ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺣﻴﺎﺗﻲ‬
‫ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬
‫ﺩﻻﻳﻞ ﺍﻫﻤﻴﺖ ﻭﻳﮋﮔﻲ ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ‬
‫‪ -1‬ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﻗﺎﺑﻞ ﺍﻋﺘﻤﺎﺩ ﻭ ﺍﻣﻦ ﻧﻴﺴﺘﻨﺪ ﺗﻮﺳﻂ ﻛﺎﺭﺑﺮﺍﻥ‬
‫ﺭﺩ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬
‫‪ -2‬ﻫﺰﻳﻨﻪ ﻫﺎﻱ ﺷﻜﺴﺖ ﺳﻴﺴﺘﻢ ﻣﻤﻜﻦ ﺍﺳﺖ ﺧﻴﻠﻲ ﺯﻳﺎﺩ ﺑﺎﺷﺪ ‪.‬‬
‫‪ -3‬ﺳﻴﺴﺘﻢ ﺑﻲ ﺍﻋﺘﻤﺎﺩ ﻣﻤﻜﻦ ﺍﺳﺖ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺍﺯ ﺑﻴﻦ ﺑﺒﺮﺩ ‪.‬‬
‫ﻗﻄﻌﺎﺗﻲ ﺍﺯ ﺳﻴﺴﺘﻢ ﺣﻴﺎﺗﻲ ﻛﻪ ﻣﻤﻜﻦ‬
‫ﺍﺳﺖ ﺩﭼﺎﺭ ﻣﺸﻜﻞ ﺷﻮﺩ ‪:‬‬
‫‪ -1‬ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -2‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -3‬ﺍﭘﺮﺍﺗﻮﺭﻫﺎﻱ ﺍﻧﺴﺎﻧﻲ ‪.‬‬
‫)‪(Dependability‬‬ ‫ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎﻱ ﺳﻴﺴﺘﻢ ‪:‬‬
‫ﺑﻪ ﻣﻌﻨﺎﻱ ﺩﺭﺟﻪ ﺍﻱ ﺍﺯ ﺍﻋﺘﻤﺎﺩ ﻛﺎﺭﺑﺮ ﺑﻪ ﺳﻴﺴﺘﻢ ﻛﻪ ﻣﻄﺎﺑﻖ‬
‫ﺧﻮﺍﺳﺘﻪ ﺍﻭ ﻋﻤﻞ ﻣﻲ ﻛﻨﺪ ﻭﺩﺭ ﻛﺎﺭﺑﺮﺩ ﻋﺎﺩﻱ ﺑﺎ ﺷﻜﺴﺖ‬
‫ﻣﻮﺍﺟﻪ ﻧﻤﻲ ﺷﻮﺩ ‪.‬‬
‫ﭼﻬﺎﺭ ﺑﻌﺪ ﺍﺻﻠﻲ ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪:‬‬
‫‪ -1‬ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ‪.‬‬
‫‪ -2‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪.‬‬
‫‪ -3‬ﺍﻣﻨﻴﺖ ‪.‬‬
‫‪ -4‬ﺣﻔﺎﻇﺖ ‪.‬‬
 ‫ﻣﻨﺤﻨﻲ ﻫﺰﻳﻨﻪ‪ /‬ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ‬

‫ﻫﺰﻳﻨﻪ‬
‫ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﻛﻪ ﺩﺭ ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ ﻣﻲ ﺗﻮﺍﻥ ﺩﺭ‬
‫ﻧﻈﺮ ﮔﺮﻓﺖ ‪:‬‬
‫‪ -1‬ﻗﺎﺑﻠﻴﺖ ﺗﺮﻣﻴﻢ ‪.‬‬
‫‪ -2‬ﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ ‪.‬‬
‫‪ -3‬ﻗﺎﺑﻠﻴﺖ ﺑﻘﺎ ‪.‬‬
‫‪ -4‬ﺗﺤﻤﻞ ﻋﻴﺐ ‪.‬‬
 ‫ﺍﺑﻌﺎﺩ ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ‬
‫ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ‬

‫ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ‬ ‫ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ‬ ‫ﺍﻣﻨﻴﺖ‬ ‫ﺣﻔﺎﻇﺖ‬

‫ﺗﻮﺍﻧﺎﻳﻲ ﺳﻴﺴﺘﻢ ﺩﺭ‬ ‫ﺗﻮﺍﻧﺎﻳﻲ ﺳﻴﺴﺘﻢ ﺩﺭ‬ ‫ﺗﻮﺍﻧﺎﻳﻲ ﺳﻴﺴﺘﻢ ﺑﻪ‬ ‫ﺗﻮﺍﻧﺎﻳﻲ ﺳﻴﺴﺘﻢ ﺩﺭ‬
‫ﺍﺭﺍﺋﻪ ﺳﺮﻭﻳﺲ ﻫﺎﻱ‬ ‫ﺍﺭﺍﺋﻪ ﺳﺮﻭﻳﺴﻬﺎﻱ‬ ‫ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﺑﺪﻭﻥ‬ ‫ﺣﻔﺎﻇﺖ ﺧﻮﺩﺵ ﺩﺭ ﻣﻘﺎﺑﻞ‬
‫ﺩﺭﺧﻮﺍﺳﺘﻲ‬ ‫ﻣﺸﺨﺺ ﺷﺪﻩ‬ ‫ﺧﺮﺍﺑﻲ‬ ‫ﻧﻔﻮﺫ ﻋﻤﺪﻱ ﻳﺎ ﺗﺼﺎﺩﻓﻲ‬
 ‫ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ‪:‬‬
‫ﺍﺣﺘﻤﺎﻝ ﺍﻳﻦ ﻛﻪ ﺳﻴﺴﺘﻢ ﺩﺭ ﻧﻘﻄﻪ ﺍﻱ ﺍﺯ ﺯﻣﺎﻥ ﻓﻌﺎﻝ ﺑﺎﺷﺪ‬
‫ﻭ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺩﺭﺧﻮﺍﺳﺘﻲ ﺭﺍ ﺗﺤﻮﻳﻞ ﺩﻫﺪ ‪.‬‬

‫ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪:‬‬

‫ﺍﺣﺘﻤﺎﻝ ﺍﻧﺠﺎﻡ ﻋﻤﻠﻴﺎﺕ ﺑﺪﻭﻥ ﺧﻄﺎ ﺩﺭ ﻣﺪﺕ ﺯﻣﺎﻥ ﻣﻌﻴﻦ‬
‫ﻭ ﺩﺭ ﻣﺤﻴﻂ ﺧﺎﺻﻲ ﻭ ﺑﺮﺍﻱ ﻫﺪﻑ ﺧﺎﺹ ‪.‬‬
‫ﺍﺻﻄﻼﺣﺎﺕ ﻗﺎﺑﻠﻴﺖ ﺍﺗﻜﺎ ‪:‬‬
‫‪ -1‬ﺧﺮﺍﺑﻲ ﺳﻴﺴﺘﻢ ‪.‬‬

‫‪ -2‬ﺧﻄﺎﻱ ﺳﻴﺴﺘﻢ ‪.‬‬

‫‪ -3‬ﻋﻴﺐ ﺳﻴﺴﺘﻢ ‪.‬‬

‫‪ -4‬ﺧﻄﺎ ﻳﺎ ﺍﺷﺘﺒﺎﻩ ﺍﻧﺴﺎﻥ ‪.‬‬

 ‫ﺳﻪ ﺭﻭﺵ ﻣﻜﻤﻞ ﺑﺮﺍﻱ ﺑﻬﺒﻮﺩ‬
‫ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪(Relability) :‬‬

‫‪ -1‬ﺍﺟﺘﻨﺎﺏ ﺍﺯ ﺧﺮﺍﺑﻲ ‪.‬‬

‫‪ -2‬ﻛﺸﻒ ﻭﺣﺬﻑ ﻋﻴﺐ ‪.‬‬

‫‪ -3‬ﺗﺤﻤﻞ ﻋﻴﺐ ‪.‬‬

 ‫)‪(Security‬‬ ‫ﺍﻣﻨﻴﺖ ‪:‬‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﻣﻨﻴﺘﻲ ﺣﻴﺎﺗﻲ ﺁﻧﻬﺎﻳﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﻋﻤﻠﻴﺎﺕ‬
‫ﺳﻴﺴﺘﻢ ﻫﻤﻮﺍﺭﻩ ﺍﻣﻦ ﺑﺎﺷﺪ ‪ .‬ﻳﻌﻨﻲ ﺣﺘﻲ ﺍﮔﺮ ﺳﻴﺴﺘﻢ‬
‫ﺧﺮﺍﺏ ﺷﻮﺩ ﻧﺒﺎﻳﺪ ﺑﻪ ﺍﻓﺮﺍﺩ ﻭ ﻣﺤﻴﻂ ﺁﺳﻴﺐ ﺑﺮﺳﺎﻧﺪ‪.‬‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﻣﻨﻴﺘﻲ ﺣﻴﺎﺗﻲ ﺩﻭ ﺩﺳﺘﻪ ﺍﻧﺪ ‪:‬‬
‫‪ -1‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ﺍﻣﻨﻴﺘﻲ ﺍﻭﻟﻴﻪ ‪.‬‬
‫‪ -2‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﺣﻴﺎﺗﻲ ﺍﻣﻨﻴﺘﻲ ﺛﺎﻧﻮﻳﻪ ‪.‬‬
 ‫ﺑﻪ ﺩﻻﻳﻞ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻗﺎﺑﻞ ﺍﻋﺘﻤﺎﺩ ﺍﻟﺰﺍﻣﺎً ﺍﻣﻦ ﻧﻴﺴﺖ ‪:‬‬
‫‪ -1‬ﻣﺸﺨﺼﺎﺕ ﻣﻤﻜﻦ ﺍﺳﺖ ﻛﺎﻣﻞ ﻧﺒﺎﺷﺪ ‪.‬‬
‫‪ -2‬ﺑﺪ ﻋﻤﻞ ﻛﺮﺩﻥ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻣﻤﻜـﻦ ﺍﺳـﺖ ﺑﺎﻋـﺚ ﺷـﻮﺩ ﻛـﻪ‬
‫ﺭﻓﺘﺎﺭ ﺳﻴﺴﺘﻢ ﻗﺎﺑﻞ ﭘﻴﺶ ﺑﻴﻨـﻲ ﻧﺒﺎﺷـﺪ ﻭ ﻧـﺮﻡ ﺍﻓـﺰﺍﺭ ﺭﺍ ﺩﺭ ﻣﺤﻴﻄـﻲ‬
‫ﭘﻴﺶ ﺑﻴﻨﻲ ﻧﺸﺪﻩ ﺍﺭﺍﺋﻪ ﺩﻫﺪ‪.‬‬
‫‪ -3‬ﺍﭘﺮﺍﺗﻮﺭ ﺳﻴﺴﺘﻢ ﻣﻤﻜﻦ ﺍﺳﺖ ﻭﺭﻭﺩﻳـﻲ ﺭﺍ ﺗﻮﻟﻴـﺪ ﻛﻨـﺪ ﻛـﻪ ﺑـﻪ‬
‫ﺗﻨﻬﺎﻳﻲ ﻧﺎﺩﺭﺳﺖ ﻧﺒﺎﺷﺪ ﺍﻣﺎ ﺩﺭ ﻭﺿﻌﻴﺖ ﺧﺎﺻﻲ ﻣﻨﺠﺮ ﺑﻪ ﻋﻤﻠﻜـﺮﺩ‬
‫ﺑﺪ ﺳﻴﺴﺘﻢ ﺷﻮﺩ ‪.‬‬
‫ﺳﻪ ﺭﻭﺵ ﻣﻜﻤﻞ ﺑﺮﺍﻱ ﺑﻬﺒﻮﺩ ﺍﻣﻨﻴﺖ ‪:‬‬
‫‪ -1‬ﺍﺟﺘﻨﺎﺏ ﺍﺯ ﺧﻄﺮ ‪.‬‬
‫‪ -2‬ﺗﺸﺨﻴﺺ ﻭ ﺭﻓﻊ ﺧﻄﺮ ‪.‬‬

‫‪ -3‬ﻣﺤﺪﻭﺩ ﻛﺮﺩﻥ ﺧﺴﺎﺭﺕ ‪.‬‬

 ‫ﺣﻔﺎﻇﺖ ‪:‬‬
‫ﺻﻔﺘﻲ ﺍﺯ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ﻛﻪ ﺗﻮﺍﻧﺎﻳﻲ ﺳﻴﺴﺘﻢ ﺭﺍ ﺩﺭ ﺣﻔﺎﻇﺖ ﺍﺯ ﺧﻮﺩﺵ‬
‫ﺩﺭ ﻣﻘﺎﺑﻞ ﺣﻤﻼﺕ ﺧﺎﺭﺟﻲ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺳﻬﻮﻱ ﻳﺎ ﻋﻤﺪﻱ ﺑﺎﺷﻨﺪ‪،‬‬
‫ﻣﻨﻌﻜﺲ ﻣﻲ ﺳﺎﺯﺩ ‪.‬‬
‫ﺍﺻﻄﻼﺣﺎﺕ ﺣﻔﺎﻇﺘﻲ ‪:‬‬
‫‪ -1‬ﺍﻓﺸﺎﮔﺮﻱ ‪.‬‬
‫‪ -2‬ﺁﺳﻴﺐ ﭘﺬﻳﺮﻱ ‪.‬‬
‫‪ -3‬ﺣﻤﻠﻪ ‪.‬‬
‫‪ -4‬ﺗﻬﺪﻳﺪﻫﺎ ‪.‬‬
‫‪ -5‬ﻛﻨﺘﺮﻝ ‪.‬‬
‫ﺍﺯ ﻃﺮﻳﻖ ﺗﻬﺎﺟﻢ ﺧﺎﺭﺟﻲ‪ ،‬ﺳﻪ ﻧﻮﻉ ﺧﺴﺎﺭﺕ ﻣﻤﻜﻦ ﺍﺳﺖ‬
‫ﭘﻴﺶ ﺁﻳﺪ ‪:‬‬
‫‪ -1‬ﻋﺪﻡ ﭘﺬﻳﺮﺵ ﺳﺮﻭﻳﺲ ‪.‬‬
‫‪ -2‬ﺗﺨﺮﻳﺐ ﺑﺮﻧﺎﻣﻪ ﻫﺎ ﻭ ﺩﺍﺩﻩ ﻫﺎ ‪.‬‬
‫‪ -3‬ﺍﻓﺸﺎﮔﺮﻱ ﺍﻃﻼﻋﺎﺕ ﻣﺤﺮﻣﺎﻧﻪ ‪.‬‬

‫ﺳﻪ ﺭﻭﺵ ﻣﻜﻤﻞ ﺑﺮﺍﻱ ﺑﻬﺒﻮﺩ ﺍﻣﻨﻴﺖ ‪:‬‬

‫‪ -1‬ﺍﺟﺘﻨﺎﺏ ﺍﺯ ﺁﺳﻴﺐ ﭘﺬﻳﺮﻱ ‪.‬‬
‫‪ -2‬ﺗﺸﺨﻴﺺ ﻭ ﺧﻨﺜﻲ ﺳﺎﺯﻱ ﺣﻤﻠﻪ ‪.‬‬
‫‪ -3‬ﻣﺤﺪﻭﺩ ﻛﺮﺩﻥ ﺍﻓﺸﺎﮔﺮﻱ ‪.‬‬
 ‫ﻓﺼﻞ‪6‬‬

‫ﻓﺮﺍﻳﻨﺪ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

 ‫ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻓﻌﺎﻟﻴﺖ ﻫﺎﺳﺖ ﻛﻪ ﻣﻨﺠﺮ ﺑﻪ‬
‫ﺗﻮﻟﻴﺪ ﻣﺤﺼﻮﻝ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺍﺳﺎﺳﻲ ﻛﻪ ﺩﺭ ﺗﻤﺎﻡ ﻓﺮﺍﻳﻨﺪ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﻣﺸﺘﺮﻛﻨﺪ ‪:‬‬

‫)‪(Requirment Specification‬‬ ‫‪ -1‬ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬

‫)‪(Developing‬‬ ‫‪ -2‬ﻃﺮﺍﺣﻲ ﻭ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
‫)‪(Validation‬‬ ‫‪ -3‬ﺍﻋﺘﺒﺎﺭ ﺳﻨﺠﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
‫)‪(Evolution‬‬ ‫‪ -4‬ﺗﻜﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪.‬‬
 ‫ﭼﺮﺧﻪ ﺣﻴﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪:‬‬
‫‪SLC: Software Life Cycle‬‬
‫ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﻃﺮﺍﺣﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭ ﺳﻴﺴﺘﻢ‬

‫ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻭ ﺗﺴﺖ ﻭﺍﺣﺪ‬

‫ﺟﺎﻣﻌﻴﺖ ﻭ ﺗﺴﺖ‬

‫ﺑﻜﺎﺭﮔﻴﺮﻱ ﻭ ﻧﮕﻬﺪﺍﺭﻱ‬
 ‫ﻣﺪﻝ ﻫﺎﻱ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪:‬‬
‫‪ -1‬ﺭﻫﻴﺎﻓﺖ ﺁﺑﺸﺎﺭﻱ ‪.‬‬
‫‪ -2‬ﺗﻮﺳﻌﻪ ﺗﻜﺎﻣﻠﻲ ‪.‬‬
‫‪ -3‬ﺗﻮﺳﻌﻪ ﺭﺳﻤﻲ ‪.‬‬
‫‪ -4‬ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﻣﺒﺘﻨﻲ ﺑﺮﻗﻄﻌﺎﺕ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ‪.‬‬
 ‫ﻣﺪﻝ ﺁﺑﺸﺎﺭی‬
‫ﻣﺪﻝ ﻣﻌﺮﻭﻑ ﻓﺮﺍﻳﻨ�ﺪ ﺗﻮﺳ�ﻌﻪ ﻧ�ﺮﻡ ﺍﻓ�ﺰﺍﺭ ﺍﺳ�ﺖ ﮐ�ﻪ ﺍﺯ‬
‫ﺳ��ﺎﻳﺮ ﻓﺮﺍﻳﻨ��ﺪﻫﺎی ﻣﻬﻨﺪﺳ��ﯽ ﻧﺎﺷ��ﯽ ﻣ��ﯽ ﺷ��ﻮﺩ ﻭ ﺷ��ﺎﻣﻞ‬
‫ﻣﺮﺍﺣﻞ ﺯﻳﺮ ﻣﯽ ﺷﻮﺩ ‪:‬‬
‫ﺗﺤﻠﻴﻞ ﻭ ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬ ‫‪-1‬‬
‫ﻁﺮﺍﺣﯽ ﺳﻴﺴﺘﻢ ﻭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬ ‫‪-2‬‬
‫ﭘﻴﺎﺩﻩ ﺳﺎﺯی ﻭ ﺗﺴﺖ ﻭﺍﺣﺪ ‪.‬‬ ‫‪-3‬‬
‫ﺟﺎﻣﻌﻴﺖ ﻭ ﺗﺴﺖ ﺳﻴﺴﺘﻢ ‪.‬‬ ‫‪-4‬‬
‫ﺑﻪ ﮐﺎﺭﮔﻴﺮی ﻭ ﻧﮕﻬﺪﺍﺭی ‪.‬‬ ‫‪-5‬‬
‫ﻣﺪﻝ ﺁﺑﺸﺎﺭی‬
 ‫ﻣﺪﻝ ﺁﺑﺸﺎﺭی‬
‫‪ .1‬ﻫﺮﻣﺮﺣﻠ��ﻪ ﻓﻘ��ﻂ ﺑ��ﺎ ﭘﺎﻳ��ﺎﻥ ﻳ��ﺎﻓﺘﻦ ﻣﺮﺣﻠ��ﻪ ﻗﺒﻠ��ﯽ ﺷ��ﺮﻭﻉ ﻣ��ﯽ‬
‫ﺷﻮﺩ‪.‬‬
‫‪ .2‬ﻫﺮﺗﮑ�����ﺮﺍﺭ ﺷ�����ﺎﻣﻞ ﺩﻭﺑ�����ﺎﺭﻩ ﮐ�����ﺎﺭی ﺍﺳ�����ﺖ ﻭﻫﺰﻳﻨ�����ﻪ ﺁﻥ‬
‫ﺑﺎﻻﺗﺮﺍﺳ�����ﺖ‪ .‬ﺑﻨ�����ﺎﺑﺮﺍﻳﻦ ﭘ�����ﺲ ﺍﺯﭼﻨ�����ﺪﺗﮑﺮﺍﺭ ﺑﺎﻳ�����ﺪﺁﻥ ﻣﺮﺣﻠ�����ﻪ‬
‫ﺭﺍﭘ��ﺬﻳﺮﻓﺖ ﻭ ﺑ��ﻪ ﻣﺮﺍﺣ��ﻞ ﺑﻌ��ﺪی ﭘﺮﺩﺍﺧ��ﺖ‪ .‬ﻣﺸ��ﮑﻼﺕ ﺍﺣﺘﻤ��ﺎﻟﯽ‬
‫ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﯽ ﻭﺍﮔﺪﺍﺭ ﻣﯽ ﺷﻮﺩ‪.‬‬
‫‪ .3‬ﻣﺸﮑﻞ ﻣﺪﻝ ﺁﺑﺸﺎﺭی ﺍﻳﻦ ﺍﺳﺖ ﮐﻪ ﺗﻘﺴ�ﻴﻢ ﺑﻨ�ﺪی ﭘ�ﺮﻭژﻩ ﺑ�ﻪ‬
‫ﺍﻳ���ﻦ ﻣﺮﺍﺣ���ﻞ ﻣﺠ���ﺰﺍ ﺁﺳ���ﺎﻥ ﻧﻴﺴ���ﺖ‪ ،‬ﻣﻌﻨ���ﺎﻳﺶ ﺍﻳ���ﻦ ﺍﺳ���ﺖ ﮐ���ﻪ‬
‫ﺗﻐﻴﻴﺮﺩﺭﺧﻮﺍﺳﺘﻪ ﻫ�ﺎی ﮐ�ﺎﺭﺑﺮ ﺩﺷﻮﺍﺭﺍﺳ�ﺖ‪ .‬ﻟ�ﺬﺍ‪ ،‬ﻣ�ﺪﻝ ﺁﺑﺸ�ﺎﺭی‬
‫ﻭﻗﺘﯽ ﺑﮑﺎﺭﮔﺮﻓﺘﻪ ﻣﯽ ﺷﻮﺩ ﮐﻪ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺑﺨﻮﺑﯽ ﺩﺭک ﺷﺪﻩ‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﮑﺎﻣﻠﯽ‬
‫ﺳﻴﺴﺘﻤﻲ ﺍﻳﺠﺎﺩ ﻣﻲ ﺷﻮﺩ ﻭ ﺑﻪ ﺗﺪﺭﻳﺞ ﺍﺻﻼﺡ ﻣﻲ ﮔـﺮﺩﺩ ﺗـﺎ ﺳﻴﺴـﺘﻢ ﻧﻬـﺎﻳﻲ‬
‫ﺗﻮﺳﻌﻪ ﻳﺎﺑﺪ ‪.‬‬
‫ﺩﻭ ﻧﻮﻉ ﺗﻮﺳﻌﻪ ﺗﻜﺎﻣﻠﻲ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﺗﻮﺳﻌﻪ ﺍﻛﺘﺸﺎﻓﻲ ‪.‬‬
‫‪ -2‬ﺳﺎﺧﺖ ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ ﻣﻮﻗﺘﻲ ‪.‬‬
‫ﺩﺭ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺳﻪ ﺍﺷﻜﺎﻝ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﻓﺮﺍﻳﻨﺪ ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﻧﻴﺴﺖ ‪.‬‬
‫‪ -2‬ﺳﻴﺴﺘﻢ ﻫﺎ ﭼﻨﺪﺍﻥ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ﻧﻴﺴﺘﻨﺪ ‪.‬‬
‫‪ -3‬ﻧﻴﺎﺯ ﺑﻪ ﺍﺑﺰﺍﺭ ﻭ ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺧﺎﺹ ‪.‬‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﻜﺎﻣﻠﻲ‬

‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬ ‫ﻧﺴﺨﻪ ﺍﻭﻟﻴﻪ‬

‫ﺗﻮﺻﻴﻒ ﻃﺮﺡ ﻛﻠﻲ‬ ‫ﺗﻮﺳﻌﻪ‬ ‫ﺗﻮﺳﻌﻪ ﻫﺎﻱ ﻣﻴﺎﻧﻲ‬

‫ﺗﺄﻳﻴﺪ‬ ‫ﻧﺴﺨﻪ ﻧﻬﺎﻳﻲ‬

‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺭﺳﻤﻲ‬
‫ﺗﺒﺪﻳﻼﺕ ﺭﺳﻤﻲ‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﺒﺘﻨﻲ ﺑﺮ ﻗﻄﻌﻪ‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺑﻪ ﻋﻨﻮﺍﻥ ﺍﺑﺰﺍﺭﻱ ﺑﺮﺍﻱ ﺗﻮﺳﻌﻪ‬
‫ﺳﺮﻳﻊ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ﻭ ﺷﺎﻣﻞ ﻣﺮﺍﺣﻞ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﺗﺤﻠﻴﻞ ﻗﻄﻌﻪ ‪.‬‬
‫‪ -2‬ﺍﺻﻼﺡ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -3‬ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ‪.‬‬
‫‪ -4‬ﺗﻮﺳﻌﻪ ﻭ ﺟﺎﻣﻌﻴﺖ ‪.‬‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﻣﺒﺘﻨﻲ ﺑﺮﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ‬

‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬
‫ﺗﺤﻠﻴﻞ ﻗﻄﻌﺎﺕ‬ ‫ﺍﺻﻼﺡ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‬
‫ﺗﻮﺳﻌﻪ ﻭ ﺟﺎﻣﻌﻴﺖ‬ ‫ﺍﻋﺘﺒﺎﺭ ﺳﺘﺠﻲ ﺳﻴﺴﺘﻢ‬
‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ‬
 ‫ﺗﻜﺮﺍﺭ ﻓﺮﺍﻳﻨﺪ ‪:‬‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻓﺮﺍﻳﻨﺪ ﺩﺭ ﭘﺎﺳﺦ ﺑﻪ ﺗﻐﻴﻴﺮ ﺩﺭ ﺧﻮﺍﺳﺖ ﻫﺎ ‪ ،‬ﺗﻜﺮﺍﺭ ﺧﻮﺍﻫﺪ‬
‫ﺷﺪ ‪.‬‬
‫ﺩﻭ ﻣﺪﻝ ﻓﺮﺍﻳﻨﺪ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺗﻜﺮﺍﺭ ﻓﺮﺍﻳﻨﺪ ﺍﺭﺍﺋﻪ ﺷﺪﻧﺪ ‪.‬‬
‫)‪(Incremental Developing Model‬‬ ‫‪ -1‬ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﺪﺭﻳﺠﻲ ‪.‬‬
‫ﻣﺸﺨﺼﺎﺕ ﻧـﺮﻡ ﺍﻓﺰﺍﺭ‪،‬ﻃﺮﺍﺣـﻲ ﻭﭘﻴـﺎﺩﻩ ﺳـﺎﺯﻱ ﺑـﻪ ﺗﻌـﺪﺍﺩﻱ ﺍﺯﺑﺨﺸـﻬﺎ‬
‫ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺑﻪ ﻧﻮﺑﺖ ﺗﻮﺳﻌﻪ ﻣﻲ ﻳﺎﺑﺪ‪.‬‬
‫)‪(Spiral Developing Model‬‬ ‫‪ -2‬ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﻣﺎﺭﭘﻴﭽﻲ ‪.‬‬
‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﺑﺎ ﺷﺮﻭﻉ ﺍﺯﻳﻚ ﻃﺮﺡ ﻛﻠﻲ ﺑﺼﻮﺭﺕ ﻣﺎﺭﭘﻴﭻ ﺍﺩﺍﻣﻪ ﻣـﻲ‬
‫ﻳﺎﺑﺪ ﺗﺎ ﻛﻞ ﺳﻴﺴﺘﻢ ﺗﻮﺳﻌﻪ ﻳﺎﺑﺪ‪.‬‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﺪﺭﻳﺠﻲ‬
‫ﺍﻣﺘﻴﺎﺯﺍﺕ ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﺪﺭﻳﺠﻲ ‪:‬‬
‫‪ -1‬ﻻﺯﻡ ﻧﻴﺴﺖ ﻣﺸﺘﺮﻳﺎﻥ ﺻﺒﺮ ﻛﻨﻨﺪ ﺗـﺎ ﻛـﻞ ﺳﻴﺴـﺘﻢ ﺗﺤﻮﻳـﻞ ﺩﺍﺩﻩ ﺷـﻮﺩ‪.‬‬
‫ﺍﻭﻟﻴﻦ ﻣﺮﺣﻠﻪ ﺍﻱ ﻛﻪ ﺍﻧﺠﺎﻡ ﺷﺪ‪ ،‬ﺧﻮﺍﺳﺘﻪ ﻫـﺎﻱ ﺣﻴـﺎﺗﻲ ﺁﻥ ﺭﺍ ﭘﺎﺳـﺦ ﻣـﻲ‬
‫ﺩﻫﺪ ﻭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﻛﺎﺭﮔﺮﻓﺘﻪ ﺷﻮﺩ‪.‬‬
‫‪ -2‬ﻣﺸﺘﺮﻳﺎﻥ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺍﺯ ﻣﺮﺍﺣﻞ ﺍﻭﻟﻴﻪ ﺑﻪ ﻋﻨﻮﺍﻥ ﺍﻟﮕﻮ‪ ،‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻨﺪ ‪.‬‬
‫‪ -3‬ﺭﻳﺴﻚ ﻛﻤﺘﺮﻱ ﺩﺭ ﻣﻮﺭﺩ ﺧﺮﺍﺑﻲ ﭘﺮﻭژﻩ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪.‬‬
‫‪ -4‬ﭼﻮﻥ ﺳﺮﻭﻳﺲ ﻫﺎﻳﻲ ﺑﺎ ﺍﻭﻟﻮﻳﺖ ﺑﺎﻻﺗﺮ‪ ،‬ﺯﻭﺩﺗﺮﺗﺤﻮﻳـﻞ ﺩﺍﺩﻩ ﻣﻴﺸـﻮﻧﺪ‪،‬‬
‫ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﺨﺶ ﻫﺎﻱ ﻣﻬﻢ ﺳﻴﺴﺘﻢ ‪ ،‬ﺑﻴﺸﺘﺮ ﻣﻮﺭﺩ ﺗﺴﺖ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﻧﺪ ‪.‬‬

‫)‪(Extreme Programming‬‬
 ‫)‪(Incremental Developing Model‬‬ ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﺗﺪﺭﻳﺠﻲ‬

‫ﺗﻌﺮﻳﻒ ﻃﺮﺡ‬ ‫ﺍﻧﺘﺴﺎﺏ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﻃﺮﺍﺣﻲ ﻣﻌﻤﺎﺭﻱ‬

‫ﻛﻠﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﺑﻪ ﻣﺮﺍﺣﻞ‬ ‫ﺳﻴﺴﺘﻢ‬

‫ﺗﻮﺳﻌﻪ ﻳﻚ‬ ‫ﺳﻴﺴﺘﻢ‬

‫ﺗﺄﻳﻴﺪ ﻣﺮﺣﻠﻪ‬ ‫ﺟﺎﻣﻌﻴﺖ ﻣﺮﺣﻠﻪ‬ ‫ﺗﺄﻳﻴﺪ ﺳﻴﺴﺘﻢ‬
‫ﻣﺮﺣﻠﻪ ﺳﻴﺴﺘﻢ‬ ‫ﻧﻬﺎﻳﻲ‬
 ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﻣﺎﺭﭘﻴﭽﻲ‬
‫ﺍﻳﻦ ﻣﺪﻝ ﻓﺮﺍﻳﻨﺪ ﻧـﺮﻡ ﺍﻓـﺰﺍﺭ ﺭﺍ ﺑﺼـﻮﺭﺕ ﺩﻧﺒﺎﻟـﻪ ﻫـﺎﻳﻲ ﺍﺯ ﻓﻌﺎﻟﻴـﺖ ﻫـﺎ ﻧﺸـﺎﻥ‬
‫ﻣﻴﺪﻫﺪﻛﻪ ﺍﺯ ﻓﺮﺍﻳﻨﺪﻱ ﺑﻪ ﻓﺮﺍﻳﻨﺪ ﺩﻳﮕﺮ ﻋﻘﺒﮕﺮﺩ ﻣﻲ ﺷﻮﺩ‪ .‬ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺑﺼﻮﺭﺕ‬
‫ﻣﺎﺭﭘﻴﭻ ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫ﻫﺮ ﺣﻠﻘﻪ ﺩﺭﻣﺎﺭﭘﻴﭻ ﺑﻪ ﭼﻬﺎﺭ ﻗﻄﺎﻉ ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﺩ ‪:‬‬
‫‪ -1‬ﺗﻨﻈﻴﻢ ﻫﺪﻑ ‪.‬‬
‫‪ -2‬ﺑﺮﺁﻭﺭﺩ ﻭ ﻛﺎﻫﺶ ﺭﻳﺴﻚ ‪.‬‬
‫‪ -3‬ﺗﻮﺳﻌﻪ ﻭ ﺍﻋﺘﺒﺎﺭ ﺳﻨﺠﻲ ‪.‬‬
‫‪ -4‬ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ‪.‬‬
(Spiral Developing Model) ‫ﻣﺪﻝ ﺗﻮﺳﻌﻪ ﻣﺎﺭﭘﻴﭽﻲ‬
 ‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻓﺮﺍﻳﻨﺪ ‪:‬‬
‫ﻫﺮ ﻓﺮﺍﻳﻨﺪ ﺩﺍﺭﺍﻱ ﭼﻬﺎﺭ ﻓﻌﺎﻟﻴﺖ ﺍﺻﻠﻲ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻳﺎ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‪.‬‬
‫)‪(Requirment Specification / Requirment Engineering‬‬
‫‪ -2‬ﺗﻮﺳﻌﻪ ﻳﺎ ﻃﺮﺍﺣﻲ ﻭ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫)‪(Software Developing / Software Designing & Implementation‬‬

‫)‪(Software Validation‬‬ ‫‪ -3‬ﺍﻋﺘﺒﺎﺭ ﺳﻨﺠﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬

‫)‪(Software Evolution‬‬ ‫‪ -4‬ﺗﻜﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
 ‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪ :‬ﻓﺮﺍﻳﻨﺪ ﺩﺭﻙ ﻭ ﺗﻌﺮﻳﻒ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻣﻮﺭﺩﻧﻴﺎﺯ‬
‫ﺳﻴﺴﺘﻢ ﻭﻣﺸﺨﺺ ﻛﺮﺩﻥ ﻗﻴﺪﻫﺎﻱ ﺭﻭﻱ ﻋﻤﻠﻴﺎﺕ ﻭ‬
‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ‪.‬‬

‫ﻣﺮﺍﺣﻞ ﺍﺻﻠﻲ ﺩﺭ ﻓﺮﺍﻳﻨﺪ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪:‬‬

‫‪ -1‬ﻣﻄﺎﻟﻌﻪ ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ ‪.‬‬
‫‪ -2‬ﺍﺳﺘﺨﺮﺍﺝ ﻭ ﺗﺤﻠﻴﻞ ﺧﻮﺍﺳﺘﻪ ‪.‬‬
‫‪ -3‬ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -4‬ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻣﻄﺎﻟﻌﻪ‬ ‫ﺍﺳﺘﺨﺮﺍﺝ ﻭﺗﺤﻠﻴﻞ‬
‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬ ‫ﺧﻮﺍﺳﺘﻪ‬
‫ﻣﺸﺨﺼﺎﺕ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ‬
‫ﮔﺰﺍﺭﺵ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬
‫ﻣﺪﻝ ﻫﺎﻱ‬
‫ﺳﻴﺴﺘﻢ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﻛﺎﺭﺑﺮ ﻭ ﺳﻴﺴﺘﻢ‬
‫ﺳﻨﺪ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
 ‫ﻁﺮﺍﺣﯽ ﻭ ﭘﻴﺎﺩﻩ ﺳﺎﺯی ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻓﺮﺍﻳﻨﺪ ﺗﺒﺪﻳﻞ ﻣﺸﺨﺼﺎﺕ ﺳﻴﺴﺘﻢ ﺑﻪ ﺳﻴﺴﺘﻢ ﺍﺟﺮﺍﻳﯽ‬
‫ﺍﺳﺖ ‪.‬‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎی ﻓﺮﺍﻳﻨﺪ ﻁﺮﺍﺣﯽ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫)‪(Architectural Design‬‬

‫)‪(Abstract Specification‬‬ ‫ﻁﺮﺍﺣﯽ ﻣﻌﻤﺎﺭی ‪.‬‬ ‫‪-1‬‬

‫)‪(Interface Design‬‬ ‫ﻣﺸﺨﺼﺎﺕ ﺍﻧﺘﺰﺍﻋﯽ ‪.‬‬ ‫‪-2‬‬
‫)‪(Component Design‬‬ ‫ﻁﺮﺍﺣﯽ ﻭﺍﺳﻂ ‪.‬‬ ‫‪-3‬‬
‫)‪(Data Structure Design‬‬ ‫ﻁﺮﺍﺣﯽ ﻣﻮﻟﻔﻪ ‪.‬‬ ‫‪-4‬‬
‫)‪(Algorithm Design‬‬ ‫ﻁﺮﺍﺣﯽ ﺳﺎﺧﺘﻤﺎﻥ ﺩﺍﺩﻩ ﻫﺎ ‪.‬‬ ‫‪-5‬‬
‫ﻁﺮﺍﺣﯽ ﺍﻟﮕﻮﺭﻳﺘﻢ ‪.‬‬ ‫‪-6‬‬
 ‫ﻣﺪﻝ ﮐﻠﯽ ﻓﺮﺍﻳﻨﺪ ﻁﺮﺍﺣﯽ‬
‫ﺧﺮﻭﺟﯽ ﻁﺮﺍﺣﯽ ‪ ،‬ﻣﺸﺨﺼﺎﺕ ﻣﺮﺣﻠﻪ ﺑﻌﺪی ﺍﺳﺖ ‪.‬‬
‫ﻫﺮﻓﻌﺎﻟﻴﺖ‬
 ‫ﺭﻭﺵ ﻫﺎی ﻁﺮﺍﺣﯽ‬
‫ﺭﻭﺵ ﻫﺎی ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ﺍﺯ ﻳﮏ ﻳﺎ ﭼﻨﺪ ﻣﺪﻝ‬
‫ﺳﻴﺴﺘﻢ ﮐﻪ ﺩﺭ ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ ﭘﺸﺘﻴﺒﺎﻧﯽ ﻣﯽ‬
‫ﮐﻨﺪ‪ ،‬ﻭﻟﯽ ﻣﺸﮑﻼﺕ ﺯﻳﺎﺩی ﺩﺍﺭﺩ‪.‬‬
‫ﺷﯽء ‪.‬‬ ‫ﻣﺪﻝ‬ ‫‪-1‬‬
‫ﺗﻮﺍﻟﯽ ‪.‬‬ ‫ﻣﺪﻝ‬ ‫‪-2‬‬
‫ﺗﻐﻴﻴﺮ ﺣﺎﻟﺖ ‪.‬‬ ‫ﻣﺪﻝ‬ ‫‪-3‬‬
‫ﺳﺎﺧﺘﺎﺭی ‪.‬‬ ‫ﻣﺪﻝ‬ ‫‪-4‬‬
‫ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ‪.‬‬ ‫ﻣﺪﻝ‬ ‫‪-5‬‬
 ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻭ ﺍﺷﻜﺎﻟﺰﺩﺍﻳﻲ‬
‫ﺍﺷﻜﺎﻟﺰﺩﺍﻳﻲ‪ :‬ﻣﻌﻤﻮﻻ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﺎﻥ ﻛﺪﻫﺎﻳﻲ ﺭﺍ ﻛﻪ ﻧﻮﺷﺘﻪ ﺍﻧﺪ ‪ ،‬ﺗﺴﺖ‬
‫ﻣﻴﻜﻨﻨﺪ‪ .‬ﻓﺮﺍﻳﻨﺪ ﺍﺷﻜﺎﻟﺰﺩﺍﻳﻲ ﺑﺎ ﻓﺮﺍﻳﻨﺪ ﺗﺴﺖ ‪ ،‬ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ‪.‬‬

‫)‪(V&V: Validation & Verification‬‬ ‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺳﻌﻲ ﻣﻲ ﻛﻨﺪ ﻧﺸﺎﻥ ﺩﻫﺪ ﻛﻪ ﺳﻴﺴﺘﻢ ﺑﺎ ﻣﺸﺨﺼﺎﺗﺶ‬
‫ﺟﻮﺭ ﺩﺭ ﻣﻲ ﺁﻳﺪ ﻭﺍﻧﺘﻈﺎﺭﺍﺕ ﺧﺮﻳﺪﺍﺭ ﺳﻴﺴﺘﻢ ﺭﺍ ﺑﺮﺁﻭﺭﺩﻩ ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫ﻣﺮﺍﺣﻞ ﻓﺮﺍﻳﻨﺪ ﺗﺴﺖ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ‪:‬‬
‫‪ -1‬ﺗﺴﺖ ﻣﻮﻟﻔﻪ ﻭ ﻭﺍﺣﺪ ‪.‬‬
‫‪ -4‬ﺗﺴﺖ ﺳﻴﺴﺘﻢ ‪.‬‬ ‫‪ -2‬ﺗﺴﺖ ﭘﻴﻤﺎﻧﻪ ‪.‬‬
‫‪ -5‬ﺗﺴﺖ ﭘﺬﻳﺮﺵ )‪.(α , β‬‬ ‫‪ -3‬ﺗﺴﺖ ﺯﻳﺮﺳﻴﺴﺘﻢ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﺍﺷﻜﺎﻟﺰﺩﺍﻳﻲ ‪:‬‬

‫ﻃﺮﺍﺣﻲ‬ ‫ﺗﺴﺖ ﻣﺠﺪﺩ‬

‫ﻳﺎﻓﺘﻦ ﺧﻄﺎ‬ ‫ﺗﺮﻣﻴﻢ ﺧﻄﺎ‬
‫ﺗﺮﻣﻴﻢ ﺧﻄﺎ‬ ‫ﺑﺮﻧﺎﻣﻪ‬

‫ﻓﺮﺍﻳﻨﺪ ﺗﺴﺖ ‪:‬‬

‫ﺗﺴﺖ ﻣﻮﻟﻔﻪ‬ ‫ﺗﺴﺖ ﭘﻴﻤﺎﻧﻪ‬ ‫ﺗﺴﺖ ﺯﻳﺮﺳﻴﺴﺘﻢ‬ ‫ﺗﺴﺖ ﺳﻴﺴﺘﻢ‬ ‫ﺗﺴﺖ ﭘﺬﻳﺮﺵ‬
‫ﻣﺮﺍﺣﻞ ﺗﺴﺖ ﺩﺭﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
 ‫ﺗﻜﺎﻣﻞ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫ﺷﺎﻣﻞ ﺍﻧﺠﺎﻡ ﺗﻐﻴﻴﺮﺍﺕ ﭘﺲ ﺍﺯ ﺑﻜﺎﺭﮔﻴﺮﻱ ﺍﺳﺖ ‪.‬‬

‫ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬ ‫ﺍﺭﺯﻳﺎﺑﻲ ﺳﻴﺴﺘﻢ ﻫﺎﻱ‬ ‫ﭘﻴﺸﻨﻬﺎﺩ ﺗﻐﻴﻴﺮﺍﺕ‬ ‫ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﺳﻴﺴﺘﻢ‬ ‫ﻣﻮﺟﻮﺩ‬ ‫ﺳﻴﺴﺘﻢ‬ ‫ﺳﻴﺴﺘﻢ‬

‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺟﻮﺩ‬ ‫ﺳﻴﺴﺘﻢ ﺟﺪﻳﺪ‬

 ‫ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﻪ ﻛﻤﻚ ﻛﺎﻣﭙﻴﻮﺗﺮ‬
‫)‪(CASE: Computer Aided Software Engineering‬‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺑﻜﺎﺭﻣﻲ ﺭﻭﺩ‬
‫ﻭ ﺷﺎﻣﻞ ﻓﻌﺎﻟﻴﺘﻬﺎﻱ ﺯﻳﺮ ﺍﺳﺖ‪:‬‬
‫‪ -1‬ﺗﻮﺳﻌﻪ ﻣﺪﻝ ﻫﺎﻱ ﮔﺮﺍﻓﻴﻜﻲ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -2‬ﺩﺭﻙ ﻃﺮﺍﺣﻲ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺩﻳﻜﺸﻨﺮﻱ ‪.‬‬
‫‪ -3‬ﺗﻮﻟﻴﺪ ﻭﺍﺳﻂ ﻛﺎﺭﺑﺮ ‪.‬‬
‫‪ -4‬ﺍﺷﻜﺎﻟﺰﺩﺍﻳﻲ ﺑﺮﻧﺎﻣﻪ ﺍﺯ ﻃﺮﻳﻖ ﺁﻣﺎﺩﻩ ﺳﺎﺯﻱ ﺩﺍﺩﻩ ﻫﺎﻳﻲ ﺭﺍﺟﻊ ﺑﻪ ﺑﺮﻧﺎﻣﻪ‬
‫ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ‪.‬‬
‫‪ -5‬ﺗﺮﺟﻤﻪ ﺧﻮﺩﻛﺎﺭ ﺑﺮﻧﺎﻣﻪ ﻫﺎ ﺍﺯ ﻧﺴﺨﻪ ﻗﺪﻳﻤﻲ ﺑﻪ ﻧﺴﺨﻪ ﻫﺎﻱ ﺟﺪﻳﺪ ﺁﻥ ‪.‬‬
 ‫ﺩﻳﺪﮔﺎﻫﻬﺎ ﺑﺮﺍﻱ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﻛﻴﺲ‪:‬‬
‫‪ -1‬ﺩﻳﺪﮔﺎﻩ ﻋﻤﻠﻜﺮﺩﻱ ‪.‬‬
‫‪ -2‬ﺩﻳﺪﮔﺎﻩ ﻓﺮﺍﻳﻨﺪﻱ ‪.‬‬
‫‪ -3‬ﺩﻳﺪﮔﺎﻩ ﺟﺎﻣﻌﻴﺖ ‪.‬‬

‫ﭘﻴﺸﻨﻬﺎﺩ ﻓﻮﮔﺘﺎ ﺑﺮﺍﻱ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻴﺲ‪:‬‬

‫)‪(Tools‬‬
‫‪ -1‬ﺍﺑﺰﺍﺭﻫﺎ‬
‫)‪(Workbenches‬‬ ‫‪ -2‬ﻣﺤﻴﻂ ﻛﺎﺭﻱ‬
‫)‪(environments‬‬ ‫‪ -3‬ﻣﺤﻴﻂ‬
Tools, workbenches, environments
‫)‪(RUP: Rational Unified Process‬‬ ‫ﻓﺮﺍﻳﻨﺪ ﻳﮑﻨﻮﺍﺧﺖ ﮔﻮﻳﺎ‬
‫‪ RUP‬ﻣﯽ ﮔﻮﻳﺪ ﻣﺪﻝ ﻫﺎی ﻓﺮﺍﻳﻨﺪ ﻋﺎﺩی‪ ،‬ﻧﻤﺎی ﻳﮑﺘﺎﻳﯽ ﺍﺯ‬
‫ﻓﺮﺍﻳﻨﺪ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﯽ ﮐﻨﺪ‪.‬‬

‫ﺍﺯ ﺳﻪ ﺩﻳﺪﮔﺎﻩ ﺗﻮﺻﻴﻒ ﺷﺪﻩ ﺍﺳﺖ ‪:‬‬

‫‪ -1‬ﺩﻳﺪﮔﺎﻩ ﭘﻮﻳﺎ ‪ :‬ﻣﺮﺍﺣﻞ ﻣﺪﻝ ﺭﺍ ﺩﺭ ﻁﻮﻝ ﺯﻣﺎﻥ ﻧﺸﺎﻥ ﻣﯽ‬
‫ﺩﻫﺪ‪.‬‬
‫‪ -2‬ﺩﻳﺪﮔﺎﻩ ﺍﻳﺴﺘﺎ ‪ :‬ﻓﻌﺎﻟﻴﺖ ﻫﺎی ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﻓﺮﺍﻳﻨﺪ ﺭﺍ ﻧﺸﺎﻥ‬
‫ﻣﯽ ﺩﻫﺪ‪.‬‬
‫‪ -3‬ﺩﻳﺪﮔﺎﻩ ﻋﻤﻠﯽ ‪ :‬ﺍﻋﻤﺎﻝ ﻣﻨﺎﺳﺒﯽ ﮐﻪ ﺑﺎﻳﺪ ﺩﺭ ﺍﺛﻨﺎی ﻓﺮﺍﻳﻨﺪ‬
‫ﺍﺟﺮﺍ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﯽ ﮐﻨﺪ ‪.‬‬
 ‫ﻣﺮﺍﺣﻞ ﻣﻮﺟﻮﺩ ﺩﺭ ‪RUP‬‬

‫‪ -1‬ﺷﺮﻭﻉ ‪ :‬ﺍﻳﺠﺎﺩ ﻳﻚ ﺣﺎﻟﺖ ﺗﺠﺎﺭﻱ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ ‪.‬‬

‫‪ -2‬ﺍﻛﺘﺸﺎﻑ ‪ :‬ﺗﻮﺳﻌﻪ ﻭﺩﺭﻙ ﺩﺍﻣﻨﻪ ﻣﺴﺌﻠﻪ‪ ،‬ﺍﻳﺠﺎﺩ ﭼﺎﺭﭼﻮﺏ ﻣﻌﻤﺎﺭﻱ‬
‫ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ‪ ،‬ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﭘﺮﻭژﻩ ﻭ ﺷﻨﺎﺳﺎﻳﻲ ﺭﻳﺴﻚ ﻫﺎﻱ ﻣﻬﻢ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -3‬ﺳﺎﺧﺖ ‪ :‬ﺑﺎﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‪ ،‬ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻭ ﺗﺴﺖ ﺳﺮﻭﻛﺎﺭ ﺩﺍﺭﺩ‪.‬‬
‫‪ -4‬ﺍﻧﺘﻘﺎﻝ ‪ :‬ﺍﻳﺠﺎﺩ ﻳﻚ ﺳﻴﺴﺘﻢ ﻣﺴﺘﻨﺪ ﺳﺎﺯﻱ ﺷﺪﻩ ‪.‬‬
‫ﺩﻳﺪﮔﺎﻩ ﻋﻤﻠﻲ ﺷﺶ ﻋﻤﻞ ﺧﻮﺏ ﭘﻴﺸﻨﻬﺎﺩ ﻣﻲ ﻛﻨﺪ ‪:‬‬
‫‪ -1‬ﺗﻮﺻﻴﻒ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﻪ ﻃﻮﺭ ﺗﻜﺮﺍﺭﻱ ‪.‬‬
‫‪ -2‬ﻣﺪﻳﺮﻳﺖ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -3‬ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﺒﺘﻨﻲ ﺑﺮ ﻗﻄﻌﻪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ ‪.‬‬
‫‪ -4‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺭﺍ ﺑﻄﻮﺭ ﻭﻳﮋﻭﺍﻝ ﻣﺪﻝ ﺳﺎﺯﻱ ﻛﻨﻴﺪ ‪.‬‬
‫‪ -5‬ﻛﻴﻔﻴﺖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺭﺍ ﻣﺪﻝ ﺳﺎﺯﻱ ﻛﻨﻴﺪ ‪.‬‬
‫‪ -6‬ﺗﻐﻴﻴﺮﺍﺕ ﺩﺭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺭﺍ ﻛﻨﺘﺮﻝ ﻛﻨﻴﺪ ‪.‬‬
‫ﺟﺮﻳﺎﻧﻬﺎﻱ ﻛﺎﺭ ﺍﻳﺴﺘﺎ ﺩﺭ‪RUP‬‬
‫‪ -1‬ﻣﺪﻝ ﺳﺎﺯﻱ ﺗﺠﺎﺭﻱ ‪.‬‬
‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -3‬ﺗﺤﻠﻴﻞ ﻭ ﻃﺮﺍﺣﻲ ‪.‬‬
‫‪ -4‬ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ‪.‬‬
‫‪ -5‬ﺗﺴﺖ ‪.‬‬
‫‪ -6‬ﺍﺳﺘﻘﺮﺍﺭ‪.‬‬
‫‪ -7‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﻭ ﺗﻐﻴﻴﺮ ﻣﺪﻳﺮﻳﺖ ‪.‬‬
‫‪ -8‬ﻣﺪﻳﺮ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -9‬ﻣﺤﻴﻂ ‪.‬‬
 ‫ﻓﺼﻞ‪7‬‬

‫ﻣﺪﻳﺮﻳﺖ ﭘﺮﻭژﻩ‬
 ‫ﺗﻔﺎﻭﺕ ﻣﻬﻨﺪﺳﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﺎ ﻣﻬﻨﺪﺳﻲ ﻫﺎﻱ ﺩﻳﮕﺮ ‪:‬‬

‫‪ -1‬ﻣﺤﺼﻮﻝ ﻧﺎﻣﻠﻤﻮﺱ ﺍﺳﺖ ‪.‬‬

‫‪ -2‬ﻓﺮﺍﻳﻨﺪ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﺳﺘﺎﻧﺪﺍﺭﺩﻱ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ‪.‬‬
‫‪ -3‬ﭘﺮﻭژﻩ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺑﺰﺭگ ‪ ،‬ﺍﻏﻠﺐ ﭘﺮﻭژﻩ ﻫﺎﻱ ﻣﻨﺤﺼﺮﺑﻪ ﻓﺮﺩﻱ‬
‫ﻫﺴﺘﻨﺪ ‪.‬‬
 ‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻣﺪﻳﺮﻳﺘﻲ‬
‫ﺍﻏﻠﺐ ﻣﺪﻳﺮﺍﻥ ﻣﺴﺌﻮﻟﻴﺖ ﻫﺎﻱ ﺯﻳﺮ ﺭﺍ ﺩﺍﺭﻧﺪ ‪:‬‬
‫‪ -1‬ﻧﻮﺷﺘﻦ ﻃﺮﺡ )ﭘﻴﺸﻨﻬﺎﺩ( ‪.‬‬
‫‪ -2‬ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﻭ ﺯﻣﺎﻧﺒﻨﺪﻱ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -3‬ﻫﺰﻳﻨﻪ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -4‬ﻧﻈﺎﺭﺕ ﻭ ﻣﺮﻭﺭ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -5‬ﺍﻧﺘﺨﺎﺏ ﻭ ﺍﺭﺯﻳﺎﺑﻲ ﭘﺮﺳﻨﻞ ‪.‬‬
‫‪ -6‬ﻧﻮﺷﺘﻦ ﻭ ﺍﺭﺍﺋﻪ ﮔﺰﺍﺭﺵ ‪.‬‬
 ‫ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﭘﺮﻭژﻩ‬
‫ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﻳﻚ ﻓﺮﺍﻳﻨﺪ ﺗﻜﺮﺍﺭﻱ ﺍﺳﺖ ﻛﻪ ﻭﻗﺘﻲ ﻛﺎﻣﻞ ﻣﻲ ﺷﻮﺩ ﻛﻪ‬
‫ﺧﻮﺩ ﭘﺮﻭژﻩ ﻛﺎﻣﻞ ﺷﺪﻩ ﺑﺎﺷﺪ ﻭ ﺷﺎﻣﻞ ﺑﺨﺶ ﻫﺎﻱ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﻣﻘﺪﻣﻪ ‪.‬‬
‫‪ -2‬ﺳﺎﺯﻣﺎﻧﺪﻫﻲ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -3‬ﺗﺤﻠﻴﻞ ﺭﻳﺴﻚ ‪.‬‬
‫‪ -4‬ﻣﻨﺎﺑﻊ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻭ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ‪.‬‬
‫‪ -5‬ﺗﻮﻗﻒ ﻛﺎﺭ ‪.‬‬
‫‪ -6‬ﺯﻣﺎﻧﺒﻨﺪﻱ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -7‬ﺭﺍﻫﻜﺎﺭﻫﺎﻱ ﻧﻈﺎﺭﺕ ﻭ ﮔﺰﺍﺭﺵ ‪.‬‬
 ‫ﻧﻘﺎﻁ ﻋﻄﻒ ﻗﻄﻌﺎﺕ ﻗﺎﺑﻞ ﺗﺤﻮﻳﻞ‬
‫ﻧﻘﻄﻪ ﻋﻄﻒ ‪ ،‬ﻧﻘﻄﻪ ﭘﺎﻳﺎﻧﻲ ﻳﻚ ﻓﻌﺎﻟﻴﺖ ﻓﺮﺍﻳﻨﺪ ﻧﺮﻡ ﺍﻓﺰﺍﺭﺍﺳﺖ‪.‬‬
‫)ﮔﺰﺍﺭﺵ ﺭﺳﻤﻲ(‬
‫ﻗﻄﻌﻪ ﻗﺎﺑﻞ ﺗﺤﻮﻳﻞ ‪ ،‬ﻧﺘﻴﺠﻪ ﺍﻱ ﺍﺯ ﭘﺮﻭژﻩ ﺍﺳﺖ ﻛﻪ ﺑﻪ ﻣﺸﺘﺮﻱ ﺗﺤﻮﻳﻞ ﺩﺍﺩﻩ‬
‫ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﻧﻘﺎﻁ ﻋﻄﻒ ﺩﺭ ﻓﺮﺍﻳﻨﺪ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻣﻄﺎﻟﻌﻪ‬ ‫ﺗﺤﻠﻴﻞ‬ ‫ﺗﻮﺳﻌﻪ‬ ‫ﻣﻄﺎﻟﻌﻪ‬ ‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬
‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ‬ ‫ﻃﺮﺍﺣﻲ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎ‬
‫ﮔﺰﺍﺭﺵ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬ ‫ﮔﺰﺍﺭﺵ‬ ‫ﻃﺮﺍﺣﻲ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬ ‫ﻛﺎﺭﺑﺮ‬ ‫ﺍﺭﺯﻳﺎﺑﻲ‬ ‫ﻣﻌﻤﺎﺭﻱ‬ ‫ﺳﻴﺴﺘﻢ‬
‫ﻧﻘﺎﻁ ﻋﻄﻒ‬
 ‫ﺯﻣﺎﻧﺒﻨﺪﻱ ﭘﺮﻭژﻩ‬
‫ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﻛﻞ ﻛﺎﺭ ﭘﺮﻭژﻩ ﺭﺍ ﺑﻪ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ‬
‫ﺗﻘﺴﻴﻢ ﻣﻲ ﻛﻨﺪ ﻭ ﺯﻣﺎﻥ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺑﺮﺍﻱ ﻛﺎﻣﻞ ﻛﺮﺩﻥ ﺍﻳﻦ‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎ ﺭﺍ ﺑﺮﺁﻭﺭﺩ ﻣﻲ ﻛﻨﺪ‪.‬‬
‫ﻓﺮﺍﻳﻨﺪ ﺯﻣﺎﻧﺒﻨﺪﻱ ﭘﺮﻭژﻩ ‪:‬‬

‫ﺷﻨﺎﺳﺎﻳﻲ‬ ‫ﺷﻨﺎﺳﺎﻳﻲ‬ ‫ﺑﺮﺁﻭﺭﺩ ﻣﻨﺎﺑﻊ‬ ‫ﺗﺨﺼﻴﺺ ﺍﻓﺮﺍﺩ‬ ‫ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩﺍﺭﻫﺎﻱ‬

‫ﻓﻌﺎﻟﻴﺖ ﻫﺎ‬ ‫ﻭﺍﺑﺴﺘﮕﻴﻬﺎﻱ ﭘﺮﻭژﻩ‬ ‫ﺑﺮﺍﻱ ﻓﻌﺎﻟﻴﺖ ﻫﺎ‬ ‫ﺑﺮﺍﻱ ﻓﻌﺎﻟﻴﺖ ﻫﺎ‬ ‫ﭘﺮﻭژﻩ‬

‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬ ‫ﻧﻤﻮﺩﺍﺭ ﻫﺎﻱ ﻓﻌﺎﻟﻴﺖ ﻭ‬

‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬ ‫ﻧﻤﻮﺩﺍﺭﻫﺎﻱ ﻣﻴﻠﻪ ﺍﻱ‬
 ‫ﻧﻤﻮﺩﺍﺭﻫﺎﻱ ﻣﻴﻠﻪ ﺍﻱ ﻭ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻌﺎﻟﻴﺖ‪:‬‬
‫ﺍﻳﻦ ﻧﻤﻮﺩﺍﺭﻫﺎ ﻧﺸﺎﻧﻪ ﮔﺬﺍﺭﻱ ﻫﺎﻱ ﮔﺮﺍﻓﻴﻜﻲ ﺍﻧﺪ ﻛﻪ ﺑﺮﺍﻱ ﺗﺸﺮﻳﺢ ﺯﻣﺎﻧﺒﻨﺪﻱ‬
‫ﭘﺮﻭژﻩ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺭﻭﻧﺪ‪.‬‬
‫ﻧﻤﻮﺩﺍﺭﻫﺎﻱ ﻣﻴﻠﻪ ﺍﻱ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ﭼﻪ ﻛﺴﻲ ﻣﺴﺌﻮﻝ ﻫﺮ ﻓﻌﺎﻟﻴﺖ‬
‫ﺍﺳﺖ ﻭ ﻓﻌﺎﻟﻴﺖ ﭼﻪ ﺯﻣﺎﻧﻲ ﺷﺮﻭﻉ ﻣﻲ ﺷﻮﺩ ﻭ ﻛﻲ ﺧﺎﺗﻤﻪ ﻣﻴﺎﺑﺪ‪.‬‬
‫ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻌﺎﻟﻴﺖ ﻭﺍﺑﺴﺘﮕﻲ ﻫﺎﻱ ﺑﻴﻦ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺩﺭ‬
‫ﭘﺮﻭژﻩ ﺭﺍ ﻧﺸﺎﻥ ﻣﻲ ﺩﻫﺪ‪.‬‬
‫ﻣﺴﻴﺮ ﺑﺤﺮﺍﻧﻲ‪:‬‬
‫ﻛﻤﺘﺮﻳﻦ ﺯﻣﺎﻥ ﻻﺯﻡ ﺑﺮﺍﻱ ﺍﺗﻤﺎﻡ ﭘﺮﻭژﻩ ﻫﺎ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺑﺎ ﺩﺭﻧﻈﺮ ﮔﺮﻓﺘﻦ‬
‫ﻃﻮﻻﻧﻲ ﺗﺮﻳﻦ ﻣﺴﻴﺮ ﺩﺭ ﮔﺮﺍﻑ ﻓﻌﺎﻟﻴﺖ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺖ ‪.‬‬
‫ﻛﻞ ﺯﻣﺎﻧﺒﻨﺪﻱ ﭘﺮﻭژﻩ ﺑﻪ ﻣﺴﻴﺮ ﺑﺤﺮﺍﻧﻲ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ ‪.‬‬
‫ﻓﻌﺎﻟﻴﺖ‬ ‫ﻣﺪﺕ )ﺭﻭﺯ(‬ ‫ﻭﺍﺑﺴﺘﮕﻲ ﻫﺎ‬
‫‪T1‬‬ ‫‪8‬‬
‫‪T2‬‬ ‫‪15‬‬
‫‪T3‬‬ ‫‪15‬‬ ‫)‪T1(M1‬‬
‫‪T4‬‬ ‫‪10‬‬
‫‪T5‬‬ ‫‪10‬‬ ‫)‪T2 , T4(M2‬‬
‫‪T6‬‬ ‫‪5‬‬ ‫)‪T1 , T2(M3‬‬
‫‪T7‬‬ ‫‪20‬‬ ‫)‪T1(M1‬‬
‫‪T8‬‬ ‫‪25‬‬ ‫)‪T4(M5‬‬
‫‪T9‬‬ ‫‪15‬‬ ‫)‪T3 , T6(M4‬‬
‫‪T10‬‬ ‫‪15‬‬ ‫)‪T5 , T7(M7‬‬
‫‪T11‬‬ ‫‪7‬‬ ‫)‪T9(M6‬‬
‫‪T12‬‬ ‫‪10‬‬ ‫)‪T11(M8‬‬

‫ﻣﺪﺕ ﻭﺍﺑﺴﺘﮕﻲ ﻫﺎﻱ ﺑﻴﻦ ﻓﻌﺎﻟﻴﺖ ﻫﺎ‬

 15 days
14/7/2012 15 days
T9
M1 T3
8 days 4/8/2012 25/8/2012

T1 M4 M6
5 days
4/7/2012 25/7/2012 T6
7 days
Start M3
T11
20 days
15 days T7 11/8/2012 5/9/2012
T2 M8
M7
10 days 25/7/2012 10 days
T4 M2 T5 10 days
15 days
T12
18/7/2012 T10
M5
25 days

T8 Finish

‫ﺷﺒﻜﻪ ﻓﻌﺎﻟﻴﺖ‬
 15 days
14/7/2012 15 days
T9
M1 T3
8 days 4/8/2012 25/8/2012

T1 M4 M6
5 days
4/7/2012 25/7/2012 T6
7 days
Start M3
T11
20 days
15 days T7 11/8/2012 5/9/2012
T2 M8
M7
10 days 25/7/2012 10 days
T4 M2 T5 10 days
15 days
T12
18/7/2012 T10
M5
25 days

T8 Finish

(‫ﺷﺒﻜﻪ ﻓﻌﺎﻟﻴﺖ )ﻣﺴﻴﺮ ﺑﺤﺮﺍﻧﻲ‬

 4/7 11/7 18/7 25/7 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9

X Start
T4
T1
T2
M1X
T7
T3
M5X
T8
M3 X
M2 X
T6
T5
X M4
T9
M7X
T10
X M6
T11
X M8
T12
X Finish
(‫ﻧﻤﻮﺩﺍﺭ ﻣﻴﻠﻪ ﺍی ﻓﻌﺎﻟﻴﺖ )ﮔﺎﻧﺖ‬
 4/7 11/7 18/7 25/7 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9

X Start
T4
T1
T2
M1X
T7
T3
M5X
T8
M3 X
M2 X
T6
T5
X M4
T9
M7X
T10
X M6
T11
X M8
T12
X Finish
(‫ﻧﻤﻮﺩﺍﺭ ﻣﻴﻠﻪ ﺍی ﻓﻌﺎﻟﻴﺖ )ﮔﺎﻧﺖ‬
 4/7 11/7 18/7 25/7 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9

X Start
T4
T1
T2
M1X
T7
T3
M5X
T8
M3 X
M2 X
T6
T5
X M4
T9
M7 X
T10
X M6
T11
X M8
T12
X Finish
(‫ﻧﻤﻮﺩﺍﺭ ﻣﻴﻠﻪ ﺍﻱ ﻓﻌﺎﻟﻴﺖ )ﮔﺎﻧﺖ‬
 ‫ﻣﺪﻳﺮﻳﺖ ﺭﻳﺴﻚ‬
‫ﺭﻳﺴﻚ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺷﺮﺍﻳﻂ ﻧﺎﻣﻄﻠﻮﺑﻲ ﺩﺍﻧﺴﺖ ﻛﻪ ﻭﺍﻗﻌﺎَ ﺭﺥ ﻣﻲ ﺩﻫﻨﺪ‪.‬‬
‫ﺭﻳﺴﻚ ﻫﺎﻱ ﭘﺮﻭژﻩ ‪ ،‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺩﺭ ﺣﺎﻝ ﺗﻮﺳﻌﻪ ﻭ ﺳﺎﺯﻣﺎﻥ ﺭﺍ ﺗﻬﺪﻳﺪ ﻣﻲ‬
‫ﻛﻨﻨﺪ ‪.‬‬

‫ﺍﻳﻦ ﺩﺳﺘﻪ ﺍﺯ ﺭﻳﺴﻚ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺗﻌﺮﻳﻒ ﻛﺮﺩ ‪:‬‬

‫‪ -1‬ﺭﻳﺴﻚ ﻫﺎﻱ ﭘﺮﻭژﻩ ‪.‬‬
‫‪ -2‬ﺭﻳﺴﻚ ﻫﺎﻱ ﻣﺤﺼﻮﻝ ‪.‬‬
‫‪ -3‬ﺭﻳﺴﻚ ﻫﺎﻱ ﻛﺎﺭﻱ ‪.‬‬
‫ﻓﺮﺍﻳﻨﺪ ﻣﺪﻳﺮﻳﺖ ﺭﻳﺴﻚ ﺷﺎﻣﻞ ﻣﺮﺍﺣﻞ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬

‫‪ -1‬ﺷﻨﺎﺳﺎﻳﻲ ﺭﻳﺴﻚ ‪.‬‬

‫‪ -2‬ﺗﺤﻠﻴﻞ ﺭﻳﺴﻚ ‪.‬‬
‫‪ -3‬ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﺭﻳﺴﻚ ‪.‬‬
‫‪ -4‬ﻧﻈﺎﺭﺕ ﺑﺮ ﺭﻳﺴﻚ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﻣﺪﻳﺮﻳﺖ ﺭﻳﺴﻚ‬

‫ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ‬ ‫ﻧﻈﺎﺭﺕ ﺑﺮ‬

‫ﺷﻨﺎﺳﺎﻳﻲ ﺭﻳﺴﻚ‬ ‫ﺗﺤﻠﻴﻞ ﺭﻳﺴﻚ‬
‫ﺭﻳﺴﻚ‬ ‫ﺭﻳﺴﻚ‬

‫ﻟﻴﺴﺘﻲ ﺍﺯ‬ ‫ﻟﻴﺴﺖ ﺭﻳﺴﻚ ﻫﺎ‬ ‫ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ﺍﺟﺘﻨﺎﺏ ﺍﺯ‬

‫ﺑﺮﺁﻭﺭﺩ ﺭﻳﺴﻚ‬
‫ﺭﻳﺴﻚ ﻫﺎﻱ ﺑﺎﻟﻘﻮﻩ‬ ‫ﺑﺎ ﺍﻭﻟﻮﻳﺖ‬ ‫ﺭﻳﺴﻚ ﻫﺎﻱ ﺍﺣﺘﻤﺎﻟﻲ‬
‫ﺍﻧﻮﺍﻉ ﺭﻳﺴﻚ ﻫﺎﻱ ﻣﻤﻜﻦ ﺩﺭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪:‬‬
‫ﭘﺮﻭژﻩ‬ ‫ﺍﻧﺘﻘﺎﻝ ﻛﺎﺭﻛﻨﺎﻥ‬
‫ﭘﺮﻭژﻩ‬ ‫ﺗﻐﻴﻴﺮ ﻣﺪﻳﺮﻳﺖ‬
‫ﭘﺮﻭژﻩ‬ ‫ﻣﻬﻴﺎ ﻧﺒﻮﺩﻥ ﺳﺨﺖ ﺍﻓﺰﺍﺭ‬
‫ﭘﺮﻭژﻩ ﻭ ﻣﺤﺼﻮﻝ‬ ‫ﺗﻐﻴﻴﺮ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﭘﺮﻭژﻩ ﻭ ﻣﺤﺼﻮﻝ‬ ‫ﺗﺄﺧﻴﺮ ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ‬
‫ﭘﺮﻭژﻩ ﻭ ﻣﺤﺼﻮﻝ‬ ‫ﺍﻧﺪﺍﺯﻩ ﻛﻮﭼﻜﺘﺮ ﺍﺯ ﺍﻧﺪﺍﺯﻩ‬
‫ﻣﺤﺼﻮﻝ‬ ‫ﻋﺪﻡ ﻛﺎﺭﺍﻳﻲ ﺍﺑﺰﺍﺭ ﻛﻴﺲ‬
‫ﻛﺎﺭ‬ ‫ﺗﻐﻴﻴﺮ ﻓﻦ ﺁﻭﺭﻱ‬
‫ﻛﺎﺭ‬ ‫ﺭﻗﻴﺐ ﻣﺤﺼﻮﻝ‬
 ‫ﺷﻨﺎﺳﺎﻳﯽ ﺭﻳﺴﮏ‬
‫ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻣﯽ ﺗﻮﺍﻧﺪ ﺑﺼﻮﺭﺕ ﻳﮏ ﻓﺮﺍﻳﻨﺪ ﺗﻴﻤﯽ ﻭ ﺑﻪ ﺭﻭﺵ‬
‫ﻁﻮﻓﺎﻥ‬
‫ﻣﻐﺰی ﺍﻧﺠﺎﻡ ﺷﻮﺩ ﻳﺎ ﺍﻳﻨﮑﻪ ﺑﺮ ﺍﺳﺎﺱ ﺗﺠﺮﺑﻪ ﻣﺪﻳﺮ ﺗﻌﻴﻴﻦ ﮔﺮﺩﺩ ‪.‬‬

‫ﺍﻧﻮﺍﻉ ﺭﻳﺴﮏ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬

‫ﻓﻦ ﺁﻭﺭی ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-1‬‬
‫ﺍﻓﺮﺍﺩ ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-2‬‬
‫ﺳﺎﺯﻣﺎﻧﯽ ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-3‬‬
‫ﺍﺑﺰﺍﺭ ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-4‬‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-5‬‬
‫ﺑﺮﺁﻭﺭﺩ ‪.‬‬ ‫ﻫﺎی‬ ‫ﺭﻳﺴﮏ‬ ‫‪-6‬‬
 ‫ﺗﺤﻠﻴﻞ ﺭﻳﺴﮏ‬
‫‪ -1‬ﺍﺣﺘﻤ��ﺎﻝ ﺭﻳﺴ��ﮏ ﻣﻤﮑ��ﻦ ﺍﺳ��ﺖ ﺧﻴﻠ��ﯽ ﮐ��ﻢ) ‪ ،( <%10‬ﮐ��ﻢ‬
‫) ‪ ، (-10 %25‬ﻣﺘﻮﺳ����ﻂ ) ‪ ،( -25 %05‬ﺯﻳ����ﺎﺩ ) ‪ ،(-50 %75‬ﻳ����ﺎ ﺧﻴﻠ����ﯽ‬
‫ﺯﻳﺎﺩ ‪ (>%)75‬ﺑﺮﺁﻭﺭﺩ ﺷﻮﺩ ‪.‬‬
‫‪ -2‬ﺍﺛ��ﺮ ﺭﻳﺴ��ﮏ ﻣﻤﮑ��ﻦ ﺍﺳ��ﺖ ﻓﺎﺟﻌ��ﻪ ﺑ��ﺮ ﺍﻧﮕﻴ��ﺰ‪ ،‬ﺟ��ﺪی‪،‬‬
‫ﻗﺎﺑﻞ ﺗﺤﻤﻞ ﻳﺎ ﺑﯽ ﺍﺭﺯﺵ ﺑﺎﺷﺪ ‪.‬‬
 ‫ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﺭﻳﺴﻚ‬
‫ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺭﻳﺴﻚ ﻫﺎﻱ ﻛﻠﻴﺪﻱ ﺭﺍ ﻛﻪ ﺷﻨﺎﺳﺎﻳﻲ ﺷﺪﻩ ﺍﻧﺪ ﺭﺍ ﺩﺭ ﻧﻈﺮ‬
‫ﻣﻲ ﮔﻴﺮﺩ ﻭ ﺭﺍﻫﺒﺮﺩ ﻫﺎﻳﻲ ﺭﺍ ﺑـﺮﺍﻱ ﻣـﺪﻳﺮﻳﺖ ﺑـﺮ ﺭﻳﺴـﻚ ﺷﻨﺎﺳـﺎﻳﻲ‬
‫ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫ﺍﻳﻦ ﺭﺍﻫﺒﺮﺩ ﻫﺎ ﺑﻪ ﺳﻪ ﺩﺳﺘﻪ ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﻧﺪ‪:‬‬
‫‪ -1‬ﺭﺍﻫﺒﺮﺩﻫﺎﻱ ﺍﺟﺘﻨﺎﺏ ‪.‬‬
‫‪ -2‬ﺭﺍﻫﺒﺮﺩﻫﺎﻱ ﻛﻤﻴﻨﻪ ﺳﺎﺯﻱ ‪.‬‬
‫‪ -3‬ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﺍﺣﺘﻤﺎﻟﻲ ‪.‬‬
 ‫ﻧﻈﺎﺭﺕ ﺑﺮ ﺭﻳﺴﮏ‬
‫ﻧﻈﺎﺭﺕ ﺑﺮ ﺭﻳﺴﮏ ﻳﮏ ﻓﺮﺍﻳﻨﺪ ﺩﺍﺋﻤﯽ ﺍﺳﺖ‬
‫ﻭ ﺷﺎﻣﻞ ﺑﺮﺁﻭﺭﺩ ﻣﻨﻈﻢ ﺭﻳﺴﮏ ﻫﺎی ﺷﻨﺎﺳﺎﻳﯽ‬
‫ﺷﺪﻩ ﺍﺳﺖ ﺗﺎ ﺗﺼﻤﻴﻢ ﮔﺮﻓﺘﻪ ﺷﻮﺩ ﺁﻳﺎ ﺍﺣﺘﻤﺎﻝ ﺁﻥ‬
‫ﺭﻳﺴﮏ ﮐﺎﻫﺶ ﻣﯽ ﻳﺎﺑﺪ ﻳﺎ ﺧﻴﺮ ﻭ ﺁﻳﺎ ﺍﺛﺮ‬
‫ﺭﻳﺴﮏ ﺗﻐﻴﻴﺮ ﻣﯽ ﮐﻨﺪ ﻳﺎ ﺧﻴﺮ ‪.‬‬
‫ﺑﺨﺶ ﺳﻮﻡ‬

‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
 ‫ﻓﺼﻞ‪8‬‬

‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

 ‫‪Requirment‬‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ ‪ :‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺍﻧﺘﺰﺍﻋﻲ ﺳﻄﺢ ﺑﺎﻻ‪.‬‬
‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫـﺎﻱ ﺳﻴﺴـﺘﻢ ‪ :‬ﺗﻮﺻـﻴﻔﺎﺕ ﺗﻔﻀـﻴﻠﻲ ﺍﺯ ﻛﺎﺭﻫـﺎﻳﻲ ﺍﺳـﺖ ﻛـﻪ‬
‫ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﺍﻧﺠﺎﻡ ﺩﻫﺪ‪.‬‬
‫‪ -3‬ﻣﺸﺨﺼﺎﺕ ﻃﺮﺍﺣﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪ :‬ﻳﻚ ﺗﻮﺻﻴﻒ ﺍﻧﺘﺰﺍﻋﻲ ﺍﺯ ﻃﺮﺍﺣـﻲ ﻧـﺮﻡ‬
‫ﺍﻓﺰﺍﺭ ﺑﺮﺍﻱ ﻃﺮﺍﺣﻲ ﺗﻔﻀﻴﻠﻲ ﺗﺮ‪.‬‬
 ‫ﺧﻮﺍﻧﻨﺪﮔﺎﻥ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻔﻲ ﺍﺯ ﻣﺸﺨﺼﺎﺕ‬
‫ﻣﺪﻳﺮﺍﻥ ﻣﺸﺘﺮﻱ‬
‫ﻛﺎﺭﺑﺮﺍﻥ ﻧﻬﺎﻳﻲ ﺳﻴﺴﺘﻢ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ‬ ‫ﻣﻬﻨﺪﺳﻴﻦ ﻣﺸﺘﺮﻱ‬
‫ﻣﺪﻳﺮﺍﻥ ﭘﻴﻤﺎﻧﻜﺎﺭ‬
‫ﻣﻌﻤﺎﺭ ﻫﺎﻱ ﺳﻴﺴﺘﻢ‬
‫ﻛﺎﺭﺑﺮﺍﻥ ﻧﻬﺎﻳﻲ ﺳﻴﺴﺘﻢ‬
‫ﻣﻬﻨﺪﺳﻴﻦ ﻣﺸﺘﺮﻱ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ‬
‫ﻣﻌﻤﺎﺭﻫﺎﻱ ﺳﻴﺴﺘﻢ‬
‫ﺗﻮﺳﻌﻪ ﺩﻫﻨﺪﮔﺎﻥ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
‫ﻣﻬﻨﺪﺳﻴﻦ ﻣﺸﺘﺮﻱ‬
‫ﻣﺸﺨﺼﺎﺕ ﻃﺮﺍﺣﻲ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬ ‫ﻣﻌﻤﺎﺭﻫﺎﻱ ﺳﻴﺴﺘﻢ‬
‫ﺗﻮﺳﻌﻪ ﺩﻫﻨﺪﮔﺎﻥ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬
 ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ‬
‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ ‪ :‬ﺍﻳﻦ ﺧﻮﺍﺳﺘﻪ ﻫـﺎ ﺑﻴـﺎﻧﻲ ﺍﺯ ﺳـﺮﻭﻳﺲ ﻫـﺎﻳﻲ‬
‫ﺍﺳﺖ ﻛﻪ ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﺍﺭﺍﺋﻪ ﺩﻫﺪ‪.‬‬
‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻏﻴﺮ ﻋﻤﻠﻜﺮﺩﻱ ‪ :‬ﻣﺤﺪﻭﺩﻳﺖ ﻫﺎﻳﻲ ﺩﺭ ﺳـﺮﻭﻳﺲ ﻫـﺎ ﻳـﺎ‬
‫ﻋﻤﻠﻜﺮﺩﻫﺎﻳﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﭘﻴﺸﻨﻬﺎﺩ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫‪ -3‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ‪ :‬ﺍﻳﻦ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺍﺯ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺳﻴﺴـﺘﻢ‬
‫ﻧﺎﺷﻲ ﻣﻲ ﺷﻮﻧﺪ ﻭ ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺁﻥ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺭﺍ ﻣﻨﻌﻜﺲ ﻣﻲ ﻛﻨﺪ ‪.‬‬
 ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ ﺑﻪ ﻋﻮﺍﻣﻞ ﺯﻳﺮ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﻧﻮﻉ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
‫‪ -2‬ﻛﺎﺭﺑﺮﺍﻥ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪.‬‬
‫‪ -3‬ﻧﻮﻉ ﺳﻴﺴﺘﻢ ‪.‬‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻏﻴﺮ ﻋﻤﻠﻜﺮﺩﻱ‬
‫ﺍﻧﻮﺍﻉ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻏﻴﺮ ﻋﻤﻠﻜﺮﺩﻱ ﻋﺒﺎﺭﺕ ﺍﻧﺪﺍﺯ‪:‬‬
‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻣﺤﺼﻮﻝ ‪.‬‬
‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﺎﺯﻣﺎﻧﻲ ‪.‬‬
‫‪ -3‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺧﺎﺭﺟﻲ ‪.‬‬
‫ﻣﻌﻴﺎﺭﻫﺎﻳﻲ ﺑﺮﺍﻱ ﻣﺸﺨﺺ ﻛﺮﺩﻥ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻏﻴﺮﻋﻤﻠﻜﺮﺩﻱ‬
‫‪ -1‬ﺳﺮﻋﺖ ‪.‬‬
‫‪ -2‬ﺍﻧﺪﺍﺯﻩ ‪.‬‬
‫‪ -3‬ﺳﻬﻮﻟﺖ ﺍﺳﺘﻔﺎﺩﻩ ‪.‬‬
‫‪ -4‬ﻗﺎﺑﻠﻴﺖ ﺍﻋﺘﻤﺎﺩ ‪.‬‬
‫‪ -5‬ﺗﻮﺍﻧﻤﻨﺪﻱ ‪.‬‬
‫‪ -6‬ﻗﺎﺑﻠﻴﺖ ﺣﻤﻞ ‪.‬‬
 ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺍﺯ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺳﻴﺴﺘﻢ ﺑﺪﺳﺖ ﻣﻲ ﺁﻳﺪ ‪،‬‬
‫ﻧﻪ ﺍﺯ ﻧﻴﺎﺯﻫﺎﻱ ﻭﻳﮋﻩ ﻛﺎﺭﺑﺮﺍﻥ ﺳﻴﺴﺘﻢ ‪ .‬ﺁﻧﻬﺎ ﻣﻌﻤﻮﻻً ﺷﺎﻣﻞ ﺍﺻﻄﻼﺣﺎﺕ‬
‫ﻭﻳﮋﻩ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﻳﺎ ﺍﺭﺟﺎﻉ ﺑﻪ ﻣﻔﺎﻫﻴﻢ ﺁﻥ ﻣﻲ ﺑﺎﺷﻨﺪ ‪.‬‬
 ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ ﺑﺎﻳﺪ ﺑﺎ ﺯﺑﺎﻥ ﻃﺒﻴﻌﻲ ‪ ،‬ﻓﺮﻡ ﻫﺎ ﻭ ﻧﻤﻮﺩﺍﺭﻫﺎﻱ‬
‫ﺷﻬﻮﺩﻱ ﻧﻮﺷﺘﻪ ﺷﻮﻧﺪ ‪.‬‬

‫ﻣﺸﻜﻼﺗﻲ ﻛﻪ ﺩﺭ ﺑﻴﺎﻥ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺑﻪ ﺯﺑﺎﻥ ﻃﺒﻴﻌﻲ ﻭﺟﻮﺩ ﺩﺍﺭﻧﺪ‬

‫ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫‪ -1‬ﻋﺪﻡ ﻭﺿﻮﺡ ‪.‬‬
‫‪ -2‬ﺁﺷﻔﺘﮕﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -3‬ﺍﺧﺘﻼﻁ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫ﺑﺮﺍﻱ ﻛﺎﻫﺶ ﺍﺷﺘﺒﺎﻫﺎﺕ ﺩﺭ ﻫﻨﮕﺎﻡ ﻧﻮﺷﺘﻦ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ ‪،‬‬
‫ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺭﺍ ﺑﻪ ﺧﺎﻃﺮ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ‪:‬‬
‫‪ -1‬ﻳﻚ ﻓﺮﻣﺖ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺍﺧﺘﺮﺍﻉ ﻛﻨﻴﺪ ﻭ ﻣﻄﻤﺌﻦ ﺷﻮﻳﺪ ﻛﻪ ﺗﻌﺮﻳﻒ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺍﺯ ﺁﻥ‬
‫ﭘﻴﺮﻭﻱ ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫‪ -2‬ﺍﺯ ﺳﺎﺯﮔﺎﺭﻱ ﺯﺑﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ ‪.‬‬
‫‪ -3‬ﺑﺮﺍﻱ ﺗﻌﻴﻴﻦ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻛﻠﻴﺪﻱ ﺁﻥ ﻫﺎ ﺭﺍ ﺑﺮﺟﺴﺘﻪ ﻛﻨﻴﺪ ‪.‬‬
‫‪ -4‬ﺗﺎ ﺟﺎﻳﻲ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺍﺯ ﻭﺍژﻩ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻜﻨﻴﺪ ‪.‬‬
 ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ‬
‫ﻧﺸﺎﻧﻪ ﮔﺬﺍﺭﻱ ﻫﺎﻱ ﻭﻳﮋﻩ ﺍﻱ ﻛﻪ ﺑﺮﺍﻱ ﻧﻮﺷﺘﻦ ﻣﺸﺨﺼﺎﺕ ﻣﻲ ﺗﻮﺍﻥ ﺑﻜﺎﺭ‬
‫ﺑﺮﺩ ‪:‬‬
‫‪ -1‬ﺯﺑﺎﻥ ﻃﺒﻴﻌﻲ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ‪.‬‬
‫‪ -2‬ﺯﺑﺎﻥ ﻫﺎﻱ ﺗﻮﺻﻴﻒ ﻃﺮﺍﺣﻲ ‪.‬‬
‫‪ -3‬ﻧﺸﺎﻧﻪ ﮔﺬﺍﺭﻱ ﻫﺎﻱ ﮔﺮﺍﻓﻴﻜﻲ ‪.‬‬
‫‪ -4‬ﻣﺸﺨﺼﺎﺕ ﺭﻳﺎﺿﻲ ‪.‬‬
 ‫ﻣﺸﺨﺼﺎﺕ ﺯﺑﺎﻥ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ‬

‫ﺯﺑﺎﻥ ﻃﺒﻴﻌﻲ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ‪ ،‬ﺷﻜﻞ ﻣﺤﺪﻭﺩﻱ ﺍﺯ ﺯﺑـﺎﻥ ﻃﺒﻴﻌـﻲ ﺑـﺮﺍﻱ‬

‫ﻧﻮﺷﺘﻦ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ‪.‬‬
‫ﺍﻣﺘﻴﺎﺯ ﺍﻳﻦ ﺭﻭﺵ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻗﺎﺑﻠﻴﺖ ﺑﻴﺎﻥ ﻭ ﺩﺭﻙ ﺯﺑـﺎﻥ ﻃﺒﻴﻌـﻲ‬
‫ﺭﺍ ﺩﺍﺭﺩ ‪ ،‬ﻭﻟﻲ ﺗﻀﻤﻴﻦ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﻧﻮﻋﻲ ﻳﻜﻨﻮﺍﺧﺘﻲ ﺑـﻪ ﻣﺸﺨﺼـﺎﺕ‬
‫ﺍﻋﻤﺎﻝ ﻣﻲ ﻛﻨﺪ ‪.‬‬
 ‫ﻭﻗﺘﻲ ﻓﺮﻡ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺑﺮﺍﻱ ﻣﺸﺨﺺ ﻛﺮﺩﻥ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﻋﻤﻠﻜﺮﺩﻱ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﮔﻴﺮﺩ‪ ،‬ﺑﺎﻳﺪ ﺷﺎﻣﻞ ﺍﻃﻼﻋﺎﺕ‬
‫ﺯﻳﺮ ﺑﺎﺷﺪ ‪:‬‬
‫‪ -1‬ﺗﻮﺻﻴﻔﻲ ﺍﺯ ﻋﻤﻠﻜﺮﺩ ﻳﺎ ﻧﻬﺎﺩﻱ ﻛﻪ ﻣﺸﺨﺺ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫‪ -2‬ﺗﻮﺻﻴﻔﻲ ﺍﺯ ﻭﺭﻭﺩﻱ ﻫﺎﻱ ﺁﻥ ﻭ ﺟﺎﻳﻲ ﻛﻪ ﺍﻳﻦ ﻭﺭﻭﺩﻱ ﻫﺎ ﻣﻲ ﺁﻳﻨﺪ ‪.‬‬
‫‪ -3‬ﺗﻮﺻﻴﻔﻲ ﺍﺯ ﺧﺮﻭﺟﻲ ﻫﺎﻱ ﺁﻥ ﻭ ﺟﺎﻳﻲ ﻛﻪ ﺍﻳﻦ ﺧﺮﻭﺟﻲ ﻫﺎ ﻣﻲ ﺁﻳﻨﺪ ‪.‬‬
‫‪ -4‬ﻧﺸﺎﻧﻪ ﺍﻱ ﺍﺯ ﺳﺎﻳﺮ ﻧﻬﺎﺩﻫﺎﻳﻲ ﻛﻪ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬
‫‪ -5‬ﺗﻮﺻﻴﻒ ﻋﻤﻠﻲ ﻛﻪ ﺑﺎﻳﺪ ﺻﻮﺭﺕ ﮔﻴﺮﺩ ‪.‬‬
‫‪ -6‬ﺍﮔﺮ ﺍﺯ ﺭﻭﺵ ﻋﻤﻠﻜﺮﺩﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪ ،‬ﭘﻴﺶ ﺷﺮﻁ ﻫﺎ ﻭ ﭘﺲ ﺷﺮﻁ ﻫﺎ‬
‫ﻣﺸﺨﺺ ﺷﻮﻧﺪ ‪.‬‬
‫‪ -7‬ﺗﻮﺻﻴﻔﻲ ﺍﺯ ﺍﺛﺮﺍﺕ ﺟﺎﻧﺒﻲ ﻋﻤﻠﻴﺎﺕ ‪.‬‬
 ‫ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻭﺍﺳﻂ‬
‫ﺍﮔﺮ ﺳﻴﺴﺘﻢ ﺟﺪﻳﺪ ﻭ ﺳﻴﺴﺘﻢ ﻣﻮﺟﻮﺩ ﺑﺨﻮﺍﻫﻨﺪ ﺑﺎ ﻫﻢ ﻛـﺎﺭ ﻛﻨﻨـﺪ‪ ،‬ﻭﺍﺳـﻂ‬
‫ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﺟﺪﻳﺪ ﺑﺎﻳﺪ ﺩﻗﻴﻘﺎً ﻣﺸﺨﺺ ﺷﻮﻧﺪ ‪.‬‬

‫ﺳﻪ ﻧﻮﻉ ﻭﺍﺳﻂ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﺎﻳﺪ ﺗﻌﺮﻳﻒ ﺷﻮﻧﺪ ‪:‬‬

‫‪ -1‬ﻭﺍﺳﻂ ﻫﺎﻱ ﺭﻭﻳﻪ ﺍﻱ ‪.‬‬
‫‪ -2‬ﺳﺎﺧﺘﻤﺎﻥ ﺩﺍﺩﻩ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯ ﻳﻚ ﺯﻳﺮﺳﻴﺴﺘﻢ ﺑﻪ ﺯﻳﺮ ﺳﻴﺴـﺘﻢ ﺩﻳﮕـﺮﻱ‬
‫ﻋﺒﻮﺭ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬
‫‪ -3‬ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻫﺎ ﻛﻪ ﺑﺮﺍﻱ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻣﻮﺟﻮﺩ ﺗﻌﻴﻴﻦ ﺷﺪﻧﺪ ‪.‬‬
 ‫ﻓﺼﻞ ‪9‬‬

‫ﻓﺮﺍﻳﻨﺪﻫﺎی ﻣﻬﻨﺪﺳﯽ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

 ‫ﻓﺮﺍﻳﻨﺪ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﻣﻄﺎﻟﻌﻪ‬ ‫ﺍﺳﺘﺨﺮﺍﺝ ﻭﺗﺤﻠﻴﻞ‬

‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬ ‫ﺧﻮﺍﺳﺘﻪ‬
‫ﻣﺸﺨﺼﺎﺕ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ‬
‫ﮔﺰﺍﺭﺵ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬
‫ﻣﺪﻝ ﻫﺎﻱ‬
‫ﺳﻴﺴﺘﻢ‬ ‫ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﻛﺎﺭﺑﺮ ﻭ ﺳﻴﺴﺘﻢ‬
‫ﺳﻨﺪ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
 ‫ﻣﻄﺎﻟﻌﺎﺕ ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ‬
‫ﻭﺭﻭﺩﻱ ﻣﻄﺎﻟﻌــﻪ ﺍﻣﻜــﺎﻥ ﺳــﻨﺠﻲ ‪ :‬ﺗﻮﺻــﻴﻒ ﻃــﺮﺡ ﻛﻠــﻲ ﺳﻴﺴــﺘﻢ ﻭ‬
‫ﭼﮕﻮﻧﮕﻲ ﺑﻪ ﻛﺎﺭﮔﻴﺮﻱ ﺁﻥ ﺩﺭ ﺳﺎﺯﻣﺎﻥ ﺍﺳﺖ ‪.‬‬
‫ﺧﺮﻭﺟﻲ ﻣﻄﺎﻟﻌﻪ ﺍﻣﻜﺎﻥ ﺳﻨﺠﻲ ‪ :‬ﮔﺰﺍﺭﺷﻲ ﺍﺳﺖ ﻛﻪ ﭘﻴﺸﻨﻬﺎﺩ ﻣﻲ ﻛﻨﺪ‬
‫ﺁﻳﺎ ﺍﺟﺮﺍﻱ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﻭ ﻓﺮﺍﻳﻨـﺪ ﺗﻮﺳـﻌﻪ ﺳﻴﺴـﺘﻢ ﺍﺭﺯﺷـﻤﻨﺪ‬
‫ﺍﺳﺖ ﻳﺎ ﺧﻴﺮ؟‬
‫ﺍﻳﻦ ﻣﻄﺎﻟﻌﺎﺕ ﺷﺎﻣﻞ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﺑﺮﺁﻭﺭﺩ ﺍﻃﻼﻋﺎﺕ ‪.‬‬
‫‪ -2‬ﺟﻤﻊ ﺁﻭﺭﻱ ﺍﻃﻼﻋﺎﺕ ‪.‬‬
‫‪ -3‬ﻧﻮﺷﺘﻦ ﮔﺰﺍﺭﺵ ‪.‬‬
‫ﺍﺳﺘﺨﺮﺍﺝ ﻭ ﺗﺤﻠﻴﻞ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺷﺎﻣﻞ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﺟﻤﻊ ﺁﻭﺭﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -2‬ﺩﺳﺘﻪ ﺑﻨﺪﻱ ‪.‬‬
‫‪ -3‬ﻣﺬﺍﻛﺮﻩ ﻭﺍﻭﻟﻮﻳﺖ ﺑﻨﺪﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -4‬ﻣﺴﺘﻨﺪ ﺳﺎﺯﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‪.‬‬
‫ﺳﻪ ﺗﻜﻨﻴﻚ ﺑﺮﺍﻱ ﺍﺳﺘﺨﺮﺍﺝ ﻭ ﺗﺤﻠﻴﻞ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪:‬‬
‫‪ -1‬ﺍﺳﺘﺨﺮﺍﺝ ﻣﺒﻨﻲ ﺩﻳﺪﮔﺎﻩ ﻫﺎ ‪.‬‬
‫‪ -2‬ﺳﻨﺎﺭﻳﻮﻫﺎ‪.‬‬
‫‪ -3‬ﺍﺗﻨﺎ ﮔﺮﺍﻓﻲ ‪.‬‬
 ‫ﺍﺳﺘﺨﺮﺍﺝ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻓﺮﺍﻳﻨﺪ ﺟﻤﻊ ﺁﻭﺭﻱ ﺍﻃﻼﻋﺎﺕ ﺭﺍﺟﻊ ﺑﻪ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﻭ‬
‫ﭘﻴﺸﻨﻬﺎﺩﻱ‪ ،‬ﻭ ﺍﺳﺘﺨﺮﺍﺝ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻭ ﻛـﺎﺭﺑﺮ ﺍﺯ ﺍﻳـﻦ‬
‫ﺍﻃﻼﻋﺎﺕ ﺍﺳﺖ ‪.‬‬
‫ﻣﻨﺎﺑﻊ ﺍﻃﻼﻋﺎﺕ ﺩﺭ ﺍﺛﻨﺎﻱ ﺍﺳﺘﺨﺮﺍﺝ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪:‬‬
‫‪ -1‬ﻣﺴﺘﻨﺪ ﺳﺎﺯﻱ ‪.‬‬
‫‪(Stakeholder).‬‬ ‫‪ -2‬ﻭﺍﮔﺬﺍﺭﻧﺪﮔﺎﻥ ﺳﻴﺴﺘﻢ‬
‫‪ -3‬ﻣﺸﺨﺼﺎﺕ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺸﺎﺑﻪ ‪.‬‬
 ‫ﻓﺮﺍﻳﻨﺪ ﺍﺳﺘﺨﺮﺍﺝ ﻭ ﺗﺤﻠﻴﻞ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﻛﻨﺘﺮﻝ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﻣﺸﺨﺼﺎﺕ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﻭﺭﻭﺩ ﺑﻪ ﻓﺮﺍﻳﻨﺪ‬
‫ﺩﺭﻙ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ‬ ‫ﺍﻭﻟﻮﻳﺖ ﺑﻨﺪﻱ‬

‫ﺳﻨﺪ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﺟﻤﻊ ﺁﻭﺭﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬ ‫ﺣﺬﻑ ﺗﻨﺎﻗﺾ ﻫﺎ‬

‫ﺩﺳﺘﻪ ﺑﻨﺪﻱ‬
 ‫ﺍﻧﻮﺍﻉ ﻭﻳﮋﻩ ﺍﻱ ﺍﺯ ﺩﻳﺪﮔﺎﻩ ﻫﺎ ‪:‬‬
‫‪ -1‬ﺗﺄﻣﻴﻦ ﻛﻨﻨﺪﮔﺎﻥ ﻭ ﺩﺭﻳﺎﻓﺖ ﻛﻨﻨﺪﮔﺎﻥ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -2‬ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺑﺎﻳـﺪ ﺑﻄﻮﺭﻏﻴﺮﻣﺴـﺘﻘﻴﻢ ﺑـﺎ ﺳﻴﺴـﺘﻢ ﻣـﻮﺭﺩ ﻧﻈـﺮ ﺭﺍﺑﻄـﻪ‬
‫ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ‪.‬‬
‫‪ -3‬ﻗﻮﺍﻧﻴﻦ ﻭ ﺍﺳﺘﺎﻧﺪﺍﺭﺩﻫﺎﻳﻲ ﻛﻪ ﺑﻪ ﺳﻴﺴﺘﻢ ﺍﻋﻤﺎﻝ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫‪ -4‬ﻣﻨﺎﺑﻊ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺗﺠﺎﺭﻱ ﻭ ﻏﻴﺮﻋﻤﻠﻜﺮﺩﻱ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -5‬ﺩﻳﺪﮔﺎﻫﻬﺎﻱ ﻣﻬﻨﺪﺳﻲ ﻛﻪ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺗﻮﺳﻌﻪ ﺩﻫﻨـﺪﮔﺎﻥ‪ ،‬ﻣـﺪﻳﺮﺍﻥ ﻭ‬
‫ﻧﮕﻬﺪﺍﺭﻧﺪﮔﺎﻥ ﺭﺍ ﻣﻨﻌﻜﺲ ﺳﺎﺯﻧﺪ ‪.‬‬
‫‪ -6‬ﺩﻳﺪﮔﺎﻩ ﻫﺎﻱ ﺑﺎﺯﺍﺭﻳﺎﺑﻲ ﻭ ﻏﻴﺮﻩ ‪.‬‬
 ‫‪ -1‬ﺩﻳﺪﮔﺎﻩ ﻫﺎﻱ ﺗﻌﺎﻣﻠﻲ ‪.‬‬
‫‪ -2‬ﺩﻳﺪﮔﺎﻩ ﻫﺎﻱ ﻏﻴﺮﻣﺴﺘﻘﻴﻢ ‪.‬‬ ‫‪:‬‬ ‫ﺩﻳﺪﮔﺎﻩ ﻫﺎ‬
‫‪ -3‬ﺩﻳﺪﮔﺎﻩ ﻫﺎﻱ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ‪.‬‬
‫‪ -1‬ﻣﻨﺎﺑﻊ ﻳﺎ ﻣﺨﺎﺯﻥ ﺩﺍﺩﻩ‪.‬‬
‫‪ -2‬ﭼﺎﺭﭼﻮﺏ ﻧﻤﺎﻳﺶ‪.‬‬
‫‪ -3‬ﺩﺭﻳﺎﻓﺖ ﻛﻨﻨﺪﻩ ﺳﺮﻭﻳﺲ ﻫﺎ ‪.‬‬

‫ﺷﻨﺎﺳﺎﻳﻲ ﺩﻳﺪﮔﺎﻩ ﻫﺎ ﺑﺎ ﺭﻭﺵ ﻃﻮﻓﺎﻥ ﻣﻐﺰﻱ ‪:‬‬

‫ﺷﻨﺎﺳﺎﻳﻲ ﻧﻬﺎﺩﻫﺎﻱ ﺑﺎﻟﻘﻮﻩ ﻛﻪ ﺑﺎ ﺳﻴﺴﺘﻢ ﺩﺭ ﺗﻌﺎﻣﻞ ﺍﺳﺖ ‪.‬‬
‫)‪(ATM‬‬ ‫ﺭﻭﺵ ﻃﻮﻓﺎﻥ ﻣﻐﺰﻱ‬
 ‫ﻣﺼﺎﺣﺒﻪ‬
‫ﻣﺼﺎﺣﺒﻪ ﻫﺎﻱ ﺭﺳﻤﻲ ﻭ ﻏﻴﺮ ﺭﺳﻤﻲ ﺑﺎ ﻭﺍﮔﺬﺍﺭﻧﺪﮔﺎﻥ ﺳﻴﺴﺘﻢ ﺑﺨﺸﻲ ﺍﺯ‬
‫ﻣﻬﻤﺘﺮﻳﻦ ﻓﺮﺍﻳﻨﺪﻫﺎﻱ ﻣﻬﻨﺪﺳﻲ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﻫﺴﺘﻨﺪ ‪.‬‬

‫ﻣﺼﺎﺣﺒﻪ ﻫﺎ ﺩﻭ ﻧﻮﻉ ﺍﻧﺪ ‪:‬‬

‫‪ -1‬ﻣﺼﺎﺣﺒﻪ ﻫﺎﻱ ﺑﺴﺘﻪ ﻛﻪ ﺩﺭ ﺁﻥ ﻫﺎ ﻭﺍﮔﺬﺍﺭﻧﺪﮔﺎﻥ ﺑﻪ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ‬

‫ﭘﺮﺳﺶ ﻫﺎﻱ ﺍﺯ ﭘﻴﺶ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﭘﺎﺳﺦ ﻣﻲ ﺩﻫﻨﺪ ‪.‬‬
‫‪ -2‬ﻣﺼﺎﺣﺒﻪ ﺑﺎﺯ ﻛﻪ ﺩﺭ ﺁﻥ ﻫﺎ ﺩﺳﺘﻮﺭ ﺟﻠﺴﻪ ﺍﺯ ﭘﻴﺶ ﺗﻌﺮﻳﻒ ﺷﺪﻩ ﻭﺟﻮﺩ‬
‫ﺩﺍﺭﺩ ‪.‬‬
 ‫ﺍﺳﺘﺨﺮﺍﺝ ﺍﻃﻼﻋﺎﺕ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺑﻪ ﺩﻭ ﺩﻟﻴﻞ‬
‫ﺩﺷﻮﺍﺭ ﺍﺳﺖ‪:‬‬
‫‪ -1‬ﺗﻤﺎﻡ ﻣﺘﺨﺼﺼﻴﻦ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺍﺯ ﻭﺍژﻩ ﻫﺎ ﻭ ﺍﺻﻄﻼﺣﺎﺕ ﺧﺎﺻﻲ ﺍﺳـﺘﻔﺎﺩﻩ‬
‫ﻣﻲ ﻛﻨﻨﺪ ‪.‬‬
‫‪ -2‬ﺑﻌﻀﻲ ﺍﺯ ﺩﺍﻧﺶ ﻫـﺎﻱ ﺩﺍﻣﻨـﻪ ﻛـﺎﺭﺑﺮﺩ ﺑـﻪ ﺣـﺪﻱ ﺑـﺮﺍﻱ ﻭﺍﮔﺬﺍﺭﻧـﺪﮔﺎﻥ‬
‫ﺭﻭﺷﻦ ﺍﺳﺖ ﻛﻪ ﻳﺎ ﻓﻜﺮ ﻣﻲ ﻛﻨﻨﺪ ﺗﺸـﺮﻳﺢ ﺁﻥ ﺁﺳـﺎﻥ ﺍﺳـﺖ ﻭ ﻳـﺎ ﺁﻥ ﻗـﺪﺭ‬
‫ﺍﺑﺘﺪﺍﻳﻲ ﺍﻧﺪ ﻛﻪ ﻧﻴﺎﺯ ﺑﻪ ﺑﻴﺎﻥ ﻛﺮﺩﻥ ﺁﻧﻬﺎ ﻧﻴﺴﺖ ‪.‬‬
 ‫ﺳﻨﺎﺭﻳﻮﻫﺎ‬
‫ﺗﻮﺻﻴﻒ ﻫﺎﻳﻲ ﺍﺯ ﺟﻠﺴﺎﺕ ﻛﺎﺭ ﺑﺎ ﺳﻴﺴﺘﻢ ﻫﺴﺘﻨﺪ ‪ .‬ﻫﺮ ﺳﻨﺎﺭﻳﻮ ﻳﻚ ﻳﺎ‬
‫ﭼﻨﺪ ﺗﻌﺎﻣﻞ ﻛﻮﭼﻚ ﺍﺳﺖ ‪.‬‬
‫ﺳﻨﺎﺭﻳﻮﻣﻤﻜﻦ ﺍﺳﺖ ﺷﺎﻣﻞ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺑﺎﺷﺪ ‪:‬‬
‫‪ -1‬ﺗﻮﺻﻴﻒ ﺍﻧﺘﻈﺎﺭ ﺳﻴﺴﺘﻢ ﻭ ﻛﺎﺭﺑﺮﺍﻥ ﭘﺲ ﺍﺯ ﺷﺮﻭﻉ ﺳﻨﺎﺭﻳﻮ ‪.‬‬
‫‪ -2‬ﺗﻮﺻﻴﻒ ﺟﺮﻳﺎﻥ ﻋﺎﺩﻱ ﺭﻭﻳﺪﺍﺩﻫﺎ ﺩﺭ ﺳﻨﺎﺭﻳﻮ ‪.‬‬
‫‪ -3‬ﺗﻮﺻﻴﻒ ﺍﺷﺘﺒﺎﻫﺎﺕ ﺍﺣﺘﻤﺎﻟﻲ ﻭ ﭼﮕﻮﻧﮕﻲ ﺍﺩﺍﺭﻩ ﺁﻥ ﻫﺎ ‪.‬‬
‫‪ -4‬ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍﺟﻊ ﺑﻪ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﻛﻪ ﺩﺭ ﻫﻤﺎﻥ ﺯﻣﺎﻥ ﻗﺎﺑﻞ‬
‫ﺍﺟﺮﺍﻫﺴﺘﻨﺪ ‪.‬‬
‫‪ -5‬ﺗﻮﺻﻴﻒ ﺣﺎﻟﺖ ﺳﻴﺴﺘﻢ ﭘﺲ ﺍﺯ ﻛﺎﻣﻞ ﺷﺪﻥ ﺳﻨﺎﺭﻳﻮ ‪.‬‬
 ‫ﻣﻮﺍﺭﺩ ﻛﺎﺭﺑﺮﺩ )‪(Use Case‬‬
‫‪ -1‬ﻣﻄﺮﺡ ﺗﻜﻨﻴـﻚ ﺍﺳـﺘﺨﺮﺍﺝ ﺩﺍﺩﻩ ﻣﺒﺘﻨـﻲ ﺑـﺮ ﺳﻨﺎﺭﻳﻮﺍﺳـﺖ ﻛـﻪ ﺩﺭ ﺭﻭﺵ‬
‫ﺷﻲءﮔﺮﺍ ﺷﺪ‪.‬‬

‫‪ -2‬ﻛﺎﺭﺑﺮﺩ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺳﻨﺎﺭﻳﻮﻫﺎ ﺭﺍ ﺑﺴﺘﻪ ﺑﻨﺪﻱ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﻫﺮ ﺳـﻨﺎﺭﻳﻮ‬

‫ﺩﻧﺒﺎﻟﻪ ﺍﻱ ﺍﺯ ﻣﻮﺭﺩ ﻛﺎﺭﺑﺮﺩ ﺍﺳﺖ ‪.‬‬

‫‪ -3‬ﺳﻨﺎﺭﻳﻮ ﻫﺎ ﻭ ﻣﻮﺍﺭﺩ ﻛﺎﺑﺮﺩ ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﻣﻮﺛﺮﻱ ﺑﺮﺍﻱ ﺍﺳﺘﺨﺮﺍﺝ ﺧﻮﺍﺳﺘﻪ‬

‫ﻫﺎ ﺑﺮﺍﻱ ﺩﻳﺪﮔﺎﻩ ﻫﺎﻱ ﺗﻌﺎﻣﻠﻲ ﺍﻧﺪ ‪.‬‬
 ATM : ‫ﻣﺜﺎﻝ ﺳﻨﺎﺭﻳﻮ‬
Viewpoint Service Information
ACCOUNT FOREIGN BANK
HOLDER CUSTOMER TELLER
Service list Service list Service list

Withdraw cash Withdraw cash Run diagnostics

Query balance Query balance Add cash
Or der cheques Add paper
Send message Send message
Transaction list
Or der statement
Transfer funds
 ATM : ‫ﻣﺜﺎﻝ ﺳﻨﺎﺭﻳﻮ‬
Viewpoint Data/Control

ACCOUNT
HOLDER Control input Da ta input
Start transaction Card details
Cancel transaction PIN
End transaction Am ount required
Select service Message
 ATM : ‫ﻣﺜﺎﻝ ﺳﻨﺎﺭﻳﻮ‬
Viewpoint hierarchy
All VPs

Services
Query balance
Withdraw cash Customer Bank staff

Services Account Foreign

Teller Manager Engineer
holder customer
Order cheques
Send message
Transaction list
Order statement
Transfer funds
 ATM : ‫ﻣﺜﺎﻝ ﺳﻨﺎﺭﻳﻮ‬
Viewpoint Documentation

Reference: Customer Reference: Cash withdrawal

Attributes: Account number Rationale: To improve customer service

PIN and reduce paperwork
Start transaction
Events: Select service Specification: Users choose this service by
Cancel pressing the cash withdrawal
transaction button. They then enter the
End transaction amount required. This is
confirmed and, if funds allow,
Services: Cash withdrawal the balan ce is delivered.
Balance enquiry
VPs: Customer
Sub-VPs: Account holder
Foreign Non-funct. Deliver cash within 1 minute
customer requirements: of amount being confirmed

Provider: Filled in later

 ATM : ‫ﻣﺜﺎﻝ ﺳﻨﺎﺭﻳﻮ‬
Event Scenario : Start Transaction
Library use-cases : ‫ﻣﺜﺎﻝ ﻣﻮﺭﺩ ﻛﺎﺭﺑﺮﺩ‬
Library use-cases : ‫ﻣﺜﺎﻝ ﻣﻮﺭﺩ ﻛﺎﺭﺑﺮﺩ‬
 ‫)‪(Ethnography‬‬ ‫ﺍﺗﻨﺎ ﮔﺮﺍﻓﻲ‬
‫ﻳﻚ ﺗﻜﻨﻴﻚ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﺩﺭﻙ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﺳﺎﺯﻣﺎﻧﻲ ﻭ‬
‫ﺍﺟﺘﻤﺎﻋﻲ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺭﻭﺩ ‪.‬‬

‫ﺍﺗﻨﺎ ﮔﺮﺍﻓﻲ ﺑﺮﺍﻱ ﻛﺸﻒ ﺩﻭ ﻧﻮﻉ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﻣﻔﻴﺪ ﺍﺳﺖ ‪:‬‬

‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯ ﺭﻭﺵ ﻛﺎﺭ ﻭﺍﻗﻌﻲ ﻧﺎﺷﻲ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯ ﻫﻤﻜﺎﺭﻱ ﻭ ﺁﮔﺎﻫﻲ ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺍﻓﺮﺍﺩ ﺩﻳﮕﺮ‬
‫ﺑﻪ ﺩﺳﺖ ﻣﻲ ﺁﻳﺪ ‪.‬‬
 ‫ﺍﺗﻨﺎ ﮔﺮﺍﻓﯽ ﻭ ﺳﺎﺧﺖ ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ ﺑﺮﺍی‬
‫ﺗﺤﻠﻴﻞ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬

‫ﺟﻠﺴﺎﺕ‬
‫ﺗﺤﻠﻴﻞ ﺍﺗﻨﺎ ﮔﺮﺍﻓﻲ‬ ‫ﺍﺗﻨﺎﮔﺮﺍﻓﻲ ﺗﺄﻛﻴﺪﻱ‬
‫ﮔﺰﺍﺭﺵ ﺩﻫﻲ‬

‫ﺍﺭﺯﻳﺎﺑﻲ ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ‬

‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﻛﻠﻲ‬ ‫ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ ﺳﻴﺴﺘﻢ‬

 ‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﯽ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻔﯽ ﺍﺯ ﮐﻨﺘﺮﻝ ﻫﺎ ﺑﺎﻳﺪ ﺑﺮ ﺭﻭی ﺳﻨﺪ‬
‫ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺍﻧﺠﺎﻡ ﺷﻮﺩ ‪:‬‬
‫ﻫﺎی ﺍﻋﺘﺒﺎﺭی ‪.‬‬ ‫ﮐﻨﺘﺮﻝ‬ ‫‪-1‬‬
‫ﻫﺎی ﺳﺎﺯﮔﺎﺭی ‪.‬‬ ‫ﮐﻨﺘﺮﻝ‬ ‫‪-2‬‬
‫ﻫﺎی ﺗﻤﺎﻣﻴﺖ ‪.‬‬ ‫ﮐﻨﺘﺮﻝ‬ ‫‪-3‬‬
‫ﻫﺎی ﻭﺍﻗﻊ ﮔﺮﺍﻳﯽ ‪.‬‬ ‫ﮐﻨﺘﺮﻝ‬ ‫‪-4‬‬
‫ﻭﺍﺭﺳﯽ ‪.‬‬ ‫ﻗﺎﺑﻠﻴﺖ‬ ‫‪-5‬‬
‫ﺗﮑﻨﻴﮏ ﻫﺎﻳﯽ ﮐﻪ ﺑﺮﺍی ﻭﺍﺭﺳﯽ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻭﺟﻮﺩ ﺩﺍﺭﻧﺪ ‪:‬‬
‫‪ -1‬ﻣﺮﻭﺭﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬
‫‪ -2‬ﺳﺎﺧﺖ ﻧﻤﻮﻧﻪ ﺍﻭﻟﻴﻪ ‪.‬‬
‫‪ -3‬ﺗﻮﻟﻴﺪ ﻣﻮﺍﺭﺩ ﺗﺴﺖ ‪.‬‬
 ‫ﻣﺮﻭﺭ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻣﺮﻭﺭ ﻣﻤﮑﻦ ﺍﺳﺖ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺭﺍ ﮐﻨﺘﺮﻝ ﮐﻨﺪ ‪:‬‬

‫ﻭﺍﺭﺳﯽ ‪.‬‬ ‫‪-1‬‬

‫ﻓﺎﺑﻠﻴﺖ ﺩﺭک ‪.‬‬ ‫‪-2‬‬
‫ﻗﺎﺑﻠﻴﺖ ﺭﺩﻳﺎﺑﯽ ‪.‬‬ ‫‪-3‬‬
‫ﻗﺎﺑﻠﻴﺖ ﺗﻄﺒﻴﻖ ‪.‬‬ ‫‪-4‬‬
 ‫ﻣﺪﻳﺮﻳﺖ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻓﺮﺍﻳﻨﺪ ﺩﺭک ﻭ ﮐﻨﺘﺮﻝ ﺗﻐﻴﻴﺮﺍﺕ ﺩﺭﺧﻮﺍﺳﺘﻪ ﻫﺎی ﺳﻴﺴﺘﻢ‬
‫ﺍﺳﺖ‪.‬‬
‫ﺑﺪﻻﻳﻞ ﺯﻳﺮ ﻭﻗﺘﯽ ﮐﺎﺭﺑﺮﺍﻥ ﻧﻬﺎﻳﯽ ﺑﺎ ﺳﻴﺴﺘﻢ ﺗﺠﺮﺑﻪ ﮐﺴﺐ‬
‫ﮐﺮﺩﻧﺪ‪ ،‬ﺧﻮﺍﺳﺘﻪ ﻫﺎی ﺟﺪﻳﺪ ﭘﻴﺪﺍ ﻣﯽ ﺷﻮﺩ ‪:‬‬

‫‪ -1‬ﻣﻌﻤﻮﻻً ﺳﻴﺴﺘﻢ ﻫﺎی ﺑﺰﺭگ ﮐﺎﺭﺑﺮﺍﻥ ﻣﺘﻨﻮﻋﯽ ﺩﺍﺭﻧﺪ ‪.‬‬

‫‪ -2‬ﺍﻓﺮﺍﺩ ﻭ ﮐﺎﺭﺑﺮﺍﻧﯽ ﮐﻪ ﺑﺎ ﺳﻴﺴﺘﻢ ﺳﺮﻭﮐﺎﺭ ﺩﺍﺭﻧﺪ ﺛﺎﺑﺖ‬
‫ﻧﻴﺴﺘﻨﺪ ‪.‬‬
‫‪ -3‬ﻣﺤﻴﻂ ﺗﺠﺎﺭی ﻭ ﺗﮑﻨﻴﮑﯽ ﺳﻴﺴﺘﻢ ﺗﻐﻴﻴﺮ ﻣﯽ ﮐﻨﺪ ‪.‬‬
‫ﺍﺯ ﺩﻳﺪﮔﺎﻩ ﺗﮑﺎﻣﻞ ‪ ،‬ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ‬
‫ﺗﻘﺴﻴﻢ ﻣﯽ ﺷﻮﻧﺪ ‪:‬‬
‫‪ -1‬ﺧﻮﺍﺳﺘﻪ ﻫﺎی ﭘﺎﻳﺪﺍﺭ ‪.‬‬

‫‪ -2‬ﺧﻮﺍﺳﺘﻪ ﻫﺎی ﻧﺎﭘﺎﻳﺪﺍﺭ ‪.‬‬

‫ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰی ﻣﺪﻳﺮﻳﺖ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﺩﺭ ﻣﺪﻳﺮﻳﺖ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺗﺼﻤﻴﻢ ﮔﻴﺮی‬
‫ﻣﯽ ﺷﻮﺩ ‪:‬‬

‫‪ -1‬ﺷﻨﺎﺳﺎﻳﯽ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬

‫‪ -2‬ﻓﺮﺍﻳﻨﺪ ﻣﺪﻳﺮﻳﺖ ﺗﻐﻴﻴﺮ ‪.‬‬
‫‪ -3‬ﺳﻴﺎﺳﺖ ﻫﺎی ﺭﺩﻳﺎﺑﯽ ‪.‬‬
‫‪ -4‬ﭘﺸﺘﻴﺒﺎﻧﯽ ﺍﺑﺰﺍﺭ ﮐﻴﺲ ‪.‬‬
‫ﺳﻪ ﻧﻮﻉ ﺍﻁﻼﻋﺎﺕ ﻗﺎﺑﻞ ﺭﺩﻳﺎﺑﯽ ﻭﺟﻮﺩ ﺩﺍﺭﻧﺪ ﮐﻪ‬
‫ﻣﯽ ﺗﻮﺍﻧﻨﺪ ﻧﮕﻬﺪﺍﺭی ﺷﻮﻧﺪ ‪:‬‬
‫‪ -1‬ﺍﻁﻼﻋﺎﺕ ﻗﺎﺑﻠﻴﺖ ﺭﺩﻳﺎﺑﯽ ﻣﺒﺪﺍء ‪.‬‬

‫‪ -2‬ﺍﻁﻼﻋﺎﺕ ﻗﺎﺑﻠﻴﺖ ﺭﺩﻳﺎﺑﯽ ﺧﻮﺍﺳﺘﻪ ﻫﺎ ‪.‬‬

‫‪ -3‬ﺍﻁﻼﻋﺎﺕ ﺭﺩﻳﺎﺑﯽ ﻁﺮﺍﺣﯽ ‪.‬‬

‫ﺍﺑﺰﺍﺭﻫﺎی ﮐﻴﺴﯽ ﮐﻪ ﺍﺯ ﻣﺪﻳﺮﻳﺖ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﭘﺸﺘﻴﺒﺎﻧﯽ ﻣﯽ ﮐﻨﺪ ‪:‬‬
‫‪ -1‬ﺫﺧﻴﺮﻩ ﺳﺎﺯی ﺧﻮﺍﺳﺘﻪ ﻫﺎ‪.‬‬
‫‪ -2‬ﻣﺪﻳﺮﻳﺖ ﺗﻐﻴﻴﺮ ‪.‬‬
‫‪ -3‬ﻣﺪﻳﺮﻳﺖ ﻗﺎﺑﻠﻴﺖ ﺭﺩﻳﺎﺑﯽ ‪.‬‬
 ‫ﻣﺪﻳﺮﻳﺖ ﺗﻐﻴﻴﺮ ﺧﻮﺍﺳﺘﻪ ﻫﺎ‬
‫ﻓﺮﺍﻳﻨﺪ ﻣﺪﻳﺮﻳﺖ ﺗﻐﻴﻴﺮﺍﺕ ﺳﻪ ﻣﺮﺣﻠﻪ ﺩﺍﺭﺩ ‪:‬‬

‫‪ -1‬ﺗﺤﻠﻴﻞ ﻣﺴﺌﻠﻪ ﻭ ﺗﻌﻴﻴﻦ ﻣﺸﺨﺼﺎﺕ ‪.‬‬

‫‪ -2‬ﺗﺤﻠﻴﻞ ﺗﻐﻴﻴﺮ ﻭ ﺗﻌﻴﻴﻦ ﻫﺰﻳﻨﻪ ‪.‬‬
‫‪ -3‬ﭘﻴﺎﺩﻩ ﺳﺎﺯی ﺗﻐﻴﻴﺮ ‪.‬‬
‫ﭼﻬﺎﺭﻡ‬ ‫ﺑﺨﺶ‬

‫ﻁﺮﺍﺣﯽ‬
 ‫ﻓﺼﻞ ‪10‬‬

‫ﻣﺪﻝ ﻫﺎی ﺳﻴﺴﺘﻢ‬

‫ﺳﻴﺴﺘﻢ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺍﺯ ﺍﺑﻌﺎﺩ ﻣﺨﺘﻠﻒ ﻧﺸﺎﻥ ﺩﺍﺩ‪:‬‬

‫‪ -1‬ﺑﻌﺪ ﺧﺎﺭﺟﻲ ﻛﻪ ﺣﻴﻄﻪ ﻳﺎ ﻣﺤﻴﻂ ﺳﻴﺴﺘﻢ ﻣﺪﻝ ﺳﺎﺯﻱ ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫‪ -2‬ﺑﻌﺪ ﺭﻓﺘﺎﺭﻱ ﻛﻪ ﺭﻓﺘﺎﺭ ﺳﻴﺴﺘﻢ ﻣﺪﻝ ﺳﺎﺯﻱ ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫‪ -3‬ﺑﻌﺪ ﺳﺎﺧﺘﺎﺭﻱ ﻛﻪ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻣﺪﻝ ﺳﺎﺯﻱ ﻣﻲ ﺷﻮﺩ ‪.‬‬

 ‫ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻒ ﻣﺪﻝ ﺳﻴﺴﺘﻢ‬

‫)‪(Data Flow Diagram‬‬ ‫‪ -1‬ﻣﺪﻝ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ‪.‬‬

‫)‪(Entity Relation Diagram‬‬ ‫‪ -2‬ﻣﺪﻝ ﺗﺮﻛﻴﺒﻲ ‪.‬‬
‫)‪(Architecture‬‬ ‫‪ -3‬ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ ‪.‬‬
‫)‪(Inheritance/Class‬‬ ‫‪ -4‬ﻣﺪﻝ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ‪.‬‬
‫‪ -5‬ﻣﺪﻝ ﻣﺤﺮﻙ‪ /‬ﭘﺎﺳﺦ ‪.‬‬
 ‫)‪(Architecture‬‬ ‫ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ‬
‫ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ ﺳﺎﺧﺘﺎﺭ ﺳﻴﺴﺘﻢ ﺍﻃﻼﻋﺎﺗﻲ ﻭ ﻣﺤﺒﻂ ﺳﻴﺴﺘﻢ ﺭﺍ ﺍﻣﺎ‬
‫ﺗﺸﺮﻳﺢ ﻣﻲ ﻛﻨﺪ‪،‬‬
‫ﺭﻭﺍﺑﻂ ﺑﻴﻦ ﺳﺎﻳﺮ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﻣﺤﻴﻂ ﻭ ﺳﻴﺴﺘﻢ‬
‫ﺭﺍ ﻣﺸﺨﺺ )‪ (Context Diagram in SSADM‬ﺩﺭﺣﺎﻝ ﺗﻮﺳﻌﻪ‬
‫ﻧﻤﻲ ﻛﻨﺪ‪.‬‬

‫ﺍﻳﻦ ﻣﺪﻝ ﺷﺎﻣﻞ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬

‫‪ -1‬ﻣﺪﻝ ﻫﺎﻱ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ‪.‬‬

‫‪ -2‬ﻣﺪﻝ ﻫﺎﻱ ﻓﺮﺁﻳﻨﺪ‪.‬‬
 ‫‪ATM‬‬ ‫ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ ﺩﺳﺘﮕﺎﻩ‬
‫ﺧﻮﺩﭘﺮﺩﺍﺯ‬
‫ﺳﻴﺴﺘﻢ ﺷﻌﺒﻪ ﻣﺮﻛﺰﻱ‬

‫ﺳﻴﺴﺘﻢ ﺍﻣﻨﻴﺘﻲ‬
‫ﺳﻴﺴﺘﻢ ﺣﺴﺎﺑﺪﺍﺭﻱ ﺷﻌﺒﻪ‬ ‫ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺣﺴﺎﺏ ﻫﺎ‬

‫ﻏﻴﺮﻩ‬ ‫ﺳﻴﺴﺘﻢ ﺗﺤﻮﻳﻠﺪﺍﺭ ﺧﻮﺩﻛﺎﺭ‬

‫ﺳﻴﺴﺘﻢ ﺷﻤﺎﺭﻧﺪﻩ ﺷﻌﺒﻪ‬ ‫ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻛﺎﺭﺑﺮﻱ‬

‫ﺳﻴﺴﺘﻢ ﻧﮕﻬﺪﺍﺭﻱ‬

‫ﻣﺸﺘﺮﻱ ﺧﻮﺩﭘﺮﺩﺍﺯ‬
 ‫ﻣﺪﻝ ﻫﺎﻱ ﺭﻓﺘﺎﺭﻱ‬
‫ﺍﻳﻦ ﻣﺪﻝ ﻫﺎ ﺑﺮﺍﻱ ﺗﻮﺻﻴﻒ ﺭﻓﺘﺎﺭ ﻛﻠﻲ ﺳﻴﺴﺘﻢ ﺑﻜﺎﺭ ﻣﻲ ﺭﻭﻧﺪ ‪.‬‬

‫ﺍﻳﻦ ﻣﺪﻝ ﺷﺎﻣﻞ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬

‫‪ -1‬ﻣﺪﻝ ﻫﺎﻱ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ‪ ،‬ﻛﻪ ﭘﺮﺩﺍﺯﺵ ﺩﺍﺩﻩ ﻫﺎ ﺭﺍ ﺩﺭﺳﻴﺴﺘﻢ ﻣﺪﻝ‬

‫ﺳﺎﺯﻱ ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫‪ -2‬ﻣﺪﻝ ﻫﺎﻱ ﻣﻴﺎﺷﻦ ﺣﺎﻟﺖ‪ ،‬ﻛﻪ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ﺳﻴﺴﺘﻢ ﭼﮕﻮﻧﻪ ﺑﻪ‬
‫ﺭﻭﻳﺪﺍﺩﻫﺎ ﭘﺎﺳﺦ ﻣﻲ ﺩﻫﺪ ‪.‬‬
 ‫)‪(DFD‬‬ ‫ﻣﺪﻝ ﻫﺎی ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ‬
‫ﺭﻭﺵ ﺷﻬﻮﺩی ﺑﺮﺍی ﻧﻤﺎﻳﺶ ﭼﮕﻮﻧﮕﯽ ﭘﺮﺩﺍﺯﺵ ﺩﺍﺩﻩ ﻫﺎ‬
‫ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﺍﺳﺖ‪) .‬ﺭﻭﺵ ﺗﺠﺰﻳﻪ ﺑﺎﻻ ﺑﻪ ﭘﺎﻳﻴﻦ(‬
‫ﺍﻳﻦ ﻣﺪﻝ ﻫﺎ ﺩﺭ ﺭﺩﻳﺎﺑﯽ ﻭ ﻣﺴﺘﻨﺪ ﺳﺎﺯی ﭼﮕﻮﻧﮕﯽ ﺍﻧﺘﻘﺎﻝ‬
‫ﺩﺍﺩﻩ ﻫﺎی ﻣﺮﺑﻮﻁ ﺑﻪ ﻳﮏ ﭘﺮﺩﺍﺯﺵ ﺩﺭ ﺳﻴﺴﺘﻢ‪ ،‬ﺑﻪ ﺗﺤﻠﻴﻞ‬
‫ﻓﺮﻡ‬ ‫ﮐﻤﮏ ﻣﯽﻓﺮﻡ ﮐﻨﻨﺪ ‪.‬‬
‫ﮔﺮﺍﻥ ﻓﺮﻡ‬
‫ﺳﻔﺎﺭﺵ ﺍﻣﻀﺎء‬
‫ﺳﻔﺎﺭﺵ‬ ‫ﺳﻔﺎﺭﺵ‬ ‫ﺳﻔﺎﺭﺵ‬
‫ﻭ ﮐﻨﺘﺮﻝ ﺷﺪﻩ‬
‫ﮐﺎﻣﻞ ﺷﺪﻩ‬ ‫ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬ ‫ﺍﺭﺳﺎﻝ ﺑﻪ ﻋﺮﺿﻪ ﮐﻨﻨﺪﻩ ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬
‫‪+‬‬
‫ﮐﺎﻣﻞ ﮐﺮﺩﻥ ﻓﺮﻡ ﺳﻔﺎﺭﺵ‬ ‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﯽ ﺳﻔﺎﺭﺵ‬ ‫ﺛﺒﺖ ﺳﻔﺎﺭﺵ‬ ‫ﺳﻨﺪ ﺳﻔﺎﺭﺵ‬
‫ﻓﺮﻡ‬ ‫ﺗﻨﻈﻴﻢ ﺑﻮﺩﺟﻪ ﻣﻮﺟﻮﺩ‬
‫ﺟﺰﺋﻴﺎﺕ‬ ‫ﺳﻔﺎﺭﺵ‬
‫ﺟﺰﺋﻴﺎﺕ ﺳﻔﺎﺭﺵ ‪ +‬ﻓﺮﻡ‬
‫ﺳﻔﺎﺭﺵ‬ ‫ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬ ‫ﻣﻴﺰﺍﻥ ﺷﻔﺎﺭﺵ ‪+‬‬
‫ﺳﻔﺎﺭﺵ ﺧﺎﻟﯽ‬
‫ﺟﺰﺋﻴﺎﺕ ﺣﺴﺎﺏ‬
‫ﺑﺮﺍی ﭘﺮﺩﺍﺯﺵ‬
‫ﻓﺎﻳﻞ ﺳﻔﺎﺭﺵ‬ ‫ﻓﺎﻳﻞ ﺑﻮﺩﺟﻪ‬
‫‪ DFD‬ﺳﻔﺎﺭﺵ‬
 ‫ﻣﺪﻝ ﻫﺎﻱ ﻣﺎﺷﻴﻦ ﺣﺎﻟﺖ‬
‫ﻣﺪﻝ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﺑﺮﺍﻱ ﭘﺎﺳﺦ ﮔﻮﻳﻲ ﺑﻪ ﺭﻭﻳﺪﺍﺩﻫﺎﻱ ﺩﺍﺧﻠﻲ ﻳﺎ ﺧﺎﺭﺟﻲ‬
‫ﺑﻜﺎﺭ ﻣﻲ ﺭﻭﺩ ﻛﻪ ﻣﻮﺟﺐ ﺍﻧﺘﻘﺎﻝ ﺳﻴﺴﺘﻢ ﺍﺯﺣﺎﻟﺘﻲ ﺑﻪ ﺣﺎﻟﺖ ﺩﻳﮕﺮ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬
‫ﻣﺸﻜﻞ ﻣﺪﻝ ﻣﺎﺷﻴﻦ ﺣﺎﻟﺖ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺗﻌﺪﺍﺩ ﺣﺎﻟﺖ ﻫﺎﻱ ﻣﻤﻜﻦ ﺑﻪ‬
‫ﺳﺮﻋﺖ ﺭﺷﺪ ﻣﻲ ﻛﻨﺪ ‪ .‬ﺍﻳﻦ ﻧﻮﻉ ﻣﺪﻝ‪ ،‬ﻣﺨﺼﻮﺻﺎ ﺑﺮﺍﻱ ﻣﺪﻝ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ‬
‫ﻫﺎﻱ ﺑﻴﺪﺭﻧﮓ‬
‫)‪ (Real-Time Systems‬ﺑﻜﺎﺭ ﻣﻲ ﺭﻭﺩ‪.‬‬
 ‫‪Entity-Relation Diagram‬‬ ‫ﻣﺪﻝ ﻫﺎﻱ ﺩﺍﺩﻩ ﻫﺎ‬
‫ﺑﺨﺶ ﻣﻬﻤﻲ ﺍﺯ ﻣﺪﻝ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﺗﻌﺮﻳﻒ ﺷﻜﻞ ﻣﻨﻄﻘﻲ ﺩﺍﺩﻩ ﻫﺎﻳﻲ‬
‫ﺍﺳﺖ ﻛﻪ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﭘﺮﺩﺍﺯﺵ ﻣﻲ ﺷﻮﻧﺪ ‪ .‬ﺍﻳﻦ ﻣﺪﻝ ﻫﺎ ﺭﺍ ﮔﺎﻫﻲ ﻣﺪﻝ‬
‫ﻫﺎﻱ ﺩﺍﺩﻩ ﻣﻌﻨﺎﻳﻲ ﻣﻲ ﻧﺎﻣﻨﺪ ‪.‬‬

‫ﺍﻣﺘﻴــﺎﺯﺍﺕ ﺍﺳــﺘﻔﺎﺩﻩ ﺍﺯ ﺩﻳﻜﺸــﻨﺮﻱ‬

‫ﺩﺍﺩﻫﺎ ‪:‬‬
‫‪ -1‬ﺭﺍﻫﻜــﺎﺭﻱ ﺑــﺮﺍﻱ ﻣــﺪﻳﺮﻳﺖ ﻧــﺎﻡ‬
‫ﺍﺳﺖ ‪.‬‬
‫‪ -2‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺨﺰﻧﻲ ﺑﺮﺍﻱ ﺍﻃﻼﻋـﺎﺕ‬
‫ﺳﺎﺯﻣﺎﻧﻲ ﻋﻤﻞ ﻣﻲ ﻛﻨﺪ‪.‬‬
 ‫‪Class‬‬ ‫ﻣﺪﻝ ﻫﺎﻱ ﺷﻲء‬
‫ﻣﺪﻝ ﻫﺎﻱ ﺷﻲء ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﺮﺍﻱ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻭ ﭘﺮﺩﺍﺯﺵ‬
‫ﺁﻧﻬﺎ ﺑﻪ ﻛﺎﺭ ﮔﺮﻓﺘﻪ ﺷﻮﻧﺪ )ﻭﺭﺍﺛﺖ ﺭﻭ ﺑﻪ ﺑﺎﻻ(‪.‬‬
‫ﻛﻼﺱ ‪ ،‬ﺍﻧﺘﺰﺍﻋﻲ ﺑﺮ ﺭﻭﻱ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺍﺷﻴﺎء ﺍﺳﺖ ﻛﻪ ﺻﻔﺎﺕ‬
‫ﻣﺘﺪﺍﻭﻝ ﻭ ﺳﺮﻭﻳﺲ ﻫﺎ ﻳﺎ ﻋﻤﻠﻴﺎﺗﻲ ﺭﺍ ﺳﻨﺎﺳﺎﻳﻲ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﺗﻮﺳﻂ ﻫﺮ‬
‫ﺷﻲء ﺍﺭﺍﺋﻪ ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫ﻣﺪﻝ ﻫﺎﻱ ﺷﻴﺌﻲ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ‪ -1‬ﻣﺪﻝ ﻫﺎﻱ ﻭﺭﺍﺛﺖ‪.‬‬

‫ﺗﻮﺳﻌﻪ ﻳﺎﺑﻨﺪ‪ ،‬ﺣﺎﻭﻱ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ‪ -2‬ﻣﺪﻝ ﻫﺎﻱ ﺗﺮﻛﻴﺒﻲ‪.‬‬
‫‪ -3‬ﻣﺪﻝ ﻫﺎﻱ ﺭﻓﺘﺎﺭﻱ ‪.‬‬ ‫ﻣﻲ ﺑﺎﺷﻨﺪ ‪:‬‬
 ‫‪UML‬‬ ‫ﻛﻼﺱ ﺷﻲء ﺩﺭ‬
‫ﺑﺼﻮﺭﺕ ﭼﻬﺎﺭ ﮔﻮﺷﻲ ﺑﺎﺳﻪ ﺑﺨﺶ‬ ‫‪UML‬‬ ‫ﻛﻼﺱ ﺷﻲء ﺩﺭ‬
‫ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﺩ ‪:‬‬
‫‪ -1‬ﻧﺎﻡ ﻛﻼﺱ ﺷﻲء ﺩﺭ ﺑﺨﺶ ﺑﺎﻻﻳﻲ ﻗﺮﺍﺭ ﺩﺍﺭﺩ ‪.‬‬
‫‪ -2‬ﺻﻔﺎﺕ ﻛﻼﺱ ﺩﺭ ﺑﺨﺶ ﻣﻴﺎﻧﻲ ﺍﻧﺪ ‪.‬‬
‫‪ -3‬ﻋﻤﻠﻴﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﻫﺮ ﻛﻼﺱ ﺷﻲء ﺩﺭ ﺑﺨﺶ ﭘﺎﻳﻴﻨﻲ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ‬
‫‪.‬‬
‫ﻛﺘﺎﺏ‬ ‫ﺿﺒﻂ ﺻﻮﺕ‬
‫ﻣﻮﻟﻒ‬ ‫ﺑﻠﻨﺪﮔﻮ‬
‫ﻭﻳﺮﺍﻳﺶ‬ ‫ﻣﺪﺕ‬
‫ﺗﺎﺭﻳﺦ ﻧﺸﺮ‬ ‫ﺗﺎﺭﻳﺦ ﺿﺒﻂ‬
‫ﺭﻭﻳﺪﺍﺩﻫﺎ‬ ‫ﺭﻭﻳﺪﺍﺩﻫﺎ‬

‫ﻛﺘﺎﺏ ﺳﺨﻨﮕﻮ‬
‫ﺗﻌﺪﺍﺩ ﺿﺒﻂ ﻫﺎ‬ ‫ﻭﺭﺍﺛﺖ ﭼﻨﺪﮔﺎﻧﻪ‬
‫ﺭﻭﻳﺪﺍﺩﻫﺎ‬
 ‫ﻣﺪﻝ ﺳﺎﺯﻱ ﺭﻓﺘﺎﺭ ﺷﻲء‬
‫ﺑﺮﺍﻱ ﻣﺪﻝ ﺳﺎﺯﻱ ﺭﻓﺘﺎﺭ ﺷﻲء ﺑﺎﻳﺪ ﻧﺸﺎﻥ ﺩﻫﻴﻢ ﻛﻪ ﭼﮕﻮﻧﻪ ﻋﻤﻠﻴﺎﺕ‬
‫ﺗﻬﻴﻪ ﺷﺪﻩ ﺗﻮﺳﻂ ﺷﻲء‪ ،‬ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﻧﺪ‪.‬‬
‫ﺩﺭ ‪ UML‬ﺭﻓﺘﺎﺭﻫﺎ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﻨﺎﺭﻳﻮ ﻫﺎﻳﻲ ﻣﺪﻝ ﺳﺎﺯﻱ ﻣﻲ ﺷﻮﺩ‬
‫ﻛﻪ ﻣﺒﺘﻨﻲ ﺑﺮ ﻣﻮﺍﺭﺩ ﻛﺎﺭﺑﺮﺩﻧﺪ ‪.‬‬
 ‫)‪(SSADM‬‬ ‫ﺭﻭﺵ ﻫﺎﻱ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ‬
‫ﻳﻚ ﺭﻭﺵ ﻣﻨﻈﻢ ﺑﺮﺍﻱ ﺗﻮﻟﻴﺪ ﻣﺪﻝ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻣﻮﺟﻮﺩ ﻳﺎ ﺳﻴﺴﺘﻤﻲ‬
‫ﺍﺳﺖ ﻛﻪ ﺑﺎﻳﺪ ﺳﺎﺧﺘﻪ ﺷﻮﺩ ‪.‬‬
‫ﺭﻭﺵ ﻫﺎﻱ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ﺩﺍﺭﺍﻱ ﺿﻌﻒ ﻫﺎﻱ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫‪ -1‬ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﺆﺛﺮﻱ ﺑﺮﺍﻱ ﺩﺭﻙ ﻣﺪﻝ ﺳﺎﺯﻱ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ‬
‫ﻏﻴﺮﻋﻤﻠﻜﺮﺩﻱ ﺳﻴﺴﺘﻢ ﻓﺮﺍﻫﻢ ﻧﻤﻲ ﻛﻨﻨﺪ ‪.‬‬
‫‪ -2‬ﭼﻨﺪﺍﻥ ﺭﻭﺷﻦ ﻧﻴﺴﺘﻨﺪ ‪.‬‬
‫‪ -3‬ﺍﺳﻨﺎﺩ ﺯﻳﺎﺩﻱ ﺗﻮﻟﻴﺪ ﻣﻲ ﻛﻨﻨﺪ ‪.‬‬
‫‪ -4‬ﻣﺪﻝ ﻫﺎﻳﻲ ﻛﻪ ﺗﻮﻟﻴﺪ ﻣﻲ ﺷﻮﻧﺪ ﺑﺴﻴﺎﺭ ﻣﺸﺮﻭﺡ ﺍﻧﺪ ‪.‬‬
 ‫ﻣﺤﻴﻂ ﻛﺎﺭﻱ ﺗﺤﻠﻴﻞ ﻭ ﻃﺮﺍﺣﻲ‬

‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﻧﻤﻮﺩﺍﺭﺳﺎﺯﻱ‬ ‫ﺍﻣﻜﺎﻧﺎﺕ ﺗﻮﻟﻴﺪ‬

‫ﺩﻳﻜﺸﻨﺮﻱ ﺩﺍﺩﻩ ﻫﺎ‬
‫ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ‬ ‫ﮔﺰﺍﺭﺵ‬

‫ﻣﺨﺰﻥ ﻣﺮﻛﺰﻱ‬
‫ﻣﻮﻟﺪ ﻛﺪ‬ ‫ﺍﻣﻜﺎﻧﺎﺕ ﺯﺑﺎﻥ ﺗﻘﺎﺿﺎ‬
‫ﺍﻃﻼﻋﺎﺕ‬

‫ﺍﺑﺰﺍﺭﻫﺎﻱ‬ ‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﺗﺤﻠﻴﻞ‪،‬‬ ‫ﺍﻣﻜﺎﻧﺎﺕ ﻭﺍﺭﺩﺍﺕ ﻭ‬

‫ﺗﻮﻟﻴﺪ ﻓﺮﻡ ﻫﺎ‬ ‫ﻃﺮﺍﺣﻲ ﻭ ﻛﻨﺘﺮﻝ‬ ‫ﺻﺎﺩﺭﺍﺕ‬
‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺭﻭﺵ ﻫﺎﻱ ﺳﺎﺧﺖ ﻳﺎﻓﺘﻪ ‪:‬‬
‫‪ -1‬ﻭﻳﺮﺍﺳﺘﺎﺭﻫﺎﻱ ﻧﻤﻮﺩﺍﺭ ‪.‬‬
‫‪ -2‬ﺍﺑﺰﺍﺭﻫﺎﻱ ﺗﺤﻠﻴﻞ‪ ،‬ﻃﺮﺍﺣﻲ ﻭ ﻛﻨﺘﺮﻝ ‪.‬‬
‫‪ -3‬ﺍﻣﻜﺎﻧﺎﺕ ﺯﺑﺎﻥ ﺗﻘﺎﺿﺎ ‪.‬‬
‫‪ -4‬ﺩﻳﻜﺸﻨﺮﻱ ﺩﺍﺩﻩ ﻫﺎ ‪.‬‬
‫‪ -5‬ﺍﺑﺰﺍﺭﻫﺎﻱ ﺗﻌﺮﻳﻒ ﻭ ﺗﻮﻟﻴﺪ ﮔﺰﺍﺭﺵ ‪.‬‬
‫‪ -6‬ﺍﺑﺰﺍﺭﻫﺎﻱ ﺗﻌﺮﻳﻒ ﻓﺮﻡ ﻫﺎ ‪.‬‬
‫‪ -7‬ﺍﻣﻜﺎﻧﺎﺕ ﻭﺍﺭﺩﺍﺕ ﻭﺻﺎﺩﺭﺍﺕ ‪.‬‬
‫‪ -8‬ﻣﻮﻟﺪ ﻫﺎﻱ ﻛﺪ ‪.‬‬
 ‫ﻓﺼﻞ‪11‬‬

‫ﻃﺮﺍﺣﻲ ﻣﻌﻤﺎﺭﻱ‬
 ‫ﻃﺮﺍﺣﻲ ﻣﻌﻤﺎﺭﻱ‬
‫ﻓﺮﺍﻳﻨﺪ ﺍﻭﻟﻴﻪ ﻃﺮﺍﺣﻲ ﺟﻬﺖ ﺷﻨﺎﺳﺎﻳﻲ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﻭ ﺍﻳﺠﺎﺩ‬
‫ﭼﺎﺭﭼﻮﺑﻲ ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﻭ ﺍﺭﺗﺒﺎﻃﺎﺕ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‪ ،‬ﻛﻪ ﺷﺎﻣﻞ ﺷﻨﺎﺳﺎﻳﻲ‬
‫ﻣﻮﻟﻔﻪ ﻫﺎﻱ ﺍﺻﻠﻲ ﺳﻴﺴﺘﻢ ﻭ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﺁﻧﻬﺎﺳﺖ ‪ ،‬ﻣﻲ ﺑﺎﺷﺪ ‪.‬‬
‫)‪(Stakeholder‬‬
‫ﺳﻪ ﺍﻣﺘﻴﺎﺯ ﻃﺮﺍﺣﻲ ﻭ ﻣﺴﺘﻨﺪ ﺳﺎﺯﻱ ﻣﻌﻤﺎﺭﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪:‬‬
‫‪ -1‬ﺍﺭﺗﺒﺎﻁ ﺑﺎ ﻭﺍﮔﺬﺍﺭﻧﺪﮔﺎﻥ ‪.‬‬
‫‪ -2‬ﺗﺤﻠﻴﻞ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -3‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺩﺭ ﻣﻘﻴﺎﺱ ﺑﺎﻻ ‪.‬‬
‫ﻓﻌﺎﻟﻴﺖ ﻫﺎﻱ ﺯﻳﺮﺩﺭﺗﻤﺎﻡ ﻓﺮﺁﻳﻨﺪﻫﺎﻱ ﻃﺮﺍﺣﻲ‬
‫ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻣﺸﺘﺮﻙ ﺍﻧﺪ‪:‬‬
‫‪ -1‬ﺳﺎﺧﺘﺎﺭ ﺩﻫﻲ ﺳﻴﺴﺘﻢ ‪.‬‬
‫‪ -2‬ﻣﺪﻟﺴﺎﺯﻱ ﻛﻨﺘﺮﻝ ‪.‬‬
‫‪ -3‬ﺗﺠﺰﻳﻪ ﭘﻴﻤﺎﻧﻪ ﺍﻱ ‪.‬‬
‫ﻣﺪﻝ ﻫﺎﻱ ﻣﻌﻤﺎﺭﻱ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺗﻮﺳﻌﻪ ﻳﺎﺑﻨﺪ ‪:‬‬

‫‪ -1‬ﻣﺪﻝ ﺳﺎﺧﺘﺎﺭﻱ ﺍﻳﺴﺘﺎ ‪.‬‬

‫‪ -2‬ﻣﺪﻝ ﻓﺮﺍﻳﻨﺪ ﭘﻮﻳﺎ ‪.‬‬
‫‪ -3‬ﻣﺪﻝ ﻭﺍﺳﻂ ‪.‬‬
‫ﺑﺨﺸﻬﺎﻱ ﻣﺨﺘﻠﻒ ﺳﻴﺴﺘﻢ‬ ‫‪ -4‬ﻣﺪﻝ ﺭﺍﺑﻄﻪ ‪.‬‬
‫ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺎ ﻣﺪﻟﻬﺎﻱ‬
‫ﻣﻌﻤﺎﺭﻱ ﻣﺘﻔﺎﻭﺗﻲ‬
‫ﻃﺮﺍﺣﻲ ﺷﻮﻧﺪ ) ﻣﻌﻤﺎﺭ ﻱ‬ ‫‪ -5‬ﻣﺪﻝ ﺗﻮﺯﻳﻌﻲ ‪.‬‬
‫ﺗﺮﻛﻴﺒ ﻲ(‪.‬‬
 ‫‪ATM‬‬ ‫ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ )ﻧﻤﻮﺩﺍﺭﺑﻠﻮﻛﻲ( ﺩﺳﺘﮕﺎﻩ‬
‫ﺧﻮﺩﭘﺮﺩﺍﺯ‬
‫ﺳﻴﺴﺘﻢ ﺷﻌﺒﻪ ﻣﺮﻛﺰﻱ‬

‫ﺳﻴﺴﺘﻢ ﺍﻣﻨﻴﺘﻲ‬
‫ﺳﻴﺴﺘﻢ ﺣﺴﺎﺑﺪﺍﺭﻱ ﺷﻌﺒﻪ‬ ‫ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺣﺴﺎﺏ ﻫﺎ‬

‫ﻏﻴﺮﻩ‬ ‫ﺳﻴﺴﺘﻢ ﺗﺤﻮﻳﻠﺪﺍﺭ ﺧﻮﺩﻛﺎﺭ‬

‫ﺳﻴﺴﺘﻢ ﺷﻤﺎﺭﻧﺪﻩ ﺷﻌﺒﻪ‬ ‫ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻛﺎﺭﺑﺮﻱ‬

‫ﺳﻴﺴﺘﻢ ﻧﮕﻬﺪﺍﺭﻱ‬

‫ﻣﺸﺘﺮﻱ ﺧﻮﺩﭘﺮﺩﺍﺯ‬
‫ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﻪ ﺧﻮﺍﺳﺘﻪ ﻫﺎﻱ ﻏﻴﺮ‬
‫ﻋﻤﻠﻜﺮﺩﻱ ﺯﻳﺮ ﺑﺴﺘﮕﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ‪:‬‬
‫‪ -1‬ﻛﺎﺭﺍﻳﻲ ‪.‬‬
‫‪ -2‬ﺣﻔﺎﻇﺖ ‪.‬‬
‫‪ -3‬ﺍﻣﻨﻴﺖ ‪.‬‬
‫‪ -4‬ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ‪.‬‬
‫‪ -5‬ﻗﺎﺑﻠﻴﺖ ﻧﮕﻬﺪﺍﺭﻱ ‪.‬‬
 ‫ﺳﺎﺯﻣﺎﻥ ﺳﻴﺴﺘﻢ‬
‫ﺭﺍﻫﺒﺮﺩ ﭘﺎﻳﻪ ﺍﻱ ﺭﺍ ﻣﺸﺨﺺ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﺑﺮﺍﻱ ﺗﻌﻴﻴﻦ ﺳﺎﺧﺘﺎﺭ ﺳﻴﺴﺘﻢ‬
‫ﺑﻜﺎﺭ ﻣﻲ ﺭﻭﻧﺪ ‪.‬‬

‫ﺳﻪ ﺳﺒﻚ ﺳﺎﺯﻣﺎﻧﻲ ﺯﻳﺮ ﻛﺎﺭﺑﺮﺩ ﻭﺳﻴﻌﻲ ﺩﺍﺭﻧﺪ ‪:‬‬

‫‪ -1‬ﻣﺪﻝ ﻣﺨﺰﻥ ‪.‬‬
‫‪ -2‬ﻣﺪﻝ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ ‪.‬‬
‫‪ -3‬ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ‪.‬‬
 ‫ﻣﺪﻝ ﻣﺨﺰﻥ‬
‫ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺳﺎﺯﻧﺪﻩ ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﻃﻮﺭﻱ ﻣﺒﺎﺩﻟﻪ ﻛﻨﻨﺪ ﻛﻪ‬
‫ﺑﻄﻮﺭ ﻣﺆﺛﺮ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﻛﺎﺭ ﻛﻨﻨﺪ ‪ .‬ﻣﺪﻝ ﺳﻴﺴﺘﻤﻲ ﻛﻪ ﻣﺒﺘﻨﻲ ﺑﺮﺩﺍﺩﻩ ﻫﺎﻱ‬
‫ﻣﺸﺘﺮﻙ ﺍﺳﺖ ‪ ،‬ﻣﺪﻝ ﻣﺨﺰﻥ ﻧﺎﻣﻴﺪﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﺩﻭ ﺭﻭﺵ ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬

‫‪ -1‬ﺗﻤﺎﻡ ﺩﺍﺩﻩ ﻫﺎﻱ ﻣﺸﺘﺮﻙ ﺩﺭ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻣﺮﻛﺰﻱ ﻧﮕﻬﺪﺍﺭﻱ ﻣﻲ‬
‫ﺷﻮﻧﺪ ﻛﻪ ﺗﻤﺎﻡ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺩﺳﺘﺮﺳﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ‪.‬‬
‫‪ -2‬ﻫﺮ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‪ ،‬ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻣﺨﺼﻮﺻﻲ ﺩﺍﺭﺩ ‪ .‬ﺩﺍﺩﻩ ﻫﺎ ﺍﺯ ﻃﺮﻳﻖ‬
‫ﺍﺭﺳﺎﻝ ﭘﻴﺎﻡ ﺑﻴﻦ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﻣﺒﺎﺩﻟﻪ ﻣﻲ ﺷﻮﺩ ‪.‬‬
 ‫ﻣﺪﻝ ﻣﺨﺰﻥ‬
‫ﺍﻛﺜﺮﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯﺣﺠﻢ ﺯﻳـﺎﺭﻱ ﺍﻃﻼﻋـﺎﺕ ﺍﺳـﺘﻔﺎﺩﻩ ﻣـﻲ ﻛﻨﻨـﺪ‪،‬‬
‫ﻃﻮﺭﻱ ﺳﺎﺯﻣﺎﻥ ﺩﻫﻲ ﺷﺪﻩ ﺍﻧﺪ ﻛﻪ ﺍﺯﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻳﺎ ﻣﺨﺰﻥ ﻣﺸﺘﺮﻙ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﻨﺪ ‪ .‬ﻟﺬﺍ ﺍﻳﻦ ﻣﺪﻝ ﻣﻨﺎﺳﺐ ﺳﻴﺴﺘﻢ ﻫـﺎﻳﻲ ﺍﺳـﺖ ﻛـﻪ ﺩﺍﺩﻩ‬
‫ﻫﺎ ﺗﻮﺳﻂ ﻳﻚ ﺯﻳﺮﺳﻴﺴﺘﻢ ﺗﻮﻟﻴﺪ ﻭ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﻳﮕـﺮ ﺍﺳـﺘﻔﺎﺩﻩ‬
‫ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﻣﺎﻧﻨﺪ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ‪،‬ﺍﻃﻼﻋﺎﺕ ﻣﺪﻳﺮﻳﺖ ﻭﺍﺑﺰﺍﺭﻫﺎﻱ ﻛﻴﺲ‬
 ‫ﺍﻣﺘﻴﺎﺯﺍﺕ ﻭ ﻣﻌﺎﻳﺐ ﻣﺨﺰﻥ ﻣﺸﺘﺮﻙ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ ‪:‬‬
‫‪ -1‬ﺭﺍﻩ ﻣﺆﺛﺮﻱ ﺑﺮﺍﻱ ﺑﻪ ﺍﺷﺘﺮﺍﻙ ﮔﺬﺍﺷﺘﻦ ﺣﺠﻢ ﺯﻳﺎﺩﻱ ﺍﺯ ﺩﺍﺩﻩ ﻫﺎ ﺍﺳﺖ ‪.‬‬
‫‪ -2‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﺑﺎﻳﺪ ﺑﺎ ﻣﺪﻝ ﻣﺨﺰﻧﻲ ﻣﻮﺍﻓﻖ ﺑﺎﺷﻨﺪ ‪.‬‬
‫‪ -3‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺩﺍﺩﻩ ﻫﺎ ﺭﺍ ﺗﻮﻟﻴﺪ ﻣﻲ ﻛﻨﻨﺪ ﺑﻪ ﭼﮕـﻮﻧﮕﻲ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ‬
‫ﺁﻥ ﻫﺎ ﺗﻮﺳﻂ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﺗﻮﺟﻬﻲ ﻧﺪﺍﺭﻧﺪ ‪.‬‬
‫‪ -4‬ﺩﺭ ﺣﺠﻢ ﺯﻳﺎﺩ ﺍﻃﻼﻋﺎﺕ ‪ ،‬ﺗﻜﺎﻣﻞ ﺩﺷﻮﺍﺭ ﺍﺳﺖ ‪.‬‬
‫‪ -5‬ﺑﺮﻓﻌﺎﻟﻴﺖ ﻫﺎﻳﻲ ﻣﺜﻞ ﺗﻬﻴﻪ ﭘﺸﺘﻴﺒﺎﻥ‪ ،‬ﺣﻔﺎﻇﺖ ‪،‬ﻛﻨﺘـﺮﻝ ﺩﺳـﺘﻴﺎﺑﻲ ﻭ ﺗـﺮﻣﻴﻢ ﺍﺯ‬
‫ﺧﻄﺎ ﻣﺘﻤﺮﻛﺰ ﺍﺳﺖ ‪.‬‬
‫‪ -6‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺨﺘﻠـﻒ ﻣﻤﻜـﻦ ﺍﺳـﺖ ﺧﻮﺍﺳـﺘﻪ ﻫـﺎﻱ ﻣﺘﻔـﺎﻭﺗﻲ ﺩﺍﺷـﺘﻪ‬
‫ﺑﺎﺷﻨﺪ‪.‬‬
‫‪ -7‬ﻣﺪﻝ ﺍﺷﺘﺮﺍﻛﻲ ﺍﺯ ﻃﺮﻳﻖ ﻃﺮﺡ ﻛﻠﻲ ﻣﺨﺰﻥ ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪ -8‬ﺗﻮﺯﻳﻊ ﻣﺨﺰﻥ ﺩﺭ ﭼﻨﺪ ﻣﺎﺷﻴﻦ ﺩﺷﻮﺍﺭ ﺍﺳﺖ ‪.‬‬
 ‫ﻣﺪﻝ ﻣﺨﺰﻥ‪ :‬ﻣﻌﻤﺎﺭﻱ ﻣﺠﻤﻮﻋﻪ ﺍﺑﺰﺍﺭ ﻛﻴﺲ ﻣﺠﺘﻤﻊ‬

‫ﻭﻳﺮﺍﺳﺘﺎﺭ ﻃﺮﺍﺣﻲ‬ ‫ﻣﻮﻟﺪ ﻛﺪ‬

‫ﻣﺘﺮﺟﻢ ﻃﺮﺍﺣﻲ‬ ‫ﻣﺨﺰﻥ ﭘﺮﻭژﻩ‬ ‫ﻭﻳﺮﺍﺳﺘﺎﺭ ﺑﺮﻧﺎﻣﻪ‬

‫ﺗﺤﻠﻴﻞ ﮔﺮ ﻃﺮﺍﺣﻲ‬ ‫ﻣﻮﻟﺪ ﮔﺰﺍﺭﺵ‬

 ‫ﻣﺪﻝ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ )‪(Client / Server‬‬
‫ﻳﻚ ﻣﺪﻝ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ‪ ،‬ﺳﻴﺴﺘﻢ ﺑﻪ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎ ﻭ‬
‫ﺳﺮﻭﻳﺲ ﺩﻫﻨﺪﻩ ﻫﺎ ﺳﺎﺯﻣﺎﻧﺪﻫﻲ ﺷﺪﻩ ﺍﺳﺖ ‪.‬‬
‫ﻗﻄﻌﺎﺕ ﺍﺻﻠﻲ ﺍﻳﻦ ﻣﺪﻝ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ ‪:‬‬
‫‪ -1‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ ﻣﺴﺘﻘﻞ ﻛﻪ ﺳﺮﻭﻳﺲ ﻫﺎﻳﻲ ﺭﺍ ﺑﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ‬
‫ﻫﺎﻱ ﺩﻳﮕﺮ ﺍﺭﺍﺋﻪ ﻣﻲ ﻛﻨﻨﺪ )ﻣﺎﻧﻨﺪ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ ﻓﺎﻳﻞ ﻭ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ ﻛﺎﻣﭙﺎﻳﻞ(‪.‬‬
‫‪ -2‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻣﺸﺘﺮﻳﺎﻥ ﻛﻪ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ ﺍﺳـﺘﻔﺎﺩﻩ ﻣـﻲ‬
‫ﻛﻨﻨﺪ )ﺯﻳﺮﺳﻴﺴﺘﻢ ﻫﺎ(‪.‬‬
‫‪ -3‬ﺷﺒﻜﻪ ﺍﻱ ﻛﻪ ﺍﺟﺎﺯﻩ ﻣﻲ ﺩﻫﺪ ﻣﺸﺘﺮﻳﺎﻥ ﺑـﻪ ﺍﻳـﻦ ﺳـﺮﻭﻳﺲ ﻫـﺎ ﺩﺳﺘﺮﺳـﻲ‬
‫ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ )ﻣﺎﻧﻨﺪ ﻓﺮﺍﺧﻮﺍﻧﻲ ﺭﻭﻳﻪ ﺍﺯ ﺭﺍﻩ ﺩﻭﺭ(‪.‬‬
 ‫ﻣﺪﻝ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ )‪(Client / Server‬‬
‫ﺍﻛﺜﺮﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯﺣﺠﻢ ﺯﻳﺎﺭﻱ ﺍﻃﻼﻋﺎﺕ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﻨﺪﺭﻭﺵ‬
‫ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﺮﺍﻱ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﻣﺒﺘﻨﻲ ﺑﺮﻣﺨﺰﻥ‬
‫ﺑﻪ ﻛﺎﺭ ﺭﻭﺩ ﻛﻪ ﺩﺭﺁﻧﻬﺎ ﻣﺨﺰﻥ ﺑﻌﻨﻮﺍﻥ ﻛﺎﺭﮔﺰﺍﺭ ﻭﺯﻳﺮﺳﻴﺴﺘﻢ ﻫﺎﻳﻲ ﻛﻪ ﺑﻪ‬
‫ﻣﺨﺰﻥ ﺩﺳﺘﻴﺎﺑﻲ ﺩﺍﺭﻧﺪ‪ ،‬ﻣﺸﺘﺮﻱ ﺍﻧﺪ‪.‬‬
‫ﻣﻬﻤﺘﺮﻳﻦ ﺍﻣﺘﻴﺎﺯ ﻣﺪﻝ ﻣﺸﺘﺮﻱ‪-‬ﻛﺎﺭﮔﺰﺍﺭ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻣﻌﻤﺎﺭﻱ ﺗﻮﺯﻳﻌﻲ‬
‫ﺍﺳﺖ‪ .‬ﺷﺒﻜﻪ ﻫﺎﻳﻲ ﺑﺎ ﭼﻨﺪﭘﺮﺩﺍﺯﻧﺪﻩ ﺑﻄﻮﺭﻣﻮﺛﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﻧﺪ‪ .‬ﺑﻪ‬
‫ﺭﺍﺣﺘﻲ ﻣﻴﺘﻮﺍﻥ ﻛﺎﺭﮔﺰﺍﺭﺟﺪﻳﺪﻱ ﺍﺿﺎﻓﻪ ﻛﺮﺩ ﻭ ﺁﻥ ﺭﺍ ﺑﺎ ﺑﻘﻴﻪ ﺳﻴﺴﺘﻢ‬
‫ﻣﺠﺘﻤﻊ ﻧﻤﻮﺩ ﻭ ﻳﺎ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ ﺭﺍ ﻃﻮﺭﻱ ﺍﺭﺗﻘﺎء ﺩﺍﺩ ﻛﻪ ﺳﺎﻳﺮﺑﺨﺶ ﻫﺎﻱ‬
‫ﺳﻴﺴﺘﻢ ﺗﺤﺖ ﺗﺎﺛﻴﺮ ﻗﺮﺍﺭﻧﮕﻴﺮﻧﺪ‪.‬‬
‫ﻣﺪﻝ ﻣﺸﺘﺮﻱ‪-‬ﻛﺎﺭﮔﺰﺍﺭ‪ :‬ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻛﺘﺎﺑﺨﺎﻧﻪ‬
‫ﻓﻴﻠﻢ ﻭﻋﻜﺲ‬

‫ﻣﺸﺘﺮﻱ ‪1‬‬ ‫ﻣﺸﺘﺮﻱ ‪2‬‬ ‫ﻣﺸﺘﺮﻱ ‪3‬‬ ‫ﻣﺸﺘﺮﻱ ‪4‬‬

‫ﺷﺒﻜﻪ ﭘﻬﻨﺎﻱ ﺑﺎﻧﺪ ﮔﺴﺘﺮﺩﻩ‬

‫ﻛﺎﺭﮔﺰﺍﺭﻭﻳﺪﺋﻮ ﻛﺎﺭﮔﺰﺍﺭﻛﺎﺗﺎﻟﻮگ‬ ‫ﻛﺎﺭﮔﺰﺍﺭﺗﺼﻮﻳﺮ‬ ‫ﻛﺎﺭﮔﺰﺍﺭﺍﺑﺮﻣﺘﻦ‬

‫ﻛﺎﺗﺎﻟﻮگ‬ ‫ﻓﺎﻳﻠﻬﺎﻱ ﺑﺮﺵ ﻓﻴﻠﻢ‬ ‫ﻋﻜﺴﻬﺎﻱ ﺩﻳﺠﻴﺘﺎﻝ‬ ‫ﻭﺏ ﺍﺑﺮﻣﺘﻦ‬
 ‫ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ) ﻣﺪﻝ ﻣﺎﺷﻴﻦ ﺍﻧﺘﺰﺍﻋﻲ(‬
‫ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ﻳﻚ ﻣﻌﻤﺎﺭﻱ‪ ،‬ﺳﻴﺴﺘﻢ ﺭﺍ ﺑﺼﻮﺭﺕ ﻣﺠﻤﻮﻋـﻪ ﺍﻱ ﺍﺯ ﻻﻳـﻪ ﻫـﺎ ﺳـﺎﺯﻣﺎﻧﺪﻫﻲ‬
‫ﻣﻲ ﻛﻨﺪ ﻛﻪ ﻫﺮ ﻻﻳﻪ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎ ﺭﺍ ﺍﺭﺍﺋـﻪ ﻣـﻲ ﻛﻨـﺪ ‪ .‬ﺑﻌﺒـﺎﺭﺗﻲ ﺩﻳﮕـﺮ ‪،‬‬
‫ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ﻭﺍﺳﻂ ﺯﻳﺮﺳﻴﺴﺘﻢ ﻫﺎ ﺭﺍ ﻣﺪﻟﺴﺎﺯﻱ ﻣﻲ ﻛﻨﺪ‪ .‬ﻫﺮﻻﻳﻪ ﻳـﻚ ﻣﺎﺷـﻴﻦ ﺍﻧﺘﺰﺍﻋـﻲ‬
‫ﺭﺍ ﺗﻌﺮﻳﻒ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﺯﺑﺎﻥ ﻣﺎﺷﻴﻦ ﺁﻥ )ﺧﺪﻣﺎﺗﻲ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻻﻳﻪ ﺍﺭﺍﺋـﻪ ﻣـﻲ ﺷـﻮﺩ(‬
‫ﺑﺮﺍﻱ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺳﻄﺢ ﺑﻌﺪﻱ ﻣﺎﺷﻴﻦ ﺍﻧﺘﺰﺍﻋﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﻣﺪﻝ ﺍﺭﺟﺎﻉ‬ ‫ﺩﺭﭘﺮﻭﺗﻜﻞ ﺷﺒﻜﻪ ‪OSI‬‬

‫ﺭﻭﺵ ﻻﻳﻪ ﺍﻱ ﺍﺯ ﺗﻮﺳﻌﻪ ﺗﺪﺭﻳﺠﻲ ﺳﻴﺴﺘﻢ ﻫﺎ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲ ﻛﻨـﺪ ‪ .‬ﭘـﺲ ﺍﺯﺗﻮﺳـﻌﻪ ﻳـﻚ‬
‫ﻻﻳﻪ‪ ،‬ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﻌﻀﻲ ﺧﺪﻣﺎﺕ ﺍﺭﺍﺋـﻪ ﺷـﺪﻩ ﺗﻮﺳـﻂ ﻻﻳـﻪ ﺁﻣـﺎﺩﻩ‪ ،‬ﺩﺭﺍﺧﺘﻴﺎﺭﻛـﺎﺭﺑﺮﺍﻥ‬
‫ﻗﺮﺍﺭﺑﮕﻴﺮﺩ‪.‬‬

‫ﻋﻴﺐ ‪ :‬ﺑﺎ ﺗﻌﺪﺍﺩﺯﻳﺎﺩ ﻻﻳﻪ ﻫﺎ ‪ ،‬ﺗﻌﻴﻴﻦ ﺳﺎﺧﺘﺎﺭ ﺳﻴﺴﺘﻢ ﻭﻣﺪﻳﺮﻳﺖ ﻻﻳﻪ ﻫﺎ ﺩﺷﻮﺍﺭ ﺍﺳﺖ ‪.‬‬
‫ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ﻧﺴﺨﻪ ﻫﺎ‬

‫ﻻﻳﻪ ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﻻﻳﻪ ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ﺷﻲء‬
‫ﻻﻳﻪ ﺳﻴﺴﺘﻢ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‬
‫ﻻﻳﻪ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ‬
 ‫ﻣﺪﻝ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ‬
‫ﻣﺪﻝ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ‪ ،‬ﺩﺭ ﺳﻄﺢ ﻣﻌﻤﺎﺭﻱ ﺑﺎ ﺟﺮﻳﺎﻥ ﻛﻨﺘﺮﻝ‬
‫ﺑﻴﻦ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﺳﺮﻭﻛﺎﺭ ﺩﺍﺭﺩ‪.‬‬
‫ﺩﻭ ﺭﻭﺵ ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬
‫‪ -1‬ﻛﻨﺘﺮﻝ ﻣﺘﻤﺮﻛﺰ ‪.‬‬

‫‪ -2‬ﻛﻨﺘﺮﻝ ﺭﻭﻳﺪﺍﺩﻱ ‪.‬‬

 ‫ﻛﻨﺘﺮﻝ ﻣﺘﻤﺮﻛﺰ‬
‫ﺩﺭ ﻣﺪﻝ ﻛﻨﺘﺮﻝ ﻣﺘﻤﺮﻛﺰ ‪ ،‬ﻳﻚ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﺑﻪ ﻋﻨﻮﺍﻥ ﻛﻨﺘﺮﻟﮕﺮ‬
‫ﻣﺤﺴﻮﺏ ﻣﻲ ﺷﻮﺩ ﻭ ﻣﺴﺌﻮﻟﻴﺖ ﻣﺪﻳﺮﻳﺖ ﺑﺮ ﺍﺟﺮﺍﻱ ﺳﺎﻳﺮ ﺯﻳﺮ‬
‫ﺳﻴﺴﺘﻢ ﻫﺎ ﺭﺍ ﺑﻪ ﻋﻬﺪﻩ ﺩﺍﺭﺩ ‪.‬‬

‫ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻨﺘﺮﻝ ﺷﺪﻩ ﺑﺮﺣﺴﺐ ﺍﻳﻨﻜﻪ ﺑﺼﻮﺭﺕ ﺗﺮﺗﻴﺒﻲ ﻳﺎ‬
‫ﻣﻮﺍﺯﻱ ﺍﺟﺮﺍء‬
‫ﻣﻲ ﺷﻮﻧﺪ ‪ ،‬ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﻧﺪ ‪:‬‬
‫‪ - -1‬ﺑﺮﮔﺸﺖ‪) .‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﺮﺗﻴﺒﻲ ﻣﺎﻧﻨﺪﺯﺑﺎﻧﻬﺎﻱ ﺑﺮﻧﺎﻣﻪ ﺳﺎﺯﻱ(‬
‫ﻣﺪﻝ ﻓﺮﺍﺧﻮﺍﻧﻲ‬
‫‪ -2‬ﻣﺪﻝ ﻣﺪﻳﺮﻳﺖ‪) .‬ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﻮﺍﺯﻱ(‬
‫ﻣﺪﻝ ﻛﻨﺘﺮﻝ ﻣﺮﻛﺰﻱ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ‬
‫ﺑﻼﺩﺭﻧﮓ‬

‫ﻓﺮﺁﻳﻨﺪﻫﺎﻱ ﺳﻨﺴﻮﺭ‬ ‫ﻓﺮﺁﻳﻨﺪﻫﺎﻱ ﻣﺤﺮﻙ‬

‫ﻛﻨﺘﺮﻟﮕﺮ ﺳﻴﺴﺘﻢ‬

‫ﻭﺍﺳﻂ ﻛﺎﺭﺑﺮ ﻓﺮﺁﻳﻨﺪﻫﺎﻱ ﻣﺤﺎﺳﺒﺎﺗﻲ‬ ‫ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ﺧﻄﺎ‬

‫ﻣﺪﻝ ﻓﺮﺍﺧﻮﺍﻧﻲ ‪ -‬ﺑﺮﮔﺸﺖ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫ﻛﻨﺘﺮﻝ‬

‫ﺑﺮﻧﺎﻣﻪ ﺍﺻﻠﻲ‬

‫ﺭﻭﺍﻝ ‪1‬‬ ‫ﺭﻭﺍﻝ ‪2‬‬ ‫ﺭﻭﺍﻝ ‪3‬‬

‫ﺭﻭﺍﻝ ‪1.1‬‬ ‫ﺭﻭﺍﻝ ‪1.2‬‬ ‫ﺭﻭﺍﻝ ‪3.1‬‬ ‫ﺭﻭﺍﻝ ‪3.2‬‬

 ‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺭﻭﻳﺪﺍﺩﻱ‬
‫ﻣﺪﻝ ﻫﺎﻱ ﺭﻭﻳﺪﺍﺩﻱ‪ ،‬ﺗﻮﺳﻂ ﺭﻭﻳﺪﺍﺩﻫﺎﻱ ﺧﺎﺭﺟﻲ‬
‫ﻣﺸﺨﺺ ﻣﻲ ﺷﻮﻧﺪ ‪ .‬ﻫﺮﺯﻳﺮﺳﻴﺴﺘﻢ ﺑﻪ ﺭﻭﻳﺪﺍﺩﻫﺎﻱ ﺧﺎﺭﺟﻲ‬
‫ﭘﺎﺳﺦ ﻣﻲ ﺩﻫﺪ‪.‬‬
‫ﺩﻭ ﻣﺪﻝ ﺍﺯ ﻛﻨﺘﺮﻝ ﺭﻭﻳﺪﺍﺩﻱ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ ‪:‬‬
‫‪ -1‬ﻣﺪﻝ ﻫﺎﻱ ﭘﺨﺸﻲ ‪.‬‬

‫‪ -2‬ﻣﺪﻝ ﻫﺎﻱ ﻭﻗﻔﻪ ﺍﻱ ‪.‬‬

 ‫ﻣﺪﻝ ﻛﻨﺘﺮﻝ ﻣﺒﺘﻨﻲ ﺑﺮ ﭘﺨﺶ ﺍﻧﺘﺨﺎﺑﻲ‬
‫ﺯﻳﺮﺳﻴﺴﺘﻢ ‪1‬‬ ‫ﺯﻳﺮﺳﻴﺴﺘﻢ ‪2‬‬ ‫ﺯﻳﺮﺳﻴﺴﺘﻢ ‪3‬‬ ‫ﺯﻳﺮﺳﻴﺴﺘﻢ ‪4‬‬

‫ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ﭘﻴﺎﻡ ﻭ ﺭﻭﻳﺪﺍﺩ‬

‫ﻋﻴﺐ ‪ :‬ﻭﺟﻮﺩﺳﺮﺑﺎﺭﺯﻳﺎﺩ ﺣﺎﺻﻞ ﺍﺯﭘﺮﺩﺍﺯﺵ ﻫﺎ‪ ،‬ﻭ ﻋﺪﻡ‬

‫ﺩﺍﻧﺴﺘﻦ ﺯﻣﺎﻥ ﺍﺩﺍﺭﻩ ﻭﻣﺪﻳﺮﻳﺖ ﺭﻭﻳﺪﺍﺩ‪.‬‬
‫ﻣﺰﻳﺖ ‪ :‬ﺗﻜﺎﻣﻞ ﻧﺴﺒﺘﺎ ﺳﺎﺩﻩ‪.‬‬
 ‫ﻣﺪﻝ ﻛﻨﺘﺮﻝ ﻣﺒﺘﻨﻲ ﺑﺮ ﻭﻗﻔﻪ‬
‫ﻭﻗﻔﻪ ﻫﺎ‬

‫ﺑﺮﺩﺍﺭ ﻭﻗﻔﻪ‬

‫ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ‪ 4‬ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ‪ 3‬ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ‪ 2‬ﺍﺩﺍﺭﻩ ﻛﻨﻨﺪﻩ ‪1‬‬

‫ﻓﺮﺁﻳﻨﺪ ‪1‬‬ ‫ﻓﺮﺁﻳﻨﺪ ‪2‬‬ ‫ﻓﺮﺁﻳﻨﺪ ‪3‬‬ ‫ﻓﺮﺁﻳﻨﺪ ‪4‬‬

‫ﻋﻴﺐ ‪ :‬ﭘﻴﭽﻴﺪﮔﻲ ﺑﺮﻧﺎﻣﻪ ﻭ ﺩﺷﻮﺍﺭﻱ ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ‪.‬‬

‫ﻣﺰﻳﺖ ‪ :‬ﭘﺎﺳﺦ ﺳﺮﻳﻊ ﺑﻪ ﺭﻭﻳﺪﺍﺩﻫﺎ‪.‬‬
 ‫ﺳﺒﻚ ﻫﺎﻱ ﺗﺠﺰﻳﻪ ﭘﻴﻤﺎﻧﻪ ﺍﻱ‬
‫ﺗﻤﺎﻳﺰ ﺭﻭﺷﻨﻲ ﺑﻴﻦ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﻭ ﭘﻴﻤﺎﻧﻪ ﻫﺎ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﺍﻣﺎ ﺧﻮﺏ‬
‫ﺍﺳﺖ ﺁﻥ ﻫﺎ ﺭﺍ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺗﺼﻮﺭ ﻛﻨﻴﻢ ‪:‬‬
‫‪ -1‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ‪ ،‬ﺳﻴﺴﺘﻤﻲ ﺍﺳﺖ ﻛﻪ ﻋﻤﻠﻴﺎﺗﺶ ﺑﻪ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺍﺋﻪ‬
‫ﺷﺪﻩ ﺗﻮﺳﻂ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﻳﮕﺮ ﺑﺴﺘﮕﻲ ﻧﺪﺍﺭﺩ ‪ .‬ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ‬
‫ﺗﺮﻛﻴﺒﻲ ﺍﺯ ﭘﻴﻤﺎﻧﻪ ﻫﺎ ﻫﺴﺘﻨﺪ ﻭ ﻭﺍﺳﻂ ﻫﺎﻳﻲ ﺩﺍﺭﻧﺪ ﻛﻪ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺎ‬
‫ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﻳﮕﺮ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺭﻭﻧﺪ ‪.‬‬
‫‪ -2‬ﭘﻴﻤﺎﻧﻪ‪ ،‬ﻣﻌﻤﻮﻻً ﻳﻚ ﻗﻄﻌﻪ ﺍﺯ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﻳﺎ ﭼﻨﺪ‬
‫ﺳﺮﻭﻳﺲ ﺭﺍ ﺑﺮﺍﻱ ﭘﻴﻤﺎﻧﻪ ﻫﺎﻱ ﺩﻳﮕﺮ ﻓﺮﺍﻫﻢ ﻣﻲ ﺳﺎﺯﺩ ‪.‬‬
‫ﻫﻨﮕﺎﻡ ﺗﺠﺰﻳﻪ ﺯﻳﺮ ﺳﻴﺴﺘﻢ ﻫﺎ ﺑﻪ ﭘﻴﻤﺎﻧﻪ ﻫﺎ ﺍﺯ ﺩﻭ ﻣﺪﻝ‬
‫ﻣﻲ ﺗﻮﺍﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ‪:‬‬
‫‪ -1‬ﻣﺪﻝ ﺷﻲءﮔﺮﺍ ‪ :‬ﺳﻴﺴﺘﻢ ﺑﻪ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺍﺷﻴﺎء ﻣﺮﺗﺒﻂ ﺗﺠﺰﻳـﻪ‬
‫ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫‪ -2‬ﻣﺪﻝ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ﻫﺎ ‪ :‬ﺳﻴﺴﺘﻢ ﺑﻪ ﭘﻴﻤﺎﻧﻪ ﻫﺎﻱ ﻋﻤﻠﻜﺮﺩﻱ ﺗﻘﺴـﻴﻢ‬

‫ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺩﺍﺩﻩ ﻫـﺎﻱ ﻭﺭﻭﺩﻱ ﺭﺍ ﭘﺬﻳﺮﻓﺘـﻪ ﭘـﺲ ﺍﺯ ﺗﺒـﺪﻳﻼﺕ ﺑـﻪ‬
‫ﺧﺮﻭﺟﻲ ﻣﻲ ﺑﺮﺩ ‪.‬‬
‫ﻣﺪﻝ ﻫﺎﻱ ﺷﻲء‬
‫ﻣﺪﻝ ﺷﻲءﮔﺮﺍﻱ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ‪،‬‬
‫ﺳﺎﺧﺘﺎﺭ ﺳﻴﺴﺘﻢ ﺭﺍ ﺑﻪ ﺻﻮﺭﺕ‬
‫ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺍﺷﻴﺎء ﺩﺭ ﻣﻲ ﺁﻭﺭﺩ‬
‫ﻛﻪ ﺍﺗﺼﺎﻝ ﺿﻌﻴﻔﻲ ﺩﺍﺭﻧﺪ ﻭ ﻭﺍﺳﻄﻲ‬
‫ﺑﺮﺍﻱ ﺁﻧﻬﺎ ﺗﻌﺮﻳﻒ ﺷﺪﻩ ﺍﺳﺖ ‪.‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ‪ ،‬ﭼﻮﻥ ﺍﺷﻴﺎء ﻭﺍﺑﺴﺘﮕﻲ‬
‫ﭼﻨﺪﺍﻧﻲ ﺑﻪ ﻫﻢ ﻧﺪﺍﺭﻧﺪ‪ ،‬ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ‬
‫ﺍﺷﻴﺎ ﺑﺪﻭﻥ ﺗﺄﺛﻴﺮ ﺑﺮ ﺍﺷﻴﺎﻱ ﺩﻳﮕﺮ ﻗﺎﺑﻞ‬
‫ﺍﺻﻼﺡ ﺍﺳﺖ ‪.‬‬
 ‫ﻟﻮﻟﻪ ﻛﺸﻲ ﻋﻤﻞ ﮔﺮﺍ )‪(DFD‬‬
‫ﺩﺭ ﻣﺪﻝ ﻟﻮﻟﻪ ﻛﺸﻲ ﻋﻤﻞ ﮔﺮﺍ ﻳﺎ ﻣﺪﻝ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ‪ ،‬ﺗﺒﺪﻳﻼﺕ‬
‫ﻋﻤﻠﻜﺮﺩﻱ‪ ،‬ﻭﺭﻭﺩﻱ ﻫﺎﻳﺸﺎﻥ ﺭﺍ ﭘﺮﺩﺍﺯﺵ ﻣﻲ ﻛﻨﻨﺪ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻳﻲ ﺭﺍ‬
‫ﺗﻮﻟﻴﺪ ﻣﻲ ﻧﻤﺎﻳﻨﺪ ‪.‬‬
‫ﺍﻣﺘﻴﺎﺯﺍﺕ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ ‪:‬‬
‫‪ -1‬ﺍﺯ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺪﺩ ﺗﺒﺪﻳﻼﺕ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫‪ -2‬ﺷﻬﻮﺩﻱ ﺍﺳﺖ‪ ،‬ﺑﻪ ﻃﻮﺭﻱ ﻛﻪ ﺍﻓﺮﺍﺩ ﻛﺎﺭﺷﺎﻥ ﺭﺍ ﺑﺮ ﺣﺴﺐ ﭘﺮﺩﺍﺯﺵ ﻭﺭﻭﺩﻱ‬
‫‪ -‬ﺧﺮﻭﺟﻲ ﻣﻲ ﻧﮕﺮﻧﺪ ‪.‬‬
‫‪ -3‬ﺗﻜﺎﻣﻞ ﺳﻴﺴﺘﻢ ﺑﺎ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﺗﺒﺪﻳﻼﺕ ﺟﺪﻳﺪ‪ ،‬ﺁﺳﺎﻥ ﺍﺳﺖ ‪.‬‬
‫‪ -4‬ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺁﻥ ﺑﺼﻮﺭﺕ ﺳﻴﺴﺘﻢ ﺗﺮﺗﻴﺒﻲ ﻳﺎ ﻫﻤﺰﻣﺎﻥ‪ ،‬ﺁﺳﺎﻥ ﺍﺳﺖ ‪.‬‬
 ‫ﺩﻳﺎﮔﺮﺍﻡ ﺟﺮﻳﺎﻥ ﺩﺍﺩﻩ ﻫﺎ ﻣﺮﺑﻮﻁ ﺑﻪ ﺳﻴﺴﺘﻢ‬
‫ﺳﻔﺎﺭﺷﺎﺕ‬

‫ﻓﺮﻡ ﺳﻔﺎﺭﺵ‬ ‫ﻓﺮﻡ ﺳﻔﺎﺭﺵ‬ ‫ﻓﺮﻡ ﺳﻔﺎﺭﺵ‬ ‫ﺳﻔﺎﺭﺵ ﺍﻣﻀﺎء ﻭ‬

‫ﻛﺎﻣﻞ ﺷﺪﻩ‬ ‫ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬ ‫ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬ ‫ﻋﺮﺿﻪ ﻛﻨﻨﺪﻩﺍﺭﺳﺎﻝ ﺑﻪ‬ ‫ﻛﻨﺘﺮﻝ ﺷﺪﻩ ‪+‬‬
‫ﻛﺎﻣﻞ ﻛﺮﺩﻥ ﻓﺮﻡ ﺳﻔﺎﺭﺵ‬ ‫ﺍﻋﺘﺒﺎﺭﺳﻨﺠﻲ ﺳﻔﺎﺭﺵ‬ ‫ﺛﺒﺖ ﺳﻔﺎﺭﺵ‬ ‫ﺳﻨﺪ ﺳﻔﺎﺭﺵ‬
‫ﻓﺮﻡ‬ ‫ﺗﻨﻈﻴﻢ ﺑﻮﺩﺟﻪ ﻣﻮﺟﻮﺩ‬
‫ﺟﺰﺋﻴﺎﺕ‬
‫ﺳﻔﺎﺭﺵ‬
‫ﺳﻔﺎﺭﺵ‬ ‫ﻣﻴﺰﺍﻥ ﺷﻔﺎﺭﺵ ‪ +‬ﺟﺰﺋﻴﺎﺕ‬
‫ﺟﺰﺋﻴﺎﺕ ﺳﻔﺎﺭﺵ ‪ +‬ﻓﺮﻡ‬ ‫ﺍﻣﻀﺎ‪ .‬ﺷﺪﻩ‬
‫ﺣﺴﺎﺏ‬
‫ﺳﻔﺎﺭﺵ ﺧﺎﻟﻲ‬
‫ﻓﺎﻳﻞ ﺳﻔﺎﺭﺵ‬ ‫ﻓﺎﻳﻞ ﺑﻮﺩﺟﻪ‬
 ‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﺮﺟﻊ‬
‫ﻫﻨﮕﺎﻡ ﺍﻳﺠﺎﺩ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺟﺪﻳﺪ ﻣﻲ ﺗﻮﺍﻥ ﺩﻭﺑﺎﺭﻩ ﺍﺯ ﺳﺎﺧﺘﺎﺭ‬
‫ﻣﻌﻤﺎﺭﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ‪ .‬ﺍﻳﻦ ﻣﺪﻝ ﻫﺎ ﺭﺍ ﻣﻌﻤﺎﺭﻱ ﻭﻳﮋﻩ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ‬
‫ﻣﻲ ﻧﺎﻣﻨﺪ ‪.‬‬

‫ﺩﻭ ﻧﻮﻉ ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ ﻭﻳﮋﻩ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪:‬‬

‫‪ -1‬ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻛﻠﻲ‪) .‬ﻣﺎﻧﻨﺪ ﻣﺪﻝ ﻛﺎﻣﭙـﺎﻳﻠﺮ ﺷـﺎﻣﻞ ﭘﻴﻤﺎﻧـﻪ ﻫـﺎﻱ‬
‫ﺗﺤﻠﻴﻠﮕﺮﻟﻐــﻮﻱ‪ ،‬ﺗﺤﻠﻴﻠﮕﺮﻧﺤــﻮﻱ‪ ،‬ﺟــﺪﻭﻝ ﻧﻤﺎﺩ‪،‬ﺩﺭﺧــﺖ ﻧﺤــﻮﻱ‪،‬‬
‫ﺗﺤﻠﻴﻠﮕﺮﻣﻌﻨﺎﻳﻲ‪ ،‬ﻭ ﻣﻮﻟﺪﻛﺪ(‬
‫‪ -2‬ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﺮﺟﻊ‪) .‬ﻣﺎﻧﻨﺪ ﻣﺪﻝ ﻫﻔﺖ ﻻﻳﻪ ﺍﻱ ﺷﺒﻜﻪ ‪(OSI‬‬
‫ﭘﻨﺞ ﺳﻄﺢ ﺳﺮﻭﻳﺲ ﻫﺎ ﺩﺭ ﻣﺪﻝ ﻣﺮﺟﻊ ﻛﻴﺲ ﻋﺒﺎﺭﺕ ﺍﻧﺪ ﺍﺯ ‪:‬‬

‫‪ -1‬ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻣﺨﺰﻥ ﺩﺍﺩﻩ ‪.‬‬

‫‪ -2‬ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺟﺎﻣﻌﻴﺖ ﺩﺍﺩﻩ ‪.‬‬
‫‪ -3‬ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻣﺪﻳﺮﻳﺖ ﻭﻇﻴﻔﻪ ‪.‬‬
‫‪ -4‬ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﭘﻴﺎﻡ ‪.‬‬
‫‪ -5‬ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻭﺍﺳﻂ ﻛﺎﺭﺑﺮ ‪.‬‬
 ‫ﻓﺼﻞ‪12‬‬

‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﻮﺯﻳﻌﻲ‬

 ‫ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﻣﻬﻢ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﻮﺯﻳﻌﻲ‬
‫)‪(Distributed Systems‬‬
‫‪ -1‬ﺍﺷﺘﺮﺍﻙ ﻣﻨﺎﺑﻊ ‪.‬‬
‫‪ -2‬ﺑﺎﺯ ﺑﻮﺩﻥ ‪.‬‬
‫‪ -3‬ﻫﻤﺰﻣﺎﻧﻲ ‪.‬‬
‫‪ -4‬ﻣﻘﻴﺎﺱ ﭘﺬﻳﺮﻱ ‪.‬‬
‫‪ -5‬ﺗﺤﻤﻞ ﻋﻴﺐ ‪.‬‬
‫‪ -6‬ﺷﻔﺎﻓﻴﺖ ‪.‬‬
 ‫ﻣﻌﺎﻳﺐ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﻮﺯﻳﻌﻲ‬
‫‪ -1‬ﭘﻴﭽﻴــﺪﮔﻲ ‪ :‬ﺳﻴﺴــﺘﻢ ﻫــﺎﻱ ﺗــﻮﺯﻳﻌﻲ ﭘﻴﭽﻴــﺪﻩ ﺗــﺮ ﺍﺯ ﺳﻴﺴــﺘﻢ ﻫــﺎﻱ‬
‫ﻣﺘﻤﺮﻛــﺰ ﻫﺴــﺘﻨﺪ ﻛــﻪ ﺩﺭﻙ ﻭﻳﮋﮔــﻲ ﻫــﺎﻱ ﺟﺪﻳــﺪ ﻭﺗﺴــﺖ ﺁﻧﻬــﺎ ﺭﺍ‬
‫ﺩﺷﻮﺍﺭﻣﻲ ﻛﻨﺪ‪.‬‬
‫‪ -2‬ﺣﻔﺎﻇﺖ ‪ :‬ﺣﻔﺎﻇﺖ ﺩﺭ ﺷﺒﻜﻪ ﭘﺮﺗﺮﺍﻓﻴﻚ ﺩﺷﻮﺍﺭ ﺍﺳﺖ ‪.‬‬
‫‪ -3‬ﻣــﺪﻳﺮﻳﺖ ﭘــﺬﻳﺮﻱ ‪ :‬ﺗــﻼﺵ ﺯﻳــﺎﺩﻱ ﺑــﺮﺍﻱ ﻣــﺪﻳﺮﻳﺖ ﻭ ﻧﮕﻬــﺪﺍﺭﻱ‬
‫ﺳﻴﺴـﺘﻢ ﻻﺯﻡ ﺍﺳــﺖ ‪ .‬ﻛﺎﻣﭙﻴﻮﺗﺮﻫـﺎﻱ ﻣﺨﺘﻠــﻒ ﺯﻳـﺎﺩﻱ ﺑــﺎ ﻧﺴـﺨﻪ ﻫــﺎﻱ‬
‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫‪ -4‬ﻏﻴﺮ ﻗﺎﺑﻞ ﭘﻴﺶ ﺑﻴﻨﻲ ﺑﻮﺩﻥ ‪ :‬ﭘﺎﺳﺦ ﺳﻴﺴﺘﻢ ‪ ،‬ﺑﻪ ﺑﺎﺭ ﺳﻴﺴـﺘﻢ‪ ،‬ﺳـﺎﺯﻣﺎﻥ‬
‫ﺁﻥ ﻭ ﺑﺎﺭ ﺷﺒﻜﻪ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ ‪.‬‬
 ‫ﺍﻧﻮﺍﻉ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﻮﺯﻳﻌﻲ‬

‫‪ -1‬ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ‪ :‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ‬

‫ﺧﺪﻣﺎﺕ ﻛﻪ ﺗﻮﺳﻂ ﻛﺎﺭﮔﺰﺍﺭ ﺑﺮﺍﻱ ﻣﺸﺘﺮﻳﺎﻥ ﺁﻣﺎﺩﻩ ﻣﻲ‬
‫ﺷﻮﻧﺪ‪.‬‬
‫‪ -2‬ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﺷﻲء ﺗـﻮﺯﻳﻌﻲ‪ :‬ﻣﺠﻤﻮﻋـﻪ ﺍﻱ ﺍﺯﺍﺷـﻴﺎء‬
‫ﻛﻪ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﺩﺭ ﺗﻌﺎﻣﻞ ﻫﺴﺘﻨﺪ‪.‬‬
 ‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﭼﻨﺪ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺍﻱ‬
‫ﺳﺎﺩﻩ ﺗﺮﻳﻦ ﻣﺪﻝ ﺳﻴﺴﺘﻢ ﺗﻮﺯﻳﻌﻲ ﺍﺳﺖ ﻛﻪ ﺳﻴﺴﺘﻢ ﺍﺯ ﺗﻌﺪﺍﺩﻱ ﻓﺮﺍﻳﻨﺪ‬
‫ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺍﺳﺖ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺮ ﺭﻭﻱ ﭘﺮﺩﺍﺯﻧﺪﻩ ﻫﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ‬
‫ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪.‬‬
‫ﻣﺘﺪﺍﻭﻝ ﺩﺭﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺑﻼﺩﺭﻧﮓ‪.‬‬

‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ‬

‫ﺳﻴﺴﺘﻢ ﺑﺼﻮﺭﺕ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎ ﻭ ﻣﺸﺘﺮﻳﺎﻥ ﻣﺪﻝ ﺳﺎﺯﻱ ﻣﻲ‬
‫ﺷﻮﻧﺪ ‪ .‬ﺩﺭ ﺳﻴﺴﺘﻢ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ‪ ،‬ﻭﺍﺳﻂ ﻛﺎﺭﺑﺮ ﻫﻤﻴﺸﻪ ﺩﺭ ﻣﺸﺘﺮﻱ‬
‫ﺍﺟﺮﺍ ﻣﻲ ﺷﻮﺩ ﻭ ﻣﺪﻳﺮﻳﺖ ﺩﺍﺩﻩ ﻫﺎ ﺩﺭ ﻛﺎﺭﮔﺰﺍﺭ ﺻﻮﺭﺕ ﻣﻲ ﮔﻴﺮﺩ ‪.‬‬
 ‫ﻣﻌﻤﺎﺭﻱ ﭼﻨﺪ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺍﻱ‪:‬‬
‫ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﺗﺮﺍﻓﻴﻚ ﭼﻨﺪ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺍﻱ‬
‫‪Sensor 1‬‬

‫‪Sensor 2‬‬ ‫ﭘﺮﺩﺍﺯﻧﺪﻩ ﺳﻨﺴﻮﺭ‬ ‫ﭘﺮﺩﺍﺯﻧﺪﻩ ﺟﺮﻳﺎﻥ ﺗﺮﺍﻓﻴﻚ‬ ‫ﻓﺮﺁﻳﻨﺪﻛﻨﺘﺮﻝ ﭼﺮﺍﻍ ﺭﺍﻫﻨﻤﺎﺋﻲ‬

‫ﻓﺮﺁﻳﻨﺪ ﻛﻨﺘﺮﻝ ﺳﻨﺴﻮﺭ‬ ‫ﻓﺮﺁﻳﻨﺪ ﻧﻤﺎﻳﺸﮕﺮ‬ ‫ﻓﺮﺁﻳﻨﺪ ﻛﻨﺘﺮﻝ ﭼﺮﺍﻍ‬

‫…‬

‫…‬
‫ﺳﻨﺴﻮﺭﻫﺎ ﻭﺩﻭﺭﺑﻴﻦ ﻫﺎﻱ‬
‫‪Sensor n‬‬ ‫ﻛﻨﺴﻮﻝ ﻫﺎﻱ ﺍﭘﺮﺍﺗﻮﺭ‬ ‫ﭼﺮﺍﻍ ﻫﺎﻱ ﺭﺍﻫﻨﻤﺎﺋﻲ‬
‫ﺟﺮﻳﺎﻥ ﺗﺮﺍﻓﻴﻚ‬
 ‫ﺳﻴﺴﺘﻢ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭ‬

‫‪c4‬‬ ‫‪c12‬‬
‫‪c4‬‬
‫‪c2‬‬ ‫‪Server‬‬
‫‪c11‬‬
‫‪s1‬‬ ‫‪s4‬‬ ‫ﻓﺮﺍﻳﻨﺪ ﻛﺎﺭﮔﺰﺍﺭ‬
‫‪c1‬‬
‫‪c10‬‬
‫‪Client‬‬
‫‪c5‬‬ ‫‪s2‬‬ ‫‪s3‬‬ ‫ﻓﺮﺍﻳﻨﺪ ﻣﺸﺘﺮﻱ‬
‫‪c9‬‬
‫‪c6‬‬
‫‪c7‬‬ ‫‪c8‬‬
 ‫ﺳﺎﺩﻩ ﺗﺮﻳﻦ ﻣﻌﻤﺎﺭﻱ ﻣﺸﺘﺮﻱ ‪ -‬ﻛﺎﺭﮔﺰﺍﺭِ ﺩﻭ ﺭﺩﻳﻔﻲ ﻧﺎﻡ ﺩﺍﺭﺩ ﻛﻪ‬
‫ﺩﺭ ﺁﻥ ﻫﺮ ﻛﺎﺭﺑﺮﺩ ﺑﻪ ﺻﻮﺭﺕ ﻳﻚ ﻛﺎﺭﮔﺰﺍﺭ ﻭ ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ‬
‫ﻣﺸﺘﺮﻳﺎﻥ ﺗﺸﻜﻴﻞ ﻣﻲ ﺷﻮﺩ ﻭ ﺑﻪ ﺩﻭ ﺻﻮﺭﺕ ﻫﺴﺘﻨﺪ ‪:‬‬

‫ﻣﺪﻝ ﻣﺸﺘﺮﻱ‬ ‫ﻧﻤﺎﻳﺶ‬ ‫ﻛﺎﺭﮔﺰﺍﺭ‬

‫ﻣﺸﺘﺮﻱ ﺿﻌﻴﻒ‬ ‫‪ -1‬ﻣﺪﻝ ﻣﺸﺘﺮﻱ ﺿﻌﻴﻒ ‪.‬‬
‫ﻣﺪﻳﺮﻳﺖ ﺩﺍﺩﻩ ﻫﺎ‬
‫ﭘﺮﺩﺍﺯﺵ ﻛﺎﺭﺑﺮﺩ‬

‫ﻧﻤﺎﻳﺶ‬
‫‪ -2‬ﻣﺪﻝ ﻣﺸﺘﺮﻱ ﻗﻮﻱ ‪.‬‬
‫ﻣﺪﻝ ﻣﺸﺘﺮﻱ‬ ‫ﭘﺮﺩﺍﺯﺵ ﻛﺎﺭﺑﺮﺩ‬
‫ﻛﺎﺭﮔﺰﺍﺭ‬
‫ﻣﺸﺘﺮﻱ ﻗﻮﻱ‬ ‫ﻣﺪﻳﺮﻳﺖ ﺩﺍﺩﻩ ﻫﺎ‬
 ‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﺷﻲء ﺗﻮﺯﻳﻌﻲ‬
‫ﺩﺭ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺷﻲء ﺗﻮﺯﻳﻌﻲ‪ ،‬ﺗﻤﺎﻳﺰﻱ ﺑﻴﻦ ﻣﺸﺘﺮﻳﺎﻥ ﻭ ﻛﺎﺭﮔﺰﺍﺭﺍﻥ‬
‫ﻭﺟﻮﺩ ﻧﺪﺍﺭﻧﺪ ‪ .‬ﺍﺷﻴﺎء ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻛﻠﻲ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲ ﺩﻫﻨﺪ ﻛﻪ‬
‫ﺍﺷﻴﺎء ﺩﻳﮕﺮ ﺁﻥ ﺭﺍ ﻓﺮﺍﺧﻮﺍﻧﻲ ﻣﻲ ﻛﻨﻨﺪ ‪.‬‬
‫ﺑﺮﺍﻱ ﺍﺩﺍﺭﻩ ﻛﺮﺩﻥ ﺍﺭﺗﺒﺎﻃﺎﺕ ﺷﻲء ﻭ ﺑﺮﺍﻱ ﺣﺬﻑ ﻭﺍﺿﺎﻓﻪ ﺍﺷﻴﺎء ﺑﻪ‬
‫ﺳﻴﺴﺘﻢ‪ ،‬ﻧﻴﺎﺯ ﺑﻪ ﻣﻴﺎﻥ ﺍﻓﺰﺍﺭ ﺩﺍﺭﺩ‪ .‬ﺩﺭ ﻧﺘﻴﺠﻪ ﻣﻴﺎﻥ ﺍﻓﺰﺍﺭ ﻫﺎ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ‬
‫ﮔﺬﺭﮔﺎﻩ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺩﺍﻧﺴﺖ ﻛﻪ ﺍﺷﻴﺎء ﺑﻪ ﺁﻥ ﻭﺻﻞ ﻣﻲ ﺷﻮﻧﺪ ‪.‬‬
‫‪01‬‬ ‫‪02‬‬ ‫‪03‬‬ ‫‪04‬‬

‫)‪S(01‬‬ ‫)‪S(02‬‬ ‫)‪S(03‬‬ ‫)‪S(04‬‬

‫ﮔﺬﺭﮔﺎﻩ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫‪05‬‬ ‫‪06‬‬

‫)‪S(05‬‬ ‫)‪S(06‬‬
 ‫ﺍﻣﺘﻴﺎﺯﺍﺕ ﻣﺪﻝ ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﺷﻲء ﺗﻮﺯﻳﻌﻲ‬
‫‪ -1‬ﺑﻪ ﻃﺮﺍﺡ ﺳﻴﺴـﺘﻢ ﺍﺟـﺎﺯﻩ ﻣـﻲ ﺩﻫـﺪ ﺗـﺎ ﺗﺼـﻤﻴﻢ ﮔﻴـﺮﻱ ﺩﺭ ﻣـﻮﺭﺩ‬
‫ﭼﮕﻮﻧﮕﻲ ﺍﺭﺍﺋﻪ ﺳﺮﻭﻳﺲ ﻫﺎ ﺑﻪ ﺗﺄﺧﻴﺮ ﺍﻓﺘﺪ ‪.‬‬
‫‪ -2‬ﻳﻚ ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﺑﺎﺯ ﺍﺳﺖ ﻛﻪ ﺍﺟﺎﺯﻩ ﻣـﻲ ﺩﻫـﺪ ﺩﺭ ﺻـﻮﺭﺕ‬
‫ﻟﺰﻭﻡ ﻣﻨﺎﺑﻊ ﺟﺪﻳﺪﻱ ﺍﺿﺎﻓﻪ ﺷﻮﻧﺪ ‪.‬‬
‫‪ -3‬ﺳﻴﺴﺘﻢ ﻗﺎﺑﻞ ﺍﻧﻌﻄﺎﻑ ﻭ ﻣﻘﻴﺎﺱ ﭘﺬﻳﺮ ﺍﺳﺖ ‪.‬‬
‫‪ -4‬ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ‪ ،‬ﺑﺎ ﺟﺎﺑﻪ ﺟﺎﻳﻲ ﺍﺷﻴﺎء ﺩﺭ ﺷﺒﻜﻪ‪ ،‬ﺳﻴﺴـﺘﻢ ﺭﺍ ﻣـﻲ‬
‫ﺗﻮﺍﻥ ﺑﻪ ﻃﻮﺭ ﭘﻮﻳﺎ ﭘﻴﻜﺮﺑﻨﺪﻱ ﻛﺮﺩ ‪.‬‬
 ‫ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﺷﻲء ﺗﻮﺯﻳﻌﻲ ﺑﻪ ﺩﻭ ﺭﻭﺵ ﺩﺭ ﻃﺮﺍﺣﻲ‬
‫ﺳﻴﺴﺘﻢ ﺑﻪ ﻛﺎﺭﮔﺮﻓﺘﻪ ﻣﻲ ﺷﻮﺩ ‪:‬‬

‫‪ -1‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺪﻝ ﻣﻨﻄﻘﻲ ﻛﻪ ﺍﺟﺎﺯﻩ ﺗﻌﻴﻴﻦ ﺳﺎﺧﺘﺎﺭ ﻭ ﺳـﺎﺯﻣﺎﻥ ﺳﻴﺴـﺘﻢ‬

‫ﺭﺍ ﻣﻲ ﺩﻫﺪ ‪.‬‬

‫‪ -2‬ﻳﻚ ﺭﻭﺵ ﻗﺎﺑﻞ ﺍﻧﻌﻄﺎﻑ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ ﻫـﺎﻱ ﻣﺸـﺘﺮﻱ ‪ -‬ﻛـﺎﺭﮔﺰﺍﺭ‬

‫ﺍﺳﺖ ‪.‬‬
 ‫‪CORBA‬‬

‫ﺑﺮﺍﻱ ﺍﺩﺍﺭﻩ ﻛﺮﺩﻥ ﺍﺭﺗﺒﺎﻃﺎﺕ ﺷﻲء ﻭ ﺑﺮﺍﻱ ﺣﺬﻑ ﻭﺍﺿﺎﻓﻪ‬

‫ﺍﺷﻴﺎء ﺑﻪ ﺳﻴﺴﺘﻢ‪ ،‬ﻧﻴﺎﺯ ﺑﻪ ﻣﻴﺎﻥ ﺍﻓﺰﺍﺭ ﺩﺍﺭﺩ‪.‬‬

‫ﺩﺭ ﻭﺍﻗﻊ‪ ،‬ﺍﺷﻴﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺳﻴﺴﺘﻢ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬

‫ﺯﺑﺎﻥ ﻫﺎﻱ ﺑﺮﻧﺎﻣﻪ ﺳﺎﺯﻱ ﻣﺨﺘﻠﻒ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻛﺮﺩ‪ ،‬ﺩﺭ‬
‫ﻣﺤﻴﻂ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺍﺟﺮﺍ ﻧﻤﻮﺩ ﻭ ﻻﺯﻡ ﻧﻴﺴﺖ ﺍﺷﻴﺎء ﺩﻳﮕﺮ‬
‫ﻣﻮﺟﻮﺩ ﺩﺭ ﺳﻴﺴﺘﻢ ﻧﺎﻡ ﺁﻥ ﻫﺎ ﺭﺍ ﺑﺪﺍﻧﻨﺪ‪.‬‬
 ‫ﭼﻬﺎﺭ ﻋﻨﺼﺮ ﻣﻬﻢ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪CORBA‬‬

‫‪ -1‬ﻣﺪﻝ ﺷﻲء ﺑﺮﺍﻱ ﺍﺷﻴﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ﻛﻪ ﺩﺭ ﺁﻥ ﻫﺎ ﺑﺴﺘﻪ ﺑﻨﺪﻱ ﺣﺎﻟﺖ‬

‫‪CORBA‬ﺷﻲء ﺍﺳﺖ‪.‬‬
‫‪ -2‬ﻛﺎﺭﮔﺰﺍﺭ ﺩﺭﺧﻮﺍﺳﺖ ﺷﻲء ‪.‬‬
‫‪ -3‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺷﻲء ‪.‬‬
‫‪ -4‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻗﻄﻌﺎﺕ ﻣﺘﺪﺍﻭﻝ ﻛﻪ ﺗﻮﺳﻂ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺩﺭﺧﻮﺍﺳﺖ‬
‫ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫ﺳﺎﺧﺘﺎﺭﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺗﻮﺯﻳﻌﻲ ﻣﺒﺘﻨﻲ ﺑﺮ ‪CORBA‬‬

‫ﺍﻣﻜﺎﻧﺎﺕ ﺩﺍﻣﻨﻪ ﻛﺎﺭﺑﺮﺩ ﺍﺷﻴﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ‬ ‫ﺍﻣﻜﺎﻧﺎﺕ ﺍﻓﻘﻲ ‪CORBA‬‬

‫ﻛﺎﺭﮔﺰﺍﺭ ﺩﺭﺧﻮﺍﺳﺖ ﺷﻲء‬

‫ﺧﺪﻣﺎﺕ ‪CORBA‬‬
 ‫ﻣﺤﺎﺳﺒﺎﺕ ﺗﻮﺯﻳﻌﻲ ﺩﺭﻭﻥ ﺳﺎﺯﻣﺎﻧﻲ‬

‫‪ -1‬ﻣﻌﻤﺎﺭﻱ ﻫﺎﻱ ﻧﻈﻴﺮ ﺑﻪ ﻧﻈﻴﺮ ‪.‬‬

‫‪ -2‬ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﺳﺮﻭﻳﺲ ﮔﺮﺍ ‪.‬‬

‫‪Service-oriented Systems‬‬
 ‫ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﻧﻈﻴﺮ ﺑﻪ ﻧﻈﻴﺮ‬
‫ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻏﻴﺮ ﻣﺘﻤﺮﻛﺰﻱ ﻫﺴﺘﻨﺪ ﻛﻪ ﻣﺤﺎﺳﺒﺎﺕ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺩﺭ ﻫﺮ‬
‫ﮔﺮﻩ ﺍﻱ ﺍﺯ ﺷﺒﻜﻪ ﺍﻧﺠﺎﻡ ﺷﻮﻧﺪ‪ ،‬ﻭ ﺣﺪﺍﻗﻞ‪ ،‬ﻫﻴﭻ ﺗﻮﺯﻳﻌﻲ ﺑﻴﻦ ﻣﺸﺘﺮﻳﺎﻥ‬
‫ﻭ ﺳﺮﻭﻳﺲ ﺩﻫﻨﺪﮔﺎﻥ ﺍﻧﺠﺎﻡ ﻧﻤﻲ ﮔﻴﺮﺩ ‪.‬‬

‫ﻣﻌﻤﺎﺭﻱ ﺳﻴﺴﺘﻢ ﺳﺮﻭﻳﺲ ﮔﺮﺍ‬

‫ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﻫﺎ ﺍﺯ ﻃﺮﻳﻖ ﭘﻴﻮﻧﺪ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺍﻳﺠﺎﺩ ﻣﻲ‬
‫ﺷﻮﺩ ﻛﻪ ﺗﻮﺳﻂ ﻋﺮﺿﻪ ﻛﻨﻨﺪﮔﺎﻥ ﺳﺮﻭﻳﺲ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﻧﺪ ‪.‬‬
 ‫ﻣﻌﻤﺎﺭﻱ ﺍﺩﺭﺍﻛﻲ ﺳﻴﺴﺘﻢ ﺳﺮﻭﻳﺲ ﮔﺮﺍ‬

‫ﺑﺎﻳﮕﺎﻧﻲ ﺳﺮﻭﻳﺲ‬
‫ﻳﺎﻓﺘﻦ‬ ‫ﺍﻧﺘﺸﺎﺭ‬

‫ﺗﺄﻣﻴﻦ ﻛﻨﻨﺪﻩ‬
‫ﻣﺘﻘﺎﺿﻲ ﺳﺮﻭﻳﺲ‬
‫ﺳﺮﻭﻳﺲ‬ ‫ﺳﺮﻭﻳﺲ‬
‫ﻣﻘﻴﺪ ﻛﺮﺩﻥ‬