Software Requirement Engineering Research Papers (original) (raw)

Top Papers
Most Cited Papers
Most Downloaded Papers
Newest Papers
People
- by Moath tarawneh
- •
- Software Engineering, Development Studies, Research Methodology, Web Applications

7th International Conference on Software Engineering (SOFT 2021) will provide an excellent
international forum for sharing knowledge and results in theory, methodology and applications of
Software Engineering and Applications. The goal of this Conference is to bring together researchers
and practitioners from academia and industry to focus on understanding Modern software
engineering concepts and establishing new collaborations in these areas.

BD Community Help Project developed by us under the
guidance of MD. SHIEFUZZAMAN makes an environment
where one can share ideas, discuss issues and effectively
collaborate with one another towards solving problems.
The purpose of this document is to present a detailed description
of BD Community Help. It will explain the purpose and
features of the system, the interfaces of the system, what the
system will do, the constraints under which it must operate and
how the system will react to external stimuli. This document is
intended for the stakeholders of the system .The features
discussed in this document are mainly functional requirements.
These requirements are described in software development
perspective to easily grasp by use. It also covers the nonfunctional requirements like performance, reliability,
availability, security and maintainability.

... Domain Analysis Requirement and Assumptions identification Classifying Modeling ElaborationConflict Identification and Resolution Prioritization Specification ... 4.4. Conflict Management Contributions among goals (positive or... more

- by Shams Siddiqui and +1
- •
- Software Engineering, Software Requirement Engineering

Test case prioritization is a technique for selecting those test cases, which are expected to outperform for de- termining faulty modules earlier. Different phases of software development lifecycle represent the total software from different point of views, where priority module may vary from phase to phase. However, information from different phases of software development lifecycle is rarely introduced and no one integrates that information to prioritize test cases. This paper presents an effective test case prioritization framework, which takes software requirements speciﬁcation, design diagrams, source codes and test cases as input and provides a prioritized order of test cases using their collaborative information as output. Requirement IDs are split into words or terms excluding stop words to calculate requirements relativity. Design diagrams are extracted as read- able XML format to calculate the degree of interconnectivity among the activities. Source codes are parsed as call graphs where vertices and edges represent classes, and calls between two classes respectively. Requirements relativity, design interconnectivity and class dependencies are multiplied by their assigned weight to calculate ﬁnal weight and select test cases by mapping the customers’ requirements and test cases using that weight. The proposed framework is validated with an academic project and the results show that use of collaborative information during prioritization process can be beneﬁcial.

- by Md Saeed Siddik and +1
- •
- Software Engineering, Software Testing, Software Requirement Engineering, Test Case Prioritization

If you are confused by the title above you are in the same boat as the vast majority of software producers when confronted with
a display of formal methods. The easiest option when dealing with an activity whose benefi ts are doubtful and which looks impenetrable is to ignore it and do without. This is precisely what most software developers do and not necessarily to the detriment of their business (unless this business has safety implications); witness Microsoft, which makes millions of dollars selling MS-DOS and Windows without a single quantifi er in sight. Even a successful mathematical product such as Mathematica, which supports the interactive computer-based use of mathematics, consists of the order of a million lines of C-based code produced with no formal development.

The International Journal of Software Engineering & Applications (IJSEA) is a bi-monthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas.

Use case modeling refers to the process of identifying scenarios written in some natural language text, particularly to capture interactions between the system and associated actors. Several approaches have been proposed to maintain the synergy of use cases with other software models, but no systematic transformation approach is available to extract use case scenarios from the textual requirements specification. In this paper, we propose a systematic transformation approach that automatically extracts various use case elements from textual problem specifications. The approach uses Natural Language (NL) parser to identify Parts-Of-Speech (POS) tags, Type Dependencies (TDs) and semantic roles from the input text specification to populate use case elements. It further makes use of the questionnaire-based approach to develop the remaining unpopulated parts of the use case template. The paper demonstrates the applicability of the proposed approach by applying both industry and research-level case studies. The results highlight that the generated output is correct, consistent, non-redundant and complete, and helpful to use case developers in further analysis and documentation. CCS CONCEPTS • Software and its engineering → Software notations and tools;

— Good requirement leads to better solutions, for the specified problem of the organization. This paper discusses about the significance of requirements management. It’s no secret that poorly understood user requirements and uncontrolled scope creep to many software project failures. Many of the application development professionals buy wrong tools for the wrong reasons. To avoid purchasing the more complex and expensive tool, the organization needs to be realistic about the particular problem for which they opt. This paper discusses types and benefits of Requirements management tools, how to select right Requirements Management Tools and when to use in the project. Keywords— Requirements, software, organization, project, failures, complex, requirements management tools

- by Daniyal Alghazzawi and +3
- •
- Software Engineering, Requirements Engineering, Software Requirement Engineering, Software Requirements Tools

It’s a great resource for someone with a modest amount of professional programming experience and a basic knowledge of data structures and algorithms. Bentley covers a wide range of topics relevant to the working programmer, including multiple chapters with case studies of algorithmic development from Bentley’s life as a professional developer, a chapter on the importance of choosing the right data structure(s) for your program, program performance/tuning, and finally a number of chapters that discuss specific algorithms and data structures.

- by Camilo Vargas
- •
- Business, Business Administration, Computer Science, Software Engineering

Requirements are descriptions of the services that a software system must provide and the constraints under which it must operate Requirements can range from high-level abstract statements of services or system constraints to detailed mathematical functional specifications Requirements Engineering is the process of establishing the services that the customer requires from the system and the constraints under which it is to be developed and operated

Abstract: Much effort has been devoted to evaluating the usability of web-based system. With the increase in the mobile-based applications coupled with the limitations and challenges of mobile devices, it becomes mandatory to evaluate the web-based systems in the context of smartphone usability. In addition, a number of international standards/models on usability are available, but seldom used for practical usability evaluation. In this study, the popular ISO 9241-11 standard was used to evaluate a web-based health awareness portal within the smartphone mobile context. The results reveal some pointers to usability issues as well as confirmation that the web-based awareness portal is relatively usable on smartphone devices within the components defined in the models.

- by Prof. Dr. Azham Hussain and +1
- •
- Software Engineering, User Experience (UX), Software Requirement Engineering, Usability Engineering

Many smart IT engineers fail to get good jobs because they don't succeed in interviews.
Why?
They never respond meaningfully and convincingly on the spot.
Why?
Two reasons: First, their preparation involves only 'technical topics'. Second, they are not aware of their own talking style and likeability.
This brochure is about world's first Information Technology Interview Simulator & Trainer. It provides infinite number of mock interviews with recording and training features.

- by Dr. Suresh Namboothiri and +1
- •
- Software Engineering, Open Source Software, Software Testing, Information Communication Technology
- by Tanvir Rahman
- •
- Software Engineering, Open Source Software, Software Testing, Software Development

Despite the fact that the business executives remain doubtful about the strategic value of information technology. One of the most critical issues facing organizations in Kuwait today is the alignment of information system strategy with the business goals and objectives. Only 28% of the surveyed companies in Kuwait claim that their IT objectives aligned to their business strategy which is a very low number. This paper uses a survey to investigate the alignment existence between the business objectives and IT strategy within different companies in different sectors located in Kuwait. The survey questionnaire distributed to IT managers and business executive managers in the selected companies. The suggested survey questionnaires have to do first, with the alignment exist between the IT strategy and the company Business objectives; Secondly, the barriers on strategic alignment arising in those companies.

This is a research progress where FODA (feature oriented domain analysis) is used to implement a formal analysis
framework that characterized commonality and variability of features for a transmission pipeline design modelling language. The features representing the pipeline physical components were analysed along the line of the system logic being able to model stakeholders design intents. It is demonstrated that FODA methodology for domain analysis fits the needs for the application of a carefully studied semantics to the development of the modelling language. It also best matches with the specifications because representing the components as features in a feature model enabled the formalization of the syntax, the semantics, and the composition constraints. These formal definitions presented useful proofs for managing the variability in the application domain in terms of the components and the requirements. This requirements engineering task will provide a formal analysis model of system information and function behavior, and will bridge the gap between the requirements documentation and the language design.

- by Bunakiye Japheth
- •
- Software Development, Software Requirement Engineering
- by Athar Mohsin
- •
- Software Requirement Engineering

3rd International Conference on Software Engineering, Security and Blockchain (SESBC 2022) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of Software Engineering, Security and Blockchain. Authors are solicited to contribute to the conference by submitting articles that illustrate research results, projects, surveying works and industrial experiences that describe significant advances in the areas of Software Engineering, Security and Blockchain.

- by Edri Adi Setiawan
- •
- Software Requirement Engineering

Dokumen Spesifikasi Kebutuhan Perangkat Lunak (SKPL) merupakan dokumen spesifikasi kebutuhan perangkat lunak yang akan dikembangkan. Dokumen ini digunakan oleh pengembang perangkat lunak sebagai acuan teknis pengembangan perangkat lunak... more

Software development cycle is based on the software requirements. Requirement elicitation is first and most
important activity in the requirement engineering. If the requirements are efficiently elicited and managed then the
stakeholders application can be accomplished within time and budget. If the requirements are not complete, consistent and
correct then projects fail because they not meet the user needs. Requirement is define as the needs of customer. Requirement
elicitation techniques and tools are used for correct and complete requirement gathering. Many requirement elicitation
techniques and tools are available. This study based on the understanding of requirement gathering techniques and tools. The
paper also summarizes the comparison of the requirement elicitation techniques and software requirement tools. Comparison
of requirement elicitation techniques and tools are based on the various parameters.

- by Mateen A . Abbasi and +1
- •
- Software Engineering, Software Requirement Engineering

With increasing advancement of technology in the past years rise various security issues and problems. In this connected world, security is a paramount and challenging issue in software development and is the demand of time. However usually engineers/developers think about it after the development of the entire software and at that it's too late. Though, the software developers are aware of the importance of security and its priority throughout software development life cycle. Considering the security challenging issues right from the early stages of software development and incorporating it during software development indicates good research and development.

Scope & Topics The International journal of Software Engineering & Applications (IJSEA) is a BiMonthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas. Authors are solicited to contribute to the journal by submitting articles that illustrate research results, projects, surveying works and industrial experiences that describe significant advances in the areas of software engineering & applications.

The aim of this report is to give a brief description of requirements management and to promote understanding of requirements management as one of an interrelated set of systems engineering disciplines, and to understand these systems... more

- by Ahmed Omar
- •
- Software Engineering, Software Testing, Software Requirement Engineering

[Context] Coping with rapid requirements change is crucial for staying competitive in the software business. Frequently changing customer needs and fierce competition are typical drivers of rapid requirements evolution resulting in requirements obsolescence even before project completion. [Objective] Although the obsolete requirements phenomenon and the implications of not addressing them are known, there is a lack of empirical research dedicated to understanding the nature of obsolete software requirements and their role in requirements management. [Method] In this paper, we report results from an empirical investigation with 219 respondents aimed at investigating the phenomenon of obsolete software requirements. [Results] Our results contain , but are not limited to, defining the phenomenon of obsolete software requirements, investigating how they are handled in industry today and their

- by Krzysztof Wnuk and +1
- •
- Requirements Engineering, Lean Software Development, Empirical Software Engineering, Software Requirement Engineering

Construction projects involve multidisciplinary and multi-actor collaborations that generate massive amounts of data over their lifecycle. Data are often sensitive, and embody rights, ownership and intellectual property of the creator. Managing project information raises concerns about security, inconsistency and loss of data. Conventional approach of dealing with the complexities of data management involves the adoption of BIM based solutions that lack suitable means for the governance of collaboration, and access and archival of managed data. To overcome the limitations of BIM, Cloud-based governance solutions have been suggested as a way forward. However, there is a lack of understanding of construction ICT (Information and Communication Technology) practices from the perspectives of data management and governance. This paper aims to fill this gap; first, by exploring barriers related to BIM adoption and collaboration practices, in particular, issues related to data management and governance that can potentially be ameliorated with Cloud technologies, and second, by identifying key requirements for Cloud-based BIM governance solutions. A structured questionnaire was conducted among informed construction practitioners in this study. The findings reveal several barriers to BIM adoption alongside ICT and collaboration issues with an urgent need to develop a BIM governance solution underpinned by cloud technology. Further, a number of important requirements for developing BIM governance solutions have been identified.

Software project management is the utilization of resources in efficient manner to complete a project within time and budget. It is like a corner stone in every successful project. Sound software project management techniques are very important for the development of software projects both for organizations that develop outsourced projects and in-house projects. The data was collected through interviews and questionnaire. Most of the respondents were project managers having postgraduate degrees. From analysis it is concluded that project management practices play important role in the successful completion of projects. Sixteen percent of projects had no project plan. Many standard software practices are not being applied constantly in the projects. The risk assessment and mitigation are not carried out until the risk occurs. The role of software project management tools and techniques and their practices are also analyzed in detail in this paper. Many believed that decision making is the most important ability of project managers. In this paper we have described different factors that cause the success or failure of projects. Our results present general guidance for project managers to make sure that their projects be successful. This study shows the importance of project management tools and techniques in the industry. It also shows how project management is important for a successful and quality software product. If a project is managed properly, we get a quality product within allocated time and budget.

- by Basharat Jehan
- •
- Computer Science, Software Engineering, Statistics, Computer Engineering

— Requirements need to be managed in order to ensure their consistency, integration and correctness. Further, it is important to conduct requirements validation to produce quality requirements with respect to their correctness, completeness and consistency. In relation to this, a number of engineering tools have been developed to perform requirements validation. However, each of the tools have different features in handling requirements, hence there is a need to identify the strengths and weaknesses of each tool to provide valuable information for software engineers to choose the most suitable tool for requirements validation. Based on seven RE tools, this paper reports the analysis of these tools based on three criteria, namely the requirements engineering activities, requirements modeling technique and requirements specification to determine their strengths and weaknesses. It was found that the validation activity is still lacking in most of the RE tools. This analysis leads to the identification of research gaps that need further exploration by the developers of requirements engineering tools.