UML لغة البرمجة الموحدة PDF

‫ﻝﻐﺔ ﺍﻝﻨﻤﺫﺠﺔ ﺍﻝﻤﻭﺤﺩﺓ ‪UML‬‬ ‫ﺘـﻡ ﺇﻁـﻼﻕ )‪ Unified Modeling Language (UML‬ﻋـﺎﻡ ‪ ١٩٩٧‬ﻜﻁﺭﻴﻘـﺔ ﻝﻭﻀـﻊ ﻤﺨﻁﻁـﺎﺕ‬ ‫ﺘﺼﻤﻴﻡ ﻝﻠﺒﺭﻤﺠﻴﺎﺕ ﺒﻬﺩﻑ‪:‬‬ ‫ ﺘﺼﻤﻴﻡ ﺍﻝﺒﺭﻤﺠﻴﺎﺕ ﺒﺸﻜل ﺍﺤﺘﺭﺍﻓﻲ‪.‬‬...

‫ﻝﻐﺔ ﺍﻝﻨﻤﺫﺠﺔ ﺍﻝﻤﻭﺤﺩﺓ ‪UML‬‬ ‫ﺘـﻡ ﺇﻁـﻼﻕ )‪ Unified Modeling Language (UML‬ﻋـﺎﻡ ‪ ١٩٩٧‬ﻜﻁﺭﻴﻘـﺔ ﻝﻭﻀـﻊ ﻤﺨﻁﻁـﺎﺕ‬ ‫ﺘﺼﻤﻴﻡ ﻝﻠﺒﺭﻤﺠﻴﺎﺕ ﺒﻬﺩﻑ‪:‬‬ ‫ ﺘﺼﻤﻴﻡ ﺍﻝﺒﺭﻤﺠﻴﺎﺕ ﺒﺸﻜل ﺍﺤﺘﺭﺍﻓﻲ‪.‬‬ ‫ ﺘﻭﺜﻴﻕ ﺍﻝﺘﺼﻤﻴﻡ ﻗﺒل ﺍﻝﺒﺩﺀ ﺒﺎﻝﺒﺭﻤﺠﺔ‪.‬‬ ‫ ﺇﻋﺎﺩﺓ ﺍﻻﺴﺘﺨﺩﺍﻡ ‪) Reusability‬ﺘﺨﻔﻴﺽ ﺍﻝﻜﻠﻔﺔ(‪.‬‬ ‫ ﺍﻝﺒﺭﻨﺎﻤﺞ ﺍﻝﺫﻱ ﺘﻡ ﺘﻁﻭﻴﺭﻩ ﻴﺅﺩﻱ ﺍﻝﻭﻅﺎﺌﻑ ﺍﻝﻤﻁﻠﻭﺒﺔ )ﺯﻴﺎﺩﺓ ﺍﻝﻭﺜﻭﻗﻴﺔ(‪.‬‬ ‫ ﺴﻬﻭﻝﺔ ﺍﻝﺘﻌﺩﻴل ﻭﺍﻝﺼﻴﺎﻨﺔ ﻭﺒﻜﻠﻔﺔ ﻤﻨﺨﻔﻀﺔ‪.‬‬ ‫ ﻤﺨﻁﻁﺎﺕ ‪ UML‬ﺘﺴﺎﻋﺩ ﺍﻝﻤﻁﻭﺭﻴﻥ ﻋﻠﻰ ﻓﻬﻡ ﺍﻝﻨﻅﺎﻡ ﺒﺴﻬﻭﻝﺔ ﻭﺴﺭﻋﺔ‪.‬‬ ‫ ﻝﻐﺔ ﺘﻭﺍﺼل ﺒﻴﻥ ﺍﻝﻤﻁﻭﺭﻴﻥ ﻭﺍﻝﻤﺼﻤﻤﻴﻥ‪.‬‬ ‫ﺘﺘﻜﻭﻥ ‪ UML‬ﻤﻥ ﻋﻨﺎﺼﺭ ﺭﺴـﻭﻤﻴﺔ ﺘﻭﻀـﻊ ﻀـﻤﻥ ﻤﺨﻁﻁـﺎﺕ ﻤﺨﺘﻠﻔـﺔ ﻝﺘﻭﺼـﻴﻑ ﺍﻝﻨﻅـﺎﻡ ‪ ،‬ﻫـﺫﻩ‬ ‫ﺍﻝﻤﺨﻁﻁــﺎﺕ ﺘﻘــﻭﻡ ﺒﺘﻭﺼــﻴﻑ ﺍﻝﻨﻅــﺎﻡ ﻭﻝــﻴﺱ ﻝﻬــﺎ ﻋﻼﻗــﺔ ﺒﻜﻴﻔﻴــﺔ ﺒﺭﻤﺠــﺔ ﻫــﺫﻩ ﺍﻝﻭﻅــﺎﺌﻑ‬ ‫‪.Implementation‬‬ ‫ﺘﺘﺄﻝﻑ ﺍﻝــ ‪ UML‬ﻤـﻥ ‪ ١٤‬ﻨـﻭﻉ ﻤـﻥ ﺍﻝﻤﺨﻁﻁـﺎﺕ ﻭﺘﻘـﺴﻡ ﺇﻝـﻰ ﻨـﻭﻋﻴﻥ ‪Structure Diagram,‬‬ ‫‪.Behavior Diagram‬‬ ‫‪ :Structure Diagram‬ﺘﺭﻜﺯ ﻋﻠﻰ ﻋﻨﺎﺼﺭ ﺍﻝﻨﻅـﺎﻡ ﺒـﺸﻜل ﻤـﺴﺘﻘل ﻋـﻥ ﺍﻝـﺯﻤﻥ ﺃﻱ ﺍﻝﺒﻴﻨـﺔ ﺍﻝـﺴﺎﻜﻨﺔ‬ ‫‪.Static Structure‬‬ ‫‪ :Behavior Diagram‬ﺘﺭﻜــﺯ ﻋﻠــﻰ ﻭﻅﻴﻔﻴــﺔ ﺍﻝﻨﻅــﺎﻡ ﺃﻱ ﺘﻐﻴﺭﺍﺘــﻪ ﻤــﻊ ﺍﻝــﺯﻤﻥ ‪Dynamic‬‬ ‫‪.Structure‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬  ‫ ‪Class diagram‬‬ ‫ﺍﻝﺼﻨﻑ ‪Class‬‬ ‫ﻫﻭ ﺘﺠﻤﻴﻊ ﻝﻤﺠﻤﻭﻋﺔ ﻤﻥ ﺍﻷﺸﻴﺎﺀ ﺍﻝﻤﺘﺸﺎﺒﻬﺔ ﻓﻲ ﺨﻭﺍﺼﻬﺎ ﺃﻭ ﺴﻠﻭﻜﻬﺎ‬ ‫ﻤﺜﺎل‪) :‬ﺍﻝﺤﻴﻭﺍﻨﺎﺕ‪ ،‬ﻭﺴﺎﺌﻁ ﺍﻝﻨﻘل‪ ،‬ﺍﻝﻨﺒﺎﺘﺎﺕ ‪ ،‬ﺍﻝﻁﻼﺏ‪(..... ،‬‬ ‫ﺍﻝﻜﺎﺌﻥ ‪Object‬‬ ‫ﻋﻨﺩ ﺇﺴﻨﺎﺩ ﻗﻴﻡ ﻝﻠـ ‪ Class‬ﻨﺤﺼل ﻋﻠﻰ ﺍﻝﻜﺎﺌﻥ ‪ Object‬ﺃﻱ ﻫﻭ ‪ Class‬ﺼﻔﺎﺘﻪ ﺘﻤﻠﻙ ﻗﻴﻡ‪.‬‬ ‫ﻤﺜﺎل‪ :‬ﺘﺤﺩﻴﺩ ﻁﺎﻝﺏ ﻤﺤﺩﺩ ﺍﺴﻤﻪ ﺃﺤﻤﺩ‪.‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬  Class Diagram ‫ ﺘﻭﻀـﻴﺢ ﻫـﺫﻩ ﺍﻷﺼـﻨﺎﻑ‬Class diagram ‫ ﻤﻬﻤـﺔ‬، Classes ‫ﻴﻤﻜﻥ ﻭﻀﻊ ﺍﻷﺸﻴﺎﺀ ﻀـﻤﻥ ﺃﺼـﻨﺎﻑ‬ ‫ ﻓﻴﻤﺎ ﺒﻴﻨﻬﺎ‬associations ‫ﻭﺍﻝﻌﻼﻗﺎﺕ‬ : Class ‫ﻝﻜل ﺼﻨﻑ‬ class name ‫ ﺍﺴﻡ‬ attributes ‫ ﻤﻤﻴﺯﺍﺕ‬ Methods ‫ ﻭﺃﺤﻴﺎﻨﹰﺎ ﻨﺴﻤﻴﻬﺎ‬operations ‫ ﻋﻤﻠﻴﺎﺕ‬ :‫ ﺒﺄﺤﺩ ﺍﻝﻁﺭﻕ ﺍﻝﺘﺎﻝﻴﺔ‬Class ‫ﻭﺒﺎﻝﺘﺎﻝﻲ ﻴﻤﻜﻥ ﺘﻤﺜﻴل‬ Class Name Class Name Class Name Att1: type 1 Att1: type 1 Att 2: type 2 = "default Att2: type 2 = "default value" value" … … … … Operation1 () Operation2 (list of parameters) Operatipn3: returned value type Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬  Associations ‫ﺍﻝﻌﻼﻗﺎﺕ ﺒﻴﻥ ﺍﻷﺼﻨﺎﻑ‬ Works in Librarian Library Employer Employee Customer Buys from SuperMarket Bill Multiplicity ‫ﺍﻝﺘﻌﺩﺩﻴﺔ‬ :‫ﻴﻤﻜﻥ ﺍﻥ ﺘﺄﺨﺫ ﺍﻝﺘﻌﺩﺩﻴﺔ ﺒﻴﻥ ﺍﻷﺼﻨﺎﻑ ﺍﺤﺩ ﺍﻷﺸﻜﺎل ﺍﻝﺘﺎﻝﻴﺔ‬ one to one 1 1 one to many 1 * one to one or more 1 1..* one to zero or more 1 0..* one to exactly n 1 n Reflexive ‫ ﻭﻨﻔﺴﻪ ﻭﺘﺴﻤﻰ ﻫﺫﻩ ﺍﻝﻌﻼﻗﺔ‬Class ‫ﻓﻲ ﺒﻌﺽ ﺍﻷﺤﻴﺎﻥ ﻴﻜﻭﻥ ﻫﻨﺎﻙ ﻋﻼﻗﺔ ﺒﻴﻥ ﺍﻝﺼﻨﻑ‬ association 1 Employee Chef 1..* Workers Responsible For Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬  ‫ﻴﻤﻜﻥ ﺃﻥ ﺘﻜﻭﻥ ‪ attributes & operations‬ﻓﻲ ﺇﺤﺩﻯ ﺍﻝﺤﺎﻻﺕ ﺍﻝﺘﺎﻝﻴﺔ‪:‬‬ ‫) ‪Public ( +‬‬ ‫) – ( ‪Private‬‬ ‫) ‪Protected ( #‬‬ ‫ﻤﺜﺎل‪:‬‬ ‫ﺍﻝﻭﺭﺍﺜﺔ ‪Inheritance & Generalization‬‬ ‫ﺘﻭﺠﺩ ﺒﻌﺽ ﺍﻝﻤﻤﻴﺯﺍﺕ ﺍﻝﻤﺸﺘﺭﻜﺔ ﺒﻴﻥ ﺍﻷﺼﻨﺎﻑ ﻭﺍﻝﺘﻲ ﻴﻤﻜﻥ ﻨﻘﻠﻬﺎ ﺒﻴﻥ ﺍﻷﺼﻨﺎﻑ ‪ Classes‬ﻭﺒﺎﻝﺘﺎﻝﻲ ﻴﻔﻀل ﻓﻲ‬ ‫ﻫﺫﻩ ﺍﻝﺤﺎﻝﺔ ﺃﻥ ﻨﺩﺨل ﻤﻔﻬﻭﻡ ﺍﻝﻭﺭﺍﺜﺔ‪.‬‬ ‫ﻴﻤﻜﻥ ﻷﺤﺩ ﺍﻷﺼﻨﺎﻑ ﻨﺴﻤﻴﻪ )‪ Child class (subclass‬ﺃﻥ ﻴﺭﺙ ‪ attributes and operations‬ﻤﻥ ﺼﻨﻑ‬ ‫ﺁﺨﺭ ﻨﺴﻤﻴﻪ )‪ Parent class (super class‬ﺤﻴﺙ ﻴﻤﻜﻥ ﺃﻥ ﻴﻨﻭﺏ ﺍﻷﺏ ﻋﻥ ﺍﺒﻨﻪ ﻭﻝﻜﻥ ﺍﻝﻌﻜﺱ ﻏﻴﺭ ﺼﺤﻴﺢ‪.‬‬ ‫ﻤﺜﺎل‪ :‬ﻤﻭﻅﻔﻴﻥ ﻓﻲ ﻤﺅﺴﺴﺔ ﻤﺎ )ﻤﺩﻴﺭ‪ ،‬ﻤﻬﻨﺩﺱ‪ ،‬ﺴﻜﺭﺘﻴﺭﺓ‪ ،‬ﺭﺌﻴﺱ ﻗﺴﻡ‪ ،‬ﻋﺎﻤل ﺒﻭﻓﻴﺔ‪ ،‬ﻋﺎﻤل ﻨﻅﺎﻓﺔ‪(... ،‬‬ ‫‪Super class‬‬ ‫‪Parent‬‬ ‫‪Sub Class‬‬ ‫‪Child‬‬ ‫ﻋﻼﻗﺔ ‪Aggregations‬‬ ‫ﻫﻲ ﻋﻼﻗﺔ ﺒﻴﻥ ﺍﻝﻜل ﻭﺍﻝﺠﺯﺀ ﻭﻴﺘﻡ ﺘﻤﺜﻴﻠﻬﺎ ﻜﻤﺎ ﻴﻠﻲ‪:‬‬ ‫*‪1..‬‬ ‫‪Vehicle parts‬‬ ‫‪Vehicle‬‬ ‫*‪1..‬‬ ‫‪City‬‬ ‫‪Country‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬  ‫ﺘﻜﻭﻥ ﺩﻭﺭﺓ ﺤﻴﺎﺓ ﺼﻑ ﺍﻝﺠﺯﺀ ﻤﺴﺘﻘﻠﺔ ﻋﻥ ﺩﻭﺭﺓ ﺤﻴﺎﺓ ﺼﻑ ﺍﻝﻜل )ﻴﻤﻜﻥ ﺭﺅﻴﺔ ﺍﻝﺠﺯﺀ ﺒﻌﻴﺩﹰﺍ ﻋﻥ ﺍﻝﻜل(‪.‬‬ ‫ﺃﻤﺜﻠﺔ‪:‬‬ ‫ﻋﻼﻗﺔ ‪Composition‬‬ ‫ﻫﻲ ﻋﻼﻗﺔ ﺒﻴﻥ ﺍﻝﻜل ﻭﺍﻝﺠﺯﺀ ﺃﻴﻀﹰﺎ ﻝﻜﻨﻬﺎ ﺃﺸﺩ ﻗﺴﻭﺓ ﺤﻴﺙ ﺃﻥ ﺩﻭﺭﺓ ﺤﻴﺎﺓ ﺼﻑ ﺍﻝﺠﺯﺀ ﺘﻌﺘﻤﺩ ﻋﻠﻰ ﺩﻭﺭﺓ ﺤﻴﺎﺓ‬ ‫ﺼﻑ ﺍﻝﻜل )ﻻ ﻴﻤﻜﻥ ﺭﺅﻴﺔ ﺍﻝﺠﺯﺀ ﺒﻌﻴﺩﹰﺍ ﻋﻥ ﺍﻝﻜل(‪.‬‬ ‫ﻴﺘﻡ ﺘﻤﺜﻴل ﻫﺫﻩ ﺍﻝﻌﻼﻗﺔ ﻜﻤﺎ ﻴﻠﻲ‪:‬‬ ‫‪Hotel‬‬ ‫‪1‬‬ ‫*‪1..‬‬ ‫‪Rooms‬‬ ‫‪Use Case diagram‬‬ ‫ﻜل ‪ Use Case‬ﺘﻤﺜل ﻭﻅﻴﻔﺔ ﻤﻥ ﻭﻅﺎﺌﻑ ﺍﻝﻨﻅﺎﻡ ﻭﺒﺎﻝﺘﺎﻝﻲ ﻴﺘﻀﻤﻥ ﻫﺫﺍ ﺍﻝﻤﺨﻁﻁ ‪:‬‬ ‫‪ -‬ﺍﻝﻭﻅﺎﺌﻑ ﺍﻝﻤﻁﻠﻭﺒﺔ ﻤﻥ ﺍﻝﻨﻅﺎﻡ‪.‬‬ ‫‪ -‬ﻝﻤﺴﺘﺨﺩﻡ ‪ actor‬ﺍﻝﺫﻱ ﻴﻘﻭﻡ ﺒﻁﻠﺏ ﻫﺫﻩ ﺍﻝﻭﻅﻴﻔﺔ )ﻗﺩ ﻴﻜﻭﻥ ﻨﻅﺎﻡ ﺁﺨﺭ(‪.‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬ ‫ﻴﺴﺎﻋﺩﻨﺎ ﻋﻠﻰ ﺒﻨﺎﺀ ‪ Use case diagram‬ﻓﻬﻡ ﺴـﻴﻨﺎﺭﻴﻭ ﺍﻝﻌﻤـل ﻭﺍﻝـﺫﻱ ﻨﺤـﺼل ﻋﻠﻴـﻪ ﻤـﻥ ﻤـﺴﺘﺨﺩﻡ‬ ‫ﺍﻝﻨﻅﺎﻡ‪.‬‬ ‫‪Association line‬‬ ‫ﻜل ‪ Use Case‬ﻋﺒﺎﺭﺓ ﻋﻥ ﺴﻴﻨﺎﺭﻴﻭ ﻴﺘﻜﻭﻥ ﻤﻥ ﻤﺠﻤﻭﻋﺔ ﻤﻥ ﺍﻝﺨﻁﻭﺍﺕ ﻝﺘﻨﻔﻴﺫ ﻭﻅﻴﻔﺔ ﻤﺤﺩﺩﺓ‪.‬‬ ‫ا‪()*+,‬ت ‪Use Case./‬‬ ‫‪Include‬‬ ‫ﺘﻤﻜﻨﻨﺎ ﻫﺫﻩ ﺍﻝﻌﻼﻗﺔ ﻤﻥ ﺇﻋﺎﺩﺓ ﺍﺴﺘﺨﺩﺍﻡ ﺍﻝﺨﻁﻭﺍﺕ ﺍﻝﻤﻭﺠﻭﺩﺓ ﺩﺍﺨل ‪Use Case‬‬ ‫ﻴﺘﻡ ﺘﻤﺜﻴل ﻫﺫﻩ ﺍﻝﻌﻼﻗﺔ ﻜﻤﺎ ﻴﻠﻲ‪:‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬  ‫‪Extension‬‬ ‫ﺘﺴﻤﺢ ﻝﻨﺎ ﻫﺫﻩ ﺍﻝﻌﻼﻗﺔ ﺒﺈﻨﺸﺎﺀ ‪ Use Case‬ﺠﺩﻴﺩﺓ ﻴﺘﻡ ﺇﻀﺎﻓﺘﻬﺎ ﺇﻝﻰ ‪ Use Case‬ﻤﻭﺠﻭﺩﺓ ﺴﺎﺒﻘﺎ ﺒﻬﺩﻑ‪:‬‬ ‫ﻤﻌﺎﻝﺠﺔ ﺤﺎﻝﺔ ﺍﺴﺘﺜﻨﺎﺌﻴﺔ ﻗﺩ ﺘﻭﺍﺠﻬﻨﺎ ﺃﻭ ﻝﻭﻀﻊ ﺸﺭﻁ ﻋﻠﻰ ﺍﻝﺨﻁﻭﺍﺕ ﻀﻤﻥ ‪ Use Case‬ﺍﻝﺤﺎﻝﻴﺔ‬ ‫ﻴﺘﻡ ﺘﻤﺜﻴﻠﻬﺎ ﻜﻤﺎ ﻴﻠﻲ‪:‬‬ ‫ﺍﻝﻭﺭﺍﺜﺔ ‪Generalization‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬ Self service Machine example Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬ Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬  ‫‪Sequence diagram‬‬ ‫ﻤﺨﻁﻁ ﻴﻬﺩﻑ ﺇﻝﻰ ﺘﻭﺼﻴﻑ ﺍﻻﺘﺼﺎﻻﺕ ﺒﻴﻥ ‪ Objects‬ﻋﺒﺭ ﺍﻝﺯﻤﻥ ﺃﻱ ﻴﺘﻡ ﺇﺩﺨﺎل ‪‬ﺒﻌﺩ ﺍﻝﺯﻤﻥ ‪ Time‬ﺇﻝﻰ‬ ‫ﺍﻝﻤﺨﻁﻁ ﻭﺒﺎﻝﺘﺎﻝﻲ ﻴﺘﻡ ﺘﻭﻀﻴﺢ ﻜل ﺍﻝﺘﻔﺎﻋﻼﺕ ﻭﺍﻻﺘﺼﺎﻻﺕ ﺒﻴﻥ ‪ Objects‬ﻭﻓﻕ ﺘﺴﻠﺴل ﺯﻤﻨﻲ‪.‬‬ ‫ﺘﺴﺘﺨﺩﻡ ﺍﻝﺭﻤﻭﺯ ﺍﻝﺘﺎﻝﻴﺔ ﻓﻲ ‪Sequence diagram:‬‬ ‫‪Active time‬‬ ‫‪Time line‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬  :‫ ﻭﻫﻲ‬Objects ‫ﺘﻭﺠﺩ ﻋﺩﺓ ﺃﻨﻭﺍﻉ ﻝﻠﺭﺴﺎﺌل ﺍﻝﻤﺘﺒﺎﺩﻝﺔ ﺒﻴﻥ‬ Message Self message Call message (synchronous) Asynchronous message Self call message Return message Self return message :‫ﻴﻭﻀﺢ ﺍﻝﺸﻜل ﺍﻝﺘﺎﻝﻲ ﻁﺭﻴﻘﺔ ﺘﻤﺜﻴل ﺍﻝﺭﺴﺎﺌل ﻓﻲ ﺍﻝﻤﺨﻁﻁ‬ Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬ Rakan. Co UML ‫ﻤﺨﻁﻁﺎﺕ‬  ‫ﺇﺫﺍ ﺃﺭﺩﻨﺎ ﺘﺤﺴﻴﻥ ﺍﻝﻨﻅﺎﻡ ﺒﺤﻴﺙ ﻴﺄﺨﺫ ﺒﻌﻴﻥ ﺍﻻﻋﺘﺒﺎﺭ ﺍﻝﻤﺘﻁﻠﺒﺎﺕ ﺍﻝﻤﺴﺒﻘﺔ ﻝﻜل ﻤﺎﺩﺓ ﻴﻜﻭﻥ ﻝﺩﻴﻨﺎ ﺍﻝﻤﺨﻁﻁ ﺍﻝﺘﺎﻝﻲ‪:‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬ ‫ﻤﺜﺎل‪ :٢‬ﻓﻲ ﻨﻅﺎﻡ ‪ self service machine‬ﻴﻘﻭﻡ ﺍﻝﺯﺒﻭﻥ ﺒﺈﺩﺨﺎل ﺍﻝﻨﻘﻭﺩ ﻭﻴﺨﺘﺎﺭ ﻤﻨﺘﺞ ﻓﺘﻘﻭﻡ ﺍﻵﻝﺔ ﺒﺎﻻﺴﺘﺠﺎﺒﺔ‬ ‫ﻝﻁﻠﺒﻪ ﻭﺒﻴﻌﻪ ﺍﻝﻤﻨﺘﺞ ﺍﻝﻤﻁﻠﻭﺏ‪.‬‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬ ‫ﻴﻤﻜﻥ ﺘﻁﻭﻴﺭ ﺍﻝﻨﻅﺎﻡ ﺒﺠﻌﻠﻪ ﻴﺄﺨﺫ ﺒﻌﻴﻥ ﺍﻻﻋﺘﺒﺎﺭ ﻗﻴﻤﺔ ﺍﻝﺩﻓﻌﺔ )ﺍﻜﺒﺭ ﺃﻭ ﺘﺴﺎﻭﻱ ﻗﻴﻤﺔ ﺍﻝﻤﻨﺘﺞ( ﻭﺃﻴﻀﺎ ﻓﻴﻤﺎ ﺇﺫﺍ ﻜﺎﻥ‬ ‫ﺍﻝﻤﻨﺘﺞ ﻤﺘﻭﻓﺭ ﺃﻭ ﻏﻴﺭ ﻤﺘﻭﻓﺭ‪.‬‬ ‫ﺘﻡ ﺒﺤﻤﺩ ﺍﷲ‬ ‫‪Rakan. Co‬‬ ‫ﻤﺨﻁﻁﺎﺕ ‪UML‬‬