CIS 3060 Systems Analysis and Design Midterm #1 Vocabulary

Vocabulary practice flashcards covering concepts from the CIS 3060 Systems Analysis and Design study guide.

Systems Development Life Cycle (SDLC)

Process of developing an IS that supports business needs.

Development methodology

Approach to implementing the SDLC.

Structured design

A formal step-by-step approach to the SDLC that moves logically from one phase to the next.

Phased development

Breaks the system into a series of versions that are developed sequentially. A version consists of the implementation of a subset of the requirements.

Prototyping

Development centers on refining a system prototype over several cycles. A system prototype consists of a rudimentary implementation of the system.

Object-oriented Systems Analysis and Design (OOSAD)

Organizes requirements around objects, which integrate behaviors (processes) and data modeled after real-world entities with which the system interacts.

Agile Development

Methodologies based on the agile manifesto that focus on addressing changing requirements instead of detailed development processes and all-inclusive documentation.

Extreme Programming

An agile framework that focuses on appropriate engineering practices for software development, such as testing and efficient coding practices, where code is tested frequently and placed into an integrative testing environment.

Scrum

An agile framework that encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve.

Business Value

Refers to the benefits to the business obtained from the information system.

Tangible benefits

Measurable and quantifiable outcomes that can often be estimated before a system is implemented.

Intangible benefits

Less concrete gains that are harder to predict and measure in advance, but still crucial to justify system development.

System request

A document describing the business reasons for building a system and the value the system is expected to provide.

Requirements Determination

Aims to turn a high-level explanation of the system stated in the system request into a more precise list of requirements.

Requirement

A statement of what the system must do or what characteristics it must have.

Functional quality

The degree to which the system meets the functional requirements.

As-is system

The current system.

To-be system

The new system.

Functional models

Models that describe business processes and the interaction of an information system with its environment, providing an external view by showing how users view the system rather than internal mechanisms.

Use case

Describes how an external user (actor) interacts with the system to achieve a specific goal, defining a functional scenario from the user's perspective.

Activity diagram

Models the behavior in a business process, which can be used to model everything from a high-level business workflow involving many use cases to the details of an individual use case.

Use-case diagram

Illustrates in a simple way the main functions of the system and the different kinds of users that will interact with it.

Logical models

Models (such as activity and use-case diagrams) that describe the business domain's activities without suggesting how they are conducted or whether an activity is computerized or manual.

Structural model

Describes the structure of the information that supports the business processes carried out by the system, presenting logical organization during analysis without indicating how it is stored, created, or manipulated.

Object

Represents information captured by the system, such as people, places, or events like meetings and appointments.

Class diagram

A static model that shows the classes and the relationships among classes that remain constant in the system over time.

Class

A template used to create objects (specific instances) in the problem domain, where all objects of a given class are identical in structure and behavior but contain different data in their attributes.

Problem domain

Refers to the business areas affected by the information system.

Attribute

Represents a piece of information or state relevant to the description of an analysis class within the problem domain.

Operation

Defines the behavior of an analysis class.