This page explains the life cycle of creating an application in the Emakin uses an agile development methodology for program life cycle. Agile development methodology tools are requirements analysis, design, implementation, testing and evaluation.
Requirements Analysis
6Kare engineering department involves comunication with costumer (system users) to determine specific features expectations, resolution of conflict in requirement.
For example: When you decide to use the Emakin programme than 6Kare engineering of department staffs will come to company(your office) and analysis documentates, comunicate with users and will keep a important of knowledge.
Requriements analysis is most important than other lifecycle steps because ın there the engineering department staffs do which options are necessary for programme working. So The costumer should say them all of idea to us.
Design
Engineering department of engineers will analys of requirements analysis documentation after they will choose needful knowledge inside from documentates and reports than do to plan and create to programme.
Costumer may countinue giving advice that step for the changeable things.
Implementation
Developer use to pools, data model and forms options in Emakin for design to process.
Testing
Testing are beginning after implementation step on Emakin. Programmers check and control when the indeks are working on Emakin than same time our achive(idea) find all of systemical mistakes before the use costumer to the Emakin.
After that established is Emakin program on by costumer computers than support staffs will teach how users handle.
Evolution
When costumer users handle after sometimes they may see some of problem in there that time 6Kare engineering department will help for solve the problems.
Other way costumer may need to new design on Emakin and programmer will do a new version than follow again four steps in lifecycle.
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.