3AIS1 SYSTEM DEVELOPMENT LIFE CYCLE

studied byStudied by 0 people
0.0(0)
learn
LearnA personalized and smart learning plan
exam
Practice TestTake a test on your terms and definitions
spaced repetition
Spaced RepetitionScientifically backed study method
heart puzzle
Matching GameHow quick can you match all your cards?
flashcards
FlashcardsStudy terms and definitions

1 / 37

flashcard set

Earn XP

Description and Tags

Week 3-4

38 Terms

1

Enterprise Data Model

• Establishes the range and general contents of organizational databases.

• Create an overall picture or explanation of organizational data, not the design for a particular database.

• Specifies scope and general content

New cards
2

Information System

• Resources that enable information collection, management, control, and dissemination throughout an organization

New cards
3

Information System Architecture

• A conceptual blueprint or plan that expresses the desired future structure for the information systems in an organization.

New cards
4

System Development Life Cycle

• The traditional methodology used to develop, maintain, and replace information systems.

• is a conceptual model that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application

New cards
5

Waterfall Model

is the first SDLC method and is often considered the classic approach to systems development, which describes a development method that is linear and sequential.

New cards
6

Feasibility Study

can be considered as preliminary investigation that helps the management to take decision about whether study of system should be feasible for development or not.

- it identifies the possibility of improving an existing system, developing a new system, and produce refined estimates for further development of system.

- It is used to obtain the outline of the problem and decide whether a feasible or appropriate solution exists or not.

New cards
7

Objective of a Feasibility Study

to acquire problem scope instead of solving the problem.

New cards
8

Output of a Feasibility Study

is a formal system proposal act as decision document which includes the complete nature and scope of the proposed system.

New cards
9

Economic Feasibility

• Assesses a system's costs and benefits

• Team tallies tangible development and operating costs for the system and compares them with expected financial benefits of the system

• Keep in mind that an information system project that's feasible at the outset could become unfeasible later

New cards
10

Technical Feasibility

Concerned with technology to be used in the system

• Team needs to assess whether technology to support the new system is available or feasible to implement

• Lack of technical feasibility

- Can also stem from an organization lacking the expertise, time, or personnel to implement the new system

New cards
11

Operational Feasibility

Measure of: - How well the proposed solution will work in the organization - How internal and external customers will react to it • "Is the information system worth implementing?"

New cards
12

Schedule Feasibility

Whether the new system can be completed on time

New cards
13

Legal Feasibility

Concerned with legal issues

New cards
14

Conceptual Modeling

- The analyst develops a diagram and other documentation to outline the scope of data involved in this particular development project without considering what databases already exist

New cards
15

Conceptual schema

A detailed, technologyindependent specification of the overall structure of organizational data.

New cards
16

Logical Schema

The representation of a database for a particular data management technology.Physical schema

New cards
17

Physical Schema

is a set of specifications that describe how data from a logical schema are stored in a computer's secondary memory by a specific database management system.Corrective maintenance

New cards
18

Corrective Maintenance

Changes made to a system to repair flaws in its design, coding, or implementation

New cards
19

Adaptive Maintenance

Changes made to a system to evolve its functionality to changing business needs or technologiesPerfective maintenance

New cards
20

Perfective Maintenance

Changes made to a system to add new features or to improve performanceChanges made to a system to add new features or to improve performance

New cards
21

Preventive Maintenance

Changes made to a system to avoid possible future problemsPilot

New cards
22

Pilot

In this method, a working version of the system is implemented in one part of the organization, such as a single work area or a single department.

New cards
23

Phase

The phased method of conversion introduces the new system gradually.

New cards
24

Parallel

The phased method of conversion introduces the new system gradually.

This method is the safest conversion method since it guarantees that, should problems such as errors in processing or inability to handle certain types of transactions arise in using the new system, the organization can still fall back to the old system without loss of time or loss of service

New cards
25

Plunge

• The phased method of conversion introduces the new system gradually.

• It can be used when installing a new system throughout an organization is impossible all at once.

New cards
26

Rapid Application Development

• The initial emphasis is on creating a prototype that looks and acts like the desired product in order to test its usefulness.

New cards
27

Joint Application Development

a methodology that involves the end-users or clients in the design and development of an application, through a succession of collaborative workshops.Spiral Model

New cards
28

Spiral Model

combines the features of the prototyping model and the waterfa II model. The spira I model is favored for large, expensive, and complicated projects.

New cards
29

V Model

It is considered to be the extension of the waterfall model, but instead of moving down, the process is bent upwards after the coding stage to form the V shape.

• defines a uniform procedure for systems development wherein system validation is carried out through activities that occur throughout the entire development.

New cards
30

Synchronize and Stabilize Model

allows teams to work in parallel on individual application modules, frequently synchronizing their code with that of other teams and debugging (stabilizing) code regularly throughout the development processPrototyping

New cards
31

Prototyping

Is the rapid development and testing of working models of new applications in an interactive, iterative process that can be used by both IS specialists and business professionals

New cards
32

Agile Methods

• Less emphasis on team coding and more emphasis on limiting the project's scope • Focuses on setting a minimum number of requirements and turning them into a working product • Agile Alliance organization - Manifesto contains principles for this methodologySCRUM Methodology

New cards
33

SCRUM Methodology

a management framework that teams use to self-organize and work towards a common goal. It describes a set of meetings, tools, and roles for efficient project delivery.

New cards
34

KANBAN Methodology

an agile method that aims at continuous improvement, flexibility in task management, and enhanced workflow

New cards
35

Programmers

These individuals design and write computer programs with commands to maintain and access data in the embedded database

New cards
36

Database architects

These individuals establish standards for data in business units, striving to attain optimum data location, currency, and quality.

New cards
37

Data administrators

These individuals have responsibility for existing and future databases and ensure consistency and integrity across databases, and as experts on database technology, provide consulting and training to other project team members.

New cards
38

Project Managers

- Project managers oversee assigned projects, including team composition, analysis, design, implementation, and support of projects.

New cards
robot