ITKE 083 - PROJECT MANAGEMENT

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/41

flashcard set

Earn XP

Description and Tags

SAS

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

42 Terms

1
New cards

Full meaning of DFD

Data Flow diagram

2
New cards

This is a diagram that is being used frequently in a software design, It visually represents the flow of data through out processes in a given system

Data Flow diagram

3
New cards

This shows the kind of information that will be input to and output from processes as well as where the data will be stored.

DFD

4
New cards

The purpose of ______ is to view systems as a whole with their scopes and boundaries while it illustrating the movement of information between components.

DFD

5
New cards

DFD focuses on the ______ of data, not the _____ flow

Flow

Process

6
New cards

This component of DFD transforms incoming data flow into outgoing data flow. Represented by a circle or a rounded rectangle.

Process

7
New cards

This component of DFD is a place where data is held temporarily. Represented by two parallel lines.

Data Store

8
New cards

This component of DFD is the source or destination of a data, outside the system. Represented by a rectangle.

External Entity

9
New cards

This component of DFD the movement of data between components. Represented by a line with an arrow.

Data Flow

10
New cards

This is the highest level overview of the entire system, It Illustrates the system's relationship with external entities.

Level 0

11
New cards

This breaks down the Level 0 diagram. Includes more details, such as a system's main functions.

Level 1

12
New cards

This level dives deeper into a specific function from Level, It depicts how data flows within that main process.

Level 2

13
New cards

Another name for Level 0

Context DFD

14
New cards

This level represents how the data enters and exits the system, where it is stored, and how the basic processes convert it from one form to another.

Level 1

15
New cards

List the steps that all programs must go through

  1. Conception

  2. Requirements gathering/exploration/modeling

  3. Design

  4. Coding and debugging

  5. Testing

  6. Release

  7. Maintenance/software evolution

  8. Retirement

16
New cards

The two main types of methodologies

  1. Traditional plan-driven models

  2. Agile development models

17
New cards

This is a series of processes used in developing a software these are defined phases that describes the life cycle of the software until its completion.

SDM- Software Development Methodologies

18
New cards

Teams use this methodology to minimize risk (such as bugs, cost overruns, and changing requirements) when adding new functionality.

Agile Development methodology

19
New cards

In this methodology teams develop the software in iterations that contain mini-increments of the new functionality.

Agile methodology

20
New cards

3 pros of agile methodology

Software is released in stages or iterations.

Early defect detection and alignment of expectations.

User benefits is frequent, incremental improvements are delivered sooner.

21
New cards

These are set of practices that support organizational culture. They center on organizational change that enhances collaboration between the departments responsible for different segments of the development life cycle, such as development, quality assurance, and operations.

DevOps Development Methodology

22
New cards

This is a well-known plan-driven methodology that consists of sequential phases (requirements, design, implementation, verification, maintenance) focusing on distinct goals.

Water Fall Methodology

23
New cards

This is a condensed development process that produces a high-quality system with low investment costs.

Rapid application development (RAD)

24
New cards

The rapid application development method contains four phases

Requirements planning

User Design

Construction

Cutover.

25
New cards

This agile methodology is a visual approach to Agile. Teams use their online board tools to represent where certain tasks are in the development process.

Kanban

26
New cards

This method is a good way for teams to identify roadblocks and to visualize the amount of work that’s getting done.

Kanban

27
New cards

This is a common Agile methodology for small teams that involves sprints. The team is led by a master whose main job is to clear all obstacles for others executing the day-to-day work.

Scrum

28
New cards

This event kicks off the sprint. This outlines what can be delivered in a sprint (and how).

Sprint planning

29
New cards

This recurring meeting acts as a sprint review—to iterate on learnings from a previous sprint that will improve and streamline the next one.

Sprint retrospective

30
New cards

This agile methodology is typically used in software development, This is an Agile framework that outlines values that will allow your team to work together more effectively.

Extreme Programming (XP)

31
New cards

List the 5 values of XP

Communication

Simplicity

Feedback

Courage

Respect

32
New cards

List the 3 cons of Agile methodologies

  1. It relies on real time communication

  2. It is really intense and requires a huge time commitment from users and laborer

  3. Developers must complete each feature within the given iteration

33
New cards

List 3 pros of DevOps

  1. It improves time to market, minimizes disruption while maximizes reliability

  2. They ensures everything happens smoothly and reliably

  3. Companies that use them enjoy time to market and customer satisfaction and improved quality

34
New cards

List 4 cons of DevOps

  1. Some customers don’t want continuous update to their systems.

35
New cards
36
New cards
37
New cards
38
New cards
39
New cards
40
New cards
41
New cards
42
New cards