Architecture Design and User Interface Principles

Architecture Design

Plan for distributing system components across computers.

Data Storage

Storage and retrieval of information in IS.

Data Access Logic

Processing required to access stored data.

Application Logic

Logic documented in DFD's use cases.

Presentation Logic

Display of information and user command acceptance.

Client Computers

Input-output devices used by end users.

Servers

Larger computers for data storage and processing.

Network

Connects client computers and servers.

Client Server Architecture

Balances processing between clients and servers.

Thick Client

Contains most application logic on client side.

Thin Client

Contains minimal application logic on client side.

Middleware

Software translating between different vendor systems.

Two-Tiered Architecture

Client handles application; server manages data.

Three-Tiered Architecture

Uses three computers for presentation, application, data.

n-Tier Architecture

Distributes application work among specialized servers.

Server-Based Architecture

Server performs all application functions.

Zero Client

Ultrathin client for virtual desktop infrastructure.

Rich Client

Processes data using mobile device resources.

Thin Web-based Client

Business logic resides on the server side.

Rich Internet Application

Browser-based with enhanced client-side technologies.

Native Apps

Designed for specific devices and operating systems.

Cross-Platform Frameworks

Develops web technologies for multiple device deployment.

Mobile Web App

Browser-based, platform-independent application.

Virtualization

Combines multiple storage devices into one unit.

Server Virtualization

Partitions physical server into smaller virtual servers.

Storage Virtualization

Combines multiple storage devices into one device.

Storage Area Network

High-speed subnetwork of shared storage devices.

Cloud Computing

Delivers computing resources as a service.

Application Program Interfaces (API)

Standardizes communication between programs and data sources.

Elasticity

Resources can be adjusted quickly based on demand.

Standardized APIs

Uniform interfaces for cloud service interactions.

Billing Model

Customers pay only for resources used.

Operational Requirements

Conditions for effective system operation.

Performance Requirements

Criteria for system speed, capacity, and reliability.

Security Requirements

Measures for protecting system data and access.

Encryption

Disguising information using mathematical algorithms.

Symmetric Encryption

Same key for encrypting and decrypting data.

Asymmetric Encryption

Different keys for encrypting and decrypting data.

User Interfaces

Methods for users to interact with systems.

System Interface

Information exchange between systems.

Navigation Mechanism

User instructions for system actions.

Input Mechanism

System method for capturing user information.

Output Mechanism

System method for delivering information to users.

Graphical User Interface (GUI)

Most common interface type today.

Human-Computer Interaction (HCI)

Improving user-computer interaction usability.

User Experience (UX)

Focus on user feelings and satisfaction.

Usability Concept

System should be easy to use and learn.

Interface Structure Design (ISD)

Defines components and functionality of interface.

Interface Metaphor

Real-world concept used in information systems.

Interface Prototyping

Mock-up of screens and reports for testing.

Heuristic Evaluation

Interface assessment against design principles.

Usability Testing

Evaluating user tasks without team assistance.

Online Processing

Real-time input transaction processing.

Batch Processing

Processing collected inputs at once.

Source Data Automation

Using technology to capture data efficiently.

Input Validation

Ensuring accuracy of user inputs.

Detail Report

Lists detailed information about items requested.

Summary Report

Presents summarized information about items.

Data Storage Formats

Methods for organizing and storing data.

Database

Collection of related information groupings.

Capture Data at the Source

Collects data directly to minimize errors and costs.

Output Design

Presents information clearly for user comprehension.

Turnaround Document

Outputs that are reused as inputs in processing.

Graphs

Visual representations of data, enhancing understanding.

Files

Optimized electronic lists for specific transactions.

DBMS

Software for creating and managing databases.

Enterprise DBMS

Handles large data volumes for entire organizations.

Master Files

Core information essential for business operations.

Transaction Files

Records used to update master files with changes.

Audit Files

Log changes to data for review and compliance.

Relational Databases

Most common database type for application development.

Primary Key

Unique identifier for each record in a table.

Foreign Key

Links tables by referencing primary keys from others.

Referential Integrity

Ensures valid relationships between linked tables.

SQL

Standard language for managing relational databases.

Object Databases

Treats data as objects with attributes and behaviors.

Data Warehousing

Stores transformed data for business intelligence use.

NoSQL Databases

Handles large, varied data sets, supporting unstructured data.

Logical ERD

Visualizes business data relationships without implementation details.

Physical Data Models

Shows implementation details of data structures.

Programming Task Assignment

Groups related modules for assignment based on skills.

Skill Deficiencies

Identified gaps in programmer capabilities requiring training.

System Development

More programmers increase project duration.

Project Splitting

Divide complex projects into smaller parts.

Coordinating Activities

Weekly meetings discuss system changes.

Development Area

Workspace for coding and programming tasks.

Testing Area

Dedicated space for system testing activities.

Production Area

Environment for deploying completed systems.

Change Control

Manage program changes during construction.

Program Log

Form for tracking program modifications.

Scope Creep

New requirements added post-design finalization.

Critical Path

Tasks affecting project completion date.

Testing

Insurance against major system failures.

Test Plan

Outline of tests to be conducted.

Stub Testing

Use stubs for unfinished modules testing.

Unit Tests

Focus on testing individual program modules.

Black-Box Testing

Tests based on program specifications.

White-Box Testing

Tests actual code for complex scenarios.

Integration Tests

Verify modules work together without errors.

Security Testing

Ensure proper handling of security functions.