Conferences related to Software Requirements

Back to Top

2020 IEEE/ACM 42nd International Conference on Software Engineering (ICSE)

ICSE is the premier forum for researchers to present and discuss the most recent innovations,trends, outcomes, experiences, and challenges in the field of software engineering. The scopeis broad and includes all original and unpublished results of empirical, conceptual, experimental,and theoretical software engineering research.


GLOBECOM 2020 - 2020 IEEE Global Communications Conference

IEEE Global Communications Conference (GLOBECOM) is one of the IEEE Communications Society’s two flagship conferences dedicated to driving innovation in nearly every aspect of communications. Each year, more than 2,900 scientific researchers and their management submit proposals for program sessions to be held at the annual conference. After extensive peer review, the best of the proposals are selected for the conference program, which includes technical papers, tutorials, workshops and industry sessions designed specifically to advance technologies, systems and infrastructure that are continuing to reshape the world and provide all users with access to an unprecedented spectrum of high-speed, seamless and cost-effective global telecommunications services.


ICASSP 2020 - 2020 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP)

The ICASSP meeting is the world's largest and most comprehensive technical conference focused on signal processing and its applications. The conference will feature world-class speakers, tutorials, exhibits, and over 50 lecture and poster sessions.


IEEE INFOCOM 2020 - IEEE Conference on Computer Communications

IEEE INFOCOM solicits research papers describing significant and innovative researchcontributions to the field of computer and data communication networks. We invite submissionson a wide range of research topics, spanning both theoretical and systems research.


2019 IEEE 28th International Symposium on Industrial Electronics (ISIE)

The conference will provide a forum for discussions and presentations of advancements inknowledge, new methods and technologies relevant to industrial electronics, along with their applications and future developments.


More Conferences

Periodicals related to Software Requirements

Back to Top

Aerospace and Electronic Systems Magazine, IEEE

The IEEE Aerospace and Electronic Systems Magazine publishes articles concerned with the various aspects of systems for space, air, ocean, or ground environments.


Communications Magazine, IEEE

IEEE Communications Magazine was the number three most-cited journal in telecommunications and the number eighteen cited journal in electrical and electronics engineering in 2004, according to the annual Journal Citation Report (2004 edition) published by the Institute for Scientific Information. Read more at http://www.ieee.org/products/citations.html. This magazine covers all areas of communications such as lightwave telecommunications, high-speed data communications, personal communications ...


Communications, IEEE Transactions on

Telephone, telegraphy, facsimile, and point-to-point television, by electromagnetic propagation, including radio; wire; aerial, underground, coaxial, and submarine cables; waveguides, communication satellites, and lasers; in marine, aeronautical, space and fixed station services; repeaters, radio relaying, signal storage, and regeneration; telecommunication error detection and correction; multiplexing and carrier techniques; communication switching systems; data communications; and communication theory. In addition to the above, ...


Computer

Computer, the flagship publication of the IEEE Computer Society, publishes peer-reviewed technical content that covers all aspects of computer science, computer engineering, technology, and applications. Computer is a resource that practitioners, researchers, and managers can rely on to provide timely information about current research developments, trends, best practices, and changes in the profession.


Computer Architecture Letters

Rigorously peer-reviewed forum for publishing early, high-impact results in the areas of uni- and multiprocessors computer systems, computer architecture workload characterization, performance evaluation and simulation techniques, and power-aware computing


More Periodicals

Most published Xplore authors for Software Requirements

Back to Top

Xplore Articles related to Software Requirements

Back to Top

IEE Colloquium on 'Software Requirements for High Integrity Systems' (Digest No.115)

IEE Colloquium on Software Requirements for High Integrity Systems, 1988

None


Software Requirements for the Certified Software Development Associate (CSDA) and IEEE Standards Bundle

Software Requirements for the Certified Software Development Associate (CSDA) and IEEE Standards Bundle, 03/27/2013

The following course is in this bundle: Software Requirements. This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Associate (CSDA) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the ...


(CSDP) Software Requirements

(CSDP) Software Requirements, 06/30/2011

This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Professional (CSDP) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the Software Engineering Body of Knowledge - or SWEBOK, upon ...


(CSDA) Software Requirements

(CSDA) Software Requirements, 01/18/2012

This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Associate (CSDA) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the Software Engineering Body of Knowledge - or SWEBOK, upon ...


Distributed elicitation of software requirements: An experimental case from Argentina and Colombia

2013 8th Computing Colombian Conference (8CCC), 2013

Software development tends more and more to be a distributed or global process where participants are geographically dispersed. This scenario requires paying attention to three aspects identified as physical distance, temporal distance and cultural distance. It is acceptable to argue that these new features will impact the software process, especially in those phases where there are demands for greater communication ...


More Xplore Articles

Educational Resources on Software Requirements

Back to Top

IEEE-USA E-Books

  • IEE Colloquium on 'Software Requirements for High Integrity Systems' (Digest No.115)

    None

  • Software Requirements for the Certified Software Development Associate (CSDA) and IEEE Standards Bundle

    The following course is in this bundle: Software Requirements. This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Associate (CSDA) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the Software Engineering Body of Knowledge - or SWEBOK, upon which the Certification Exam is based. Within each course module, there is a list of textbooks, courses and relevant reference materials to assist you in preparing for the Certification Exam. The Software Requirements Assessment Course is concerned with the elicitation, analysis, specification and validation of software requirements. Software Requirements Assessment is an integrated overview of software requirements in software development projects. Key issues include software requirement fundamentals, the requirements process, requirements elicitation, writing and interpretation, requirement analysis, specification, validation and practical considerations in software development. Also included are quizzes to assess knowledge comprehension. The following IEEE standards are included in this package: IEEE 1362-1998, IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document, IEEE 1233-1998 - IEEE Guide for Developing System Requirements Specification - Institute of Electrical and Electronics Engineer, IEEE 830-1998 IEEE Recommended Practice for Software Requirements Specifications - Institute of Electrical and Electronics Engineers.

  • (CSDP) Software Requirements

    This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Professional (CSDP) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the Software Engineering Body of Knowledge - or SWEBOK, upon which the Certification Exam is based. Within each course module, there is a list of textbooks, courses and relevant reference materials to assist you in preparing for the Certification Exam. The Software Requirements Knowledge Area (KA) is concerned with the elicitation, analysis, specification and validation of software requirements. It is widely acknowledged within the software industry that software engineering projects are critically vulnerable when these activities are performed poorly. Software requirements express the needs and constraints placed on a software product that contribute to the solution of some real-world problem. This course is intended to assess your understanding of software requirements through inline quizzes and feedback. Specific topics addressed in this course are: fundamentals of software requirements, requirements process, requirements elicitation, requirements analysis, requirements specifications, requirements validation, and practical considerations.

  • (CSDA) Software Requirements

    This tutorial is part of a series of eLearning courses designed to help you prepare for the examination to become a Certified Software Development Associate (CSDA) or to learn more about specific software engineering topics. Courses in this series address one or more of the fifteen Knowledge Areas that comprise the Software Engineering Body of Knowledge - or SWEBOK, upon which the Certification Exam is based. This course is intended to assess your understanding of software requirements through inline quizzes and feedback. The CSDA credential is intended for graduating software engineers and entry- level software professionals and serves to bridge the gap between your educational experience and real-world work requirements. The Software Requirements Knowledge Area (KA) is concerned with the elicitation, analysis, specification and validation of software requirements. It is widely acknowledged within the software industry that software engineering projects are critically vulnerable when these activities are performed poorly. Software requirements express the needs and constraints placed on a software product that contribute to the solution of some real-world problem.

  • Distributed elicitation of software requirements: An experimental case from Argentina and Colombia

    Software development tends more and more to be a distributed or global process where participants are geographically dispersed. This scenario requires paying attention to three aspects identified as physical distance, temporal distance and cultural distance. It is acceptable to argue that these new features will impact the software process, especially in those phases where there are demands for greater communication and collaboration among team members. This paper presents a controlled experiment carried out in a university setting which tries to acquire a better knowledge elicitation stage distributed software requirements, as well as analyzes the use of university settings to perform these validations.

  • Software requirements for high integrity systems-the CEGB guidelines for the use of programmable electronic systems for reactor protection

    A description is given of the CEGB's guidelines for the use of programmable electronic systems for reactor protection. System and hardware requirements are briefly described, with a fuller discussion of the requirements and restrictions for the use of software within protection systems. The maximum figures which are allowed to be ascribed to software in the reliability calculation for a system containing the software are discussed. The author concludes that the PES guidelines limit the use of software within a reactor protection system and only allow very conservative claims to be made for its correctness and reliability. For a system to be classified as 'highly reliable' it has to incorporate diversity and redundancy of design and implementation.<<ETX>>

  • Software requirements for railway signalling systems

    A railway signalling system transmits command information to trains. This command information must be interlocked with information relating to train position, state of points and other items of railway equipment to ensure the safety of train movements; processor-based systems are used for these functions. The software for such systems, for example the BR Solid State Interlocking (SSI) and Radio Electronic Token Block (RETB) systems may be considered in terms of a multi-level structure comprising 4 levels. The lowest level, safety management, manages the safety of the system hardware, including self tests and comparisons between parallel redundant processors. The next level is concerned with communications and interfacing. The functional program level implements the rules of the signalling or train control system. It is common to the whole railway network and is configured to the requirements of a specific location by the geographical data level.<<ETX>>

  • Thai software requirements specification pattern

    Although natural language has been widely accepted for writing software requirements specifications but writing skills are still needed for software engineers. Ambiguities are often encountered in requirements since software engineers do not have good writing skills or writing experience. In this study, we present a Thai software requirements specification pattern by using controlled syntax. Our pattern can help software engineers to answer the questions: “How to start writing software requirements specification?” and “What information should be gathered?”. Each component of the pattern is designed and described based on our controlled syntax.

  • AHP_GORE_PSR: Applying analytic hierarchy process in goal oriented requirements elicitation method for the prioritization of software requirements

    Goal Oriented Requirements Engineering (GORE) is concerned with the identification of goals of the software according to the need of the stakeholders. In GORE, goals are the need of the stakeholders. These goals are refined and decomposed into sub-goals until the responsibility of the last goals are assigned to some agent or some software system. In literature different methods have been developed based on GORE concepts for the identification of software goals or software requirements like fuzzy attributed goal oriented software requirements analysis (FAGOSRA) method, knowledge acquisition for automated specifications (KAOS), i* framework, attributed goal oriented requirements analysis (AGORA) method, etc. In AGORA, decision makers use subjective values during the selection and the prioritization of software requirements. AGORA method can be extended by computing the objective values. These objective values can be obtained by using analytic hierarchy process (AHP). In AGORA, there is no support to check whether the values provided by the decision makers are consistent or not. Therefore, in order to address this issue we proposed a method for the prioritization of software requirements by applying the AHP in goal oriented requirements elicitation method. Finally, we consider an example to explain the proposed method.

  • Towards a dynamic software requirements specification

    This paper focuses on software requirements documentation and more specifically on the software requirements specification document. It aims to help the requirements engineers to be more efficient in writing this document. Indeed we propose a dynamic document model to represent software requirements specification where most part of it will be automatically fed from a requirements database. Hence authors will focus mainly on the text part of the specification that requires their problem domain knowledge and writing expertise. So a central challenge for this research work is how to make dynamic software requirements specification. A case study related to the software requirements specification of a hotel reservation system will be built based on the new model.



Standards related to Software Requirements

Back to Top

IEEE Recommended Practice for Software Acquisition


IEEE Recommended Practice for Software Requirements Specifications

The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes ...


IEEE Standard - Adoption of International Standard ISO/IEC 12119:1994(E) - Information Technology - Software Packages - Quality Requirements and Testing

IEEE Std 1465-1998 is an adoption of ISO/IEC 12119: 1994(E). IEEE Std 1465-1998 may be employed to a) Specify quality requirements for software, and provide instructions on how to test against these requirements. b) Manage and improve the organizationÕs quality processes and personnel. c) Establish management and engineering environments based on the quality requirements and methods in ISO/IEC 12119: 1994(E). ...


IEEE Standard Classification for Software Anomalies


IEEE Standard for a Software Quality Metrics Methodology

Methodology for establishing quality requirements and identifying, implementing, analyzing, and validating software quality metrics.


More Standards