click below
click below
Normal Size Small Size show me how
mgis finals!!!
| Term | Definition |
|---|---|
| Ethics | Study of moral choices and rules governing behavior, especially in organizational and professional contexts. |
| Morals vs Ethics | Morals = internal beliefs about right/wrong; Ethics = external rules or guidelines. |
| PAPA Framework | Privacy, Accuracy, Property, Accessibility — core ethical issues in IS. |
| Privacy (PAPA) | Who has the right to access personal information? |
| Accuracy (PAPA) | Who is responsible for correctness and reliability of data? |
| Property (PAPA) | Who owns information? Who should pay for its use? |
| Accessibility (PAPA) | Who is allowed to access information? Under what conditions? |
| Ethical Dilemma | A situation where every decision option compromises some ethical principle. |
| Utilitarian Approach | Choose the option producing the greatest good for the greatest number. |
| Rights Approach | Respect the rights of individuals when making decisions. |
| Fairness / Justice Approach | Treat all parties equally or fairly. |
| Common Good Approach | What decision best promotes community well-being? |
| Virtue Approach | Choose the action that aligns with good moral character. |
| Project | A temporary endeavor with a defined beginning and end that produces a unique product or service. |
| Triple Constraint | Scope, Time, Cost — changing one impacts the others. |
| Project Scope | Defines what is included and excluded in the project. |
| Work Breakdown Structure (WBS) | Hierarchical decomposition of a project into manageable tasks. |
| Critical Path | Sequence of tasks that determines minimum project duration; tasks have zero slack. |
| Project Failure Causes | Poor requirements, scope creep, unrealistic estimates, weak communication, lack of user involvement. |
| Nine PM Knowledge Areas | Scope, Time, Cost, Quality, HR, Communications, Risk, Procurement, Integration. |
| Project Manager Core Skills | Leadership, communication, coordination, and problem-solving. |
| Scope Creep | Uncontrolled expansion of project requirements without adjustments to time, cost, or resources. |
| Waterfall Model | Linear, sequential development approach with rigid phases; poor flexibility. |
| Problems with Waterfall | Slow feedback, late discovery of errors, difficult to adapt to change. |
| Agile Development | Iterative, flexible process with customer collaboration and frequent working increments. |
| Scrum | Agile framework using sprints, daily standups, backlogs, and a Scrum Master/Product Owner. |
| Sprint | Time-boxed cycle (usually 2–4 weeks) delivering a usable product increment. |
| Product Backlog | Prioritized list of all desired features, enhancements, or fixes. |
| Burndown Chart | Graph showing remaining work over time in a sprint. |
| Extreme Programming (XP) | Agile method emphasizing simplicity, frequent releases, and pair programming. |
| Open Source Development | Collaborative, community-driven approach where source code is publicly available. |
| Business Process | A structured set of activities that produce a specific outcome for customers or stakeholders. |
| BPM (Business Process Management) | Continuous approach to designing, analyzing, improving, and optimizing business processes. |
| Process Redesign (Reengineering) | Radical changes to improve cost, quality, speed, or customer satisfaction. |
| Enablers of BPM | Processes, metrics, IT tools, and organizational culture that support improvement. |
| BPMN | Graphical notation for modeling and communicating business processes. |
| Activity (BPMN) | A task performed in the process; represented by a rounded rectangle. |
| Gateway (BPMN) | Decision point where process flow splits or merges; diamond symbol. |
| Exclusive Gateway | Only one outgoing path is taken. |
| Parallel Gateway | Multiple parallel paths executed simultaneously. |
| Event (BPMN) | Start, intermediate, and end events that affect process flow; circle symbol. |
| Swimlanes / Pools / Lanes | Visual divisions showing roles, departments, or participants in a process. |
| Artifacts (BPMN) | Additional info such as notes or data objects. |
| Database | Organized collection of structured data stored electronically. |
| Table | Structure containing columns and rows for storing data. |
| Record | A single row representing one instance of an entity. |
| Attribute | A field describing a characteristic of a record. |
| Primary Key | Unique identifier for a record; cannot be null or duplicated. |
| Foreign Key | A field linking to a primary key in another table, creating relationships. |
| Normalization | Organizing data to reduce redundancy and improve data integrity. |
| Structured Data | Organized, table-friendly data like numbers and categories. |
| Unstructured Data | Data without a predefined model: videos, images, PDFs, emails, text. |
| Big Data | Very large, fast, diverse datasets requiring advanced tools; defined by Volume, Velocity, Variety. |
| NoSQL | Non-relational database systems designed for scale and unstructured data. |
| ACID | Atomicity, Consistency, Isolation, Durability — guarantees reliable database transactions. |
| Schema | Blueprint of database structure (tables, fields, relationships). |
| Query | Command requesting or manipulating database data (e.g., SQL SELECT). |
| Information Security | Protection of confidentiality, integrity, and availability of information. |
| CIA Triad | Confidentiality, Integrity, Availability. |
| Common Vulnerabilities | User error, OS flaws, network complexity, weak policies, lack of training. |
| Malware | Malicious software such as viruses, worms, ransomware, Trojans. |
| Phishing | Deceptive attempt to trick users into giving personal information. |
| Social Engineering | Manipulating people to compromise security systems. |
| Authentication | Verifying identity (passwords, biometrics, MFA). |
| Authorization | Giving permission to access resources after authentication. |
| First Line of Defense | People — training, awareness, behavior. |
| Second Line of Defense | Policies — acceptable use, access rules, security guidelines. |
| Third Line of Defense | Technology — firewalls, IDS/IPS, encryption. |
| Firewall | Security tool filtering network traffic to block unauthorized access. |
| SQL Injection | Attack where malicious SQL is inserted into input to manipulate a database. |
| Anscombe’s Quartet | Four datasets with identical stats but different shapes, proving why visualization matters. |
| Lie Factor | Ratio of size shown in graphic vs actual data value; should be close to 1. |
| Chartjunk | Unnecessary decorative elements that distract from the data. |
| Data-Ink Ratio | Proportion of a graphic’s ink that represents actual data; higher is better. |
| Tufte’s Principles | Show the data, reduce clutter, maximize data-ink ratio, provide context. |
| Present Data in Context | Use proper scales, labels, timeframes, and comparisons so viewers interpret correctly. |
| Show the Data | Avoid hiding trends or outliers; emphasize the information, not decoration. |
| Cut the Clutter | Remove unnecessary elements (3D effects, heavy borders, excess icons). |