Test1 Flashcards

1
Q

Explain SDLC

A

Systems development life cycle, a framework defining tasks performed at each step
in the software development process

Planning
Analysis
Design
Implementation

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

SDLC Planning

A

Understanding why an information system should be
built and determining how the project team will go about
building it
- project initiation
- project management

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

Analysis SDLC

A

Who will use the system, what will the system do, where and when will it be used

  • Analysis strategy
  • requirements gathering
  • system proposal
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Design SDLC

A

How the system will operate in terms of infrastructure;
the user interface; the specific programs, databases,
and files

  • Design strategy
  • architecture design
  • database and file specification
  • program design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Implementation SDCL

A

Build the system

  • system construction
  • installation
  • system support
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is traditional

A

SDLC Methodology
Structed and plan driven, sequential and phased approached. Each phase depends on the outcome of the previous phase and runs
sequentially

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

what is agile

A

Iterative methodology that incorporates a cyclic and collaborative process.

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

advantages and disadvantages of traditional

A

Advantages
* Discipline with tangible outputs at the end of each phase
* Control with a timeline
Disadvantages
* Lack of flexibility— little room for change once a phase is deemed
complete

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

advantages and disadvantages of agile

A

Advantages
* embraces change/flexible
* constant feedback
Disadvantages
* harder to control the timeline with constant change to system

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

What is SCRUM

A

An iterative and incremental framework for developing,
delivering, and sustaining software products.

Sprint is the basic unit of development iteration in Scrum

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

SCRUM team

A

Master
Accountable for establishing Scrum as defined in the Scrum Guide

Product owner
Accountable for maximizing the value of the product resulting from the work of the Scrum Team and for effective Product Backlog Management

Developers
creating a plan for the sprint, instilling quality by adhering to a definition of done, adapting their plan toward end goal

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

SCRUM artifacts

A

product backlog
breakdown of work to be done and contains an ordered list of requirements that the team maintains for a system/product

spring backlog
subset of items from the product backlog intended for developers to address in the upcoming sprint

increment
potentially releasable output of the sprint that meets the sprint goal

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

SCRUM events

A

Sprint Planning
develop goal, select product backlogs, and form sprint backlog

Daily Scrum/Sprint Review
- meeting to inspect progress
- presents completed work to stakeholders

Sprint Retrospective
Team - reflects and inspects past sprints, and identities improvement

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

Explain the three levels of SAFe

A

Scaled Agile Framework
A framework for extending process to larger-scope items in parallel work streams, over longer time increments, across multiple delivery teams

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

Value stream

A

deliver the value to the business or customer.

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

ART (agile release train)

A

A group of Agile teams brought together to deliver value

17
Q

program increment

A

A timebox in which an ART delivers incremental
value, typically 8 – 12 weeks long

18
Q

RTE

A

Agile Release Train engineer
Continuous inter-team coordination and status reporting

19
Q

Innovative and planning iteration

A

dedicated time for planning
and learning, final system verification, validation, and documentation for PI

20
Q

what is a stakeholder

A

A stakeholder is any person or organization,
who can be positively or negatively impacted
by, or cause an impact on the actions of a
company, government, or organization.

21
Q

Identify stakeholders using the onion model

A

From inside to outside

the product
the system
the containing system
the wider enviornment

22
Q

Innermost ring, the system

A

Normal operator
maintenance operator
support operator

23
Q

middle ring, containing system

A
  • functional beneficiary(who gets the system)
  • interfacing system owners
  • purchaser
24
Q

Outer ring, the wider environment

A

financial beneficiaries (who gets the financial gains of the product)
- politician
- champion
- sponsor
- negative stakeholders
- regulator
- public

25
Q

Three approaches to discover requirements

A

from individuals
from groups
from things

26
Q

requirements from individuals

A

interview
- direct way to find what stakeholders want

observation
- observing stakeholders to understand the working environment

27
Q

requirements from groups

A

bring together a group of people to uncover
requirements quickly

define mission
planning
discover requirement
document
validate finding

28
Q
A
29
Q

What is DT

A
30
Q

Explain the DT process (steps) in the IDEO model

A
31
Q

Develop a use case diagram for a given system

A
32
Q

Develop a use case narrative for one use case

A
33
Q

What is use case and user stories

A
34
Q

Discuss the implications of the three figures (next 3 slides) on the importance of system analysis and design.

Pie Chart

A

Maintenance cost >60% of the total cost
Good requirements (and design) –> lower maintenance cost later

35
Q

Discuss the implications of the three figures (next 3 slides) on the importance of system analysis and design.

Line Chart

A

Cost to fix a error (or make a change) increase exponentially over time
The later to make change, the more expensive
Good requirements –> less later changes –> lower overall cost

36
Q

Discuss the implications of the three figures (next 3 slides) on the importance of system analysis and design.

Bar Chart

A

It is easy to introduce errors and difficult to identify and remove the errors in the analysis and design phases.
More than 50% of errors are introduced in the requirements and most of them pass to the operations (in use) phase, when they are very expensive to fix.