Configure and Build System
One person's magic is another’s engineering. Supernatural is a null word.

After the requirements or features that the business has identified and approved, Cloud Development delivers the process and governance through the build phase, whether using Agile or Waterfall methodologies. You can define both functional and technical specifications, conversion mappings, and monitor progress, like burndown, velocity and budget consumption. There is an automatic and comprehensive tractability matrix for every step with detailed versioning so you will always know who did what, when and why.



Migrate Code and Objects

What is it: Track every Object that you need to migrate from current version of the system to the new version. Assign estimated hours to objects and then review progress in burn-down charts.

Why do I need it: Provides real-time progress and complete traceability even when migrating 1,000's of objects.

Learn More

Specify New Functionality

What is it: Write specifications directly in CCP where you are one click away, and linked to, the original Requirement, approved Alternative and all other relevant traceable content required to provide accountability.

Why do I need it: As a critical link in the development life-cycle and traceability matrix, writing specifications in CCP instead of MS Work provides powerful functionality.

Learn More

Reports, Interfaces, Concersions and Enhancements (RICE)

What is it: RICE is an acronym for Reports, Interfaces, Conversions and Enhancements, work that requires development, either through Agile or Waterfall methodologies. Track and manage participants, hours, incidents, estimates, approvals and every aspect of the development life-cycle.

Why do I need it: Allows for excellent team collaboration and communication, especially if you are using off-shore resources. By tracking work, re-work and incidents, CCP provides complete developer accountability, effectiveness, accuracy and cost.

Learn More

Sprints

What is it: CCP provides Sprints for two areas of team work during a project. The first is around defining configurable system functionality for the product modules and the second is for development work. Group configuration options and features for development into time slices and manage discreetly.

Why do I need it: Ensures that incremental progress is made for easier management and rectification hence mitigating against schedule slippage and ensure incremental value is being added on a regular basis.

Learn More

Data Conversions

What is it: Map legacy data to specific tables and columns in the new system. Define specific rules for mapping and converting, add notes, assign as a Cut-Over Task, and build a library of old to new system mappings for future use.

Why do I need it: Provides a complete audit trail of all changes, allows multi-user access and extensive security for sensitive data, like Payroll.

Learn More

Implement ERP Security

What is it: Designed to help you track the identification, creation and testing of system security roles. Provides an electronic approval signature on roles so you have complete traceability and accountability.

Why do I need it: Ensures granular level security and facilitates SOD through third party solutions.

Learn More

Package and Deploy Code

What is it: Used to request a package build. Identify projects and objects. Also allows you to define unlimited promotion schedules, like one for test data refresh, another for code promotion to the testing environment and yet another to baseline the testing environment ready for a new class to begin.

Why do I need it: Provides a complete audit trail of every object promoted from Development to Test to Production environments without having to be a Technical guru.

Learn More


© Copyright 2017, Ascendive Inc All rights Reserved