01787nas a2200229   4500000000100000000000100001008004100002260001200043653004600055653002000101653002700121100003000148700003000178700002500208700002800233245012400261856009800385300001000483490000600493520104400499022001401543       2013                            d  c06/201310aBusiness Process Modeling Notation (BPMN)10aCode Generation10aProcess Transformation1 aJuan Manuel Cueva-Lovelle1 aCristina Pelayo G-Bustelo1 aJaime Solis-Martinez1 aNatalia Garcia-Menendez00aBPLOM: BPM Level-Oriented Methodology for Incremental Business Process Modeling and Code Generation on Mobile Platforms  uhttp://www.ijimai.org/journal/sites/default/files/files/2013/06/ijimai20132_2_2_pdf_13432.pdf  a13-270 v23 aThe requirements engineering phase is the departure point for the development process of any kind of computer application, it determines the functionality needed in the working scenario of the program. Although this is a crucial point in application development, as incorrect requirement definition leads to costly error appearance in later stages of the development process, application domain experts’ implication remains minor. In order to correct this scenario, business process modeling notations were introduced to favor business expert implication in this phase, but notation complexity prevents this participation to reach its ideal state. Hence, we promote the definition of a level oriented business process methodology, which encourages the adaptation of the modeling notation to the modeling and technical knowledge shown by the expert. This approach reduces the complexity found by domain experts and enables them to model their processes completely with a level of technical detail directly proportional to their knowledge.  a1989-1660