ریشم بننا کھیل نہیں
ناطق کی نظموں کے مجموعہ کو سانجھ پبلی کیشنز لاہور نے 2019ء میں ’’ریشم بننا کھیل نہیں‘‘ کے نام سے شائع کیا۔تینوں کتابوں کے دیباچے بھی اس مجموعہ میں شامل ہیں۔یہ مجموعہ قارئین کیلئے ایک نادر تحفہ ثابت ہوا،الگ الگ مجموعوں کو پڑھنے کی بجائے سارا متن ایک ہی مجموعہ میں قارئین کی دلچسپی کو دوبالا کرنے کیلئے شائع کیا گیا۔یقیناًیہ ایک عمد ہ کاوش ہے۔فہمیدہ ریاض لکھتی ہیں کہ:
’’علی اکبر جواں سال ہے اور ایوان ادب میں دلربا شان سے داخل ہوا ہے۔اس کا بے خوف مشاہدہ ادب کیلئے مسرت کی نوید ہے اس کی شاعری میں بھڑکتے ہوئے شعلے چہاراطراف کو خاکستر کرتے نظر آتے ہیں۔‘‘(7)
ریشم بننا کھل نہیںایسا معلوم ہوتا ہے کہ انہوں نے اپنی ایک ایک نظم سے یہ ریشم بنا ہے۔تینو ں کتب کو ایک ہی جلدمیںلے آنا کوئی آسان کام نہیں تھا۔ قاری کے لئے مسرت کی گھڑی ہے کہ اسے ناطق کی شاعری کو ایک ساتھ پڑھنے کا موقع ملا۔ یقیناً یہ ایک عمدہ کاوش ہے۔
The relationship between Pakistan and America has always been a focus of the media of both countries as well as the international media. Even a slight shift in the policies of these two countries for each other is capable of making newspaper headlines and attracting maximum attention of the press of both countries. This study is a comparative analysis of the editorial pages of daily Dawn (English) and daily Jang (Urdu) to explore the agenda setting role of two of Pakistan’s oldest and most credible newspapers, vis-à-vis the Pakistan-US relationship. The research takes into consideration a total of 20 years of Pakistan-US relations by dividing the period into two groups which are ten years before the incident of 9/11 and ten years after 9/11. This understudied period is specifically important because the relations between Pakistan and America during these phases have vacillated between periods of engagements, wherein Pakistan enjoyed the status of the most favoured ally without compromising its regional interest, and the periods of disengagements wherein Pakistan faced sanctions from the US and was left alone to deal with the aftermath of the Afghan war and the War on Terrorism. Hence, this study obtains interesting insights about how the two Pakistani newspapers which represent the Urdu and the English press of Pakistan highlighted the agenda-setting role of the press through the coverage of the issues between Pakistan and US on their editorial pages.
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.