Recently on SearchSoftwareQuality
IBM's OpenAPI Comment Parser helps devs document APIs
IBM's OpenAPI Comment Parser gives developers a new tool to simplify the process of documenting APIs, so that developers down the line will be able to use them with less effort.
More Highlights
- User acceptance testing best practices for Agile teams
Dig into the basics of user acceptance testing, including who handles the task, what should go into test criteria and other best practices.
- Agile FAQ: Get started with these Agile basics
Check out these tips on Agile basics for a quick catch-up or a great head start on maximizing the value of using Agile methods in your organization.
- 5 advantages of GitLab CI/CD pipelines
Products can ease the oft-cumbersome CI/CD process. In this video tutorial, walk through five ways GitLab enables and eases CI/CD for DevOps teams and professionals.
Definitions
- static analysis (static code analysis)
Static analysis, also called static code analysis, is a method of computer program debugging that is done by examining the code without executing the program.
- MoSCoW method
The MoSCoW method is a four-step approach to prioritizing which project requirements will provide the best return on investment (ROI).
- structured programming (modular programming)
Structured programming (sometimes known as modular programming) is a programming paradigm that facilitates the creation of programs with readable code and reusable components.
Browse Software Quality Topics
Software development methodologies
Agile software development refers to software development methodologies that follow the Agile Manifesto valuing: Individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan.
Popular agile methodologies include Scrum and Extreme Programming (XP). Agile methodologies use short iterations for development and emphasize collaboration and cross-functional teams with members from the business, development, and test.
Recent Definitions
- The Three Ways (The Phoenix Project)
The Three Ways refer to a set of three principles that form the core premise of DevOps practices.
- improvement kata
The improvement kata is a four-step routine for working toward a goal in a systematic way.
- MoSCoW method
The MoSCoW method is a four-step approach to prioritizing which project requirements will provide the best return on investment (ROI).
Highlights
- Agile FAQ: Get started with these Agile basics
- 7 techniques for better Agile requirements gathering
- Snyk shows developers top-priority vulnerabilities
More Software development methodologies Topics
Back to TopSoftware design and development
Software development fundamentals include the basics for understanding the various phases and processes of the software development lifecycle. It's important for those in software development to understand terminology, the various models and methodologies, tools, and the various phases of a lifecycle. Software development fundamentals would include understanding the basis of requirements management, software architecture, test engineering, quality engineering, configuration management and measurement and analysis.
Recent Definitions
- embedded system
An embedded system is a combination of computer hardware and software designed for a specific function or functions within a larger system.
- structured programming (modular programming)
Structured programming (sometimes known as modular programming) is a programming paradigm that facilitates the creation of programs with readable code and reusable components.
- use case
A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.
Highlights
- Agile FAQ: Get started with these Agile basics
- Follow Google's lead with programming style guides
- Altova debuts debugger for low-code applications
More Software design and development Topics
- Code refactoring and management
- Integrated development environments and dev tools
- Low code and citizen development
- Model-, behavior- and test-driven development
- UI and UX design
SDLC
Application lifecycle management (ALM) fundamentals cover best practices in the software industry for all phases of the software development lifecycle (SDLC). Regardless of SDLC methodology used, whether traditional waterfall, agile, or a combined approach, a project's success or failure can be dependent on the team's familiarity with ALM fundamentals and adherence to software development processes such as requirements, design, development, test, release, and maintenance. Knowing ALM fundamentals will provide the necessary skills to ensure a high quality software development project.
Recent Definitions
- Docker
Docker is an open source software platform to create, deploy and manage virtualized application containers on a common operating system (OS), with an ecosystem of allied tools.
- use case
A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.
- application lifecycle management (ALM)
Application lifecycle management (ALM) is the integrated system of people, tools and processes that supervise a software application from its initial planning through retirement.
Highlights
- IBM's OpenAPI Comment Parser helps devs document APIs
- 5 advantages of GitLab CI/CD pipelines
- 7 techniques for better Agile requirements gathering
More SDLC Topics
- CICD in software development
- Software documentation
- Software performance management
- Software requirements
- Version control
Dev teams and skills
Part of software project management requires staffing the project with personnel that have the right skills for successful completion of an application. Organizational decisions regarding hiring, appropriately staffing and training project teams for high-performance must be made to ensure a team's success. Dynamics in communication styles, work locations, cultures and time zones all need to be considered as a team is getting staffed. Employee skills and training needs are factors in determining project resource allocation and staff professional development.
Recent Definitions
- build server
A build server is a machine on which a software project can be continuously built from changes that are committed to the repository.
- data center outsourcing (DCO)
DCO (data center outsourcing) is the practice of outsourcing the day-to-day provisioning and management of computing and storage resources and environments to a third party provider.
- multitasking (in humans)
Multitasking, in a human context, is the practice of doing multiple things simultaneously, such as editing a document or responding to email while attending a teleconference. The concept of multitasking began in a computing context.
Highlights
- Agile FAQ: Get started with these Agile basics
- Microsoft fuels 'developer velocity' with Azure, new tools
- Virtual software development and testing conferences to attend
More Dev teams and skills Topics
- Outsourcing software development and testing
- Software developer skills and training
- Software testing skills and career advice
Test types
There's no shortage of ways to test software. Quality assurance engineers can rely on functional, performance, exploratory and many other software test types, many of which run without human intervention. In this section, we provide tips, features, guides and more to explain these different kinds of tests, and how to use them.
Recent Definitions
- static analysis (static code analysis)
Static analysis, also called static code analysis, is a method of computer program debugging that is done by examining the code without executing the program.
- software requirements specification (SRS)
A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform... (Continued)
- functional specification
A functional specification is a formal document used to describe a product's intended capabilities, appearance, and interactions with users in detail for software developers.
Highlights
- User acceptance testing best practices for Agile teams
- Software performance testing requirements and prerequisites
- 10 exploratory testing techniques for QA professionals
More Test types Topics
- Exploratory testing
- Functional testing
- Non-functional testing
- Penetration testing
- Regression testing
- User acceptance testing
Testing tools and techniques
Software quality management (SQM) refers to the processes used to manage quality in software applications. Software quality management would include defining standards, regulations and processes that would verify work products delivered through the software development lifecycle (SDLC.) Software quality management would also work towards incorporating a knowledge base of best practices, selecting tools to manage the various aspects of quality, monitoring status and verifying and evaluating current methods, procedures and tools with the aim of continuous improvement.
Recent Definitions
- use case diagram (UML use case diagram)
A use case diagram is a way to summarize details of a system and the users within that system.
- test case
A test case is a set of actions performed on a system to determine if it satisfies software requirements and functions correctly.
- debugging
Debugging, in computer programming and engineering, is a multistep process that involves identifying a problem, isolating the source of the problem, and then either correcting the problem or determining a way to work around it.
Highlights
- Agile FAQ: Get started with these Agile basics
- Altova debuts debugger for low-code applications
- Effective QA practices for RPA bot maintenance
More Testing tools and techniques Topics
- AI in software testing
- Automated and autonomous testing
- Continuous testing
- Mobile app testing tools and techniques
- Software test design and planning
- Testing APIs, microservices and distributed systems