Chapter 6 - Moving Into Design

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/29

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 9:47 AM on 4/18/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

30 Terms

1
New cards

Design Phase

Determines how the new system will operate using requirements gathered during analysis to create a system blueprint.

2
New cards

Purpose of Analysis Phase

Figure out what the business needs.

3
New cards

Purpose of Design Phase

Figure out how to build the system.

4
New cards

System Specification

Final deliverable of design phase containing all design documents for approval.

5
New cards

Business vs System Requirements

Business requirements explain why the system is built; system requirements explain how it will be built.

6
New cards

System Requirements

Technical details that form the blueprint of the system.

7
New cards

System Design

Process of determining overall system architecture including hardware, software, people, and communication.

8
New cards

Redesigned Workflows and Procedures

Updated processes included in the system and communicated through training and user documentation.

9
New cards

Alternative Matrix

Tool used to compare different system solutions in the design phase.

10
New cards

Architecture Design

Defines system structure and converts nonfunctional requirements like performance and security into system design.

11
New cards

Hardware and Software Specification

Document describing required hardware and software for the system.

12
New cards

Interface Design

Design of system inputs, outputs, and navigation flow.

13
New cards

Physical Process Model

Shows how system processes operate in reality and supports system functionality.

14
New cards

Program Specifications

Detailed instructions for programmers to build the system.

15
New cards

Physical Data Model

Defines how data is stored physically in the system.

16
New cards

CRUD Matrix

Tool showing Create, Read, Update, Delete relationships between processes and data.

17
New cards

Data Storage Design

Specifies how and where data will be stored in the system.

18
New cards

Custom Development

Building a system from scratch with full control and flexibility.

19
New cards

Custom Development Advantages

Allows customization, builds internal skills, and solves unique problems.

20
New cards

Custom Development Disadvantages

Time-consuming, requires skilled team, risk of failure, and existing workload issues.

21
New cards

Packaged Software

Pre-built software that organizations can purchase or license.

22
New cards

ERP Systems

Integrated systems that automate multiple business processes (e.g., SAP, Oracle, Infor).

23
New cards

Packaged Software Limitation

May not fully match business needs and requires adaptation.

24
New cards

Workaround

Custom add-on created to extend packaged software functionality; not supported by vendors.

25
New cards

Systems Integration

Combining packaged software, legacy systems, and new software into one system.

26
New cards

Systems Integration Challenge

Difficulty in making different systems communicate and share data properly.

27
New cards

Outsourcing

Hiring external vendors to develop or provide systems.

28
New cards

Outsourcing Advantages

Lower cost, faster setup, reduced need for in-house staff and infrastructure.

29
New cards

Outsourcing Risks

Loss of control, data security risks, and reduced internal skill development.

30
New cards

Outsourcing Risk Management

Understand requirements and choose reliable vendors with proven track records.