You have 5 applications on your Appian platform in production. Users are now beginning to use multiple applications across the platform, and the client wants to ensure a consistent user experience across all applications You notice that some applications use rich text some use section layouts, and others use box layouts. The result is that each application has a different color and size for the header. What would you recommend to ensure consistency across the platform?
Correct Answer: B
Explanation The best way to ensure consistency across the platform is to create a rule that can be used across the platform for section headers. This rule can be created in the common application, and then each application can be updated to reference this rule. This will ensure that all of the applications use the same color and size for the header, which will provide a consistent user experience. The other options are not as effective. Option A, creating constants for text size and color, and updating each section to reference these values, would require updating each section in each application. This would be a lot of work, and it would be easy to make mistakes. Option C, creating one rule for each application, would also require updating each application. This would be less work than option A, but it would still be a lot of work, and it would be easy to make mistakes. Option D, creating a rule in each individual application, would not ensure consistency across the platform. Each application would have its own rule, and the rules could be different. This would not provide a consistent user experience. Best Practices: * When designing a platform, it is important to consider the user experience. A consistent user experience will make it easier for users to learn and use the platform. * When creating rules, it is important to use them consistently across the platform. This will ensure that the platform has a consistent look and feel. * When updating the platform, it is important to test the changes to ensure that they do not break the user experience.
Question 12
You are the lead developer for an Appian project, in a backlog refinement meeting You are presented with the following user story. As a restaurant customer. I need to be able to place my food order online to avoid waiting in line for take out.' Which two functional acceptance criteria would you consider 'good'?
Correct Answer: B,D
Explanation Functional acceptance criteria are the conditions that a user story must satisfy to be accepted by the user or stakeholder. They should be specific, measurable, achievable, relevant, and testable. In this case, two functional acceptance criteria that would be considered 'good' are: * The user will receive an email notification when their order is completed. This is a specific, measurable, achievable, relevant, and testable criterion that describes a feature that the user needs to be informed of their order status. * The user cannot submit the form without filling out all required fields. This is a specific, measurable, achievable, relevant, and testable criterion that describes afeature that the user needs to provide valid and complete information for their order. The other options are not as good. Option A, the user will click Save, and the order information will be saved in the ORDER table and have audit history, is not a functional acceptance criterion, but rather a technical implementation detail that is not relevant or visible to the user. Option C, the system must handle up to 500 unique orders per day, is not a functional acceptance criterion, but rather a non-functional requirement that describes a performance or quality attribute of the system.
