Thanks to this 100% online Master's Degree, you will design Software structures highly oriented towards Quality, maintenance, and scalability. 

The concept of Software Quality  has evolved from a purely functional approach to a more holistic view of the product. Currently, it is understood as a set of attributes that determine its ability to meet explicit and implicit needs under specific conditions. In light of this, specialists need to have a comprehensive understanding of the most modern methodologies to evaluate the performance of distributed architectures and DevOps environments. 

In this context, TECH offers a cutting-edge Master's Degree in Software Quality. The syllabus will delve into topics such as database normalization and component decoupling. It will also provide students with the keys to designing scalable architectures. Additionally, the course materials will explore the use of metrics to evaluate the Quality of solutions. As a result, graduates will develop a comprehensive understanding of Quality Assurance processes, mastering everything from the planning of automated tests to the implementation of international standards.  

To reinforce all of these concepts, TECH uses the innovative Relearning method, which consists of progressively reiterating key concepts for proper assimilation. Furthermore, the university program provides professionals with a variety of real-world case studies, allowing students to practice in simulated environments to bring them closer to the reality of IT practice. In this regard, to access the educational resources, graduates will only need an electronic device capable of connecting to the internet. Moreover, the program will have the collaboration of a distinguished International Guest Director, who will deliver 10 comprehensive Masterclasses.

A prestigious International Guest Director will offer 10 intensive Masterclasses on the latest trends in Software Quality” 

This Master's Degree in Software Quality contains the most complete and up-to-date program on the market. The most important features include:

• The development of case studies presented by experts in Software development 
• The graphic, schematic and eminently practical contents with which it is conceived gather scientific and practical information on those disciplines that are indispensable for professional practice 
• Practical exercises where the self-assessment process can be carried out to improve learning 
• Its special emphasis on innovative methodologies  
• Theoretical lessons, questions for experts and individual reflection work 
• Content that is accessible from any fixed or portable device with an internet connection 

The curriculum is based on the revolutionary Relearning methodology, which will help you solidify complex concepts with efficiency and immediacy”

It includes faculty members who are professionals in the field of Software Development, sharing their real-world experience, as well as recognized specialists from leading societies and prestigious universities. 

The multimedia content, developed with the latest educational technology, will provide the professional with situated and contextual learning, i.e., a simulated environment that will provide an immersive learning experience designed to prepare for real-life situations. 

This program is designed around Problem-Based Learning, whereby the student must try to solve the different professional practice situations that arise throughout the program. For this purpose, the professional will be assisted by an innovative interactive video system created by renowned and experienced experts. 

You will deepen your knowledge of modern automation tools to perform functional, performance, and regression testing"

You will understand the fundamentals of Software Quality in the development of advanced computer systems"

This curriculum examines, from a critical and interdisciplinary perspective, the role of international organizations, the evolution of digital regulation, data governance, and the impact of technologies such as artificial intelligence, blockchain, and cybersecurity. Throughout the syllabus, the geopolitical and technological analysis is integrated with a focus on the development and management of Software, preparing professionals to intervene in complex systems and interconnected digital environments. 

You will analyze the most cutting-edge techniques to ensure the security and reliability of Software” 

Module 1. Software Quality. Technology Readiness Levels (TRLs) 

1.1. Elements Influencing Software Quality (I) Technical Debt  

1.1.1. Technical Debt. Causes and Consequences 
1.1.2. Software Quality. General Principles  
1.1.3. Software with and without Quality Principles  
1.1.3.1. Consequences 
1.1.3.2. The Need for Applying Quality Principles in Software 
1.1.4. Software Quality. Types  
1.1.5. Quality Software. Specific features  

1.2. Elements Influencing Software Quality (II) Associated Costs  

1.2.1. Software Quality. Influencing Elements  
1.2.2. Software Quality. Misconceptions  
1.2.3. Software Quality. Associated Costs  

1.3. Software Quality Models (I). Knowledge Management  

1.3.1. General Quality Models  

1.3.1.1. Total Quality Management  
1.3.1.2. European Foundation for Quality Management (EFQM) Model  
1.3.1.3. Six Sigma Model  

1.3.2. Knowledge Management Models  

1.3.2.1. Dyba Model  
1.3.2.2. SEKS Model  

1.3.3. Experience Factory and QIP Paradigm  
1.3.4. Quality in Use Models (25010)  

1.4. Software Quality Models (III). Quality in Data, Processes, and SEI Models  

1.4.1. Data Quality Model  
1.4.2. Software Process Modeling  
1.4.3. Software & Systems Process Engineering Metamodel Specification (SPEM)  
1.4.4. SEI Models  

1.4.4.1. CMMI  
1.4.4.2. SCAMPI  
1.4.4.3. IDEAL  

1.5. ISO Standards for Software Quality (I). Analysis of the Standards  

1.5.1. ISO 9000 Standards  

1.5.1.1. ISO 9000 Standards  
1.5.1.2. ISO Family of Quality Standards (9000)  

1.5.2. Other ISO Standards Related to Quality  
1.5.3. Quality Modeling Standards (ISO 2501)  
1.5.4. Quality Measurement Standards (ISO 2502n)  

1.6. ISO Standards for Software Quality (II). Requirements and Assessment  

1.6.1. Standards on Quality Requirements (2503n)  
1.6.2. Standards on Quality Assessment (2504n)  
1.6.3. ISO/IEC 24744:2007  

1.7. TRL Development Levels (I). Levels 1 to 4  

1.7.1. TRL Levels  
1.7.2. Level 1: Basic Principles  
1.7.3. Level 2: Concept and/or Application  
1.7.4. Level 3: Critical Analytical Function  
1.7.5. Level 4: Component Validation in Laboratory Environment 1.8

1.8. TRL Development Levels (II). Levels 5 to 9  

1.8.1. Level 5: Component Validation in Relevant Environment  
1.8.2. Level 6: System/Subsystem Model  
1.8.3. Level 7: Demonstration in Real Environment  
1.8.4. Level 8: Complete and Certified System  
1.8.5. Level 9: Success in Real Environment  

1.9. TRL Development Levels. Uses  

1.9.1. Example of Company with Laboratory Environment  
1.9.2. Example of an R&D&I Company  
1.9.3. Example of an Industrial R&D&I Company  
1.9.4. Example of a Laboratory-Engineering Joint Venture Company  

1.10. Software Quality. Key Details  

1.10.1. Methodological Details  
1.10.2. Technical Details  
1.10.3. Project Management Details in Software  

1.10.3.1. Quality of IT Systems  
1.10.3.2. Software Product Quality  
1.10.3.3. Software Process Quality 

Module 2. Software Project Development. Functional and Technical Documentation 

2.1. Project Management 

2.1.1. Project Management in Software Quality 
2.1.2. Project Management Advantages 
2.1.3. Project Management Typology 

2.2. Methodology in Project Management 

2.2.1. Methodology in Project Management 
2.2.2. Project Methodologies. Typology 
2.2.3. Methodologies in Project Management. Application 

2.3. Requirements Identification Phase 

2.3.1. Identification of Project Requirements 
2.3.2. Management of Project Meetings 
2.3.3. Documentation to Be Provided 

2.4. Models 

2.4.1. Initial Phase 
2.4.2. Analysis Phase 
2.4.3. Construction Phase 
2.4.4. Testing Phase 
2.4.5. Delivery 

2.5. Data Model to Be Used 

2.5.1. Determination of the New Data Model 
2.5.2. Identification of the Data Migration Plan 
2.5.3. Data Set 

2.6. Impact on Other Projects 

2.6.1. Impact of a Project. Examples 
2.6.2. Risk in the Project 
2.6.3. Risk Management 

2.7. Project Must 

2.7.1. Must of the Project 
2.7.2. Identification of Project Must 
2.7.3. Identification of the Execution Points for Project Delivery 

2.8. The Project Construction Team 

2.8.1. Roles to be Involved According to the Project 
2.8.2. Contact with HR for Recruitment 
2.8.3. Project Deliverables and Schedule 

2.9. Technical Aspects of a Software Project 

2.9.1. Project Architect. Technical Aspects 
2.9.2. Technical Leaders 
2.9.3. Construction of the Project Software 
2.9.4. Code Quality Assessment, Sonar 

2.10. Project Deliverables 

2.10.1. Functional Analysis 
2.10.2. Data Model 
2.10.3. State Diagram 
2.10.4. Technical Documentation 

Module 3. Software Testing. Test Automation 

3.1. Software Quality Models 

3.1.1. Product Quality 
3.1.2. Process Quality 
3.1.3. Usability Quality 

3.2. Process Quality 

3.2.1. Process Quality 
3.2.2. Maturity Models 
3.2.3. ISO 15504 Standards 

3.2.3.1. Purposes 
3.2.3.2. Context 
3.2.3.3. Stages 

3.3. ISO/IEC 15504 Standard 

3.3.1. Process Categories 
3.3.2. Development Process Example 
3.3.3. Profile Fragment 
3.3.4. Stages 

3.4. CMMI (Capability Maturity Model Integration)  

3.4.1. CMMI. Capability Maturity Model Integration 
3.4.2. Models and Areas. Types 
3.4.3. Process Areas 
3.4.4. Capability Levels 
3.4.5. Process Management 
3.4.6. Project Management 

3.5. Change Management and Repositories 

3.5.1. Change Management in Software 

3.5.1.1. Configuration Item. Continuous Integration 
3.5.1.2. Lines 
3.5.1.3. Flowcharts 
3.5.1.4. Branches 

3.5.2. Repository 

3.5.2.1. Version Control 
3.5.2.2. Work Team and Repository Use 
3.5.2.3. Continuous Integration in the Repository 

3.6. Team Foundation Server (TFS) 

3.6.1. Installation and Configuration 
3.6.2. Creating a Team Project 
3.6.3. Adding Content to Source Code Control 
3.6.4. TFS on Cloud 

3.7. Testing 

3.7.1. Motivation for Conducting Tests 
3.7.2. Verification Testing 
3.7.3. Beta Testing 
3.7.4. Implementation and Maintenance 

3.8. Load Testing 

3.8.1. Load Testing 
3.8.2. Testing with LoadView 
3.8.3. Testing with K6 Cloud 
3.8.4. Testing with Loader 

3.9. Unit, Stress, and Endurance Testing 

3.9.1. Motivation for Unit Testing 
3.9.2. Tools for Unit Testing 
3.9.3. Motivation for Stress Testing 
3.9.4. Testing Using StressTesting 
3.9.5. Motivation for Endurance Testing 
3.9.6. Testing Using LoadRunner 

3.10. Scalability. Designing Scalable Software 

3.10.1. Scalability and Software Architecture 
3.10.2. Independence Between Layers 
3.10.3. Coupling Between Layers. Architectural Patterns 

Module 4. Software Project Management Methodologies. Waterfall Methodologies vs. Agile Methodologies 

4.1. Waterfall Methodology 

4.1.1. Waterfall Methodology 
4.1.2. Waterfall Methodology. Influence on Software Quality 
4.1.3. Waterfall Methodology Examples 

4.2. Agile Methodology 

4.2.1. Agile Methodology 
4.2.2. Agile Methodology. Influence on Software Quality 
4.2.3. Agile Methodology. Examples 

4.3. Scrum Methodology 

4.3.1. Scrum Methodology 
4.3.2. Scrum Manifesto 
4.3.3. Application of Scrum 

4.4. Kanban Panel 

4.4.1. Kanban Method 
4.4.2. Kanban Panel 
4.4.3. Kanban Panel. Application Example 

4.5. Project Management in Waterfall 

4.5.1. Phases in a Waterfall Project 
4.5.2. Vision in a Waterfall Project 
4.5.3. Deliverables to Consider 

4.6. Project Management in Scrum 

4.6.1. Phases in a Scrum Project 
4.6.2. Vision in a Scrum Project 
4.6.3. Deliverables to Consider 

4.7. Waterfall vs. Scrum Comparison 

4.7.1. Planning a Pilot Project 
4.7.2. Project Applying Waterfall. Example 
4.7.3. Project Applying Scrum. Example 

4.8. Client Vision 

4.8.1. Documents in Waterfall 
4.8.2. Documents in Scrum 
4.8.3. Comparison 

4.9. Kanban Structure 

4.9.1. User Stories 
4.9.2. Backlog 
4.9.3. Kanban Analysis 

4.10. Hybrid Projects 

4.10.1. Building the Project 
4.10.2. Project Management 
4.10.3. Deliverables to Consider 

Module 5. TDD (Test Driven Development). Test-Driven Software Design 

5.1. TDD. Test Driven Development 

5.1.1. TDD. Test Driven Development 
5.1.2. TDD. Influence of TDD on Quality 
5.1.3. Test-Based Design and Development. Examples 

5.2. TDD Cycle 

5.2.1. Choosing a Requirement 
5.2.2. Running Tests. Types 

5.2.2.1. Unit Tests 
5.2.2.2. Integration Tests 
5.2.2.3. End-To-End Tests 

5.2.3. Test Verification. Failures 
5.2.4. Creating the Implementation 
5.2.5. Running Automated Tests 
5.2.6. Eliminating Duplication 
5.2.7. Updating the Requirements List 
5.2.8. Repeating the TDD Cycle 
5.2.9. TDD Cycle. Theoretical and Practical Example 

5.3. TDD Implementation Strategies 

5.3.1. Fake Implementation 
5.3.2. Triangular Implementation 
5.3.3. Obvious Implementation 

5.4. TDD. Usage. Advantages and Disadvantages 

5.4.1. Advantages of Use 
5.4.2. Limitations of Use 
5.4.3. Quality Balance in Implementation 

5.5. TDD. Best Practices 

5.5.1. TDD Rules 
5.5.2. Rule 1: Have a Test that Fails Before Writing Production Code 
5.5.3. Rule 2: Do Not Write More than One Unit Test 
5.5.4. Rule 3: Do Not Write More Code than Necessary 
5.5.5. Mistakes and Anti-patterns to Avoid in TDD 

5.6. Simulating a Real Project to Use TDD (I) 

5.6.1. Project Overview (Company A) 
5.6.2. Applying TDD 
5.6.3. Proposed Exercises 
5.6.4. Exercises. Feedback 

5.7. Simulating a Real Project to Use TDD (II) 

5.7.1. Project Overview (Company B) 
5.7.2. Applying TDD 
5.7.3. Proposed Exercises 
5.7.4. Exercises. Feedback 

5.8. Simulating a Real Project to Use TDD (III) 

5.8.1. Project Overview (Company C) 
5.8.2. Applying TDD 
5.8.3. Proposed Exercises 
5.8.4. Exercises. Feedback 

5.9. Alternatives to TDD. Test Driven Development 

5.9.1. TCR (Test Commit Revert) 
5.9.2. BDD (Behavior Driven Development) 
5.9.3. ATDD (Acceptance Test Driven Development) 
5.9.4. TDD. Theoretical Comparison 

5.10. TDD TCR, BDD and ATDD. Practical Comparison 

5.10.1. Defining the Problem 
5.10.2. Solving with TCR 
5.10.3. Solving with BDD 
5.10.4. Solving with ATDD 

Module 6. DevOps. Software Quality Management 

6.1. DevOps. Software Quality Management 

6.1.1. DevOps 
6.1.2. DevOps and Software Quality 
6.1.3. DevOps. Benefits of DevOps Culture 

6.2. DevOps. Relationship with Agile 

6.2.1. Accelerated Delivery 
6.2.2. Quality 
6.2.3. Cost Reduction 

6.3. DevOps Implementation 

6.3.1. Problem Identification 
6.3.2. Implementation in a Company 
6.3.3. Implementation Metrics 

6.4. Software Delivery Cycle 

6.4.1. Design Methods 
6.4.2. Agreements 
6.4.3. Roadmap 

6.5. Error-Free Code Development 

6.5.1. Maintainable Code 
6.5.2. Development Patterns 
6.5.3. Code Testing 
6.5.4. Software Development at the Code Level: Best Practices 

6.6. Automation 

6.6.1. Automization Types of Tests 
6.6.2. Cost of Automation and Maintenance 
6.6.3. Automization. Mitigating Errors 

6.7. Deployment 

6.7.1. Evaluating Objectives 
6.7.2. Designing an Automated and Adapted Process 
6.7.3. Feedback and Responsiveness 

6.8. Incident Management 

6.8.1. Incident Preparation 
6.8.2. Incident Analysis and Resolution 
6.8.3. How to Prevent Future Errors 

6.9. Automating Deployments 

6.9.1. Preparation for Automated Deployments 
6.9.2. Evaluating the Health of the Automated Process 
6.9.3. Metrics and Rollback Capabilities 

6.10. Best Practices. Evolution of DevOps 

6.10.1. Best Practices Guide Applying DevOps 
6.10.2. DevOps. Methodology for the Team 
6.10.3. Avoiding Niches 

Module 7. DevOps and Continuous Integration. Advanced Practical Solutions in Software Development 

7.1. Software Delivery Flow 

7.1.1. Identifying Actors and Artifacts 
7.1.2. Designing the Software Delivery Flow 
7.1.3. Software Delivery Flow: Requirements Between Stages 

7.2. Process Automation 

7.2.1. Continuous Integration 
7.2.2. Continuous Deployment 
7.2.3. Environment Configuration and Secret Management 

7.3. Declarative Pipelines 

7.3.1. Differences Between Traditional, Code-Based, and Declarative Pipelines 
7.3.2. Declarative Pipelines 
7.3.3. Declarative Pipelines in Jenkins 
7.3.4. Comparison of Continuous Integration Providers 

7.4. Quality Gates and Enriched Feedback 

7.4.1. Quality Gates 
7.4.2. Quality Standards with Quality Gates. Maintenance 
7.4.3. Business Requirements in Integration Requests 

7.5. Artifact Management 

7.5.1. Artifacts and Life Cycle 
7.5.2. Artifact Storage and Management Systems 
7.5.3. Security in Artifact Management 

7.6. Continuous Deployment 

7.6.1. Continuous Deployment as Containers 
7.6.2. Continuous Deployment with PaaS 
7.6.3. Continuous Deployment of Mobile Applications 

7.7. Improving Pipeline Runtime: Static Analysis and Git Hooks 

7.7.1. Static Analysis 
7.7.2. Code Style Rules 
7.7.3. Git Hooks and Unit Tests 
7.7.4. The Impact of Infrastructure 

7.8. Container Vulnerabilities 

7.8.1. Container Vulnerabilities 
7.8.2. Image Scanning 
7.8.3. Periodic Reports and Alerts 

Module 8. Database (DB) Design. Normalization and Performance. Software Quality 

8.1. Database Design 

8.1.1. Databases. Types 
8.1.2. Databases Used Today 

8.1.2.1. Relational 
8.1.2.2. Key-Value 

8.1.2.3. Graph-Based 

8.1.3. Data Quality 

8.2. Entity-Relationship Model Design (I) 

8.2.1. Entity-Relationship Model. Quality and Documentation 
8.2.2. Entities 

8.2.2.1. Strong Entity 
8.2.2.2. Weak Entity 

8.2.3. Attributes 
8.2.4. Set of Relationships 

8.2.4.1. One to One 
8.2.4.2. One to Many 
8.2.4.3. Many to One 
8.2.4.4. Many to Many 

8.2.5. Keys 

8.2.5.1. Primary Key 
8.2.5.2. Foreign Key 
8.2.5.3. Primary Key in a Weak Entity 

8.2.6. Constraints 
8.2.7. Cardinality 
8.2.8. Inheritance 
8.2.9. Aggregation 

8.3. Entity-Relationship Model (II). Tools 

8.3.1. Entity-Relationship Model. Tools 
8.3.2. Entity-Relationship Model. Practical Example 
8.3.3. Feasible Entity-Relationship Model 

8.3.3.1. Visual Sample 
8.3.3.2. Table Representation Sample 

8.4. Database Normalization (DB) (I) Quality Considerations in Software 

8.4.1. DB Normalization and Quality 
8.4.2. Dependencies 

8.4.2.1. Functional Dependency 
8.4.2.2. Properties of Functional Dependency 
8.4.2.3. Derived Properties 

8.4.3. Keys 

8.5. Database (DB) Normalization (II). Normal Forms and Codd’s Rules 

8.5.1. Normal Forms 

8.5.1.1. First Normal Form (1FN) 
8.5.1.2. Second Normal Form (2FN) 
8.5.1.3. Third Normal Form (3FN) 
8.5.1.4. Boyce-Codd Normal Form (BCNF) 
8.5.1.5. Fourth Normal Form (4FN) 
8.5.1.6. Fifth Normal Form (5FN) 

8.5.2. Codd's Rules 

8.5.2.1. Rule 1: Information 
8.5.2.2. Rule 2: Guaranteed Access 
8.5.2.3. Rule 3: Systematic Treatment of Null Values 
8.5.2.4. Rule 4: Database Description 
8.5.2.5. Rule 5: Comprehensive Sub-language 
8.5.2.6. Rule 6: View Updates 
8.5.2.7. Rule 7: Insert and Update 
8.5.2.8. Rule 8: Physical Independence 
8.5.2.9. Rule 9: Logical Independence 
8.5.2.10. Rule 10: Integrity Independence 

8.5.2.10.1. Integrity Rules 

8.5.2.11. Rule 11: Distribution 
8.5.2.12. Rule 12: Non-Subversion 

8.5.3. Practical Example 

8.6. Data Warehouse/OLAP System 

8.6.1. Data Warehouse 
8.6.2. Fact Table 
8.6.3. Dimension Table 
8.6.4. Creation of the OLAP System. Tools 

8.7. Database (DB) Performance 

8.7.1. Index Optimization 
8.7.2. Query Optimization 
8.7.3. Table Partitioning 

8.8. Simulation of Real Project for DB Design (I) 

8.8.1. Project Overview (Company A) 
8.8.2. Application of Database Design 
8.8.3. Proposed Exercises 
8.8.4. Proposed Exercises. Feedback 

8.9. Simulation of Real Project for BD Design (II) 

8.9.1. Project Overview (Company B) 
8.9.2. Application of Database Design 
8.9.3. Proposed Exercises 
8.9.4. Proposed Exercises. Feedback 

8.10. Relevance of Database Optimization in Software Quality 

8.10.1. Design Optimization 
8.10.2. Query Code Optimization 
8.10.3. Stored Procedure Code Optimization 
8.10.4. Impact of Triggers on Software Quality. Usage Recommendations 

Module 9. Designing Scalable Architectures. Architecture in the Software Life Cycle 

9.1. Design of Scalable Architectures (I) 

9.1.1. Scalable Architectures 
9.1.2. Principles of a Scalable Architecture 

9.1.2.1. Reliable 
9.1.2.2. Scalable 
9.1.2.3. Maintainable 

9.1.3. Types of Scalability 

9.1.3.1. Vertical 
9.1.3.2. Horizontal 
9.1.3.3. Combined 

9.2. DDD (Domain-Driven Design) Architectures 

9.2.1. The DDD Model. Domain Orientation 
9.2.2. Layers, Responsibility Distribution, and Design Patterns 
9.2.3. Decoupling as a Basis for Quality 

9.3. Design of Scalable Architectures (II). Benefits, Limitations, and Design Strategies 

9.3.1. Scalable Architecture. Benefits 
9.3.2. Scalable Architecture. Limitations 
9.3.3. Strategies for the Development of Scalable Architectures (Descriptive Table) 

9.4. Software Life Cycle (I). Stages 

9.4.1. Software Life Cycle 
9.4.1.1. Planning Stage 
9.4.1.2. Analysis Stage 
9.4.1.3. Design Stage 
9.4.1.4. Implementation Stage 
9.4.1.5. Testing Stage 
9.4.1.6. Installation/Deployment Stage 
9.4.1.7. Use and Maintenance Stage 

9.5. Models of Software Life Cycles 

9.5.1. Waterfall Model 
9.5.2. Iterative Model 
9.5.3. Spiral Model 
9.5.4. Big Bang Model 

9.6. Software Life Cycle (II). Automation 

9.6.1. Software Development Life Cycle. Solutions 
9.6.1.1. Continuous Integration and Continuous Development (CI/CD) 
9.6.1.2. Agile Methodologies 
9.6.1.3. DevOps/Production Operations 
9.6.2. Future Trends 
9.6.3. Practical Examples 

9.7. Software Architecture in the Software Life Cycle 

9.7.1. Benefits 
9.7.2. Limitations 
9.7.3. Tools 

9.8. Simulating a Real Project for Software Architecture Design (I) 

9.8.1. Project Overview (Company A) 
9.8.2. Application of Software Architecture Design 
9.8.3. Proposed Exercises 
9.8.4. Proposed Exercises. Feedback 

9.9. Simulating a Real Project for Software Architecture Design (II) 

9.9.1. Project Overview (Company B) 
9.9.2. Application of Software Architecture Design 
9.9.3. Proposed Exercises 
9.9.4. Proposed Exercises Feedback 

9.10. Simulating a Real Project for Software Architecture Design (III) 

9.10.1. Project Overview (Company C) 
9.10.2. Application of Software Architecture Design 
9.10.3. Proposed Exercises 
9.10.4. Proposed Exercises. Feedback 

Module 10. ISO Quality Criteria, IEC 9126. Software Quality Metrics 

10.1. Quality Criteria. ISO, IEC 9126 Standard 

10.1.1. Quality Criteria
10.1.2. Software Quality. Justification. ISO, IEC 9126 Standard 
10.1.3. Software Quality Measurement as a Key Indicator 

10.2. Software Quality Criteria. Characteristics 

10.2.1. Reliability 
10.2.2. Functionality 
10.2.3. Efficiency 
10.2.4. Usability 
10.2.5. Maintainability 
10.2.6. Portability 
10.2.7. Security 

10.3. ISO Standard, IEC 9126 (I). Introduction 

10.3.1. Description of ISO, IEC 9126 Standard 
10.3.2. Functionality 
10.3.3. Reliability 
10.3.4. Usability 
10.3.5. Maintainability 
10.3.6. Portability 
10.3.7. Quality in Use 
10.3.8. Software Quality Metrics 
10.3.9. ISO 9126 Quality Metrics 

10.4. ISO Standard, IEC 9126 (II). McCall and Boehm Models 

10.4.1. McCall Model: Quality factors 
10.4.2. Boehm Model 
10.4.3. Intermediate Level. Characteristics 

10.5. Software Quality Metrics (I). Components 

10.5.1. Measurement 
10.5.2. Metrics 
10.5.3. Indicator 

10.5.3.1. Types of Indicators 

10.5.4. Measurements and Models 
10.5.5. Scope of Software Metrics 
10.5.6. Classification of Software Metrics 

10.6. Software Quality Measurement (II). Measurement Practice 

10.6.1. Metric Data Collection 
10.6.2. Measurement of Internal Product Attributes 
10.6.3. Measurement of External Product Attributes 
10.6.4. Measurement of Resources 
10.6.5. Metrics for Object-Oriented Systems 

10.7. Design of a Single Software Quality Indicator 

10.7.1. Single Indicator as a Global Qualifier 
10.7.2. Indicator Development, Justification and Application 
10.7.3. Example of Application. Need to Know the Detail 

10.8. Simulation of Real Project for Quality Measurement (I) 

10.8.1. Project Overview (Company A) 
10.8.2. Application of Quality Measurement 
10.8.3. Proposed Exercises 
10.8.4. Proposed Exercises. Feedback 

10.9. Real Project Simulation for Quality Measurement (II) 

10.9.1. Project Overview (Company B) 
10.9.2. Application of Quality Measurement 
10.9.3. Proposed Exercises 
10.9.4. Proposed Exercises. Feedback 

10.10. Real Project Simulation for Quality Measurement (III) 

10.10.1. General Description of the Project (Company C) 
10.10.2. Application of Quality Measurement 
10.10.3. Proposed Exercises 
10.10.4. Proposed Exercises. Feedback 

You will manage Software projects with a focus on continuous improvement and the delivery of sustainable value”