Here are the key terms from the chapter. The page where each term is first explained is in parentheses afterthe term.1. Agile Methodologies (p. 47)2. Application software (p. 30)3. Boundary (p. 32)4. Cohesion (p. 35)5. Component (p. 32)6. Computer-aided softwareengineering (CASE) (p. 45)7. Constraint (p. 33)8. Coupling (p. 35)9. Decomposition (p. 33)10. Environment (p. 32)11. Information systems analysisand design (p. 30)12. Interface (p. 33)13. Interrelated (p. 32)14. Joint application design (JAD)(p. 45)15. Modularity (p. 35)16. Participatory design (PD) (p. 47)17. Prototyping (p. 44)18. Purpose (p. 32)19. Rapid application development(RAD) (p. 45)20. Repository (p. 45)21. System (p. 32)22. Systems analysis (p. 40)23. Systems analyst (p. 37)24. Systems design (p. 41)25. Systems development life cycle(SDLC) (p. 38)26. Systems development methodology(p. 38)27. Systems implementation andoperation (p. 41)28. Systems planning and selection(p. 40)Match each of the key terms above with the definition that best fits it.1. The first phase of the SDLC in which an organization’s total information system needsare analyzed and arranged, and in whicha potential information systems project isidentified and an argument for continuing ornot continuing with the project is presented.2. The process of developing and maintainingan information system.3. A systems development approach that originated in northern Europe, in which usersand the improvement of their work livesare the central focus.4. Software designed to process dataand support users in an organization.Examples include spreadsheets, wordprocessors, and database managementsystems.5. The organizational role most responsiblefor the analysis and design of informationsystems.6. A structured process in which users,managers, and analysts work togetherfor several days in a series of intensivemeetings to specify or review systemrequirements.7. Building a scaled-down version of thedesired information system.8. A group of interrelated procedures usedfor a business function, with an identifiable boundary, working together for somepurpose.9. An irreducible part or aggregation ofparts that make up a system, also called asubsystem.10. Dependence of one part of the system onone or more other system parts.11. The line that marks the inside and outsideof a system and that sets off the systemfrom its environment.12. The overall goal or function of a system.13. Phase of the SDLC, in which the systemchosen for development in systems analysis is first described independently of anycomputer platform and is then transformedinto technology-specific details from whichall programming and system constructioncan be accomplished.14. Phase of the SDLC, in which the currentsystem is studied and alternative replacement systems are proposed.15. Everything external to a system that interacts with the system.16. Point of contact where a system meets itsenvironment or where subsystems meeteach other.17. A limit to what a system canaccomplish.18. Final phase of the SDLC, in which theinformation system is coded, tested, andinstalled in the organization, and in whichthe information system is systematicallyrepaired and improved.19. A standard process followed in an organization to conduct all the steps necessary toanalyze, design, implement, and maintaininformation systems.20. The series of steps used to mark thephases of development for an informationsystem.21. The process of breaking the descriptionof a system down into small components;also known as functional decomposition.22. Dividing a system up into chunks or modules of a relatively uniform size.23. The extent to which subsystems depend oneach other.24. The extent to which a system or subsystemperforms a single function.25. Software tools that provide automatedsupport for some portion of the systemsdevelopment process.26. A centralized database that contains alldiagrams, forms and report definitions,data structures, data definitions, processflows and logic, and definitions of otherorganizational and system components; itprovides a set of mechanisms and structures to achieve seamless data-to-tool anddata-to-data integration.27. Systems development methodology created to radically decrease the time neededto design and implement informationsystems.28. Current approaches to systemsdevelopment that focus on adaptivemethodologies, people instead of roles,and an overall self-adaptive developmentprocess.
Here are the key terms from the chapter. The page where each term is first explained is in parentheses after
the term.
1. Agile Methodologies (p. 47)
2. Application software (p. 30)
3. Boundary (p. 32)
4. Cohesion (p. 35)
5. Component (p. 32)
6. Computer-aided software
engineering (CASE) (p. 45)
7. Constraint (p. 33)
8. Coupling (p. 35)
9. Decomposition (p. 33)
10. Environment (p. 32)
11. Information systems analysis
and design (p. 30)
12. Interface (p. 33)
13. Interrelated (p. 32)
14. Joint application design (JAD)
(p. 45)
15. Modularity (p. 35)
16. Participatory design (PD) (p. 47)
17. Prototyping (p. 44)
18. Purpose (p. 32)
19. Rapid application development
(RAD) (p. 45)
20. Repository (p. 45)
21. System (p. 32)
22. Systems analysis (p. 40)
23. Systems analyst (p. 37)
24.
25. Systems development life cycle
(SDLC) (p. 38)
26. Systems development methodology
(p. 38)
27. Systems implementation and
operation (p. 41)
28. Systems planning and selection
(p. 40)
Match each of the key terms above with the definition that best fits it.
1. The first phase of the SDLC in which an organization’s total
are analyzed and arranged, and in which
a potential information systems project is
identified and an argument for continuing or
not continuing with the project is presented.
2. The process of developing and maintaining
an information system.
3. A systems development approach that originated in northern Europe, in which users
and the improvement of their work lives
are the central focus.
4. Software designed to process data
and support users in an organization.
Examples include spreadsheets, word
processors, and
systems.
5. The organizational role most responsible
for the analysis and design of information
systems.
6. A structured process in which users,
managers, and analysts work together
for several days in a series of intensive
meetings to specify or review system
requirements.
7. Building a scaled-down version of the
desired information system.
8. A group of interrelated procedures used
for a business function, with an identifiable boundary, working together for some
purpose.
9. An irreducible part or aggregation of
parts that make up a system, also called a
subsystem.
10. Dependence of one part of the system on
one or more other system parts.
11. The line that marks the inside and outside
of a system and that sets off the system
from its environment.
12. The overall goal or function of a system.
13. Phase of the SDLC, in which the system
chosen for development in systems analysis is first described independently of any
computer platform and is then transformed
into technology-specific details from which
all
can be accomplished.
14. Phase of the SDLC, in which the current
system is studied and alternative replacement systems are proposed.
15. Everything external to a system that interacts with the system.
16. Point of contact where a system meets its
environment or where subsystems meet
each other.
17. A limit to what a system can
accomplish.
18. Final phase of the SDLC, in which the
information system is coded, tested, and
installed in the organization, and in which
the information system is systematically
repaired and improved.
19. A standard process followed in an organization to conduct all the steps necessary to
analyze, design, implement, and maintain
information systems.
20. The series of steps used to mark the
phases of development for an information
system.
21. The process of breaking the description
of a system down into small components;
also known as functional decomposition.
22. Dividing a system up into chunks or modules of a relatively uniform size.
23. The extent to which subsystems depend on
each other.
24. The extent to which a system or subsystem
performs a single function.
25. Software tools that provide automated
support for some portion of the systems
development process.
26. A centralized database that contains all
diagrams, forms and report definitions,
data structures, data definitions, process
flows and logic, and definitions of other
organizational and system components; it
provides a set of
data-to-data integration.
27. Systems development methodology created to radically decrease the time needed
to design and implement information
systems.
28. Current approaches to systems
development that focus on adaptive
methodologies, people instead of roles,
and an overall self-adaptive development
process.
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
