• Corpus ID: 8465751

Acquiring Cots Software Selection Requirements Acquiring Cots Product Requirements Lessons Learned

@inproceedings{Maiden1998AcquiringCS,
  title={Acquiring Cots Software Selection Requirements Acquiring Cots Product Requirements Lessons Learned},
  author={Neil A. M. Maiden},
  year={1998}
}
0 7 4 0 7 4 5 9 / 9 8 / $ 1 0 . 0 0 © 1 9 9 8 I E E E lthough procuring off-the-shelf systems from commercial suppliers is increasingly popular in our industry, fitting those systems to customer requirements remains problematic. The London Ambulance Service fiasco in 1992 exemplifies a system failure due, at least in part, to poor commercial off-the-shelf product selection. Following the system’s introduction in October 1992, a number of social and technical problems arose. The entire system… 
1 Citations

Figures from this paper

A study on software component selection methods

TLDR
It is argued that previous knowledge and decision on component selection can definitely reduce time for selection activities by guiding us through previous successful or failed case experience.

References

SHOWING 1-10 OF 15 REFERENCES

System Implementation Using Commercial Off-The-Shelf ( COTS ) Software

TLDR
Preliminary results obtained from an ongoing research experiment are described, which involves developing a prototype of a distributed database management * NRC Report Number 40173 and communications system.

COTS, integration and critical systems

TLDR
It would seem profitable to review solutions used in security applications, where the concept of a firewall is well understood and other interesting properties, such as non-interference, have been extensively studied.

ACRE: selecting methods for requirements acquisition

TLDR
The ACRE framework provides guidelines for requirements engineering practitioners using questions driven from a set of facets which define the strengths and weaknesses of each method.

Software package requirements and procurement

TLDR
The paper outlines the problems of specifying requirements and deploying these requirements in the procurement of software packages and outlines the key components of a programme of research in this area.

Architectural Mismatch or Why it's hard to build systems out of existing parts

TLDR
This paper uses the experience of building a family of software design environments from existing parts to illustrate a variety of types of mismatch that center around the assumptions a reusable part makes about the structure of the application in which is to appear.

Task scripts , use cases and scenarios in object oriented analysis

TLDR
The paper sets out to improve and clarify the terminology in use with respect to concepts such as use cases, scenarios and scripts and, in doing so, offers a generification of the use case concept: the task script.

Evaluating software engineering methods and tool part 5: the influence of human factors

TLDR
The principles of feature analysis are discussed and how to identify features and establish a means of scoring products against those features is described.

The skull beneath the skin: entity-relationship models of information artifacts

TLDR
It is concluded that, as a cheap, coarse-grained, and easy-to-learn modelling technique, ERMIA usefully fills a gap in the range of available HCI analysis techniques.