Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Credentials > Analyst > Flashcards

Analyst Flashcards

1
Q

appian do’s

A 
provide business value
limit time scope (rapid time deployment)
showcase software (UI)
solves pain point
lack of collaboration -> news tab
visibility -> interface
automation -> process models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

appian dont’s

A

complex integration
poorly defined requirements
large data transformation
replace system without improvements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

HR -> Form -> Database

A

bad idea, just moves data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Analyst

A 
Defines user roles and responsibilities
bridge between business users and app developers
make requirements clear for everyone
prototypes of records, reports, news
writes acceptance criteria
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Designer

A

Builds the application

  • configure records, reports, forms, processes
  • relational db schemas and views
  • deploy to test or production environments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

lead designer

A

Designs the solution that meets analyst requirements and performs at scale
- does everything designer does
- design solution that meets requirements of analyst
scalable, maintainable, intuitive application
- db integrations between appian and other systems

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

developer

A

Builds custom plugins in Java
- custom java plugins when no feature exists
functions
smart services
cdt
servlets
- setting embedded interfaces using js in external portal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

tester

A

Makes sure what a designer builds fuctions correctly to meet analyst requirements
- test scripts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

product owner

A

Prioritizes the backlog

- what will go on backlog, priorities, and when they will be delivered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

scrum master

A

Removes blockers and ensures that the team follows an agile methodology
using agile methodology, keeps ppl on track

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

definition of done

A

A user story should meet these criteria before it can be considered complete

  • unit tested
  • code review
  • documentation written
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

story points

A

A way to measure the complexity of work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

user stories

A

Describe a requirement from the user perspective
something user can do and covers functionality that needs to be built
as a i want to , because

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

backlog

A

Prioritized list of features that need to be delivered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

definition of ready

A

A user story should meet these criteria before it can be included in a sprint

  • story points assigned
  • story written
  • test plan defined
  • acceptance criteria defined
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

sprint review

A

Meeting held at the end of each sprint to go over what was accomplished

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

acceptance criteria

A

Defines the parameters of a feature and adds detail to a user story

  • each user story needs to meet
  • add details to basic user story
  • understand specific needs of end user
  • analyst responsible for writing acceptance criteria
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

sprint

A

Defined period of time when work gets done
1-4 weeks where work gets done (2 weeks for appian)
- created shippable product, no matter how basic it is

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

agile

A

small quick releases rather than delivering large application at the end
split project into smaller releases to deliver the most value

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

does appian work well with agile?

A

yes, works well with small iterative releases
- more stakeholder involvement
frequent custom demos
respond to changes more quickly

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

scrum

A

type of agile method
iterative process for managing applications

daily meeting, sprint review, sprint retrospective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

daily meeting (standup)

A

answer 3 questions
what did you do yesterday?
what are you doing today?
are there any blockers?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

sprint retrospective

A

happens after sprint review

allow team to discuss what they can improve to make next sprint productive

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

scrum roles

A

product owner
scrum master
developer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

example user story

A

as a student, i want to buy a parking pass, because i want to drive to school
- small enough to complete multiple in a single sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

epics

A
  • many stories and spam multiple sprints
  • represent larger requirement
  • doesnt need to be completed in single sprint
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

tools for agile

A

physical (whiteboards with backlog sprint dont on it)

jira
pivotal tracker
move cards
track velocity of team
	how much they can get done in a sprint
viewing record of what was done
reporting on the team metrics
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

sprint 0

A

plan and define logistics of the first application release

  • does not provide shipable product at the end
  • purpose is to identify project goals and define release plan
  • dont need to provide high level detail of user stories

important time to work together

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

actions that happen during sprint 0

A

chartering, sprint cadence, personas, story mapping, defition of ready/done, story sizing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

chartering

A
  • team given high level overview of what project is, why its being done, and the goals
  • end of sprint 0 should have a charter
31
Q

sprint cadence

A

how long sprints will be

32
Q

personas

A
  • define roles of users that will interact with application

- knowing users will drive user stories

33
Q

story mapping

A
  • break down high level requirements into smaller stories that can be more effecitvely prioritized
  • visual representation of project requirements
  • helps with logical order of stories that go into the backlog
34
Q

story sizing

A

points dont represent time it takes to get story done, just complexity and difficulty

35
Q

gathering requirements

A

user roles, defining data

36
Q

GR defining data

A
  • record (central object working around)
  • process built to affect the data
  • reports driven by what data you collect
    where:
    data come from 3 places (relational, internal, external)

what do you want to collect?
define data in process flows
store in temporarily or store it in db

37
Q

analyst mode

A

drawing out process flow and define what tasks should happen and what conditions to meet when there are decision points

38
Q

designer mode

A

configure process model diagram and make it work

39
Q

scirpt task

A

system work

40
Q

user input task

A

task users can complete

41
Q

gateways

A

divert process flow

42
Q

swimlanes

A

organize flow in logical manner

43
Q

what helps clarify a process?

A

swim lanes and annotations

44
Q

types of charts in reports

A

pie, bar, column, line, grids

45
Q

how to get data in reports

A

sql queries, expressions

46
Q

interfaces

A
  • maximum of 2 columns
  • buttons show up left or right
  • text black, error is red
  • rich text for style text
  • appian style guide for interface designers
47
Q

mockups

A

understand how user interact with interface (web or mobile)

editable grid better on desktop view than mobile

48
Q

news posts focus

A
  • make sure always targetted to specific group
  • shouldnt be log of everything that happened in system
  • use exceptional events/escalations to alert wider groups
  • can also target one person (loan request denied)
49
Q

when to use tempo

A

if user needs to make decision over applications

  • full access to news
  • start many actions
  • records/reports
50
Q

when to use sites

A

one application focus

  • actions/record lists/reports
  • news cannot be accessed in sites
51
Q

weapping up development

A

test based on acceptance criteria. analyst makes sure features properly tested (high impact functionality, bug fixes)

52
Q

who writes out the test cases

A

analyst since they are the expert on the team for business requirements

53
Q

end of sprint demo

A 
user story finished:
demo each functionality
ensure isntant feedback
changes can be picked up quickly
product owner or designers can give demo
54
Q

who are the business users

A

target audience for demo

make sure it goes over their needs

55
Q

tell show tell technique

A

tell them what they are going to see
show them what you told them they are going to see
then tell them what they just saw
keeps presenter on track

56
Q

how to keep on track during demo

A

use a script
demonstrate value at the beginning
start with best features first
capture their attention

57
Q

can users use platform after deployed?

A

yes, users should be involved in frequent demos to make sure they get what they want and need

58
Q

appian quick reference guide

A

help end users to understand appian interface

59
Q

choosing next project

A

make enhancements to previous projects,

objects in appian can be reused across applications

60
Q

decision designer

A

allow users to create test and manage business rules without using any code

61
Q

conditions

A

business rules defined

62
Q

what can decision be used for?

A

used for what process to start next or who to assign task to

63
Q

DD unique

A

all decisions need to be unique (no overlap)

only output single hit

64
Q

DD first

A

can be overlapping data, but return first one it hits

65
Q

DD rule order

A

can be multiple hits, output every single one in order they were hit

66
Q

naming for decision designers columns

A

useCamelCase

67
Q

choice label

A

what they see

68
Q

choice value

A

value represented by label

69
Q

appian object data types

A

process,folders,users,groups

objects that support an application

70
Q

naming for expression/decisions

A

PascalCase

71
Q

who can make decision designer

A

analyst or designers

72
Q

when you use a qeury rule or expression rule to define the value of a dropdown in your decision, rule executed during design time (in decision designer), does not get re-executed during runtime

A

True

73
Q

create grid image column

A 
a!gridImageColumn(
	label: "Category",
	field: "categoryId",
	data: a!forEach(
		items: index(local!datasubset.data, "categoryId", null),
		expression: a!documentImage(document: rule!VMR_DetermineCategoryIcon(categoryId: fv!item))
	)
)

Credentials (2 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions