Abstract: Companies that are in a constantly changing context need enterprise agility to create new ways of doing business. For this reason, companies are changing their organization to one based on business processes. That is, companies expect to achieve business agility through the agility of their business processes. However, process automation is focused on technology and not on business process strategy. Therefore, the agility of the business process is achieved in part of the business process cycle. Companies can improve enterprise agility if they achieve agility throughout the business process cycle. This paper proposes a framework for automating business processes - FABP, to respond to business requirements with agility. The FABP uses the enterprise integration approach, where the activities of business process automation processes exchange models and reconfigure models through development driven by models from start to finish. The FABP focuses on agility for the definition of the business process strategy. That is, in the ability to reconfigure the enterprise model to obtain the business process strategy model. In this way, improve agility throughout the business process cycle. The result of the reconfiguration of the enterprise model to obtain the business process strategy model is partial. Therefore, it is concluded that the FABP allows to improve the agility of the business process and therefore the business agility. The paper presents a FABP that allows to respond with agility to the enterprise requirements.Abstract: Companies that are in a constantly changing context need enterprise agility to create new ways of doing business. For this reason, companies are changing their organization to one based on business processes. That is, companies expect to achieve business agility through the agility of their business processes. However, process automation is focused...Show More
Abstract: In aerospace development and manufacturing environments, the cost of tests contributes a significant portion to the overall program costs. An extensive test program results in increased costs and unforeseen delays in fielding needed products and technologies. On average test represents approximately 30% of overall costs. The lack of a well thought out test strategy developed early and maintained through the entire program lifecycle results in high operational field failures, increased test equipment and unit production costs, delays in unit integration, redundant manufacturing tests, and poor transition into production as well as an increase in program risks. This paper describes the concept of an evolving program test strategy and the role of a Test Architect to achieve the goal of reducing test costs across the entire program lifecycle. Defining a test strategy results in clearly structured test plan and architecture, optimized test event planning and comprehensive test artifacts early in the program lifecycle. As a Subject Matter Expert, the Test Architect sets and drives the test strategy ensuring an overall test program is optimized and aligned across three phases of development: User Operations, Development and Production. To achieve a robust test strategy, the Test Architect uses a Socratic approach to question why a test needs to be performed, increasing the likelihood of executing a successful development test program, facilitating a seamless transition into production and optimizing the support of the deployed product.Abstract: In aerospace development and manufacturing environments, the cost of tests contributes a significant portion to the overall program costs. An extensive test program results in increased costs and unforeseen delays in fielding needed products and technologies. On average test represents approximately 30% of overall costs. The lack of a well thought ...Show More