The various project templates and different kinds of work output can be edited through the administration function only. Please see the administration section below for more details.

Once your project is created, you will start seeing items in your To Do list:

Click on any of these tasks to work with them. At this stage, you can update the details, but most importantly, you can add activities. Activities define the flow of a task and allows the communication of requirements between users of the console.

For example:

Once the user saves this activity, the status of the task updates:

The project sponsor and owner can now see that something has been actioned. The details of the activities against a task shows up in the task history.

If a task requires multiple interactions, the assigned user of a task can provide details for the next step and re-assign the task to another user who will now see it in their To Do list.

Closing a task is as simple as clicking the Close button against the task. Any sub-tasks still open will also be closed.

It is good practice (but not required) to provide an activity note when closing a task:

Once closed, the status of the task changes:

And the task is removed from the To Do list.

You can re-open a task that was accidentally closed through the project.

Once a project is completed, it should be closed. Closing a project results in any associated tasks also being closed and the project is listed with a strike-through line in the administration tree:

At this stage, clicking on the project text no longer has any effect. To get back to a closed project (to edit or reopen it), you must click on the little image in front of it.

To create a new project, click on Projects in the administration tree (or select Project Management from the start menu if you are using the portal interface).

The key to using this interface is to work from top to bottom. Start by entering a meaningful project name and a good description as shown in the example below:

Then decide when the project is due:

The default due date is always 7 days from the project date. You can change this to suit.

Next you need to decide if you require a new repository or you can use an existing one. If you choose to use the project name for a new repository, it will automatically be created when you finish the project. You can also select additional repositories to include:

If you choose to use an existing repository, then nothing will be changed.

Now pick all the users assigned to the project. You can of course change this later but making sure that you have included any user even peripherally involved with the project will make your project creation easier.

The next step is to assign the project sponsor. The sponsor is typically the business owner in charge funding the delivery of the project. By providing the sponsor with a user name and credentials, the sponsor will be able to follow up on the status of the project without contacting any person directly:

If you don’t have a specific sponsor, you can just leave your own user name.

In addition to users actually able to sign into your console, you may also have other stake holders (such as external providers of hardware). To ensure that you can assign tasks to these providers, you can enter the names of stake holders:

We now have all the key information about the people involved in the project and it is time to create the tasks. To make this part easy, select a template option in the project assistant:

This will instantly create the most common tasks associated with that template as shown:

You can at this point change the desired tasks and assign users before actually creating the project:

If you need to add further tasks or remove tasks, you can do so by using the plus and minus buttons on the far right of the task list.

Once you have all your tasks ready, click on Create.

Your project is now created:

You will notice the status of the tasks differ. Tasks with a red exclamation mark have dependencies on other tasks that stops them from being actioned. Items with a yellow question mark have not yet been started.

Other icons you will see is a yellow walking man for tasks that are in progress and a green tick for tasks that have been completed.

At this stage you should review the due dates for each task as well as provide more information if required. You do this by clicking on the link for the task:

For these “headline” tasks, you can now create sub tasks (or in time, the assigned user can do so also):

Once completed, click on save to update the task details and create the sub tasks:

Composable Architecture Platform is designed for working in an enterprise environment and we recognize that deploying a project under such circumstances is far more complex than simply writing rules and making the application work.

At the same time, the anatomy of an enterprise project is reasonably standard across different project and enterprise types. Needs that involve other departments (such as firewall rules, security reviews, user acceptance testing and so on) are usually known quantities that simply needs to be addressed early to ensure the on-time delivery of a solution.

Composable Architecture Platform assists with reminding you and your co-workers about tasks that needs to be completed. You can also assign a project sponsor who will be able to log in and see the status of projects that is sponsored. This improves visibility and cuts down on unnecessary project status meetings.