Introduction
Cloud-based PAAS and SAAS products are popular platforms for multi-tenant enterprise deployment and usage. The platform has features to design and deploy new applications runtime from the web given the application metadata - user interface, process workflow, business services, and the database schema. The application has the capability to be upgraded using OSGI based component versioning, registry, and deployment model. The business drivers are captured in the Business Driver / Process impact matrix. Customer Service level agreements and time to market objectives are captured. The assessment of components of Infrastructural Architecture as per their Business Value and Technical Quality is performed. Business, Technology & Service Drivers will be prioritized. Typically, three options are provided to meet immediate market needs, middle-ground approach and long term market need. Enterprises go for parallel paths once the core is built to address immediate market needs and then the long term market needs. SLAs for availability are typically related to application availability while upgrades happen to the current version. A hot deploy approach switch will be available to have parallel deployed nodes and the switch can happen to back up while the primary is upgraded. The product will have support the following deployment models-Hosted Solution- SAAS and Packaged Implementation on an in-house private cloud.
Executive Committee, Steering Committee ad Project Management Office will be created for the governance of the project. The project plan will be created with milestones, well-defined scope, planned tasks, resource plan, resource chart, and project agreement for two options in parallel starting with the core. The financial Plan and project break down will be shared with the customer for review and sign off by the client. Project teams were selected and roles & responsibilities were assigned to the team members for core and two parallel options. Staged implementation based on application and high functional priority will be planned in the initial iteration. Iterative reworking of the entire codebase was done to meet long term componentization and productization goals. Medium priority and low priority functionality were planned for the next iterations. The core functionality will be built lightweight to start with to meet the needs of the immediate market needs option and the core will be evolved to longterm market needs in the second option plan.
Constant checkpoints and feedback will be planned between customer and project teams. Risks will be addressed in the plan to eliminate, moderate, or mitigate all significant internal and external risks posed to the deliverables, quality, schedule, and budget of this project in a cost-effective manner. Risks were identified very early. The risk assessment will be done for technical, project, and resource risks. The mitigation strategy was addressed for each risk. Effectiveness was assessed during the project and exposure to risk was reassessed. The project structure will be finalized in terms of scope and resources. The scope of implementation/deliverables will be finalized before the creation of the Communication plan, resource plan, change management plan, risk management plan, configuration plan, acceptance plan, quality plan, and project completion plan. Assumptions/ constraints were documented for both options and core build plans. An overall understanding of portfolio-architecture will be gained during the architecture phase. Technical deployment models, assessment matrix, AS-IS architecture will be created. The technical quality and business value of each application in the portfolio were assessed. Interviews will be conducted with business users. Legal and Regulatory impacts were documented. Business and Technology issues were addressed for providing quality data management. Information architecture and a complete data model will be created for T0-BE architecture.
Platform as a service products will be designed and developed with features such as application design, forms design, binding the forms to the services. The services will have the capability to handle file-based, JMS based, web services-based, and database integration. The typical features of the PAAS/SAAS platform are customization functionality – the ability to customize certain aspects of the platform like Screens, Data Fields, Workflows, etc. , Workflow, Notifications ability to send notifications in the form of emails or other formats based on certain rules, Business Rules –functionality to define business rules,.Reporting, Search, Document Management - the ability to support core document management features, integration with third-party document management software, Scheduler – allow for admin users to schedule periodic actions, Calendar Functionality – support scheduling calendar events, internationalization – support for multiple languages and locales. Custom Data features will be created with a custom field, validation for custom fields, custom action on entities, custom trigger. Typical custom screens functionality will consist of custom forms, custom entity view screens, custom entity search screens, custom entity lists, custom composite screens, and custom menus.