IM GONNA SWEAT PUSS OUT OF MY COCKALATORY

project

A temporary endeavor undertaken to create a unique product, service, or result.

Software engineering

The practice of using computer science, mathematics, and the software engineering design process to solve technical problems, increase efficiency and productivity, and improve software systems.

Computer science

The study of algorithms, data structures, and the theory of computation.

Agile software development

A software development methodology that emphasizes flexibility and adaptability over strict planning and control.

planning

The process of setting goals, defining tasks, and estimating resources for a project.

control

The process of monitoring progress, identifying problems, and taking corrective action to ensure that a project meets its goals.

software process

A set of activities, methods, and practices that guide the development of software products

software life cycle model

A high-level description of the stages that a software product goes through from conception to completion

waterfall model

A software life cycle model that envisions software development as a set of steps performed in sequence

requirements analysis

The process of gathering requirements for a software product from the customer or user

system design

The process of creating a high-level design of a software product

implementation

The process of creating the software product

testing

The process of exercising the software product to ensure that it meets the requirements

deployment

The process of making the software product available to users

maintenance

The process of fixing defects in the software product, adding new features, and updating the software product

defect

A problem in a software product that causes it to behave incorrectly

agile

A software development methodology that emphasizes flexibility and adaptability over strict planning and control

iterative

Describing a process that involves repeating the same steps

spiral model

A software life cycle model that combines the iterative nature of prototyping with the systematic approach of the waterfall model

risk

The likelihood that something will go wrong in the software development process

incremental

Describing a process that involves adding to a product over time

prototype evolution model

A software life cycle model that involves developing a software product in increments, with each increment being a prototype

prototype

A preliminary version of a software product that is used to evaluate the product and gather feedback

heavyweight

Requiring a lot of documentation, planning, and control

lightweight

Requiring less documentation, planning, and control

Agile Software Development

A set of software development processes that are meant to be more in line with how humans actually work and think

Scrum

A popular agile software development process that is meant to be a framework for teams to work within.

Transparency

The property of being honest about what is being done and what is not being done

Adaptation

The process of changing course as needed.

Product Backlog

A list of all the work that needs to be done on the project, as the project is currently understood

Product Goal

A high-level objective that the team is working towards.

Product Backlog Item

A unit of work on the product backlog.

Sprint Backlog

A list of all the work that needs to be done during the sprint

Potentially Shippable Product Increment

A working product that is better than the one the stakeholders have now

Product Owner

A member of the team who is responsible for the product backlog.

Scrum Master

A member of the team who is responsible for ensuring that the team is following the Scrum framework.

Development Team

The team that is responsible for implementing the product backlog items.

Sprint

A fixed period of time during which all implementation work takes place.

Sprint Planning Meeting

A meeting where the team plans the work that will be done during the sprint.

Daily Scrum

A short meeting where the team coordinates their work.

Sprint Review

A meeting where the team demonstrates the work they have done to stakeholders.

Sprint Retrospective

A meeting where the team reflects on the work that has been done during the sprint, and identifies ways to improve.

Definition of Done

The team's criteria for what constitutes a completed product increment.

Acceptance Criteria

A set of conditions that must be met in order for the implementation to be considered correct.

Quality

The degree to which a system, component, or process meets specified requirements.

Quality assurance

The process of making sure that the software meets its requirements.

Defect

Anything that doesn't meet the requirements, such as an error, omission, or inconsistency

validation

The process of ensuring that the software meets the customer's needs and expectations

verification

The process of ensuring that the software meets its requirements

defect detection

The process of finding defects in the software

defect correction

The process of fixing defects in the software

defect prevention

The process of preventing defects from occurring in the first place

functional correctness

The degree to which the software does what it's supposed to do

review

A process or meeting during which a work product is examined by a group of people to identify defects

work product

Anything produced as part of the software development process, such as requirements, design documents, or code

peer review

A review in which the work product is examined by a group of peers, or people of similar experience and expertise

walkthrough

A type of review in which the author of the work product explains the work product to a group of people

inspection

A type of review in which the work product is examined by a group of people using a formal process

requirements verification

The process of ensuring that the requirements are clear, complete, and testable

requirements validation

The process of ensuring that the requirements meet the customer's needs and expectations

design verification

The process of ensuring that the design meets the requirements

coding standards

A set of guidelines that developers follow when writing code

code reviews

A process in which a developer's code is examined by a group of peers to identify defects

unit testing:

The process of testing individual units or components of code to ensure that they work correctly

static analysis

The process of analyzing code without executing it

Quiet backshots with Philip Riley

HIS BUTTHOLE MAKES MY PENIS TIP CREAMY.

Requirement

A statement of some behavior or property that the software must exhibit in order to fulfill the product vision

Functional requirement

A statement about what the software must do.

Non-functional requirement

A statement about how the software must behave

Product vision

A high-level description of the problem to be solved and the solution to be developed

Efficiency

How much memory or CPU the software must use software must be.

Reliability

How rarely the software must crash or produce incorrect results

Compatibility

What other software or hardware the software must work with

Availability

What percentage of the time the software must be available

Security

The level of protection the software must provide against unauthorized access and other security threats

Usability

The ease of use, pleasurability, and learnability of the software.

Scalability

How well the software must perform as the number of users or the amount of data increases

Maintainability

How easy it must be to fix bugs, add features, or otherwise modify the software

Portability

How easy it must be to move the software from one platform to another

Stakeholder

Anyone who has an interest in the software

Requirements document

A formal document that describes the requirements of the software

User story

A lightweight way of documenting requirements, typically consisting of a short, informal description of a feature of the software, written from the perspective of the end user

Use case

A lightweight way of documenting requirements, typically consisting of a short, informal description of a feature of the software, but detailed enough to be used as a basis for testing

User interface mockup

A simpler and less expensive version of a prototype, used to help stakeholders understand what the software will look like and how it will behave

Storyboard

A series of pictures or drawings that show how the software will be used

Diagram

A visual representation of how the software will work behind the scenes

Requirements review

The process of ensuring that the requirements are correct, complete, consistent, and unambiguous

Performance

How fast the software must be