Bootcamp Project Requirements

You are required to design, build, and configure an application to complete Bootcamp. This is also
known as the Bootcamp “Final Project,” and this document outlines the project guidelines to which you
should adhere.

You will select a User Story that provides your client requirements. You must meet all requirements
outlined in the User Story, and in addition, your application must include some basic functionality
outlined below.

Minimum Application Features

Tempo

● At least one meaningful system news event with a record tag. Remember, don’t just do “News
for the sake of News.” News should be staged with meaningful messages for each actor with
both system and social posts. In your presentation, you should explain how you envision each
of your actors using news and what the benefit is to each of their roles.
● User Input Tasks
● At least one meaningful record
● At least one report with a minimum of two charts/graphs
● At least one meaningful Action in Tempo
● At least one meaningful Related Action
● At least one Site
Designer

● Groups
● CDT(s)
● Data store
● Queries
● Interface(s)
● Expression Rules
● At least two process models (with swimlanes)
● At least one sub-process model
● At least one gateway
● Appropriate security on all objects

Bootcamp Project Reqs 1/3

Extras (optional)

● Images
● Exception
● Escalation
● Comment/hazard
● Upload document (KC, folder)
● Link to document
● SAIL Recipe(s)
● Links
● Status Icons
● Task Report
● Mobile Use Case. Remember to describe the benefits of mobile overall and demo Appian’s
mobile capabilities as part of your presentation.

Project Assistance

In your project, as within Appian, we encourage you to work independently to find solutions and know
when to ask questions. For assistance with application components and/or troubleshooting, you should
first look to the product documentation followed by the Community Discussion board
(https://community.appian.com).

If you are unable to find a resolution, you should feel free to ask your colleagues. Bootcamp is meant to
be a collaborative environment, so you should regularly seek assistance from one another. If your
colleagues are unable to assist, you should ask your instructor for help.

Project Milestones

● Application Architecture: Planning for your application must be in the form of an Application
Architectural document, which must be submitted, reviewed, and approved by your instructor.
There is no deadline for your planning documents, but you should not begin building your
application until your proposed solution has been approved.

You should submit your proposal via email, google docs, post to news, etc. Any images or
attachments should be embedded in the doc. The application architecture must include:

1. Record planning - Identify the fields used in all CDTs for your application and create
mockups for your records
2. Process Model high level diagrams - This can be done on paper, in Appian, or using other
tools. This is only necessary for any processes with more than one actor

Bootcamp Project Reqs 2/3

 3. Report planning - Create basic mockups for all grids and graphs you would like to use in
a report
4. News - Identify the scenario for when a system news post will be generated, and
provide a sample message and viewers of the post

● Project Review: The Project Review typically happens on Wednesday afternoon before your
project is due. This is an opportunity for you to walk your instructor through your project so
that s/he can provide feedback on the application’s functionality as well as guidance for the
remaining project time.

● Project Submission: You should email your exported application to your instructor as an
attachment prior to Friday morning at 9am – no exceptions. Your instructor will not review any
projects submitted after that deadline.

Presentation

After you’ve had the opportunity to build an application independently, we invite your colleagues to
attend a short demonstration of your application. This is an opportunity for you to show off what you’ve
learned in just two short weeks! Your colleagues will have the opportunity to ask you questions about
your design decisions and provide feedback on how to think about and use Appian in the future.

Presentation Introduction

Your evaluators have been provided with a copy of your User Story, but it helps them to understand
your presentation if you introduce the actors. You are required to create ONE slide (and only ONE slide)
with the names of your actors and their role in the software. For example:

Actors

● Hilary – HR Manager, view reports

● Ian – IT Staff, provide new staff with equipment
● Nelley – New staff going through onboarding process

Presentation Logistics

Presentations typically begin at 9:00AM ET. The duration of the presentation is 20-25 minutes. Your
instructor will provide you with time and location details the day before your presentation.

Bootcamp Project Reqs 3/3