This page explains the life cycle of creating an application in the Emakin BPMS. Applications are created and run with agile methodology steps in the Emakin BPMS.
Agile methodology in the Emakin BPMS uses an adaptive approach where there is no detailed planning and there is clarity on future tasks only in respect of what features need to be developed. There is feature-driven development and the Emakin BPMS adapts to the changing product requirements dynamically. The product is tested very frequently, through the release iterations, minimizing the risk of any major failures in the future.
The following steps describe how to work the agile methodology life cycle in the Emakin BPMS.
Requirements Analysis
The requirements analysis step starts with to design process diagram in the Emakin BPMS. A task is created for each process step in the diagram and task links are created. The process diagram shows an application working digit.
The second step is data model design. Also, data models define how data is connected to each other. The process is divided into sections, sub section, and elements to define features for each element in the data model.
Design
The design step corresponds to form design in the Emakin BPMS. The form design section is a connected data model of elements and utilizes elements to create form content.
Implementation and Testing
Implementation and testing steps are actualized at the same time in the Emakin BPMS. The following steps explain how to test and implement process.
Send the form to the user.
If the process runs, you will see the task in your inbox. When you open the task, you will see the designed form.
Enter information into to form, and click the action button to move to the next step in workflow.
Evolution
Evolution step is last loop structure in the Emakin BPMS. When faced any process problem, it is solved by using life cycle steps without stopping the process.