The premise behind 'third wave' Business Process Management (BPM1) is effective support for change at levels. Business Process Modeling (BPM2) notations such as BPMN are used to effectively conceptualize and communicate process configurations to relevant stakeholders. In this paper we argue that the management of change throughout the business process model lifecycle requires greater conceptual support achieved via a combination of complementary notations. As such the focus in this paper is on the co-evolution of operational (BPMN) and organizational (i*) models. Our intent is to provide a way of expressing changes, which arise in one model, effectively in the other model. We present constrained development methodologies capable of guiding an analyst when reflecting changes from an i* model to a BPMN model and vice-versa. 2 ) notations such as BPMN are used to effectively conceptualize and communicate process configurations to relevant stakeholders. In this paper we argue that the management of change throughout the business process model lifecycle requires greater conceptual support achieved via a combination of complementary notations. As such the focus in this paper is on the co-evolution of operational (BPMN) and organizational (i*) models. Our intent is to provide a way of expressing changes, which arise in one model, effectively in the other model. We present constrained development methodologies capable of guiding an analyst when reflecting changes from an i* model to a BPMN model and vice-versa.

No abstract

The research aims to develop an enhanced MD5 algorithm for the secure web development. The existing MD5 algorithm has many weaknesses that makes it vulnerable to different attacks such as brute force, rainbow table, birthday, dictionary etc. Despite these, the MD5 algorithm is still used in different applications, security protocols and even in the transmission and storage of digital data for verification, integrity and security of data by using checksum. The research focuses on mitigating the weaknesses inherent in the existing MD5 algorithm to secure web application and maintain data integrity and security. The research documents the proposal and implementation of an enhanced MD5 algorithm by varying its length and using a key to hash the data into its cipher form.

No abstract

The fundamental step in systems implementation is requirements gathering. This step is categorized into early phase requirements elicitation and systems modelling. Requirement elicitation involves gathering stakeholders' intentions, goals, rationale and organizational context that can be modelled with agent-oriented conceptual modelling such as i*. On the other hand, systems' modelling is portraying abstract version of interaction among interrelated components within a whole system via UML languages such as Use Case diagrams. The co-evolution of Agent-Oriented conceptual model such as i* and Use Case Diagrams aims to close the gap of capturing organizational requirements and system requirements. However, changes made in i* must be reflected in the Use Case diagram to ensure consistency in requirements. Therefore, this paper proposes a methodology supporting the co-evolution of these two otherwise disparate approaches in a synergistic fashion.