Gerência e Qualidade de Software - Aula 03 - Processos de software

Introduction to Software Management and Quality

Overview of Software Processes

• The lecture focuses on software processes, emphasizing the relationship between quality management activities and development processes.

• The importance of standard 207 is highlighted as a crucial reference for software engineers, covering all aspects from acquisition to maintenance and operation.

• Standard 207 helps define terminology to avoid conflicts in understanding software processes and is also used for product evaluation.

Key Concepts in Software Process

• The standard considers software as part of a system, encompassing various stages including acquisition, supply, development, operation, maintenance, and eventual disposal.

• A process is defined as a set of interrelated activities that transform inputs into useful outputs for clients or internal stakeholders.

Objectives and Structure of Processes

• Each process has a specific objective; it aims to deliver value either externally (to clients) or internally (within an organization).

• Terminology related to processes includes concepts like stages (time periods for executing activities), disciplines (related activity sets), tasks (breakdowns of activities), and procedures (steps involved).

Roles and Artifacts in Processes

• Emphasis on roles within processes rather than individual identities; participants are defined by their responsibilities.

• Resources necessary for executing processes are identified along with artifacts produced during the process—these can be intermediate outputs or final products.

Implementation of Standard 207

• Standard 207 outlines objectives but does not dictate specific steps or procedures; it serves as a foundational guideline that requires adaptation based on organizational needs.

Understanding Software Process Groups

Overview of Process Groups

• The discussion begins with an overview of the four defined groups of processes in software development, emphasizing their importance for companies acquiring and providing software.

Types of Processes

• The first group includes agreement processes, which focus on the necessary agreements between a company and its software providers.

• Next are organizational enabling processes, essential for developing, maintaining, and operating software. This includes human resource management to hire and train personnel.

• Technical management processes are also crucial; they involve project management that can be formal or informal but must occur to ensure effective project execution.

Technical Processes

• The final group consists of technical processes, which encompass development activities familiar to most practitioners. These include requirements definition, business analysis, and system architecture design.

Implementation and Testing

• During implementation, testing is integral; it involves verification and validation processes that extend beyond mere testing to ensure quality throughout the development lifecycle.

Conclusion on Normative Standards

• The speaker concludes by highlighting that the discussed standard (ISO/IEC 12207:2007) is one among many focusing on process rather than product details. Future lessons will delve into quality management processes within this framework.

Key Quality Management Processes

Essential Quality Processes

• Key quality management processes include:

• Quality management,

• Measurement,

• Quality assurance,

• Verification,

• Validation.

Project Management Insights