Raja Zoq-Ul- Arfeen
PhD
Pir Mehr Ali Shah Arid Agriculture University
Rawalpindi
Punjab
Pakistan
2015
Completed
Applied Sciences
English
http://prr.hec.gov.pk/jspui/bitstream/123456789/6870/1/Raja_Zoq_ul_Arfeen_Forestry_%26_Range_Management_PMAS_2015_13.02.2016.pdf
2021-02-17 19:49:13
2024-03-24 20:25:49
1676725973049
ڈاکٹرشہزاد احمد کی شاعری کا فنی جائزہ
سہل ممتنع
ڈاکٹرشہزاداحمد نعت خوانی سے نعت گوئی کی طرف مائل ہوئے ہیں۔ انھیں خیال آفرینی و مرصع کاری سے زیادہ ابلاغ کی فکر رہتی ہے۔ اس لیے وہ کلام میں سادگی کو اہمیت دیتے نظر آتے ہیں۔اُن کے کلام میں بھاری بھرکم تراکیب کی جگہ عام بول چال کے سادہ الفاظ ادائے مطلب کے لیے استعمال ہوئے ہیں۔ ان کی نعت کی مرکزی خصوصیت سہل ممتنع ہے جس کے بارے میں مولانا حسرت موہانی لکھتے ہیں :
’’سہل ممتنع سادگی وحسن بیان کی اُس صنف کا نام ہے جس کو دیکھ کر ہر شخص بظاہر یہ سمجھے کہ یہ بات میرے دل میں بھی تھی اور ایسا کہنا ہر شاعر کے لیے آسان ہے مگر جب کوشش کرکے ویسا لکھنا چاہے تو نہ لکھ سکے۔‘‘ (۲۴)
یہی سادہ اسلوب ہمیں ڈاکٹر شہزاد احمد کی نعت میں بڑے سلیقے سے برتا ہوا ملتا ہے۔ مثال میں دو شعر ملاحظہ ہوں:
آپ صرف اپنے محبوب کا
مجھ کو شیدا بنا دیجیے
پھر جہاں میں ہے تیرگی چھائی
اپنا جلوہ دکھائیے آقاؐ
غنائی لہجہ
شاعری میں موسیقیت نہ ہو تو کلام فصاحت سے کوسوں دُور رہتا ہے۔ موسیقیت کے لیے آواز کے زیرو بم کے استعمال سے واقفیت ضروری ہے۔ ڈاکٹر شہزاد احمد چوں کہ نعت خوانی سے بھی وابستہ ہیں۔ اس لیے اُن کے کلام میں غنائیت کا عنصر اوج پر ہے۔ پروفیسرنویدعاجز ؔ اس بارے میں یوں رقم طراز ہیں:
’’انھوں نے نعتیں محافل میں پڑھنے کے لیے لکھی ہیں، اس لیے اُن کی سب سے بڑی خوبی موسیقیت اور روانی ہے۔ ’’حبیبی یارسول اللہ، درودتم پر سلام تم پر اور بسم اللہ ‘‘ کی ردیف میں کہی گئی نعتیں مترنم لہجے کی حامل ہیں۔‘‘(۲۵)
ڈاکٹر شہزاداحمد کے کلام میں روانی اور مترنم لہجے کے اشعار کی کمی نہیں۔ چند مثالیں ملاحظہ ہوں:سیرت طیبہ کی تشریعیاتی حیثیت کا تحقیقی و تاریخی مطالعہ A Research review of the legislative Status of the Sirah of Holy Prophet ﷺ
The deeds and actions of the Holy Prophet ﷺ is a practical interpretation of the Holy Qur'an. Allah Almighty has stated his Shari'ah in short but comprehensive words that “take what the Holy Prophet ﷺ has given you and which you forbid”. Therefore, his command is the command of Allah Almighty and not yours. That is why the Holy Qur'an has declared his obedience to be the obedience of Allah Almighty. And from the instructions of the selected scholars of the ummah, it is clear that the legislative status of The Sirah is authenticated. Allah Almighty has given him a special position of Shariah.
As for the legislative status of Sira-e-Taiba, both the special and the general legislation are specific or special to him. Special legislation etc i.e. you have legislated for a specific person at certain times like accepting the condition of a person that he will convert to Islam if he prays only two prayers. The other person cannot join. The general legislation in which you have enacted all kinds of legislation for the common ummah is included. The center and axis of Islamic law is your caste. You have complete control over the status and sanctity, likes and dislikes as you like, for whom you can make Shariah whenever you want. It is as if you are a follower of the Shari'ah. He also has full authority in the brief description of the Qur'an, in the adherence to the Absolute, and the explanation of similarities. You are authorized to legislate as a Shari'ah and Shari'ah in all areas of worship, affairs, debates, and crimes.
Therefore, in this article, the legislative status of His Sira-e-Taiba has been explained in the light of Qur'an and Hadith, Sahabah and Tabi'een, and the commandments of Imams and jurists. Resolving Requirement Traceability Conflicts in Distributed Scrum
Requirement traceability is the set of practices used to trace changes in requirements during development process. It ensures that each step of development is correct and confirms to the needs of prior and next steps. In agile methods like Scrum, there are short development cycles and the product owner creates product backlog and shares with Scrum team. In the distributed Scrum, teams are distributed across different geographic locations and team members discuss requirements, create designs, code and documentation. Co-located teams can discuss and trace the requirements easily but it becomes difficult for teams to gather, trace and manage requirements in the distributed Scrum. Sometimes requirements are repeated in different artifacts, which create requirement redundancy that cause requirement conflicts and interpret different meanings for the same requirement. Redundant requirements are difficult to trace, locate and create links. Many other studies discussed requirement traceability tools and frameworks but these tools didn?t focus on resolving requirement traceability in the distributed Scrum. To resolve the requirement traceability conflicts in the distributed Scrum, this study proposed a requirement traceability model. The proposed model is consisting of five steps including identifying the redundant requirements, remove redundant requirements, assigning unique IDs to requirements, storing requirement information and resolving the requirement traceability conflicts in the distributed Scrum. The study helped to locate, prevent and remove requirement redundancies and resolve the requirements conflicts in the distributed Scrum software development. A survey was conducted in software industry and the results of survey were analyzed and presented in the form of graphs. The most of the companies participated in survey were large in size. The survey results were analyzed using the SPSS tool and presented in the form of graphs. The survey results suggested that requirement traceability conflicts can be resolved by assigning unique IDs to requirements, removing inconsistent and redundant requirements, involving users into requirement elicitation process, proper communication with different stakeholders, using tools like JIRA. The proper planning in Scrum meetings with the whole team can avoid requirements conflicts. The proposed model is more beneficial in terms of removing redundant requirements and resolving requirement traceability conflicts in the distributed Scrum.