U3

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

1/100

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

101 Terms

1
New cards

software requirement

establishing the needs of stakeholders that are to be solved by software

2
New cards

requirement

a condition or capability needed by the user to solve a problem

3
New cards

requirement

software capability that must be met or possessed by a system

4
New cards

functional requirement

specify something that the application or system should do

5
New cards

functional requirement

a behavior of the system that takes input and provides output

6
New cards

performance requirement

software requirements can also be a non-functional, it can be a

7
New cards

non-functional requirements

define the quality attributes of a software system, describe how the system should be

8
New cards

non-functional requirements

ensure the performance, maintainability, usability, and effectiveness of the entire system

9
New cards
  1. Business Requirements

  2. Architectural and Design Requirements

  3. System and Integration Requirements

3 types of requirements

10
New cards

business requirements

known as stakeholder requirements specifications

11
New cards

business requirements

describe the characteristics of the proposed system

12
New cards

architectural and design requirements

more detailed and determines the overall design required to implement the business requirements.

13
New cards

system and integration requirements

  1. break-down the steps needed to meet the business requirements

  2. detailed description of each and every requirement

14
New cards

requirement analysis

analyzing customers’ needs to obtain a definition of the software requirements

15
New cards

requirement analysis

helps organizations to determine the actual needs of stakeholders and enables the development team to communicate with the stakeholders

16
New cards

requirement analysis

is the process of defining user expectations for a new software being built or modified

17
New cards

requirement engineering

requirement analysis is also known as

18
New cards
  1. Eliciting requirements

  2. Analyzing requirements

  3. Requirements modeling

  4. Review and retrospective

the requirements analysis process involves the following steps

19
New cards

eliciting requirements

communicating with the customers to determine what their requirements are

20
New cards

requirements gathering

eliciting requirements is sometimes also called

21
New cards

analyzing requirements

determine the quality of the requirements

22
New cards

requirements modeling

requirements are usually documented in different formats such as use cases, user stories, natural-language documents, or process specifications.

23
New cards

review and retrospective

conducted to reflect on the previous iterations of requirements gathering in a bid to make improvements in the process going forward

24
New cards

review and retrospective

team members reflect on what happened in the iteration and identify actions for improvement going forward

25
New cards
  1. stakeholder issues

  2. engineer/developer issues

2 requirement analysis issues

26
New cards

requirement analysis techniques

used to map the business workflow

27
New cards

business process modeling notation (BPMN)

is similar to creating process flowcharts to simplify understanding the business process

28
New cards

business process modeling notation (BPMN)

widely popular as a process improvement methodology

29
New cards

UML (Unified Modeling Language)

consists of an integrated set of diagrams that document the artifacts of a software system

30
New cards

UML (Unified Modeling Language)

useful technique while creating object-oriented software

31
New cards

UML (Unified Modeling Language)

validating the architectural design

32
New cards

flowchart technique

sequential flow and control logic of a set of activities that are related.

33
New cards

flowchart

are in different formats such as linear, cross-functional, and top-down used to representdata flows, system interactions

34
New cards

advantage of using flowchart

  1. easy to read and write for both the technical and non-technical team members

  2. show the parallel process by function, critical attributes of a process

35
New cards

data flow diagram

visually represent systems and processes that are complex and difficult to describe in text

36
New cards

data flow diagram

represent the flow of information through a process or a system and sub process through which the data moves

37
New cards

data flow diagram

describes various entities and their relationships with the help of standardized notations and symbols

38
New cards

role activity diagrams (RAD)

is a role-oriented process model that represents role-activity diagrams

39
New cards

role activity diagrams (RAD)

are a high-level view that captures the dynamics and role structure of an organization

40
New cards

roles

are used to grouping together activities into units of responsibilities

41
New cards

activities

are the basic parts of a role

42
New cards

activity

may be either carried out in isolation or it may require coordination with other activities within the role

43
New cards

gantt charts

visual representation of tasks that are scheduled along with the timelines

44
New cards

gantt charts

help to know what is scheduled to be completed by which date. The start and end dates of all the tasks in the project can be seen in a single view.

45
New cards

IDEF (integrated definition for function modeling)

child and parent systems with the help of a box

46
New cards

IDEF (integrated definition for function modeling)

provides a blueprint to gain an understanding of an organization’s system

47
New cards

workflow technique

visual diagram that represent one or more business processes

48
New cards

workflow technique

used by BA for taking notes during requirements elicitation

49
New cards
  1. Information Gathering

  2. Workflow Modeling

  3. Business process Modeling

  4. Implementation, Verification & Execution

workflow technique process comprises of four stages:

50
New cards

object oriented methods

uses object oriented paradigm and modeling language for designing a system

51
New cards

object oriented methods

emphasis on finding and describing the object in the problem domain

52
New cards

object oriented methods

method is applicable to the system which has dynamic requirements. It is a process of deriving use cases, activity flow, and events flow for the system

53
New cards

object oriented analysis

can be done through textual needs, communication with system stakeholder and vision document

54
New cards

So, when the object receives a message, state changes through behavior

The object has a state, and state changes are represented by behavior

55
New cards

gap analysis

is a technique that helps to analyze the gaps in the performance of a software application to determine whether the business requirements are met or not

56
New cards

gap

denotes the difference between the present state and the target state

57
New cards

need analysis, need assessment, or need-gap analysis

gap analysis is also known as

58
New cards
  1. Business Process Modeling Notation (BPMN)

  2. UML (Unified Modeling Language)

  3. Flowchart Technique

  4. Data Flow Diagram

  5. Role Activity Diagrams (RAD)

  6. Gantt Charts

  7. IDEF (Integrated Definition for Function Modeling)

  8. Workflow Technique

  9. Object Oriented Methods

  10. Gap Analysis

10 requirement analysis techniques that can be used for software development process

59
New cards

Business Process Modeling Notation (BPMN)

knowt flashcard image
60
New cards

UML (Unified Modeling Language)

knowt flashcard image
61
New cards

Flowchart Technique

knowt flashcard image
62
New cards

Data Flow Diagram

knowt flashcard image
63
New cards

Role Activity Diagrams (RAD)

knowt flashcard image
64
New cards

Gantt Charts

knowt flashcard image
65
New cards

IDEF (Integrated Definition for Function Modeling)

knowt flashcard image
66
New cards

Workflow Technique

knowt flashcard image
67
New cards

Object Oriented Methods

knowt flashcard image
68
New cards

Gap Analysis

knowt flashcard image
69
New cards

analysis model

Software engineers perform analysis modeling and create an _________________ to provide information of 'what' software should do instead of 'how' to fulfill the requirements in software

70
New cards

analysis model

functions that software should perform, behavior it should exhibit, and constraints that are applied on the software

71
New cards

analysis model

determines the relationship of one component with other components. The clear and complete requirements specified in the __________ help the software development team to develop the software according to those requirements

72
New cards

analysis model

operates as a link between the 'system description' and the 'design model'

73
New cards

system description

provides information about the entire functionality of the system, which is achieved by implementing the software, hardware and data

74
New cards
  1. Scenario based element

  2. Class based elements

  3. Behavioral elements

  4. Flow oriented elements

analysis model is organized into four elements namely:

75
New cards

scenario based element

represents the system user point of view

76
New cards

scenario based element

use case diagram, user stories are

77
New cards

class based elements

the object of this type of element manipulated by the system. It defines the object, attributes and relationship

78
New cards

class based elements

class diagram, collaboration diagram are

79
New cards

behavioral elements

represent state of the system and how it is changed by the external events

80
New cards

behavioral elements

sequenced diagram, state diagram are

81
New cards

flow oriented elements

an information flows through a computer-based system it gets transformed

82
New cards

flow oriented elements

data flow diagram, control flow diagram are

83
New cards

structured analysis

top-down approach, which focuses on refining the problem with the help of functions performed in the problem domain

84
New cards

DFD (Data-Flow Diagram)

also known as bubble chart and work flow diagram

85
New cards

DFD (Data-Flow Diagram)

depicts data sources, data sinks, data storage and processes performed on data as nodes and logical flow of data as links between the nodes

86
New cards

data dictionary

is a repository that stores description of data objects to be used by the software

87
New cards

data dictionary

stores an organized collection of information about data and their relationships, data-flows, data types, data stores, processes and so on

88
New cards

data dictionary

comprises the source of data, which are data objects and entities

89
New cards

object-oriented modeling

used to describe system requirements using prototypes

90
New cards

object-oriented modeling

analyzes the problem domain and then partitions the problem with the help of objects

91
New cards

object-oriented modeling

defines a system as a set of objects, which interact with each other by the services they provide

92
New cards

object modelling

develops the static structure of the software system in terms of objects

93
New cards

dynamic modelling

a way of describing how an individual object responds to events

94
New cards

functional modelling

is the final component of object-oriented analysis

95
New cards

functional model

shows the processes that are performed within an object and how the data changes as it moves between methods

96
New cards

Structured Analysis/Structured Design (SASD) approach

is the traditional approach of software development based upon the waterfall model.

97
New cards

Unified Modeling Language (UML)

is a representation of a software in terms of it's structure, behavior and interactions, before the actual coding process begins

98
New cards

use-cases

are represented with the help of a use-case diagram, which depicts the relationships among actors and use cases within a system

99
New cards

use case

is the primary form of system/software requirements for a new software program underdeveloped. It specify the expected behavior (what), and not the exact method of making it happen (how)

100
New cards