How should you design for multiple processes and forms, while minimizing repeated code?
You are tasked to build a large scale acquisition application for a prominent customer. The acquisition process tracks the time it takes is fulfill a purchase request with an award.
The customer has structured the contract so that there are multiple application dev teams.
How should you design for multiple processes and forms, while minimizing repeated code?
A . Create a Center of Excellence (CoE)
B . Create a common objects application.
C . Create a Scrum of Scrums sprint meeting for the team leads
D . Create duplicate processes and forms as needed
Answer: B
Explanation:
To build a large scale acquisition application for a prominent customer, you should design for multiple processes and forms, while minimizing repeated code. One way to do this is to create a common objects application, which is a shared application that contains reusable components, such as rules, constants, interfaces, integrations, or data types, that can be used by multiple applications. This way, you can avoid duplication and inconsistency of code, and make it easier to maintain and update your applications. You can also use the common objects application to define common standards and best practices for your application development teams, such as naming conventions, coding styles, or documentation guidelines. Verified References: [Appian Best Practices], [Appian Design Guidance]
Latest ACD300 Dumps Valid Version with 35 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund