Root at 16:25, 22 October 2025

2025-10-22T16:25:55Z

← Older revision		Revision as of 17:25, 22 October 2025
Line 16:		Line 16:
	A common structural problem in PHP is deeply nested code, which makes it difficult to read and maintain.		A common structural problem in PHP is deeply nested code, which makes it difficult to read and maintain.

	<syntaxhighlight>// Bad practice:		<syntaxhighlight lang="php">// Bad practice:
	if (condition1) {		if (condition1) {
	if (condition2) {		if (condition2) {
Line 36:		Line 36:
	Rather than including or requiring files manually, use autoloaders to load classes automatically. This is a structural improvement that makes code more maintainable.		Rather than including or requiring files manually, use autoloaders to load classes automatically. This is a structural improvement that makes code more maintainable.

	<syntaxhighlight>// Instead of this:		<syntaxhighlight lang="php">// Instead of this:
	require 'User.php';		require 'User.php';
	require 'Order.php';		require 'Order.php';
Line 49:		Line 49:
	Global variables can make code unpredictable and harder to maintain. Encapsulate your data and use dependency injection or pass them as arguments.		Global variables can make code unpredictable and harder to maintain. Encapsulate your data and use dependency injection or pass them as arguments.

	<syntaxhighlight>// Avoid this:		<syntaxhighlight lang="php">// Avoid this:
	global $database;		global $database;

Line 61:		Line 61:
	Coupling refers to the degree to which one class knows about another class. If classes are too dependent on each other, it results in tight coupling, making the system harder to modify.		Coupling refers to the degree to which one class knows about another class. If classes are too dependent on each other, it results in tight coupling, making the system harder to modify.

	<syntaxhighlight>// bad		<syntaxhighlight lang="php">// bad
	class Order {		class Order {
	public function calculateTotal() {		public function calculateTotal() {
	$shipping = new Shipping();		$shipping = new Shipping();
	return $this-~~>~~subtotal + $shipping-~~>~~calculate();		return $this->subtotal + $shipping->calculate();
	}		}
	}		}
Line 74:		Line 74:

	public function __construct(Shipping $shipping) {		public function __construct(Shipping $shipping) {
	$this-~~>~~shipping = $shipping;		$this->shipping = $shipping;
	}		}

	public function calculateTotal() {		public function calculateTotal() {
	return $this-~~>~~subtotal + $this-~~>~~shipping-~~>~~calculate();		return $this->subtotal + $this->shipping->calculate();
	}		}
	}</syntaxhighlight>		}</syntaxhighlight>
Line 86:		Line 86:
	These are objects that know too much or do too much, essentially violating the Single Responsibility Principle (SRP). Breaking them down helps in making the system modular and maintainable.		These are objects that know too much or do too much, essentially violating the Single Responsibility Principle (SRP). Breaking them down helps in making the system modular and maintainable.

	<syntaxhighlight>// Bad		<syntaxhighlight lang="php">// Bad
	class System {		class System {
	public function authenticateUser() { /.../ }		public function authenticateUser() { /.../ }
Line 114:		Line 114:
	Rather than hardcoding values, it's better to use configuration files or constants.		Rather than hardcoding values, it's better to use configuration files or constants.

	<syntaxhighlight>// Bad		<syntaxhighlight lang="php">// Bad
	function getConnection() {		function getConnection() {
	return new DatabaseConnection(~~"~~localhost~~"~~, ~~"~~root~~"~~, ~~"~~password123~~"~~);		return new DatabaseConnection("localhost", "root", "password123");
	}		}
	// Better		// Better
Line 125:		Line 125:
	Not handling potential errors can lead to unexpected system crashes or bugs.		Not handling potential errors can lead to unexpected system crashes or bugs.

	<syntaxhighlight>// Bad		<syntaxhighlight lang="php">// Bad
	function divide($a, $b) {		function divide($a, $b) {
	return $a / $b;		return $a / $b;
Line 132:		Line 132:
	function divide($a, $b) {		function divide($a, $b) {
	if ($b == 0) {		if ($b == 0) {
	throw new DivisionByZeroException(~~"~~Cannot divide by zero~~"~~);		throw new DivisionByZeroException("Cannot divide by zero");
	}		}
	return $a / $b;		return $a / $b;
Line 155:		Line 155:

	By focusing on structural quality assurance developers can ensure that their codebase remains maintainable, scalable, and less prone to bugs.		By focusing on structural quality assurance developers can ensure that their codebase remains maintainable, scalable, and less prone to bugs.
	~~<!-- From bodyContent 1543044.mraw -->~~

	[[Category:Quality Assurance definitions]]		[[Category:Quality Assurance definitions]]

Maintenance script: Added category Quality Assurance definitions

2025-10-19T17:51:24Z

Added category Quality Assurance definitions

← Older revision		Revision as of 18:51, 19 October 2025
Line 157:		Line 157:
	<!-- From bodyContent 1543044.mraw -->		<!-- From bodyContent 1543044.mraw -->

			[[Category:Quality Assurance definitions]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Quality Assurance definitions/Structural QA to Structural QA: Cleaned title and categorized

2025-10-19T17:51:24Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Quality Assurance definitions/Structural QA to Structural QA: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 10:25, 19 April 2025

2025-04-19T10:25:58Z

Show changes

imported>Unknown user at 10:25, 19 April 2025

2025-04-19T10:25:58Z

← Older revision	Revision as of 11:25, 19 April 2025
(No difference)

imported>Unknown user at 10:25, 19 April 2025

2025-04-19T10:25:58Z

New page

Structural QA - Revision history

Root at 16:25, 22 October 2025

Maintenance script: Added category Quality Assurance definitions

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Quality Assurance definitions/Structural QA to Structural QA: Cleaned title and categorized

imported>Unknown user at 10:25, 19 April 2025

imported>Unknown user at 10:25, 19 April 2025

imported>Unknown user at 10:25, 19 April 2025