The purpose of a vendor audit is to evaluate a potential supplier’s ability to produce and support a product. Producing a product involves the ability to understand user requirements, to turn those requirements into a functional specification and then into a usable product. Support covers everything from long-term financial stability, answering questions about products, providing a forum for cu...

The paper outlines an experiment conducted in two different academic environments, in which FIT tests were used as a functional requirements specification. Common challenges for functional requirements specifications are identified, and a comparison is made between how well prose and FIT user acceptance tests are suited to overcoming these challenges from the developer’s perspective. Experiment...

This paper presents a language called ScreenSpec that can be used to quickly specify screens during the requirements elicitation phase. Experiments and case studies presented in this paper show that it is easy to learn and effective to use. ScreenSpec was successfully applied in 9 real projects. Visual representation generated from ScreenSpec can be attached to requirements specification (e.g. ...

We know many of our IT projects fail and disappoint. The poor state of requirements methods and practice is frequently stated as a factor for IT project failure. In this paper, I discuss what I believe is the fundamental cause: we think like programmers, not engineers and managers. We do not concentrate on value delivery, but instead on functions, on use-cases and on code delivery. Further, man...

The elicitation of end-user requirements is primarily focusing on the industry, where companies endeavor to discover and satisfy their customer’s requirements. Increasingly however, companies which are working in the same or in different fields are getting together, in order to do joint research and development, despite the fact that they may be potential competitors. These kinds of projects ha...

A framework for the debugging of formal specifications for Cyber-Physical Systems is presented. Two debugging algorithms are presented. The first checks for erroneous or incomplete temporal logic specifications without considering the system. The second can be utilized for the analysis of reactive requirements with respect to system test traces. The specification debugging framework is applied ...

When specifying user requirements, not only it is critical to ensure correct and unambiguous specification of functional requirements, but also that of non-functional requirements (NFRs). In fact, resolving ambiguities from user specified natural language NFRs and specifying the correct ones in a formal language have attracted significant attention. Our current research focuses on the issues pe...

Requirements Elicitation requires a data scientist to communicate with a customer. A typical result of a requirements elicitation process in Software Engineering is an SRS (System Requirements Specification) document. For Data Science projects, there may not be an explicit need for a formal written SRS. However, it may be benefitial to record observations made during the process, if without the...

The COSMIC-FFP is a standard method that has been proven effective for measuring the functional size of business applications and realtime software systems from their functional user requirements specification. Despite of this, the methods based on COSMIC-FFP usually require a mapping between the concepts in the requirements specification and their own terms and do not take into account non-fun...