System acquisition based on software product assessment
Proceedings of the 18th international conference on Software engineering
OTSO: a systematic process for reusable software component selection
OTSO: a systematic process for reusable software component selection
Enterprise resource planning: ERP adoption by European midsize companies
Communications of the ACM
Acquiring COTS Software Selection Requirements
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
The Treatment of Non-Functional Requirements in MIKE
Proceedings of the 5th European Software Engineering Conference
Systematic Formulation of Non-Functional Characteristics of Software
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Software Package Requirements and Procurement
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Combined Selection of COTS Components
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Procurement of enterprise resource planning systems: experiences with some Hong Kong companies
Proceedings of the 28th international conference on Software engineering
Evaluating and selecting software packages: A review
Information and Software Technology
Expert Systems with Applications: An International Journal
Expert Systems with Applications: An International Journal
Journal of Systems and Software
A non-functional requirements tradeoff model in Trustworthy Software
Information Sciences: an International Journal
| Hi-index | 0.00 |
We present a proposal for selecting ERP products from a formal description of their relevant characteristics. The work is based on a previous and successful collaboration with a midsize company in the field of software package selection. An ERP was selected following a systematic methodology called SHERPA. In this past experience, SHERPA relied on natural language descriptions of the application domain, user needs and candidate ERP solutions. In this paper, we show that a formal language may be used for modeling this application domain, translating user needs into requirements over the ERP products, and for reflecting how concrete ERP, products adjust to them. Having selection criteria used during ERP acquisition formally modeled, as well as user needs and ERP product descriptions, we expect to obtain more reliable and understandable results in this process.