CMIS 270 Exam 1 Study guide

studying the current system, and determining what the new requirements are going to be, along with determining alternate designs that meet the need of the end user

Analysis

a non detailed description of the solution to the problem

Analysis deliverable

limit to what they system can accomplish

Constraints

everything external to the system

Environment

functional features of the system are chosen

Logical Design

Samples of screenshots, reports, or websites to be created

Logical design deliverable

Documentation of fixes and troubleshooting

Maintenance deliverable

the logic from the previous step is turned into technological details, from this, programming and system creation can be accomplished

Physical design

A data dictionary

Physical design deliverable

-Focus: what the system is to do and how -Organization: data files designed for each application -State of data: much duplication and redundancy -Stability: limited - more inaccuracy

Process oriented information system

weighing the options of each project and choosing the one you think would be best determining what resources would be needed for each

Project identification

looking into the problem to see potential ways to fix it.

Project initiation

what system takes to fulfill purpose

Inputs

points where the system meets the environment

Interface

components dependent on another

Interrelationships

establishes the limits of the system

boundary

identifies they financial benefits and costs associated with the project

economic feasibility

likelihood project will attain its desired objectives

operational feasibility

understanding how the organizations would react to the new system (how would stakeholders and employees view it. Job loss for employees?)

organizational and cultural feasibility

set which can't be broken down

components/subsystem

-Focus: on the data the system needs to operate -Organization: Data files designed for organization -State of data: limited duplication and redundancy -Stability: more accurate and enduring

data oriented information systems

ramifications of any possible legal actions, and will the system comply with laws?

legal/contractual feasibility

working out bugs, applying changes, and starting these steps all over again

maintenance

Lists of projects to be undertaken

project identification deliverable

scope statement, project schedule plan

project initiation deliverable

do we have what we need or can we get it?

resource feasibility

deadlines and resource constraints

schedule feasibility

•Project identification and selection •Project initiation and planning •Analysis •Logical design •Physical design •Implementation •Maintenance

system development lifecycle stages (in order)

- 4 factors a. Project size b. Project structure c. The development groups experience with the application and technology area d. The user group's experience with development projects and application data

technical feasibility

analyzing those demands from the end user and brainstorming things like requirements for the system

agile - analysis

receiving feedback and providing a demo for the end users. Then do a retrospective and look back on the project to see if there are any improvements to be made

agile - demo

Actual building of the system takes place here

agile - do

Design team plans the system, tackling the highest priority items first

agile - estimate and plan

communicating with the end user to get and idea of what kind of system they want built.

agile - market

Setting an order to which components of the system are most important

agile - prioritize

•Market •Analysis •Prioritize •Estimate and plan •Do •Demo

agile method stages (in order)

1. economic 2. organizational and cultural 3.technical 4. schedule 5. resource 6. operational 7. legal/ contractual

7 categories of feasibility

1. Purpose 2. Boundary 3. Environment 4. Interface 5. Inputs 6. Components/subsystems 7. Interrelationships 8. Outputs 9. Constraints

9 characteristics of a system

should fulfill the purpose of the system

Outputs

Overall goal or function

Purpose (characteristic of a system)

• Analytical • Technical • Interpersonal • Business • Managerial

5 roles of a system analyst

coding, testing, and installation, the true system building takes place here

Implementation

user manuals, actual code, test plans, user documentation, system documentation

Implementation deliverable

data and process oriented

types of information systems