1

S
C
A
L
F T W A R E
B
5
I P
6 7 8
L S E C U R I T Y R A D
9
I C O G
11 12
S O F T W A R E E N G I N E E R I N G I R
Y S R L I
13 14 15
E A I N P R O G R E S S
17 18
D D S D M M H P M K
I M E A E E A
L C H A R A C T E R I S T I C S N T N
G N H E S H A
R G O A O O L
 A D
M O
Across
set of rules and operations grouped and scheduled for the
3
execution of a process
6 is a nonfunctional requirement
Rapid Application Development means an adaptive software
7 development model based on prototyping and quick feedback
with less emphasis on specific planning
its focus on reducing waste and improving efficiency in the
10
interest of providing more value to customers
11 discipline
of engineering which focuses on the development,
production and creation of programs.
13 is
one of the columns and represents the status of an activity in
kanban
17 dynamic systems development method
19 Refers to software functionality factors
is a computer programming model that organizes software
20 design
around data, or objects, rather than functions and logic
is the way in which the tasks of the project will be accomplished
23 system, including how to put its omponents together and the
functions to be performed by each
24 The
less resource a piece of software uses, the better. Processor,
memory and disk space usage should be minimized
25 is
where the team comes together to move the product forward,
inspired by a scrum in the sport of rugby
26 the
characteristics of the components of the system required to
implement the logical design.
27 work
teams are represented by colors, depending on the number
of members.
N U D Y
A R O S
Down
characteristic of a system or application that indicates its ability
1 to continue to perform well under increased or increased
workload.
are product features or functions that developers must
2 implement to enable users to accomplish their tasks.Describe
system behavior under specific conditions
traditional methodology, it has inflexible stages, it doesn't allow
4
going back from stage
5 software type
It is a way of managing a project by dividing it into several phases.
8 It involves constant collaboration with stakeholders and
continuous improvement at every stage.
They allow to visualize the different types of roles in a system and
9
how those roles interact with the system, type of UML diagram
12 Identification
of inconvenient situations to avoid and solve them.
Linear model stage
14 includes
gathering all the specific details required for a new
system as well as determining the first ideas for prototypes
15 code that anyone can inspect, modify, and enhance
16 the
prototype developed initially is incrementally improvement
on the basis of customer feedback until it finally gets accepted
18 systematic
way for development, which allows to manage and
administer a project and that it can be successful
21 A
system that operates in different environments from which it’s
originally designed makes it good
22 Systems Development Life Cycle