Fig 1 - uploaded by Nagy Ramadan
Content may be subject to copyright.
![Requirement Engineering Framework 3.2 Requirements Elicitation It is the process of collecting requirements from stakeholders. System constrains, boundaries, identification of problems are stated in this stage. This stage is also known as " Requirements gathering " . Some questions should be answered in this stage [4]: Does the system contribute to high level objectives? Can the system be implemented within given budget?](profile/Nagy-Ramadan/publication/308186449/figure/fig1/AS:407575095988224@1474184883410/Fig-1-Requirement-Engineering-Framework-32-Requirements-Elicitation-It-is-the-process.png)
Requirement Engineering Framework 3.2 Requirements Elicitation It is the process of collecting requirements from stakeholders. System constrains, boundaries, identification of problems are stated in this stage. This stage is also known as " Requirements gathering " . Some questions should be answered in this stage [4]: Does the system contribute to high level objectives? Can the system be implemented within given budget?
Source publication
![Fig. (4) Requirement prioritization process [4]](profile/Nagy-Ramadan/publication/308186449/figure/fig2/AS:407575095988225@1474184883519/Fig-4-Requirement-prioritization-process-4_Q320.jpg)
Engineering (RE) plays an important role in the success of software development life cycle. As RE is the starting point of the life cycle, any changes in requirements will be costly and time consuming. Failure in determining accurate requirements leads to errors in specifications and therefore to a mal system architecture. In addition, most of soft...
Similar publications
A implementação de softwares que atenda as expectativas dos usuários, em relação às funcionalidades desejadas, custos e prazos ainda é um processo complexo. O alto índice de falhas na construção de sistemas representa perda de qualidade e elevação de custos aos desenvolvedores, comprometendo os resultados perante o cliente-usuário. Como ferramenta...
Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and int...
Requirements specification has long been recognized as a critical activity in software development processes because of its impact on project risks when poorly performed. A large amount of studies address theoretical aspects, propositions of techniques, and recommended practices for Requirements Engineering (RE). To be successful, RE has to ensure...
Context: Over the past 20 years, software startups have created many products that have changed human life. Since these companies are creating brand-new products or services, requirements are difficult to gather and highly volatile. Although scientific interest in software development in this context has increased, the studies on requirements engin...
Aspect-Oriented Requirements Engineering (AORE) extends the existing requirements engineering approaches to support the identification and handling of crosscutting concerns. Crosscutting concerns are considered as potential aspects and can lead to the phenomenal "tyranny of the dominant decomposition". Requirements-level aspects are responsible for...
Citations
... Additionally, verification serves to validate that the finished product fully complies with the stated specifications. [21]. ...
... • The validation process determines whether the specifications created during the elicitation step satisfy all of the user's requirements (users). Developers employ several task sets throughout the validation phase to make sure that the software created can be linked to the needs of the user [21]. ...
Global human population growth has forced farms to evolve in order to produce more livestock products more efficiently while also paying attention to public health, environmental sustainability, and animal welfare. However, problems arise when some diseases appear to affect farm animals and large companies providing livestock products dominate the market. It is necessary to develop a platform or application that can be used to solve these two problems, especially for breeders who have farms on a small scale. This study aims to outline the process of understanding engineering requirements by utilizing the Loucopoulos and Karakostas Requirements Engineering Process Model method, which consists of elicitation of requirements, specification of requirements, as well as validation and verification of requirements. The development process is carried out by hiring breeders and potential customers to determine the priority needs of the platform. The results showed that of the 25 defined functional needs, there were 22 final functional needs that were validated with values above 50%. The E Farm platform should be further developed based on the defined demands since a total of 22 validated needs have been determined to be able to represent 88% of the needs required by users.
... Scrum does not restrict specific techniques; however, it establishes a framework to work in. Requirements Management activities will be found in iterative RE, short releases, and customer-feedback [12]. This could especially be elaborated via Product Backlog tracking (by changing the requirements (added/deleted) to/from Product Backlog), and Sprint Planning meetings. ...
Requirements are one of the important factors for software success. However, Requirements Engineering (RE) activities, in the Waterfall process model, are done sequentially in the analysis phase, which makes it difficult when RE practitioners think and reason about them in Agile Software Development (ASD) process model. RE practitioners need to find the established RE activities conventions in the ASD process model, especially with an increase of software companies, which transform to the ASD process model, in order to foster their transition to the new model. The objective of this study is to provide RE activities in ASD to allow RE practitioners to utilize the appropriate activity for specific ASD methodology. RE activities in ASD are handled repetitively and on a small scale, which makes them embedded in the development life cycle. This paper focuses on highlighting them in different ASD methodologies and discusses the practices that resolve the traditional Waterfall model issues. Although the ASD model has resolved some traditional RE issues, it introduced other issues, such as a consequence of trying to achieve an adequate balance between agility and stability. In addition, there is a lack of practices that target non-functional requirements.
... Dalam proses pertama yaitu elicitation yang memiliki aktivitas utama untuk kumpulkan data dari pihak terkait. Kegiatan ini menghasilkan identifikasi masalah, perumusan kendala sistem, dan kendala sistem [11]. Dalam proses requirement engineering elicitation terdapat dua aspek yaitu problem domain yang berarti area permasalahan yang harus disesuaikan dengan sistem perangkat lunak, dan terdapat User yang menjadi stakeholder dalam pengembangan system perangkat lunak. ...
... Scrum's artifacts serve as a representation of work to maximize the transparency of information that describes a product that's being developed with containing a commitment to ensure the progress of each role can be measured. Thus, it reinforces empiricism and the Scrum values for the team and their stakeholders [8], [19]. ...
Software development management system is important in application development. A proper software development management system will create a team that can adapt to system requirements and changes during application development. Various software development management systems are developed and widely implemented in software development, one of which is Agile Scrum. This study aims to implement well-documented Scrum for end-to-end application development, including the development of servers and mobile applications that we develop. We developed a bus application called SICITRA, with the main feature of being able to help passengers share their travel information with those closest to them. Scrum is used because it has agility which can make application development faster and more organized, and there is a close relationship between everyone involved in the project. The results of this study are that by using well-documented Scrum, we can make it easier to track progress, become a guide during system development, become history and evaluate Scrum implementation during development.
... This is a widely used strategy in distributed scrum development to improve effective communication among teams. As teams are working from different locations, with varying hours of working due to temporal differences, so project owners try to adjust overlapping working hours of distributed teams by allowing team members to attend meetings from home [1,9,[16][17][18][19][20][21][22][23][24][25]. ...
... Informal communication is the strategy adopted by different teams, to build trust among team members. By adopting different modes of informal communication (i.e., individual or teleconferences, video conferences, emails, instant messages) with formal documentation can help to build trust among team members [14,19,[25][26][27][28][29][30]. ...
... Although scrum do not require heavy documentation but, lack of documentation in distributed scrum development leads to many challenges, i.e., misunderstood or unclear requirements, requirement traceability issues, requirement change management, etc. To avoid these issues, it is important to maintain a formal requirement document with a standard template understandable to all distributed teams [19,[27][28][29][30][46][47][48][49]. ...
... Engineering requirements is the process of analyzing, specifying, validating, and maintaining the quality requirements of a system [60,64]. The improper identification of requirements can lead to defects in the specifications of an AI solution [65]. Improperly outlined requirements for DT can lead to ethical issues within FAMA, which affect various stakeholders. ...
... The DT integration into the activities and processes of organizations generates several ethical requirements while contributing to solving existing ethical issues before their implementation [4]. Ethical requirements must be integrated into the engineering processes of quality requirements [60,64,65]. Ethical principles can generate a better involvement of stakeholders, especially end-users. ...
Digital technologies affect all areas and activities of society. Accounting is no exception to this trend, as organizational information system accounting increasingly integrates digital technologies. The paper aims to study the integration of ethical requirements with the quality requirements in implementing digital technologies based on artificial intelligence, blockchain, the internet of things, and cloud computing in financial and managerial accounting. This empirical study of 396 accountants from Romanian organizations involves investigating the influence of ethical and quality requirements of digital technologies on the perception of users’ satisfaction in financial and managerial accounting. Empirical research encompasses a quantitative approach using structural equation modeling and artificial neural network analysis in a two-stage procedure. Some of the existing ethical issues can be addressed by implementing new digital technologies but implementing these emerging technologies can generate other ethical and quality issues that accounting and IT professionals must address in a combined effort. The research results show that the ethical requirements that influence the perception of financial and managerial accounting are security and trust. Among the quality requirements, the most critical influence in the perception of accountants is reliability.
... It entails identifying stakeholders' needs; recognizing the context of the requirements; representing those requirements in an easily understandable manner; and negotiating, validating, documenting, and managing those requirements. Failing to identify correct needs leads to flaws in specifications and the other components of a system [28]. Inadequately defined requirements can cause many difficult problems, which have an impact on different direct and indirect stakeholders of software systems. ...
... Requirements engineering encompasses many sub-processes. The major five sub-processes are requirements elicitation, requirements analysis and negotiation, requirements specification, requirements validation, and requirements management [27][28][29][30][31]. ...
Context: Ethics have broad applications in different fields of study and different contexts. Like other fields of study, ethics have a significant impact on the decisions made in computing concerning software artifact production and its processes. Hence, in this research, ethics is considered in the context of requirements engineering during the software development process. Objective: The aim of this paper is to discuss the investigation results regarding ethical problems of requirements engineering processes by taking sample software developing companies and exposing existing research gaps. Method: This research uses interviewing, focus group discussions, purposive sampling, and qualitative analysis research methods. Result: This research finds an absence of industry practices, professional responsibility code of conduct standards, and other guidelines within companies when integrating ethical concerns of software during requirements engineering. It also indicates that almost all companies have no identification methods and checking mechanisms for ethical concern considerations. Furthermore, the major identified ethical concerns are classified into six categories as requirements identification problems, quality-related problems, carrying out unpermitted activities, unwillingness to give requirements, knowledge gaps and lack of legal grounds/rules for accountability. Conclusion: From the findings of this research, it can be concluded that, in the case software companies, there is no specific method for identifying ethical concerns. Additionally, there are no standards and guidelines used within the companies. This implies the need to overcome the existing and emerging ethical issues of requirements engineering.
... This research paper is based on the three cycles in DSR: relevance, design, and rigor (Hevner & Chatterjee, 2010). We also followed an agile software development method, the scrum framework, in the building phase to ensure the creation of high-quality products (Darwish & Megahed, 2016) and used Google's Speech-to-Text recognition to provide the video's transcript to users. The "asmeany" app was evaluated in two stages. ...
Hearing loss or deafness affects the daily lives of many people around the world. One of the issues that people who are deaf or hard of hearing face is the difficulty in understanding the audio content of the videos they are watching. This study proposes an Android app to assist individuals with hearing disabilities in Saudi Arabia by providing transcript displays for any video uploaded into the App. A three-cycle design science research (DSR) methodology was adopted for this study, and the app was developed according to the agile software methodology, Scrum. The “asmeany” app was evaluated within two stages, focusing on sociotechnical and technical performance perspectives to assess the app’s usability and utility. The usability of “asmeany” was evaluated by ten deaf people from Saudi Arabia using A-SUS, with /encouraging results. When the app’s utility was evaluated using unit testing, all the stories and scenarios passed; thus, the app is error free and performs as expected. As a result of this DSR project, three design principles are recommended for use in building any IT artifact for deaf people or those with hearing loss.
... Sprint: Scrum is empirical based agile framework, structured on the basis of control theory of empiricism under the canopy of agility, which helps in addressing complicated processes and increased productivity and quality of software product development. scrum approach is based on the precepts and values of the agile statement ,which promote a various style for managing software development tasks, cooperation over contract negotiation, and responding to changes fo overall plan [30]. The sprint duration is very significant so that the user stories are as small as possible. ...
... SCRUM adalah kerangka kerja manajemen berbasis tim yang dinamis, sehingga penggunaan SCRUM dapat beradaptasi dengan perubahan saat membuat sistem informasi (Karabulut & Ergun, 2018). Penggunaan metode SCRUM yang tepat memastikan produk berkualitas tinggi ( (Ramadan & Megahed, 2016). Metode SCRUM memiliki 6 tahapan dasar (Pohl & Hof, 2015). ...
Educational facilities and infrastructure are all equipment/facilities used in the learning process to achieve educational goals. Educational facilities and infrastructure have a function to support the learning process carried out by students and teachers in the classroom. Management of educational facilities and infrastructure is a management activity that begins with planning needs, procurement, inventory, storage, school maintenance efficiently and on target. An example of the implementation of facilities and infrastructure management activities is at SMAN 4 Malang, where the facilities and infrastructure management activities carried out are data collection of goods and rooms catalogs as well as data collection of borrowed goods and rooms. Management of facilities and infrastructure at SMAN 4 Malang is difficult because of the large amount of data that must be managed. The development of the ADI STETSA Information System (Digital Application Studium Et Sapientia) for SMAN 4 Malang was developed using the SCRUM method because in this method everyone can adaptively overcome complex problems while productively and creatively producing high-value products. The process of developing the ADI STETSA information system was carried out in 5 sprints. The resulting information system can be used for infrastructure services at SMAN 4 Malang. Sarana dan prasarana pendidikan adalah semua perlengkapan/fasilitas yang digunakan dalam proses pembelajaran untuk mencapai tujuan pendidikan. Sarana dan prasarana pendidikan memiliki fungsi untuk mendukung proses pembelajaran yang dilakukan siswa dan guru di dalam kelas. Pengelolaan sarana dan prasarana pendidikan merupakan kegiatan manajemen yang dimulai dengan perencanaan kebutuhan, pengadaan, inventarisasi, penyimpanan, pemeliharaan sekolah secara efisien dan tepat sasaran. Contoh pelaksanaan kegiatan pengelolaan sarana dan prasarana terdapat di SMAN 4 Malang, dimana kegiatan pengelolaan sarana dan prasarana yang dilakukan adalah pendataan katalog barang dan ruangan serta pendataan barang dan ruangan yang dipinjam. Pengelolaan sarana dan prasarana di SMAN 4 Malang sulit dilakukan karena banyaknya data yang harus dikelola. Pengembangan Sistem Informasi ADI STETSA (Aplikasi Digital Studium Et Sapientia) untuk SMAN 4 Malang dikembangkan dengan menggunakan metode SCRUM karena dalam metode ini setiap orang dapat secara adaptif mengatasi masalah kompleks sambil secara produktif dan kreatif menghasilkan produk bernilai tinggi. Proses pengembangan sistem informasi ADI STETSA dilakukan sebanyak 5 sprint. Sistem informasi yang dihasilkan dapat digunakan untuk layanan sarana prasarana di SMAN 4 Malang.
