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 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 future.
The following steps describe how to work agile methodology life cycle in the Emakin BPMS.
Requirements Analysis
Requirements analysis step starts to design process diagram in the Emakin BPMS. Task is created for each process step in the diagram and task links are created.Process diagram shows an application working digit.
Second step is data model design. Also data models define how data is connected to each other. Process is divided section, sub section and elements after to define features for each elements in the data model.
Design
Design step corresponds to form design in the Emakin BPMS. Form design section is connected data model of elements and to utilize elements for 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 form to user.
- If process run, you will see task in to your inbox. When you open task, you will see designed form.
- Enter information in to form, click action button.
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.