The diagram below represents the eSpace life cycle.

In this diagram you can easily identify two different cycles: the personal development cycle and the team development cycle. The personal development cycle endures while the developer is designing the eSpace and running it in its Personal Area, protected from the rest of the developers. The team development cycle, on the other hand, is a more complex phase where developers collaborate to publish a single version of the eSpace to be available to all developers and end-users.

If you are working in a single-developer environment you can also take advantage of both cycles, since you might want to experiment and evaluate the eSpace without interfering with the version that end-users are using, therefore running it in your Personal Area. There are performance benefits in the development process if you decide to run the eSpace in your Personal Area.

Personal cycle

The personal cycle allows each developer to design his/her own eSpace and experiment with it in their own Personal Area. The Personal Area is an area stored in the Platform Server you are connected to and with reserved rights concerning its management.

The Personal cycle, fully supported by Service Studio, is divided into the following steps:

    1. Create or open the eSpace. See how to Create an eSpace or Open an eSpace;

    2. Design the eSpace in your workspace. See how to Design the eSpace;

    3. Run the eSpace in your Personal Area. See how to Run the eSpace;

    4. Collect the feedback from this personal test and do one of the following:

      1. Return to step 1.

      2. Publish your eSpace, making it available to all users, as explained below in the Team cycle.

Once you have run the eSpace in your Personal Area, you can test it. See Execute the eSpace in Personal Area.

Team cycle

The team cycle allows developers to publish eSpaces in the Public Area, which is an area stored in the Platform Server you are connected to, available for all developers and users.

The Team cycle, fully supported by Service Studio, is divided into the following steps:

    1. Create or open the eSpace. See how to Create an eSpace or Open an eSpace;

    2. Design the eSpace in your workspace. If you are working in a multi-developer scenario, each developer will design components or parts of the application. See how to Design the eSpace

    3. If you are working in a multi-developer scenario, aggregate the developer contributions in a single eSpace by working in teams.

    4. Publish the eSpace in the Public Area. See 1-Click Publish.

See Also

About Public Area | About Personal Area | Run the Personal Area | 1-Click Publish | About Working in Teams