SWE
A systematic approach to the analysis, design, assessment, implementation, test, maintenance and reengineering of software
Software Engineering
This type of testing is done by having a human test the code by hand
Manual testing
This principle says that your code should be as simple as possible
KISS (Keep It Simple, Stupid)
This core Agile value is emphasized over following a plan
Respond to Change
This command is used to add all files to the staging area
git add .
This stage of the SDLC shows the customer how the software will meet the requirements
Design
This type of testing is done by allowing the customer or end-user to interact with the code
Acceptance testing
This principle says that you should avoid duplication of data or logic (copying and pasting)
DRY (Don't Repeat Yourself)
This core Agile value is emphasized over contract negotiation
Customer Collaboration
-m
This stage of the SDLC involves building the system
Development
This type of testing focuses on smaller sections of the code rather than testing the whole software
Unit testing
This principle says that you should never code functionality for something you might need, or something that is not a current issue
YAGNI (You Aren't Going to Need It)
This core Agile value is emphasized over processes and tools
Individuals and Interactions
Use this command to change from your current branch to a branch called "branch2"
git checkout branch2
This type of requirement describes features that the program should be able to do
Functional requirement
This type of testing is used to expose defects in the interfaces and interactions between integrated components or systems
Integration testing
This principle says to leave comments to explain objects and making functionality easier to understand
Document Your Code
This role in Agile i responsible for coaching and encouraging team members
Scrum Master
This is the collaboration platform built on top of Git, used to create, host, and share projects
GitHub
This type of requirement places constraints and goals in place for the product
Non-functional requirement
This type of testing is used to test functionality, performance, and scalability in a black-box environment
System testing
This principle says that each class/function/module in a program should only handle one thing. Not adding too many responsibilities to a single element
Single Responsibility
This role in Agile has the authority to make real-time decisions about the project
Product Owner
Use this command to merge a branch called "changes" into your current branch
git merge changes