Ist Test 3- Chpt 10

Front 1

Systems development life cycle (SDLC)

Back 1

also known as the "waterfall model," is a series of well-defined phases performed in sequence that serves as a framework for developing a system or project

Front 2

Planning Phase

Back 2

one of the most crucial phases of the SDLC model, during this phase the systems designer must understand and define the problem the organization faces, taking care not to define the symptoms rather than the underlying problem.

Front 3

Internal Users

Back 3

are employees who will use the system regularly, and they can offer important feedback on the system's strengths and weaknesses.

Front 4

External Users

Back 4

aren't employees but do use the system; they include customers, contractors, suppliers, and other business partners. Although they aren't normally part of the task force, their input is essential.

Front 5

Joint application Design (JAD)

Back 5

a collective activity involving users, top management, and IT professionals. It centers on a structured workshop (called a JAD session) where users and system professionals come together to develop an application. It involves a detailed agenda, visual aids, a leader who moderates the session, and a scribe records the specifications. It results in a final document containing definitions for data elements, work-flows, screens, reports, and general systems specifications.

Front 6

Feasibility Study

Back 6

analyzes a proposed solution's feasibility and determines how best to present the solution to management. It usually has five major dimensions: economic, technical, operational, scheduling, and legal.

Front 7

Economic feasibility

Back 7

assesses a system's costs and benefits.

Front 8

Technical feasibility

Back 8

is concerned with technology to be used in the system. The team needs to assess whether technology to support the new system is available or feasible to implement.

Front 9

Operational feasibility

Back 9

is the measure of how well the proposed solution will work in the organization and how internal and external customers will react to it.

Front 10

Scheduling feasibility

Back 10

is concerned with whether the new system can be completed on time.

Front 11

Legal feasibility

Back 11

is concerned with legal issues, including political repercussions and meeting the requirements of the Information Privacy Act.

Front 12

Requirements-Gathering and Analysis Phase

Back 12

analysts define the problem and generate alternatives for solving it.

Front 13

Design Phase

Back 13

analysts choose the solution that's the most realistic and offers the highest payoff for the organization. Details of the proposed solution are outlined, and the output of this phase is a document with exact specifications for implementing the system, including files and databases, forms and reports, documentation, procedures, hardware and software, networking components, and general system specifications.

Front 14

Computer-aided systems engineering (CASE)

Back 14

tools automate parts of the application development process. These tools are particularly helpful for investigation and analysis in large-scale projects because they automate parts of the design phase.

Front 15

Prototyping

Back 15

a small-scale version of the system is developed, but one that's large enough to illustrate the system's benefits and allow users to offer feedback.

Front 16

Proof-of-concept Prototype

Back 16

shows users how a particular task that wasn't technically feasible can be done.

Front 17

Selling Prototype

Back 17

is used to sell a proposed system to users or management by showing some of its features.

Front 18

Implementation Phase

Back 18

during this, the solution is transferred from paper to action, and the team configures the system and procures components for it.

Front 19

Parallel Conversion

Back 19

the old and new system run simultaneously for a short time to ensure that the new system works correctly.

Front 20

Phased-in-phased-out conversion

Back 20

as each module of the new system is converted, the corresponding part of the old system is retired. This process continues until the entire system is operational.

Front 21

Plunge (direct cutover) Conversion

Back 21

the old system is stopped and the new system is implemented.

Front 22

Pilot Conversion

Back 22

the analyst introduces the system in only a limited area of the organization, such as a division or department. If the system works correctly, it's implemented in the rest of the organization in stages or all at once.

Front 23

Request for Proposal (RFP)

Back 23

is a written document with detailed specifications used to request bids for equipment, supplies, or services from vendors.

Front 24

Request for information (RFI)

Back 24

is a screening document for gathering vendor information and narrowing the list of potential vendors. It can help manage the selection of vendors by focusing on the project requirements that are crucial to selecting vendors.

Front 25

Insourcing

Back 25

happens when an organization's team develops the system internally.

Front 26

Self-sourcing

Back 26

is when end users develop their own information systems with little or no formal assistance from the information system team. These users might not know how to write programming code but are typically skilled enough to use off-the-shelf software, such as spreadsheet and database packages, to produce custom-built applications.

Front 27

Outsourcing

Back 27

an organization hires an external vendor or consultant who specializes in providing development services.

Front 28

Crowdsourcing

Back 28

the process of outsourcing tasks that are traditionally performed by employees or contractors to a large group of people (a crowd) through an open call.

Front 29

Maintenance Phase

Back 29

the information system is operating, enhancements and modifications to the system have been developed and tested, and hardware and software components have been added or replaced.

Front 30

Service-oriented architecture (SOA)

Back 30

is a philosophy and a software and system development and methodology that focuses on the development, use, and reuse of small, self-contained blocks of codes (called services) to meet the software needs of an organization.

Front 31

Rapid Application Development (RAD)

Back 31

concentrates on user involvement and continuous interaction between users and designers. It combines the planning and analysis phases into one phase and develops a prototype of the system. It uses an iterative process (also called "incremental development") that repeats the design, development, and testing steps as needed, based on feedback from users.

Front 32

Extreme Programming (XP)

Back 32

divides a project into smaller functions, and developers can't go on to the next phase until the current phase is finished. Each function of the overall project is developed in a step-by-step fashion.

Front 33

Pair programming

Back 33

is where two programmers participate participate in one development effort at one workstation. Each programmer performs the action the other is not currently doing.

Front 34

Agile Methodology

Back 34

is similar to XP in focusing on an incremental development process and timely delivery of working software. However, there's less emphasis on team coding and more emphasis on limiting the projects scope.

Front 35

Agile Methodology

Back 35

is similar to XP in focusing on an incremental development process and timely delivery of working software. However, there's less emphasis on team coding and more emphasis on limiting the projects scope.