Analysis Flashcards

Consists the 3 parts; UML, business analysis and requirement analysis (60 cards)

1
Q

What is analysis in business?

A

It’s often used to identify problems or opportunities, evaluate options and make informed decisions

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

What is the SWOT analysis?

A

It’s a strategic planning technique used to evaluate the strengths, weaknesses, opportunities and Threats involved in a project a business venture

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

What is root cause analysis?

A

A methodical approach used
to identify the underlying cause of a problem

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

What are the 4 different root cause analysis methods covered in class?

A
  • 5 whys
  • Fishbone Diagram
  • Pareto Chart
  • FMEA
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the 5 whys method?

A

repeatedly asking “why?” to
uncover the underlying causes
of a problem.

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

What is the Fishbone (Ishkawa) Diagram?

A

It identifies many possible causes for an effect problem.

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

What is the Pareto rule?

A

A generalized phenomenon that
highlights uneven power distribution
“80% of the issues are determined by 20 % of the causes.”

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

What’s FMEA?

A

A Structured & proactive method
used to identify and asses potential failures in a product/service

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

What does FMEA stand for?

A

Failure Modes & Effects Analysis

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

What’s the process for creating an FMEA?

A

1) Identify the process/subsystem to analyze
2) Identify potential failure
3) Determine the RPN (Severity x Occurrence x Detention)
4) Prioritize the failure models based on the RPN, and identify the high-priority failure models
5) Identify & implement actions to reduce or eliminate the high-priority failure modes
6) Periodically review and update the FMEAS as needed to ensure continuous improvement &, effectiveness in addressing the identified failure modes.

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

What is an Agile environment?

A

A workspace or project setting that embraces the principles of agile methodology

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

What is an agile methodology?

A

A method that emphasizes flexibility, collaboration iterative progress & quick adaptation to changes

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

What is a domain model?

A

It’s a sketch of the elementary entities of the system & the relationship between them. This doesn’t rely on a specific software (platform independent)

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

What does a domain model consist of?

A
  • Conceptual objects
  • Attributes
  • Relationships & Multiplicity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are relationships in a domain model?

A

It’s a link or association between 2+ entities

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

What are aggregations & compositions?

A

They are subsets of association

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

What’s an aggregation?

A

It’s a relationship where the child can exist without the parent

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

What’s a composition?

A

A relationship where the child cannot exist without the parent

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

What’s a requirement?

A
  • A need for automation coming from the business’ perspective
    OR
  • A demand for expected behavior & quality required from the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What focus a “business perspective” requirement does have?

A
  • The business request
  • The user request
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What can a “system perspective” requirement be?

A
  • Functional
  • Non-functional
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is a business requirement?

A

A high-level statement that defines why a project or a system is needed

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

What are the key traits of a business requirement?

A
  • Strategic: Tied to long-term goals
  • Non-technical: expressed in business terms, not system features
  • Scope setting: Guides which user & system requirement are relevant
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What are the questions that a Business requirement answer?

A
  • WHY is this initiative important?
  • WHAT business problem does it solve
  • WHAT value will it create?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What is a user requirement?
It defines what the user needs from a system to achieve their goals expressed from their POV
26
What are the key traits of a user requirement?
- User-centric: Focused on the users needs, not the system implementation - Actionable: Describes a task/process - Non-technical: Uses plain language
27
What are the questions that a user requirement answers?
- WHO the user it - Why it matters to them - WHAT action they want to perform
28
In what form can the answers of a user requirement look like?
It can be in a form of a user story or user cases
29
What is a user story?
"As a user, I want to do [X] so that I can benefit [Y]"
30
What are user cases?
A step-by-step guide on how a user achieves a goal
31
What is a Functional requirement?
It defines a specific behaviors or capabilities a system must have to fulfill user a business needs
32
What are the specificities of a technical requirement?
- Actions: What the system must perform - Features: Discreet functionalities - Inputs/Outputs: How the system responds to user action or data
33
What are the key traits of a technical requirement?
- System Centric: Focused on software behavior, not user goals - Testable: Must have clear pass/fail criteria - Implementation-Agnostic: Describes what and not how
34
What are Non-functional requirements?
It defines specific behavior or capabilities a system must have to fulfill user and business needs
35
What are the specificities of a non-functional requirement?
- Quality Standards: performance, security, usability, etc. - Constraints: Technical or operational limits - Measurement criteria: Quantifiable metrics
36
What are the key traits of a non-technical requirement?
- System-wide: applies globally, not to individual features - Measurable: Defined with metrics - Often Implicit: Divided from user expectations
37
What are the 6 steps for an Agile flow?
1) Define business requirements 2) Discover User requirements 3) Create user stories 4) Derive Functional requirements 5) Identify non-functional requirements 6) Sprint planning & execution
38
What does a user story always consists of?
- A short description - An oral agreement - An acceptance criteria
39
What is the INVEST model?
A set of criteria used to evaluate the quality of a user story in agile movement
40
What does INVEST stand for?
- Independent - Negotiable - Valuable - Estimable - Small - Testable
41
What the "Independent" stand for in the INVEST model?
The story can be developed & delivered without relying on other stories
42
What the "Negotiable" stand for in the INVEST model?
The story's scope is flexible and open to discussion
43
What the "Valuable" stand for in the INVEST model?
Delivers a clear value to the user to the business
44
What the "Estimable" stand for in the INVEST model?
The team can estimate the effort request
45
What the "Small" stand for in the INVEST model?
The story is small enough to complete in a sprint
46
What the "Testable" stand for in the INVEST model?
The story has a clear acceptance criteria to verify completion
47
What are the steps that consist an agile process?
1) Gather User stories 2) Refine User stories 3) Estimate Effort 4) Prioritize the backlog
48
What is a backlog?
A list of tasks, features or items to be completed as part of a larger product roadmap
49
Who gathers user stories in the agile process?
The product owner collaborates with the stakeholders
50
How do they gather user stories in the agile process?
They conduct interviews, surveys, or workshops & document needs as user stories
51
What is the output from gathering user stories in the agile process?
Raw stories are added to the product backlog
52
Who refines user stories in the agile process?
The PO, Scrum master, and the dev team
53
How do they refine user stories in the agile process?
They apply INVEST criteria & split the large stories in smaller ones
54
What is the output from refining user stories in the agile process?
Priortized, well-defined stories in the backlog
55
What's the technique used to estimate the effort in the agile process?
Playing poker: Uses the Fibonacci sequence to assign in the backlog.
56
Why do we estimate the effort in the agile process?
It ensures realistic sprint commitments
57
What's the method used to prioritize the backlog in the agile process?
MoSCoW prioritization
58
What is the MoSCoW prioritization? (what does it stand for)
- Must have - Should have - Can have - Won't have
59
Who prioritizes the backlog in the agile process?
The product owner
60