Course Description
In software engineering, we work in teams because the problems we face are too big for one person to handle alone. Communication is key, and teams include developers, testers, architects, system engineers, customers, and project managers.
Planning is important for large projects. Implementation involves more than just writing code – it also means following guidelines, writing documentation, and creating unit tests. But unit tests alone aren't enough; we need to make sure all the pieces fit together. Metrics help us identify areas where there may be problems and if our code meets certain standards.
Even after coding, our work isn't done. Maintaining software for large projects can keep many people busy for a long time. Project management is important for success, and engineers need the right tools.
There are different methods of software testing. Static testing involves examining code, while dynamic testing involves running the actual program. Both check functionality.
Detailed Learning Outcomes
By earning the Project Management Certification (PMC), candidates demonstrate the ability to:
Module 1 - Foundation
- Course Objectives
- What is Systems Engineering
- What is Software Systems Engineering?
- Why Should We Use Standards?
- Basic Principles for Standards
- ISO Compared to IEEE
- How Standards are Developed
- Organization of the SESC Standards
- Clauses
- Normative vs. Informative
- What Is in a Standard?
- What Is Not in a Standard?
- Where Standards Can Be Obtained?
- How to Tailor and Apply Standards
- Final Thoughts
- Other Resources
Module 2 - STDB
- Introduction to IEEE/EIA 12207
- Application of the IEEE/EIA 12207
- Applying the IEEE/EIA 12207 to Organizations and Projects
- 12207 Life Cycle Processes and Roles
- IEEE/EIA 12207 Processes and Their Interactions
- Tailoring the Processes
- The Structure of Life Cycle Processes
- The Influence of Total Quality Management
- The Relationship Between Systems and Software
- The Relationship Between Organizations and Parties
- Responding to Technology Evolution
- Events and Milestones
- Documenting Outputs
- The Role of Software Metrics
- Certification and Compliance
- Other Related Standards and Their Relationship
Module 3 - Module STDC - IEEE 12207 Project Life Cycles
- Overview of Project Lifecycle
- Types of Prototypes
- Applying Prototyping to Life Cycle Models
- Risks of Prototyping
- Commercial Items (COTS) and Reuse
- Selecting a Software Lifecycle Model
- Which Development Strategy to Pick?
- Using Risk Analysis to Determine the Right Development Strategy
- SLCM Selection Criteria
- Steps in Creating Life Cycle Processes
- SLCM Plans
- SLCM Plan Contents
- Considerations in Implementing and Maintaining the Software
- Establishing Life Cycle Processes
- Monitoring Life Cycle Processes
- Evaluating the Impact of Changes on Life Cycle Processes
Certification Validity & Renewal
The Project Management Certification (PMC) issued by GIPMC is valid for three (3) years from the date of certification award.
Renewal is designed to:
- Maintain professional credibility
- Ensure continued alignment with modern project practices
- Protect the long-term value of the certification
Renewal Process Includes:
- Completion of defined continuing professional development or knowledge refresh requirements
- Successful renewal assessment or verification, as applicable
- Submission of renewal application before certification expiry
Timely renewal allows professionals to retain active certification status without interruption.