CFP last date
20 May 2024
Reseach Article

Article:A Goal Oriented Approach for the Definition of a Business Process Requirement Model

by Atsa Etoundi Roger, Fouda Ndjodo Marcel, Atouba Christian Lopez
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 9 - Number 7
Year of Publication: 2010
Authors: Atsa Etoundi Roger, Fouda Ndjodo Marcel, Atouba Christian Lopez
10.5120/1401-1890

Atsa Etoundi Roger, Fouda Ndjodo Marcel, Atouba Christian Lopez . Article:A Goal Oriented Approach for the Definition of a Business Process Requirement Model. International Journal of Computer Applications. 9, 7 ( November 2010), 1-7. DOI=10.5120/1401-1890

@article{ 10.5120/1401-1890,
author = { Atsa Etoundi Roger, Fouda Ndjodo Marcel, Atouba Christian Lopez },
title = { Article:A Goal Oriented Approach for the Definition of a Business Process Requirement Model },
journal = { International Journal of Computer Applications },
issue_date = { November 2010 },
volume = { 9 },
number = { 7 },
month = { November },
year = { 2010 },
issn = { 0975-8887 },
pages = { 1-7 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume9/number7/1401-1890/ },
doi = { 10.5120/1401-1890 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T19:57:58.728535+05:30
%A Atsa Etoundi Roger
%A Fouda Ndjodo Marcel
%A Atouba Christian Lopez
%T Article:A Goal Oriented Approach for the Definition of a Business Process Requirement Model
%J International Journal of Computer Applications
%@ 0975-8887
%V 9
%N 7
%P 1-7
%D 2010
%I Foundation of Computer Science (FCS), NY, USA
Abstract

This paper presents a Goal Oriented Approach for the Definition of a Business Process Requirement Model, taking into account the level of importance and constraints inherent in these requirements. The level of importance of a goal is the credit which the user associates to it, while constraints are non-functional needs related to that which this goal must satisfy. The approach proposed in this article revolves around four major activities: the identification of user requirements; selection of the various goals; transformation of the requirements into knowledge bits and lastly, development of the requirement model. We showed in this paper that this step enabled us to describe in an exhaustive way a business process.

References
  1. Lubars, M., Potts, C., Richer, C.: A review of the state of the practice in requirements modeling.Proc. IEEE Symp. Requirements Engineering, San Diego 1993.
  2. Karen Mc Graw, Karan Harbison, User Centered Requirements, The Scenario-Based Engineering Process. Lawrence Erlbaum Associates Publishers, 1997.
  3. The Standish Group, Chaos. Standish Group Internal Report, http://www.standishgroup.com/chaos.html, 1995
  4. Voas J., « COTS Software - The Economical Choice ? », IEEE Software, vol. 15 (3), p. 16-19,March, 1998.
  5. Tran V., Liu D.-B., « A Procurement-Centric Model for Engineering Component Based Software Engineering », Proceedings of the 5th IEEE International Symposium on Assessment of Software tools (SAST), Los Alamitos, California, USA, June, 1997.
  6. Bornwsword L., Obendorf P., Sledge C., « Developing New Processes for COTS-Based Systems », IEEE Software, vol. 34 (4), p. 48-55, July-August, 2000.
  7. Güngör-En C., Baraçli H., « A Brief Literature Review of Enterprise Software Evaluation and Selection Methodologices : A Comparison in the Context of decision- Making Methods », Procedings of the 5th International Symposium on Intelligent Manufacturing Systems,p. 874-883, May, 2006.
  8. Kahina Hassam, Bart George, Régis Fleurquin, Salah Sadou, « utilisation de la transformation de modèles pour faciliter la sélection de composants logiciels », IDM’2008 5-6 juin Mulhouse, 2008.
  9. Farida Semmak, Joël Brunet, « Un métamodèle orienté buts pour spécifier les besoins d’un domaine », 23e Congrès INFORSID, pp 115- 132, mai 2005.
  10. Bouchra El Asri, Mahmoud Nassar, Bernard Coulette, Abdelaziz Kriouile, « Architecture d’assemblage de composants multivues dans VUML », Revue RSTIL’Objet, PP 1- 32, 2005.
  11. Minel J.-L., « Le résumé automatique de textes : solutions et perspectives», in Proceedings of TAL, Résumé automatique de textes, vol. 45/1, p. 7-13, 2004.
  12. Mehdi Yousfi-Monod,Violaine Prince, « Compression de phrases par élagage de leur arbre morpho-syntaxique : Une première application sur les phrases narratives », RSTI- TSI–25/2006. Document numérique, pp 437-468, 2006
  13. G. Grosz , « Ingénierie des besoins : problèmes et perspectives », Centre de recherche , Paris Sorbonne 1, 2005.
  14. François Ott, Pierre Vaast, « livre de grammaire : sixième en troisième», Hatier, 1991
  15. François Ott, Pierre Vaast, « livre de grammaire : Première en Terminale», Hatier, 1991
  16. Zave P., Jackson M., « Four Dark Corners of requirements Engineering », ACM Transactions on Software Engineering and Methodology, 1997
  17. Michael Jackson. «Problem Frames. Analyzing and structuring software development problems». Addison-Wesley, 2001
  18. Jean-Noël Gillot, « La gestion des processus métiers: l'alignement des objectifs stratégiques de l'entreprise et du système d'information par les processus», pp132-147, IDM’1997
  19. Alan W. Brown, Sterling Software et Kurt C. Wallnau, «the Current State of CBSE», IEEE Software, Software Engineering Institue, October 1998
  20. R. Atsa Etoundi, M. Fouda Ndjodo, « Human Resource Constraints driven Virtual Workflow Specification », IEEE SITIS pp 176-182, 2005.
  21. R. Atsa Etoundi, M. Fouda Ndjodo, « Feature- Oriented Business Process and Workflow », IEEE SITIS pp 114-121, 2005.
Index Terms

Computer Science
Information Sciences

Keywords

Business Process Modeling Requirement Engineering Software Component Requirement Relevancy Application Engineering Requirement representation