1998
DOI: 10.1007/bf02919971
|View full text |Cite
|
Sign up to set email alerts
|

Requirements for a COTS software component: A case study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2003
2003
2006
2006

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 1 publication
0
7
0
Order By: Relevance
“…To the best of knowledge of the authors of this article, there are no standard or widespread methodologies for the development of RFP for the deployment of ERP systems, either for public or private sector companies or for international organizations, with the exception of some general procurement guidelines and principles (e.g., World Bank Procurement Guidelines, WTO Agreement on Government Procurement). Nevertheless, several templates with broadspectrum guidelines have been proposed for RFP preparation (see, for example, a collection of samples on freetemplates.com 2 , the Punjab Information Technology Board 3 , Infotivity Technologies, Inc. 4 Figure 2. The proposed RFP preparation process for an ERP acquisition in an international environment…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…To the best of knowledge of the authors of this article, there are no standard or widespread methodologies for the development of RFP for the deployment of ERP systems, either for public or private sector companies or for international organizations, with the exception of some general procurement guidelines and principles (e.g., World Bank Procurement Guidelines, WTO Agreement on Government Procurement). Nevertheless, several templates with broadspectrum guidelines have been proposed for RFP preparation (see, for example, a collection of samples on freetemplates.com 2 , the Punjab Information Technology Board 3 , Infotivity Technologies, Inc. 4 Figure 2. The proposed RFP preparation process for an ERP acquisition in an international environment…”
Section: Related Workmentioning
confidence: 99%
“…They should define the general qualities of the application [4], and may be classified in: Architectural requirements, dealing with issues of structure and integration (e.g., interaction of the new system with legacy systems); application domain requirements, specifying subjects related to the context in which the system will behave (i.e., application security specifications); and organizational requirements, constraints relevant to the entities (customer and vendor/integrator) involved in the implementation (e.g., software development strategy, organizational vision).…”
Section: Contentmentioning
confidence: 99%
See 1 more Smart Citation
“…Beus-Dukic motivates the need for NFRs [1] in the field of commercial offthe-shelf components (COTS) and defines NFR's informally as the general qualities of a software product.…”
Section: Related Workmentioning
confidence: 99%
“…As moving the focus from functional to non-functional requirements a number of topics, which should be addressed by the approach, come into light, as reported in [19].…”
Section: W38: Detailing Non-functional Requirements For Components Smentioning
confidence: 99%