Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
courses:cs397:winter2017:buzzword_bingo [2017/05/02 20:40] – admin | courses:cs397:winter2017:buzzword_bingo [2017/05/05 16:14] (current) – [Buzzword Bingo] admin | ||
---|---|---|---|
Line 2: | Line 2: | ||
//In progress from class discussion...// | //In progress from class discussion...// | ||
+ | |||
+ | We identified some important buzzwords and then researched them together in class to try to understand some of the terms we repeatedly see when exploring software tools. | ||
===== Full-stack Development ===== | ===== Full-stack Development ===== | ||
- | development | + | Development |
* System admin - Linux, shell scripting | * System admin - Linux, shell scripting | ||
- | * | + | * Search - Elasticsearch; |
- | * | + | * Caching - Varnish |
- | * | + | * Version Control - Git, Mercurial SVN |
- | * | + | * Back-end: Apache, PHP, MongoDB, SQL, MySQL |
- | * | + | * Front-end: HTML, CSS, JavaScript, jQuery, AJAX, XML, WebSocket |
+ | |||
+ | Resources: | ||
- | https:// | + | * https:// |
- | https:// | + | |
- | http:// | + | |
===== Data-driven development ===== | ===== Data-driven development ===== | ||
Line 29: | Line 33: | ||
==== Flux ==== | ==== Flux ==== | ||
- | used by Facebook | + | |
- | + | | |
- | application architecture for client side apps | + | |
Line 37: | Line 40: | ||
Sources: | Sources: | ||
- | https:// | + | * https:// |
- | https:// | + | |
===== DevOps (software DEVelopment and Information Technology OPerationS) ===== | ===== DevOps (software DEVelopment and Information Technology OPerationS) ===== | ||
Line 85: | Line 88: | ||
Refers to the measurement of a particular characteristic of a software program' | Refers to the measurement of a particular characteristic of a software program' | ||
Examples of metrics: number of tests run and passed, number of defects, software development effort estimation (realistic predictions of the effort required to develop or maintain software), assessing performance of a server under heavy load | Examples of metrics: number of tests run and passed, number of defects, software development effort estimation (realistic predictions of the effort required to develop or maintain software), assessing performance of a server under heavy load | ||
+ | |||
There are three types of metrics: | There are three types of metrics: | ||
- | - Process Metrics: measures the process efficiency of the Software Development Life Cycle | + | * Process Metrics: measures the process efficiency of the Software Development Life Cycle |
- | - Product Metrics: measures the quality of the software product | + | |
- | - Project Metrics: measures the efficiency of a project team or any tools being used in the project | + | |
JMeter: http:// | JMeter: http:// | ||
+ | |||
Source: http:// | Source: http:// | ||
Line 106: | Line 112: | ||
===== Triage ===== | ===== Triage ===== | ||
- | Triage is the act of analyzing, understanding, | + | Triage is the act of analyzing, understanding, |
+ | |||
+ | Source: http:// | ||
=====Monitoring===== | =====Monitoring===== | ||
Project managers monitor the progress of a project. Three levels of monitoring include: activity levels, status reports, and milestone analysis. | Project managers monitor the progress of a project. Three levels of monitoring include: activity levels, status reports, and milestone analysis. | ||
- | Triage | ||
- | |||
- | Allows threads to temporarily stop being mutually exclusive as they wait for a condition to be met. | ||
- | |||
===== Branch Deploy ===== | ===== Branch Deploy ===== | ||
Line 129: | Line 133: | ||
Uses: SVN and GitHub (and other VCS) | Uses: SVN and GitHub (and other VCS) | ||
- | Sources: http:// | + | Sources: |
- | https:// | + | * http:// |
+ | | ||