Emakin uses an agile development methodology for program life cycle.
Agile development is an alternative to traditional project management where emphasis is placed on empowering people to collaborate and make team decisions in addition to continuous planning, continuous testing and continuous integration.
Agile development methodology tools are requirements analysis, design, implementation, testing and evaluation.
Requirements Analysis
6Kare engineering department involves communication with costumer (system users) to determine specific features expectations, resolution of conflict in requirement.
For example: When you decide to use the Emakin program 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.
Requirements analysis is most important than other life cycle steps because in 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
Software design is the process by which an agent creates a specification of a software artifact, intended to accomplish goals, using a set of primitive components and subject to constraints.[1]
In Emakin, developer use to pools, data model and forms for design to process.
Implementation
Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.
Design step and implementation step are at the same time working on process in Emakin.
Testing
Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customer at frequent intervals, working at a sustainable pace.
For to testing step in the Emakin, click on the related folder and your process then send(forward etc.) your task to inbox after that check to tasks in your inbox. If you see your task in inbox, that mean your process is working. If your process doesn't work; examine your pools, forms and data model in your process.
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 life cycle.
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.