Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IT261 Systems Design - Illinois State University > Systems Design Chapter 02 > Flashcards

Systems Design Chapter 02 Flashcards

1
Q

Project

A

A planned undertaking that has a beginning and an end that produces a desired result or product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

SDLC - Systems Development Life Cycle

A

A process of building, deploying, using, and updating an information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Predictive Approach

A

an SDLC approach that assumes project can be planned & organized in advance and it is developed according to plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Adaptive Approach

A

flexible approach, assuming project cannot be planned in advance, must be modified as it progresses.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project Planning Phase

A

Identify scope of new system, ensure project is feasible, develop a schedule, resource plan, and budget for the remainder project

  1. Define Problem
  2. Produce Schedule
  3. Confirm Feasibility
  4. Staff Project
  5. Launch Project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Analysis Phase

A

Understand and document the business needs and the processing requirements of the new system. (discovery & understanding)

  1. Gather information
  2. Define Sys Requirements
  3. Build Prototypes for discovery of requirements
  4. Prioritize requirements
  5. Generate and evaluate alternatives
  6. Review recommendations with management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Design Phase

A

To design the solution system based on the reqirements defined and decisions made during analysis.

  1. Design & integrate network
  2. Design the application architecture
  3. Design the user interface
  4. Design the system interface
  5. Design & integrate the database
  6. Prototype for design details
  7. Design and integrate the system controls
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Implementation Phase

A

activities include programming, testing, and installing the system

  1. Construct software components
  2. Verify and test
  3. Convert data
  4. Train users and document the system
  5. Install the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Support Phase

A

Keep the system running. Not part of initial development but is considered part of the SDLC.

  1. Maintain the system
  2. Enhance the system
  3. Support the users
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Traditional SDLC Project Phases

A

Project planning, Analysis, Design, Implementation, and Support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Waterfall Model

A

Most predictive of SDLC approaches. Each phase is completed before starting next (still predictive)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Modified Waterfall Model

A

Sill predictive but phases overlap (still predictive)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Sprial Model

A

Adaptive SDLC approach that cycles over and over thru development activities till project is complete

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Prototype

A

premlimary working model showing some aspect of a larger system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Iteration

A

Development process in which work activities-analysis, design, implementation are done again and again on different system components. They are repeated til the system is closer to what is ultimately needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Sprial Model

A

Adaptive SDLC approach that cycles over and over thru development activities till project is complete

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Prototype

A

premlimary working model showing some aspect of a larger system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Iteration

A

Development process in which work activities-analysis, design, implementation are done again and again on different system components. They are repeated til the system is closer to what is ultimately needed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Project

A

A project with beginning and end that produces a result or product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Incremental Development

A

an approach that completes parts of a system in several iterations and then puts them into operation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Problem Domain

A

The area of the user’s business for whcih a system is being developed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Application

A

The portion of the new system that satisfies the user’s needs in the problem domain

23
Q

Help Desk

A

Support staff to assist users with technical or processing problems with the new system.

24
Q

System Development Methodology

A

Guidelines for completing every activity in the SDLC including models, tools, and techniques

25
Q

Model

A

representation of an important aspect of the real world

26
Q

abstraction

A

we abstract (seperate out) as aspect of particular importance to us.

27
Q

Models of system components

A
  1. flowchart
  2. data flow diagram (DFD)
  3. entity-relationship diagram (ERD)
  4. structure chart
  5. Use case diagram
  6. Sequence Diagram
28
Q

Models used to manage the development process

A
  1. Gantt chart
  2. Organizational hierarchy chart
  3. Financial analysis models - NPV, ROI
29
Q

Tools

A

Software support that helps create models or other components required in the project

Includes:

  1. Project Management apps
  2. Drawing/graphics apps
  3. Word processor/text editor
  4. visual modeling tool
  5. Integrated development environment
  6. database management application
  7. reverse engineer tool
  8. code generator tool
30
Q

Integrated Development Environments (IDE)

A

Tools that help programmers with a variety of programming tasks

31
Q

Visual Modeling Tools

A

Tools that help the analyst create and verify important system models, often generating program code

32
Q

Technique

A

Guidelines that help an analyst complete a system development activity or task

Includes:

  1. Stragegic Planning
  2. Project Management
  3. User Interviewing techniques
  4. Data Modeling
  5. Relational database design
  6. structured analysis
  7. Structured design
  8. Structured Programming
  9. Software testing
  10. Object oriented analysis and design tech
33
Q

Traditional Approach to Sys Dev

A

includes variations based on techniques used to develop systems with structured and modular programming. often reffered to as Structured System Development

34
Q

Structured Approach

A

System dev using structured analysis, design, and programming techniques

35
Q

Structured Program

A

program or prog module that has one beginning and one ending . Each step in the program execution consists of:

  1. Sequence of program statements
  2. Decision where one set of statements or another set of statements executes
  3. repetition of a set of statements
36
Q

Top Down Programming

A

dividing more complex programs into a hierarchy of program modules i.e. main line statement in php calling functions beneath

37
Q

Structured Design

A

Technique providing guidelines for deciding what the set of programs should be, what each program should accomplish and how the programs should be organized into a hierarchy. i.e. the many different parts of a payroll sys.

38
Q

Structure Chart

A

a graphical model showing the hierarchy of prgram modules from the structured design. visual representation of the payroll sys.

39
Q

Program Modules

A

i.e. enter time cards module, get employee pay rates. Loosely coupled means each module is as independant of the other mods as possible.

40
Q

highly cohesive

A

each module accomplishes one clear task

41
Q

Structured Analysis

A

technique used to define what processing the system needs to do, what data it needs to store and use, and what inputs and outputs are needed

42
Q

data flow diagram DFD

A

strucutred analysis model showing the inputs, processes, storage, and outputs of a system. i.e. university course diagram in book

43
Q

Entity-relationship diagram ERD

A

structured analysis and information engineering model of the data needed by a system. i.e. customer 1 - zero to many orders - 1 order to 1-many order items. (relationship view in access)

44
Q

Information Engineering

A

Traditional system development methodology thought to be more rigorous and complete than the structured approach because of its focus on strategic planning, data modeling, and automated tools

45
Q

OBJECT ORIENTED APPROACH

A

An approach to Sys Dev that views an info sys as a collection of interacting objects that work together to accomplish tasks

46
Q

Object

A

thing in the computer system that can respond to messages

47
Q

Object-oriented analysis OOA

A

Defining all types of object that work in the system and showing what user interactions, called use cases are required to complete tasks

48
Q

Object-oriented design OOD

A

defines all of the additional tyupes of objected necessary to communicate with people and devices in the system, shows how the objects interact to complete tasks, and refines the definition of each to of object so it can be implemented with a specific language or environment

49
Q

Object-oriented Programming OOP

A

Writing statements in a programming language to define what each type of object does, including the messages that the objects send to each other

50
Q

Class diagram

A

a graphical model used in the object oriented approache to show classes of objects in the system. i.e. customer/account/savings acct/checking acct diagram Shows one to many as well as hiarchy

51
Q

TREND - UP Process

A

Object oriented system development methodology offered by IBM’s Rational Software

52
Q

TREND - Extreme Programming XP

A

Sys dev approach that adapts techniques from many sources and add some new ideas. “lightweight” system methodology - keep it simple and efficient.

53
Q

TREND - SCRUM

A

The video from class. refers to rugby’s system for getting an out of play ball back into play. Similarities between the sport and sys dev app. Both quick adaptive and self organizing.

54
Q

Repository

A

database that stors info about the system in visual modeling tool including models, descriptions and references that link the models together.

IT261 Systems Design - Illinois State University (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions