<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel rdf:about="http://hdl.handle.net/123456789/7921">
<title>Department of Software Engineering</title>
<link>http://hdl.handle.net/123456789/7921</link>
<description/>
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://hdl.handle.net/123456789/8042"/>
<rdf:li rdf:resource="http://hdl.handle.net/123456789/8035"/>
<rdf:li rdf:resource="http://hdl.handle.net/123456789/8037"/>
<rdf:li rdf:resource="http://hdl.handle.net/123456789/8032"/>
</rdf:Seq>
</items>
<dc:date>2026-04-04T10:43:21Z</dc:date>
</channel>
<item rdf:about="http://hdl.handle.net/123456789/8042">
<title>Impact and Challenges of Requirements Management in Enterprise Resource Planning (ERP) via ERP Thesaurus</title>
<link>http://hdl.handle.net/123456789/8042</link>
<description>Impact and Challenges of Requirements Management in Enterprise Resource Planning (ERP) via ERP Thesaurus
Rahat Izhar; Saba Izhar; Dr. Shahid Nazir Bhatti; Dr. Amr Mohsen Jadi
Managing requirements efficiently aids the system design team to understand the existence and significance of any individual requirement, there are numerous requirements management practices that benefit in decision making but significantly many lacks to account the important factors that have substantial influence in managing requirements in context of ERP systems in particular. As highlighted comprehensively later in literature review section, requirements management failure is one of the pivotal aspects for the project(s) failure. The prime problem/lacking in software design and development is when it comes to requirements management the most vital thing that gets ignored is thinking before performing activities. As it should be the main step to save time, money and efforts. Further prominence other aspects in this are pivotal value about the software’s running in industries, the question arises when their business need ERP system, and when requirements change or new requirements are emerged into the system, what are the obstacles faced and how these obstacles are accomplished. ERP systems are becoming the need of industries nowadays as various industries are facing problems regarding data loss; it is challenging for the owners to fetch all the information when they need it, accounting systems are slower and consuming a lot of time and many other issues likewise. This paper further illustrates in detail the important traits, issues toward businesses may have when ERP is implemented and when requirements are changed or not managed professionally what issues are faced by requirement engineering team and industries and thus how to resolve them.
</description>
<dc:date>2018-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://hdl.handle.net/123456789/8035">
<title>Impact and Challenges of Requirement Engineering in Agile Methodologies: A Systematic Review</title>
<link>http://hdl.handle.net/123456789/8035</link>
<description>Impact and Challenges of Requirement Engineering in Agile Methodologies: A Systematic Review
Sehrish Alam; S. Asim Ali Shah; Shahid Nazir Bhatti; Dr. Amr Mohsen Jadi
Requirement Engineering is one of important stage in development life cycle. All requirements required for development of product is collected in this phase. A high standard product can be developed by agile methodology in less budget and time. Importance of agile practices have been enhanced since it offers assist cooperation too software engineering. Being basic phase of software engineering, requirement engineering has different processes. The elements of direct correspondence is one of spry way which not at all like to other conventional and traditional approaches .Although a lot of research has been done on agile practices and role of requirement in agile methodologies but still there is need of studies on change manage management ,requirement prioritization, prototyping and nonfunctional requirement in agile methodologies. Aim of this review paper is to present the limitations in presentation of requirement engineering phases in agile practices and what are the issues and challenges that agile person faces in implementation of agile practices. Many research studies from different sources have been reviewed on basis of inclusion and exclusion criteria. Most RE activities has been discussed in review. Evidence helps to prove that how RE process was performed in scrums. Mostly research has been conducted on general agile methodologies, few authors specified RE practices in other methodologies of agile. Finding of this research is the work of researchers that will be beneficial for those who are interested in finding interesting area of research in this field because many techniques of agile (extreme programming, crystal methodology, lean ) requires further study and practical results as clarified by studies.
</description>
<dc:date>2017-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://hdl.handle.net/123456789/8037">
<title>Role of visualization in tacit knowledge: extraction and applications in software requirements</title>
<link>http://hdl.handle.net/123456789/8037</link>
<description>Role of visualization in tacit knowledge: extraction and applications in software requirements
Zainab Sultan; Rabiya Abbas; Shahid Nazir Bhatti; Amr Mohsen Jadi
Requirements have a proven role and considered as an important factor in designing and producing good quality software. Further available literature depicts precisely, comprehensively that poorly defined, organized requirements increase the cost of development, time for the development and more importantly leads to software product failure. It is of highest priority and importance for the developers, retailers as well as for the clients to verify that the designed and planned system satisfies their needs or not. In today’s world while designing, developing system, the knowledge extraction becomes an important area for research and key focus in order to compile and share knowledge. In knowledge extraction, explicit and tacit knowledge are the two categories of knowledge. Explicit knowledge is simple to perceive and understand due to its simplicity and clarity. Tacit knowledge is not that easily understandable due to its complex nature and as it resides under the experts’ mind. In this research, we have given enumerated illustrations and account of nature of tacit knowledge and different frameworks. Another vital contribution in this research is that it establishes rules and proposes a framework for tacit knowledge derivations. Further, implementing these proposed rules will help eliciting tacit knowledge without consuming more cost and effort. We have also focused on UI generation via different visualization tools or technologies developed for requirements representation that will be further validated by using case studies and using real events or scenarios data.
</description>
<dc:date>2017-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://hdl.handle.net/123456789/8032">
<title>The Impact of Analytical Assessment of Requirements Prioritization Models: An Empirical Study</title>
<link>http://hdl.handle.net/123456789/8032</link>
<description>The Impact of Analytical Assessment of Requirements Prioritization Models: An Empirical Study
Aneesa Rida Asghar; Atika Tabassum; Dr. Shahid Nazir Bhatti; Dr. S Asim Ali Shah
Requirements prioritization is one of the important parts of managing requirements in software development process which plays its role in the success or failure of a software product. A software product can go wrong or fail if right requirements are not prioritized at right time. Thus, there is a need of a vast or complete requirements prioritization technique or model that spans all the factors that must be considered while prioritizing requirements whether it’s for a traditional software development or agile software development. There are several requirements prioritization methodologies that aid in decision making and in prioritizing requirements but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. A requirement prioritization methodology that takes account of important factors such as time and human behavioral factors that has an influence in prioritizing requirements is required. This new model/ technique expected to overcome the lack that is in existing prioritization techniques because of not considering time gap factor and human behavioral factor. Extensive study on literature of agile methodology, requirements elicitation and prioritization has been done to find out factors that influence the decision making process of requirement prioritization. It is found that as agile methodologies such as XP, SCRUM deliver products in increments, there is a time gap between each increment of approximate 4 weeks or more, this time lapse could cause human behavioral to change either because of market demand or any other personal reason and, thus, influences the prioritization decision. These factors could be termed as time factor and human behavioral factors. Thus, a requirement prioritization technique or model is needed that takes account of all such factors while prioritizing requirements whether it’s for a traditional software development or agile software development.
</description>
<dc:date>2017-01-01T00:00:00Z</dc:date>
</item>
</rdf:RDF>
