IS 385 Final

OOD & UML, Output, Input, Database, UI, UX, Implementation, Quality Management, Maintenance

Object-oriented analysis and design (OOAD)

A systems development approach that views a system as a collection of interacting objects that combine data (attributes) and behavior (methods), and models these using object-oriented principles.

Object

A specific instance of a class that encapsulates data about something in the real world and the operations that can be performed on that data.

Class

A template or blueprint that defines a group of similar objects with common attributes, behavior (methods), and relationships.

Attribute

A data element that describes a property or characteristic of a class or object (for example, CustomerName, OrderDate).

Method (operation)

An action or function that an object can perform or that can be performed on an object; it defines the behavior of the class.

Encapsulation

The object-oriented principle of bundling data and methods together within a class and hiding internal details from other objects through a well-defined interface.

Inheritance

A mechanism that lets a new class (subclass) reuse and extend the attributes and methods of an existing class (superclass).

Polymorphism

The object-oriented ability for different classes to respond to the same message (method call) in different, class-specific ways.

Message passing

The object-oriented concept in which one object sends a message to another object to request that a method be executed.

Unified Modeling Language (UML)

A standardized visual modeling language used to specify, visualize, construct, and document an object-oriented information system.

UML “thing”

A fundamental modeling element in UML (such as a class, use case, node, or interface) that represents a concept, object, or relationship in the system.

UML relationship

A connection between UML things (e.g., association, aggregation, generalization, dependency) that describes how elements interact or depend on each other.

Structural diagram (UML)

A UML diagram type that shows the static structure of the system, such as classes, objects, and their relationships.

Behavioral diagram (UML)

A UML diagram type that shows dynamic aspects of the system, such as interactions and changes over time (e.g., sequence, activity, statechart).

Use case

A description of how an external actor interacts with the system to achieve a specific goal or business task.

Use case diagram

A UML behavioral diagram that shows actors, use cases, and their relationships to illustrate the system’s functional scope.

Actor (UML)

A person, organization, external system, or device that interacts with a system and participates in one or more use cases.

Use case scenario

A text-based narrative that describes the typical flow of events for a use case, including inputs, actions, and outputs.

Activity diagram

A UML behavioral diagram that models the flow of activities, decisions, and parallel processes within a use case or business process.

Class diagram

A UML structural diagram that shows classes, their attributes and methods, and the relationships among classes.

Sequence diagram

A UML interaction diagram that shows objects, the messages they exchange, and the time ordering of those messages along a vertical time axis.

Communication diagram

A UML interaction diagram that emphasizes the structural organization of objects that send and receive messages to carry out a behavior.

Statechart diagram

A UML behavioral diagram that shows the possible states of an object and the events that trigger transitions between those states.

Package (UML)

A grouping mechanism in UML used to organize related classes, diagrams, or other modeling elements into higher-level containers.

Aggregation

A whole–part relationship between classes where the “whole” is composed of “parts,” but the parts can exist independently of the whole.

Composition

A strong form of aggregation in which the parts cannot meaningfully exist without the whole; if the whole is destroyed, the parts are too.

Association

A structural relationship between two classes indicating that their objects are connected in some way (for example, Customer “places” Order).

Generalization

A UML relationship that models “is-a” hierarchies where a more specific subclass inherits from a more general superclass.

CRC card (Class–Responsibility–Collaborator)

A simple analysis tool where each index card represents a class, its responsibilities, and its collaborating classes.

Repository (model repository)

A central storage location for UML diagrams, specifications, and related project artifacts used to keep models consistent.

Iterative UML process

An approach where analysts progressively refine UML diagrams (use case, activity, sequence, class, statechart) in repeated cycles of analysis and design.

System output

Information produced by an information system and delivered to users via reports, screens, mobile devices, audio, or other media.

Output design objectives

The key goals for output: serve the intended purpose, fit the user, deliver the right quantity, be available where needed, arrive on time, and use an appropriate method.

Designing output to fit the user

Customizing format, detail, and delivery method so that different user groups can easily interpret and use system output.

Output content

The specific data and information items included in a report or display, chosen to support a user’s decision or task.

Output method

The medium used to deliver output, such as printed reports, screens, mobile apps, audio, or electronic documents.

Hard copy output

Output printed on paper (for example, reports, listings, labels) that can be carried, filed, or marked up by users.

Soft copy output

Non-printed output such as screens, web pages, dashboards, and audio or video that is viewed electronically.

Display screen output

Output presented on desktop or laptop monitors, often interactive and suitable for frequently accessed and short-lived information.

Mobile device output

Output formatted for smartphones or tablets, emphasizing concise content, icons, gestures, and responsive layouts.

Audio output / podcasts

Spoken or sound-based output used when users need their hands free or when text displays are impractical.

Electronic output

Output delivered through email, websites, blogs, or RSS feeds; easy to update and broadcast but sometimes less structured.

Output bias

Unintentional distortion in how output is presented, leading users to misinterpret results, for example through selective data or misleading scales.

Dashboard

A screen display that consolidates key performance indicators and summary information to support quick decision making.

Infographic

A visually rich display that combines charts, icons, images, and short text to tell a data-driven story at a glance.

Responsive Web design

A design approach that allows a website to adapt to different devices and screen sizes while preserving content and functionality.

Skeuomorphic design

A style that mimics real-world objects using 3-D effects and shadows; now often replaced by flatter designs.

Flat Web design

A clean, two-dimensional design style that uses simple shapes and bright colors, avoiding heavy shadows and realism.

Web 2.0 technologies

Social and collaborative web technologies (e.g., blogs, wikis, social networks) that enable users to create, share, and comment on content.

Social media output

Information and content published on social platforms that supports communication, branding, and collaboration.

Stickiness (website)

The ability of a website or app to attract users and keep them engaged so that they spend more time and return frequently.

App (mobile application)

A small, focused software program for smartphones or tablets, often downloaded from an app store and designed for quick, specialized tasks.

Green IT for output

Practices that reduce environmental impact by limiting unnecessary printing, encouraging electronic output, and managing energy use of devices.

System input

Data that users or devices enter into an information system to be processed into information.

Input design objectives

Goals for input design: effectiveness, accuracy, ease of use, consistency, simplicity, and attractiveness.

Effective input

Input forms and screens that capture exactly the data needed for the system to perform required functions.

Accurate input

Input design that minimizes errors through clear labels, validation checks, and well-structured fields.

Easy-to-use input

Input forms or screens that users can complete quickly without confusion or excessive training.

Consistent input design

Using similar layout, grouping, and behavior for input forms across the system so users can transfer knowledge between screens.

Simple input layout

Designing uncluttered forms that focus the user’s attention on essential fields and steps.

Attractive input

Using fonts, spacing, and visual structure to make forms appealing so users feel comfortable completing them.

Form (paper or web)

A structured document with spaces for users to enter data; often serves as the source document for computer input.

Good form design

Following guidelines to make forms easy to fill in, fit their purpose, ensure accurate completion, and remain visually appealing.

Source document

An original paper or electronic document that records data at its point of origin and is later used for input to the system.

Turnaround document

Output that is later returned as input, for example a bill with a tear-off portion that customers send back.

Web-based fill-in form

An online form that collects data via a browser and submits it directly to a database or transaction system.

Input validation

Automatic checks applied to fields, such as type, range, and presence, to ensure that data entered meets predefined rules.

Edit mask

A pattern applied to a field that controls the format of data input, such as dates or phone numbers.

Default value

A value automatically supplied for a field, which users can accept or change, reducing keystrokes and errors.

Error message (input)

Feedback to the user explaining why input is invalid and how to correct it; should be clear, specific, and non-punitive.

Incomplete web form handling

The practice of returning a form when required fields are missing, highlighting errors and explaining what must be completed.

Navigation element

A standard control, such as a menu bar, back button, or home icon, that helps users move between input pages or sections.

Hamburger menu

A three-bar icon that opens a navigation menu, commonly used in mobile and web interfaces.

Breadcrumb trail

A navigation aid showing a user’s path or page hierarchy, allowing quick jumps back to earlier pages.

Fat footer

A large, information-rich footer area at the bottom of a page that provides navigation links and key information.

Database

An organized collection of related data stored for convenient access, management, and updating.

Database management system (DBMS)

Software used to define, create, maintain, and control access to a database.

Relational database model

A database model that organizes data into two-dimensional tables (relations) with rows and columns.

Table (relation)

A set of rows and columns representing data about one entity type in a relational database.

Row (tuple)

A single record in a table, representing one instance of an entity.

Column (attribute)

A named field in a table that stores a specific type of data for all rows.

Primary key

A field or combination of fields that uniquely identifies each row in a table.

Foreign key

A field in one table that is the primary key of another table, used to represent relationships between tables.

Concatenated (composite) key

A primary key made up of two or more fields used together to uniquely identify a row.

Entity–relationship (E-R) diagram

A graphical model that shows entities, their attributes, and the relationships among them.

One-to-many relationship

A relationship where one instance of an entity can be associated with many instances of another entity, such as one Customer to many Orders.

Many-to-many relationship

A relationship where many instances of one entity can relate to many instances of another; typically decomposed into two one-to-many relationships using an associative entity.

Normalization

A process of organizing fields and tables in a database to reduce redundancy and avoid update anomalies.

Unnormalized form

A table structure that may contain repeating groups or multi-valued attributes, not yet suitable for efficient processing.

First normal form (1NF)

A table design in which there are no repeating groups and each field contains only atomic (indivisible) values.

Second normal form (2NF)

A design that is in 1NF and in which every non-key attribute depends on the whole primary key, not just part of it.

Third normal form (3NF)

A design that is in 2NF and in which all non-key attributes depend only on the primary key and not on other non-key attributes.

Functional dependency

A relationship where the value of one attribute determines the value of another attribute.

Data redundancy

The unnecessary duplication of data in multiple places, which can lead to inconsistencies and larger storage requirements.

Update anomaly

A data inconsistency caused by redundant data being updated in some places but not others.

Insert anomaly

A situation where certain facts cannot be stored because other required data is missing.

Delete anomaly

Unintended loss of data when a row is deleted because it contained multiple facts.

Data warehouse

A large, subject-oriented, integrated, time-variant, and non-volatile collection of data used primarily for decision support and analytics.

Data mart

A smaller, focused subset of a data warehouse tailored to the needs of a specific department or business function.

Denormalization

The intentional introduction of redundancy into a database, often in data warehouses, to improve query performance.