Lec 1

1- can be cheap or implemented in effective timely manner or the more viable and
achieve the good quality measure

System planning
System analysis
System design
System analyst

2- is a process of collecting and interpreting facts, identifying the problems, and

decomposition of a system into its component

System planning
System analysis
System design
System analyst

3- is a process of planning a new business system or replacing an existing system by

defining its components or modules to satisfy the specific requirements

System planning
System analysis
System design
System analyst

4- is a step by step process for developing high quality information systems

System planning
System analysis
design
B and C
5- is a valued member of the IT department team who helps plan, develop, and maintain
information systems

System planning
System analysis
System design
System analyst

6- Analysts shouldn’t have excellent communicators with strong analytical and critical
thinking skills
T
F

7- is a set of related components that produces specific result

System
mission-critical system
Business today

8- is one that is vital to a company’s operations

system
mission-critical system
Business today

9- is being shaped by three major trends driven by the power of the internet
System
mission-critical system
Business today

10- refers to the combination of hardware, software, and services that people use to
manage, communicate, and share information

IT
IS
CS

11- Information technology can mean the difference between success and failure
T
F

12- consumers can go online to purchase an enormous variety of products and services

B2C

B2B
13- is many times greater

B2C

B2B

C2C

14- Large scale market – emotionally driven –brand awareness

B2C

B2B

C2C

15- niche market – raitionally driven – lead gen

B2C

B2B

C2C

16- is an overview of a company’s mission, functions, organization, etc …

business profile
business process
Business process modeling notation (bpmn)

17- is a specific set of transactions, events, and results that can be described and
documented.

business profile
business process
Business process modeling notation (bpmn)

18- includes standard shapes and symbols to represent events, processes, workflows, and
more

business profile
business process
Business process modeling notation (bpmn)
19- develop long-range plans, called strategic plans, which define the company’s overall
mission and goals

Top managers
Middle managers
Supervisors
Operational

20- employees include users who rely on transaction processing systems.

Top managers
Middle managers
Supervisors
Operational

21- provide direction, necessary resources, and performance feedback to supervisors and
team leaders

Top managers
Middle managers
Supervisors
Operational

22- often called team leaders, oversee operational employees and carry out day-to-day
functions

Top managers
Middle managers
Supervisors
Operational

23- produces a graphical representation of a concept or process that systems developers

can analyze, test, and modify

Modeling
Prototyping
CASE Tools
business model
24- describes the information that a system must provide and the value that provided to
the customers in 9 blocks to show a brief information and viable to know the organization

Modeling
Prototyping
CASE Tools
business model

25- tests system concepts and provides an opportunity to examine input, output, and user
interfaces before final decisions are made

Modeling
Prototyping
CASE Tools
business model

26- Is a technique that uses powerful software, called CASE tool, to help systems analysts
develop and maintain information systems

Modeling
Prototyping
CASE Tools
business model

27- A prototype is an early working version of an information system

T
F

28- prototyping slows the development process significantly

T
F

29- CASE tools provide an overall framework for systems development and support a wide
variety of design methodologies
T
F

30- Biggest commercial tools in CASE Tools

Visual Paradigm
Visual code
Visual basic
 Lec 2

1- is a traditional systems development technique that is time-tested and easy to

understand and based on an overall plan, similar to a blueprint for constructing a building,
so it is called a predictive approach

Structured analysis
system analysis
system planning
waterfall model

2- the result of each phase is called a deliverable, which flows into the next phase in

Structured analysis
system analysis
system planning
waterfall model

3- The purpose of this phase is to perform a preliminary investigation to evaluate an IT

related business opportunity or problem

Structured analysis
system analysis
system planning
waterfall model

4- Waterfall and parallel models does not emphasize interactivity among the phases
T
F

5- Structured analysis uses a series of phases, called the ………… to plan, analyze, design,
implement, and support an information system

SDLC
SDL
DLC
6- Required for building a logical model of the new system , The first step is requirements
modeling, where the analyst investigates business processes

system implementation
system analysis
system planning
system design

7- Create a physical model that will satisfy all documented requirements for the system

system implementation
system analysis
system planning
system design

8- The objective of the systems implementation phase is to deliver a completely

functioning and documented information system

system implementation
system analysis
system planning
system design

9- determine whether the system operates properly and if costs and benefits are within
expectations

system implementation
systems evaluation
system planning
system design

10- IT staff maintains, enhances, and protects the system. Maintenance changes correct
errors and adapt to changes in the environment

system support and secuirity

system analysis
system planning
system design
11- is also determined, which programmers will use to transform the logical design into
program modules and code

Application design
application system
application architecture

12- The objective during system support and secuirity phase is to manimize return on the
IT investment
T
F

13- A well-designed system must be secure, unreliable, maintainable, and scalable

T
F

14- The deliverable for the systems analysis phase is the

Application design
application system
system design
system requirements document

15- Waterfall model is hard to understand due to its simple linear structure , It helps to
define the goals and deliverables at the early stage of the project
TT
TF
FT
FF

16- pros of waterfall model :

Each stage are clearly defined and understood

This model works effectively with smaller projects where the requirements are clearly
Project management is simple and effective as there are no unnecessary changes
all of these

17- cons of waterfall model :

Definitely not a great choice complex and longterm project

Impossible to make changes at the later stage
This SDLC model doesn’t work for maintenance type project
No working model of the software until the end of the life cycle
all of these
18- Successful execution of the project depends on precise requirements
T
F

19- Cutting the Project down to subprojects, Parallel development methodology attempts
to address the problem of long delays between the analysis phase and the delivery of the
system , Reduce the time to deliver a system; thus, there is less chance of changes in the
business environment causing rework

Waterfall model
parallel model
objected oriented model

20- The result is a set of software objects that represent actual people, things,
transactions, and events. Using an O-O programming language, a programmer then writes
the code that creates the objects and it about how to develop with some special design
patterns, as the class is a blueprint of the objects

Waterfall model
parallel model
objected oriented model

21- Structured analysis treats processes and data as separate components

T
F

22- object-oriented analysis combines data and the processes that act on the data into
things called ……..

Classes
objects
types

23- The most important and fundamental requirements are bundled into the first version
of the system; this is a type of JAD development
T
F

24- breaks an overall system into a series of versions that are developed sequentially

Phased development
system analysis
system design
25- based methodologies attempt to address both weaknesses of structured design
methodologies by adjusting the SDLC phases and system developed quickly and into the
hands of the users

RAD
JAD
SAD

26- RAD-based methodologies recommend that analysts use special techniques such as
computer-aided software engineering (CASE) tools, joint application design (JAD) sessions,
fourth-generation or visual programming languages
T
F

27- The difference is that RAD focuses on teambased fact-finding, which is only one phase
of the development process, whereas JAD is more like a compressed version of the entire
process
T
F

28- Performs the analysis, design, and implementation phases concurrently, and all three
phases are performed repeatedly in a cycle

Prototyping development
phase development
Agile devolpment

29- the basics of analysis and design are performed, and work immediately begins on a
system prototype. A quick-and-dirty program that provides a minimal amount of features

Prototyping development
phase development
Agile devolpment

30- The key advantage of a prototyping-based methodology is that it very quickly provides
a system with which the users can interact
T
F

31- builds an overall plan for the information system, just as a contractor might use a
blueprint for constructing a building.

Structured analysis
Agile methods
The Agile Manifesto
32- in contrast, attempt to develop a system incrementally, by building a series of
prototypes and constantly adjusting them to user requirements

Structured analysis
Agile methods
The Agile Manifesto

33- is a document that identifies four key values and 12 principles that its authors believe
software developers should use to guide their work

Structured analysis
Agile methods
The Agile Manifesto

34- Agile methods typically use a spiral model, which represents a series of iterations, or
revisions, based on user feedback
T
F

35- agile approach emphasizes continuous feedback, and each incremental step is affected
by what was learned in the prior steps
T
F

36- Founded on four core values: communication, simplicity, feedback, and courage

Scrum
DevOps
Xp extreme

37- is a term that is well known to rugby fans. In rugby, a scrum is used to restart a game

Scrum
DevOps
Xp project

38- begins with user stories that describe what the system needs to do. Then,
programmers code in small, simple modules and test to meet those needs

Scrum
DevOps
Xp project
39- is a set of practices that combines software development and IT operations. It aims to
shorten the systems development life cycle and provide continuous delivery with high
software quality

Scrum
DevOps
Xp project

40- DevOps is complementary with Agile software development; several DevOps aspects
came from

Scrum methods
agile methodology
Xp project

41- XP projects deliver results sooner than even the RAD approaches, and they rarely get
bogged down in gathering requirements for the system
T
F

42- the creators of the Scrum method believe that no matter how much you plan, as soon
as the software begins to be developed, chaos breaks out and the plans go out the
window.

T
F

43- Teams are self-organized and self-directed. Unlike other approaches, Scrum teams
have a designated team leader
T
F

44- Teams organize themselves in a symbiotic manner and set their own goals for each
sprint (iteration)

scrum methods
agile methods
xp extreme

45- provides developer services to support teams to plan work, collaborate on code
development, and build and deploy applications

Microsoft office
Microsoft visual studio
Microsoft Azure DevOps
46- The Merging of DevOps and Agile approaches improve the quality and decrease the
time of project for

56%
37%
47%
50%

47- improve the communication between the customer with development team

Agile
DevOps
Rad

48- can address the gap between development and operation team within a cloud
environment

Agile
DevOps
Rad

49- All Cloud DevOps Environments now merge the 2 methods to solve the problem Like
Azure DevOps
T
F

50- Choosing a methodology is simple, because one methodology is always best

T
F
 Lec 3

1- The IT team reviews a proposal to determine if it presents a strong business case

Business planning
Strategic planning
Swot Analysis

2- is the process of identifying long-term organizational goals, strategies, and resources

Business planning
Strategic planning
Swot Analysis

3- analysis can focus on a specific product or project, an operating division, the entire
company, or the mission statement itself

Business planning
Strategic planning
Swot Analysis

4- A strategic plan looks beyond dayto-day activities and focuses on a horizon that is
three, five, ten, or more years in the future.
T
F

5- The starting point for most projects is called a

systems request
System design
system analysis

6- Internal and external factors affect every business decision that a company makes
T
F
7- uses four main yardsticks to measure a proposal: operational feasibility, economic
feasibility, technical feasibility, and schedule feasibility

feasibility study
feasibility case

8- are benefits that can be measured in dollars

Intangible benefits
Tangible benefits

9- are advantages that are difficult to measure in dollars but are important to the
company

Intangible benefits
Tangible benefits

10- The first step in evaluating feasibility is to identify and weed out systems requests that
are not feasiblity

Evaluating feasibility
setting priorities
PRELIMINARY INVESTIGATION

11- system requests that are not currently feasible can be resubmitted as new hardware,
software, or expertise becomes available.
T
F

12- The feasibility is not the only thing that can make it a standard for choosing the
requirement, such process have 2 another metrics

Evaluating feasibility
setting priorities
PRELIMINARY INVESTIGATION

13- the analyst interacts with managers, users, and other stakeholders , The analyst
performs fact-finding to get the problem or opportunity, project scope and constraints,
project benefits, and estimated development time and costs.

Evaluating feasibility
setting priorities
PRELIMINARY INVESTIGATION
14- Which processes have greatest impact on the organization’s strategic objectives?
health
importance

15- (or Dysfunction) Which processes are in deepest trouble

health
importance

16- All requirements can’t be addressed to a PICK chart

T
F

17- Projects where management has a choice in implementing them are

discretionary projects
nondiscretionary projects
system projects

18- Projects where no choice exists are called

discretionary projects
nondiscretionary projects
system projects

19- f the systems request involves a new information system or a substantial change in an
existing system, systems analysts might need to develop a ……….

business profile
fishbone diagram
Project scope

20- A popular technique for investigating causes and effects is called a

business profile
fishbone diagram
Project scope

21- means defining the specific boundaries, or extent, of the project

business profile
fishbone diagram
Project scope
22- Projects with very general scope definitions are at risk of expanding gradually, without
specific authorization, in a process called

business profile
fishbone diagram
project scope
Project creep

23- Constraints on the system must be identified. A constraint is a requirement or

condition that the system must satisfy or an outcome that the system must achieve
T
F

24- Is the constraint something that must be met as soon as the system is developed or
modified

Present versus future

Internal versus external
Mandatory versus desirable

25- Is the constraint due to a requirement within the organization

Present versus future

Internal versus external
Mandatory versus desirable

26- Is the constraint mandatory? Is it absolutely essential to meet the constraint

Present versus future

Internal versus external
Mandatory versus desirable

27- The objective of …….. is to gather data about project usability, costs, benefits, and
schedules

Fact finding
organization charts
pareto chart

28- can map the issues of the system arranged by descending to keep track of mistakes
processed from the Issue register, the curve is a cumulative to the bars
organization charts
pareto chart
fact finding
29- estimates should be developed for the requirements modeling tasks for the next SDLC
phase

Time and cost

Operational feasibility
Technical feasibility
Economic feasibility

30- Evaluation of the project’s feasibility, beginning with reviewing the answers to the
questions

Evaluate feasibility
Operational feasibility
Technical feasibility
Economic feasibility

31- Fact -finding should have included a review of user needs, requirements, and
expectations

Schedule feasibility
Operational feasibility
Technical feasibility
Economic feasibility

32- The fact -finding data should identify the hardware, software, and network resources
needed to develop, install, and operate the system

Time and cost

Operational feasibility
Technical feasibility
Economic feasibility

33- Using the fact -finding data, financial analysis tools can be applied to assess feasibility.
The cost -benefit data will be an important factor for management to consider

Operational feasibility
Technical feasibility
Schedule feasibility
Economic feasibility
34- The fact -finding data should include stakeholder expectations regarding acceptable
timing and completion dates

Operational feasibility
Technical feasibility
Schedule feasibility
Economic feasibility

35- If cost and benefit data were gathered, financial analysis and impact statements can’t
be prepared using spreadsheets and other decision-support tools
T
F

36- Present Results It might be that no action is necessary or that some other strategy,
such as additional training, is needed
T
F

37- To solve a minor problem, a simple solution might be chosen without performing
further analysis
T
F

38- The report includes an evaluation of the systems request, an estimate of costs and
benefits, and a case for action
T
F
 Lec 4

1- is someone who is responsible for overseeing all relevant tasks , typically perform four
activities, or functions: planning, scheduling, monitoring, and reporting

Project manager
software engineer
software manager

2- includes planning, scheduling, monitoring and controlling, and reporting on information

system development

Project management
Systems development
project triangle

3- where the three legs are cost, scope, and time. The challenge is to find the optimal
balance among these factors.

Project management
Systems development
project triangle

4- tend to be dynamic and challenging

Project management
Systems development
project triangle

5- A successful project must be completed on time, within budget, and deliver a quality
product that satisfies users and meets requirements
T
F

6- There isn’t always a balance between constraints and interactive elements such as
project cost, scope, and time
T
F
7- Decisions need to be all-or-nothing, but recognize that any change in one leg of the
triangle will affect the other two legs
T
F

8- • identifying all project tasks • estimating the completion time and cost of each.

Planning
Scheduling
Monitoring
Reporting

9- creation of a specific timetable. • Project scheduling uses Gantt charts and PERT/CPM
charts

Planning
Scheduling
Monitoring
Reporting

10- guiding, supervising, and coordinating the project team’s workload. • monitor the
progress, evaluate the results, and take corrective action

Planning
Scheduling
Monitoring
Reporting

11- includes regular progress reports to management, users, and the project team itself •
Effective reporting requires strong communication skills and a sense of what others want
and need to know about the project

Planning
Scheduling
Monitoring
Reporting

12- involves breaking a project down into a series of smaller tasks

WBS
WBA
WBDS
13- is a horizontal bar chart that represents a set of tasks . It can simplify a complex
project by combining several activities into a task group that contains subsidiary tasks.
This allows a complex project to be viewed as a set of integrated modules

Gantt charts
Ghandi charts
PERT/CPM chart

14- was developed by the U.S. Navy to manage very complex projects, such as the
construction of nuclear submarines

PERT
CPM
COM

15- was developed by private industry to meet similar project management needs. The
distinction between the two methods has disappeared over time

PERT
CPM
COM

16- is a bottom-up technique because it analyzes a large, complex project as a series of

individual tasks . This chart lists the tasks to be performed on the vertical axis, and time
intervals on the horizontal axis

Gantt charts
Ghandi charts
PERT/CPM chart

17- A WBS must clearly identify each task and include an estimated duration
T
F

18- is any work that has a beginning and an end and requires the use of company
resources such as people, time, or money

task, or activity
events, or milestones
wbs

19- is a recognizable reference point that can be used to monitor progress

task, or activity
events, or milestones
wbs
20- represents the work that one person can complete in one day. This approach,
however, can present some problems

person day
person week
person month

21- if it will take one person 20 days to perform a particular task, it might be true that two
people could complete the same task in 10 days
T
F

22- Project managers often use a ………. for estimating the duration of each task

weighted formula
Heighted formula

23- Tasks in a work breakdown structure must be arranged in a logical sequence called a

Task patterns
network diagram
Reporting

24- A complex task pattern is a chain of multiple patterns, if it complete for a project it
called a

Task patterns
network diagram
Reporting

25- Members of the project team regularly report their progress to the project manager,
who in turn reports to management and users

Task patterns
network diagram
Reporting

26- Task patterns can’t involve dependent tasks, multiple successor tasks, and multiple
predecessor tasks
T
F
27- The project manager must keep track of the tasks and progress of team members,
compare actual progress with the project plan

Project management
project monirtoring and control

28- a review of a project team member’s work by other members of the team.

Project management
structured walk-through

29- The most important practice of Agile development is the daily SCRUM practice which
called the

daily stand –up

Stand Up meeting
Risk management

30- is a daily status meeting among all team members and it is held roughly for 15 minutes

daily stand –up

Stand Up meeting
Risk management

31- is the process of identifying, analyzing, anticipating, and monitoring risks to minimize
their impact on the project

daily stand –up

Stand Up meeting
Risk management

32- is an event that could affect the project negatively

Risk
object
plan

33- includes a review of the project’s scope, stakeholders, budget, schedule, and any other
internal or external factors that might affect the project

risk management plan

Risk identification
Qualitative risk analysis
34- the analyst lists each risk and assesses the likelihood that it could affect the project

risk management plan

Risk identification
Qualitative risk analysis

35- evaluates each risk by estimating the likelihood or probability that it will occur and the
degree of impact. And mapping the evaluation to the risk matrix

risk management plan

Risk identification
Qualitative risk analysis

36- The purpose of ………….. is to understand the actual impact in terms of dollars, time,
project scope, or quality

risk management plan

Risk identification
Qualitative risk analysis

37- In some situations, adding more people to a project actually might increase the time
necessary to complete the project because of a principle called

Brooks law
Franklin Law
Michel Law
Trevor Law
 Lec 5

1-often find it difficult to clearly describe what they want the system to do When they do
list the requirements, the result tends to be an unprioritized set of conflicting capabilities

Customers
managars
empolyes

2-It may be tempting to “just do something” to give the appearance of productivity, but a
systems project that does not satisfy business requirements serves no useful purpose

System design
system analysis
system planning

3-Practicing fact -finding to describe the current system and identification of the
requirements for the new system, such as: Outputs , Inputs , Processes , Performance and
Security

Requirements Modeling
Data and Process Modeling
Object Modeling
Development Strategy

4- How to represent graphically system data and processes using traditional structured
analysis techniques

Requirements Modeling
Data and Process Modeling
Object Modeling
Development Strategy

5- While structured analysis treats processes and data as separate components

Requirements Modeling
Data and Process Modeling
Object Modeling
Development Strategy
6- Various development options and prepares for the transition to the systems design is
something about Make or Buy , Include software trends and architectures (Microservices,
Service Oriented Architecture SOA, Monolithic or traditional software) acquisition and
development alternatives, outsourcing, and formally documenting requirements for the
new system

Requirements Modeling
Data and Process Modeling
Object Modeling
Development Strategy

7- is a document that describes the nature of a project

SRS
SRT
SDCL

8- Requirements For Object Oriented development

Use case
srs
personas

9- Requirements For Structured Development

Use case
srs
personas

10- Requirements For Agile development

Use case
srs
personas

11- The team can also use combinations of them to simplify every problem in the project.
T
F

12- identifies the data flowing into a process, the business rules that transform the data,
and the resulting output data flow

Structured analysis
DFD Data flow Diagram
separate components
Class Diagram
13- is the best tool for such modeling

Structured analysis
DFD Data flow Diagram
separate components
Class Diagram

14- Analysts often use both modeling(Data & Process + Object modeling) methods to gain
as much information as possible
T
F

15- Enable the analyst to identify a problem, evaluate the key elements, and develop a
useful solution

Analytical skills
Interpersonal skills
Soft skills

16- Especially valuable to a systems analyst who must work with people at all
organizational levels

Analytical skills
Interpersonal skills
Soft skills

17- System developers view users as …….. in the development process. Greater user
involvement usually results in better communication, faster development times, and more
satisfied users

partners
customers
managers

18- is a popular fact-finding technique that brings users into the development process as
active participants

JAD
RAD
LAD
19- Users have ……. a in an information system, and they should participate fully in the
development process

vital stake
vital snake
visual stake

20- successful systems shouldn’t be user-oriented, and users need to be involved, formally
or informally, at every stage of system development
T
F

21- Develops an agenda, acts as a facilitator, and leads the JAD session

JAD project leader

Top Management
Managers
users

22- Provides enterprise-level authorization and support for the project

JAD project leader

Top Management
Managers
users

23- Provide department-level support for the project and understanding of how the
project must support business functions and requirements

JAD project leader

Top Management
Managers
users

24- Provide operational-level input on current operations, desired changes, input and
output requirements, user interface issues, and how the project will support day-to-day
tasks.

JAD project leader

Top Management
Managers
users
25- Provide technical assistance and resources for JAD team members on issues such as
security, backup, hardware, software, and network capability

JAD project leader

Recorder
System Analyst & other IT staff members
users

26- Documents results of JAD sessions and works with systems analysts to build system
models and develop CASE tool documentation

JAD project leader

Recorder
System Analyst & other IT staff members
users

27- JAD is more expensive and can be cumbersome if the group is too large relative to the
size of the project __ JAD allows key users to participate effectively in the requirements
modeling process
TT
TF
FT
FF

28- RAD can result in a more accurate statement of system requirements, a better
understanding of common goals, and a stronger commitment to the success of the new
system
T
F

29- The project team uses …… to build the prototypes and create a continuous stream of
documentation

AGILE
CASE tools
Models

30- RAD relies heavily on ……. and user involvement. The RAD process allows users to
examine a working model as early as possible

Prototyping
agile
models
31- It is especially important to unlimit the cost of changes that typically occur in a long,
drawn - out development schedule
T
F

32-RAD Systems can be developed more quickly with significant cost savings
T
F

33- RAD stresses the mechanics of the system itself and does not emphasize the
company’s strategic business needs. A system might work well in the long term
T
F

34- RAD also helps a development team design a system that requires a highly interactive
or complex user interface
T
F

35- successful systems must be …… , and users need to be involved, formally or informally,
at every stage of system development

user-oriented
Object oriented
 Lec 6

1- attempt to develop a system incrementally, by building a series of prototypes and

constantly adjusting them to user requirements

Agile methods
Agile
Agile Approaches

2- emphasizes continuous feedback, and each incremental step is affected by what was
learned in the prior steps

Agile methods
Agile
Agile Approaches

3- The Agile methodologies outlined below share much of the same overarching
philosophy, as well as many of the same characteristics and practices

Agile methods
Agile
Agile Approaches

4- Many agile developers prefer use CASE tools at all, and rely instead on whiteboard
displays and arrangements of movable sticky notes
T
F

5- Scrum teams commit to ship working software through set intervals called

Sprints
methods
Agile
6- Their goal is to create learning loops to quickly gather and integrate customer
feedbacks

Scrum
Kanban
lean

7- An agile team uses a series of scrums to pause the action and allow the players to reset
the game plan, which remains in effect until the next scrum
T
F

8- Scrum moves fast, with sprints of two to at most ……… weeks with clear start and finish
dates. The short time frame forces complex tasks to be split into smaller stories, and helps
the team learn quickly.

5
4
3
2

9- advocates for the customer, manages the product backlog, and helps prioritize the work
done by the development team.

product owner
scrum master
development team

10- helps the team stay grounded in the scrum principles

product owner
scrum master
development team

11- chooses the work to be done, delivers increments, and demonstrates collective
accountability

product owner
scrum master
development team
12- Scrum teams are self-organizing and everyone is equal, despite having different
responsibilities. The team is united by the goal of shipping value to customers

Velocity
Backlog
nobody
Burndown chart

13- the number of story points completed in a sprint —is the central metric for scrum
teams

Velocity
Backlog
nobody
Burndown chart

14- is the way to figure the velocity .

Velocity
Backlog
nobody
Burndown chart

15- is a set of work items ordered and stated, something to do like a requirement to
implement, bug to solve

Velocity
Backlog
nobody
Burndown chart

16- ……………. not only makes release and iteration planning easier, it broadcasts all the
things the team intends to spend time on —including internal work that the customer will
never notice

well -prioritized agile backlog

well -prioritized method backlog
well –prioritized scrum backlog

17- The entire lifecycle is completed in fixed time -period called a

sprint
backlogs
scrum
18- is a prioritized list of value the team can deliver

method backlog
scrum backlog
Product Backlog

19- owns the backlog and adds, changes, and reprioritizes as needed.

The Product Owner

The backlog Owner
The system Owner

20- in ……..the team chooses the backlog items they will work on in the upcoming sprint

Sprint Planning
System Planning
data Planning

21- Often, each item on the Sprint Backlog is broken down into ……

Data
tasks
informations

22- Once the Sprint starts, the team executes on the

method backlog
scrum backlog
sprint Backlog
Product Backlog

23- Scrum does not specify how the team should execute. That is left for the team to
decide
T
F

24- The Daily Scrum is daily meeting limited to ….. Minuts

15
25
20
30
25- provides a visual way of tracking progress for each backlog item

THE TASK BOARD

THE SPRINT BURNDOWN

26- A graph that plots the daily total of remaining work. Remaining work is typically in
hours. It provides a visual way of showing whether the team is “on track” to complete all
the work by the end of the Sprint

THE SPRINT BURNDOWN

THE TASK BOARD

27- The team demonstrates what they’ve accomplished to stakeholders

Sprint Review
THE TASK BOARD
Sprint Retrospective
Increment

28- The team takes time to reflect on what went well and which areas need improvement

Sprint Review
THE TASK BOARD
Sprint Retrospective
Increment

29- The product of a Sprint is called the

Sprint Review
THE TASK BOARD
Sprint Retrospective
Increment

30- The entire cycle is repeated for the next sprint

T
F

31- Sprint Planning selects the Previos items on the Product Backlog and the cycle repeats
T
F
32-Aglie method advantages

Agile, or adaptive, methods are very flexible and efficient in dealing with change.
Frequent deliverables constantly validate the project and reduce risk.
stress team interaction and reflect a set of community based values
all of these

33- Aglie method disadvantages

Team members need a high level of technical and interpersonal skills

A lack of structure and documentation can introduce risk factors, such as blurring of roles
and responsibilities, and loss of corporate knowledge.
all of these

34- While broadly fitting under the umbrella of Agile, both Scrum and Kanban are quite
similer
T
F

35- focuses on fixed length sprints -- has defined roles ---- uses velocity as a key metric ---
My Advice is to use it when IT team support many organizations like IT company

SCRUM
Kanban
36- is more of a continuous flow model. ---- does not define any specific roles for the
team. -- champions the use of cycle tim.----- My Advice is to use it when IT team support
one organization

SCRUM
Kanban

37- help users, managers, and IT professionals understand the design of 31 a system.
Modeling involves graphical methods and nontechnical language that represent the
system at various stages of development

Model
use case
DFD
BPM

38- is a top-down representation of a function or process

DFD
use case
BPM
FFD
39- Start at the top and work downwards

organization chart
Bubble chart
FDD
DFD

40- represents one or more business processes and includes various shapes and symbols
to represent events, processes, and workflow

Bubble chart
FDD
DFD
BPM

41- is a widely used method of visualizing and documenting software systems design

Bubble chart
FDD
DFD
UML

42- UML uses object -oriented programming concepts, but it is independent of any specific
programming language and can be used to describe business processes and requirements
generally
T
F
 Lec 7

1-To obtain answers to these questions, the analyst develops a

fact-finding plan
fact-finding system
fact-finding design

2- is a popular approach to modeling enterprise architectures

Zachman Framework
TOGAF Framework

3- helps businesses define and organize requirements before a project starts, keeping the
process moving quickly with few errors

Zachman Framework
TOGAF Framework

4- is an important fact-finding tool during the systems analysis phase

Interviewing
review
Form

5- is a planned meeting during which the analyst obtains information from another
person

review
Form
interview
Document review

6- can save time and provide an opportunity to observe interaction among the
participants

Group interviews
presonal interviews
7- Group interviews can’t present problems
T
F

8- Upper -level managers can provide the big picture to help understand the system as a
whole
T
f

9- A specific plan for the meeting should be

Developed
Designed
Discussed

10- Analysts sometimes hear only what they expect to hear. Concentrate on what is said
and notice any nonverbal communication that takes place. This process is called

engaged listening
meeting
interview

11- Interviewee with strong opinions about the current or future system might distort the
facts
T
F

12- can help the analyst understand how the current system is supposed to work

Interview
Form
Document review
questionnaire

13- also called a survey, is a document containing a number of standard questions that can
be sent to many individuals

Interview
Form
Document review
questionnaire
14- can be used to obtain information about a wide range of topics, including workloads,
reports received, volumes of transactions handled, job duties, difficulties, and opinions of
how the job could be performed better or more efficiently

Analysists
Designers
Document reviewers
questionnaires

15- also allows the analyst to verify statements made in interviews and determine
whether procedures really operate as they are described

interview
Form
Personal observation
Document review

16- Examples of actual documents should be collected using a process called

Research
Sampling
Forms

17- can include the Internet, IT magazines, and books to obtain background information,
technical material, and news about industry trends and developments

Research
Sampling
Forms

18- Keeping accurate records of interviews, facts, ideas, and observations is essential to
successful systems development

Documentation
Sampling
Forms
interview
 Lec 8

1- practice-based methodology for effective modeling and documentation of software-

based systems

Agile Modeling
Agile Method
Agile Technies

2- are fictional characters, which you create based upon your research in order to
represent the different user types that might use your service, product, site, or brand in a
similar way

Agile Modeling
Agile Method
Agile Technies
personas

3- powerful technique to describe the users and customers of a product in order to make
the right product decisions

Agile Modeling
Agile Method
Agile Technies
personas

4- At a …… level AM is a collection of Core Practices, depicted in the pattern language map

High
detailed
average
low
5- At a more ………. level AM is a collection of values, principles, and practices for modeling
software that can be applied on a software development project in an effective and
lightweight manner

High
detailed
average
low

6- a project management approach that involves breaking the project into phases and
emphasizes continuous collaboration and improvement

Agile Modeling
Agile Methodology
Agile Technies
personas

7- This ……… cuts straight to the nitty-gritty. “It focusses on: What does my typical user
want to do with my product?

Persona
Method
Agile

8- The objective of a goal-directed ……… is to examine the process and workflow that user
would prefer to utilize in order to achieve their objectives

Persona
Method
Agile

9- is also goal - directed and it also focusses on behaviour

role -based perspective

persona
aglie

10- The personas of the role -based perspectives are massively ……… and incorporate data
from both qualitative and quantitative sources

Data-driven
system-driven
information-driven
11- The role -based perspective focusses on the …….s role in the organization

User
designer
manager

12- is rooted in the ability of stories to produce involvement and insight

engaging perspective
fictitious people
fictional persona

13- Through an understanding of characters and stories, it is possible to create a vivid and
realistic description of

engaging perspective
fictitious people
fictional persona
Engaging personas

14- does not emerge from user research (unlike the other personas) but it emerges from
the experience of the UX (User Experience) design team

engaging perspective
fictitious people
fictional persona
Engaging personas

15- can incorporate both goal and role -directed personas, as well as the more traditional
rounded personas

engaging perspective
fictitious people
fictional persona
Engaging personas

16- Any persona description should be based on knowledge gained from direct interaction
with the target customers and users
T
F

17- This allows analyst to capture the user and the customer-specific needs, and it makes
divergent or conflicting goals Harder to see
T
F

18- Whenever create several personas for a product, choose one -- is the character mainly
design and build the product for

fictitious people
fictional persona
Engaging personas
primary persona

19- can help personas be believable :

Base personas on first-hand user research (as discussed above)

Choose a representative name and picture
Formulate personas together with the development team
all of these

20- Make personas visible and accessible to everyone involved in the development effort

fictitious people
fictional persona
Engaging persona
Visualize persona

21- A good tool for managing the requirements and user stories is ……… boards

Azure DevOps
Microsoft visual studio
Asp.net
 Lec 9

1- is built that describes how the system will be constructed ---- Design Phase Based

Physical Model
logical model
DFD

2- shows what the system must do., regardless of how it will be implemented physically ---
Analysis Phase Based

Physical Model
logical model
DFD

3- Systems analysts use one graphical techniques to describe an information system

T
F

4- uses various symbols to show how the system transforms input data into useful
information

DFD
ERD
SRS

5- DFD show program logic or processing steps

T
F
average
low
6- A set of DFDs provides a logical model that shows what the system does, not how it
does it

Data flow Diagram

Agile Method
Agile diagram
personas

7- is a path for data to move from one part of the information system to another

SRS
Data flow
Agile

8- A data flow in a DFD represents one only data item.

T
F

9- The APPLY INSURANCE PREMIUM process, for instance, produces output, but has no
input data flow

SPONTANEOUS GENERATION
BLACK HOLE
GRAY HOLE

10- CALCULATE GROSS PAY

SPONTANEOUS GENERATION
BLACK HOLE
GRAY HOLE

11- e is a process that has at least one input and one output, but the input obviously is
insufficient to generate the output shown

SPONTANEOUS GENERATION
BLACK HOLE
GRAY HOLE

12- is rooted in the ability of stories to produce involvement and insight

engaging perspective
fictitious people
fictional persona
13- is used in a DFD to represent data that the system stores because one or more
processes need to use the data at a later time

Data base
data store
data structure

14- The grading system is simple enough that no additional DFDs are needed to model the
system

T
F

15- A data store must be connected to a process with a data flow

T
F

16- There is an exception to the requirement that a data store must have at least one
incoming and one outgoing data flow
T
F

17- A DFD shows external abd interal entities that provide data to the system or receive
output from the system -- shows the boundaries of the system and how the system
interfaces with the outside world
TT
TF
FF
FT

18- DFD entities are also called …….. because they are data origins or final destinations

terminators
fictionals
personas
19- During requirements modeling, interviews, questionnaires, and other techniques were
used to gather ….. about the system,

informatians
Forms
FACTS

20- When a DFD is exploded, the higher-level diagram is called the

parent diagram
child diagram

21- lower-level diagram is referred to as

parent diagram
child diagram

22- is the process of drawing a series of increasingly detailed diagrams, until all functional
primitives are identified

Leveling
Balancing

23- maintains consistency among a set of DFDs by ensuring that input and output data
flows align properly
Leveling
Balancing

24- This set of lower-level DFDs is based on the ……... To create lower-level diagrams

Order system
level system
balance system