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. The Emakin BPMS
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.