Skip to main content

Software Development Lifecycle

Purpose:​

The purpose of this policy is to define the framework for the software development lifecycle (SDLC) within the Pitaka platform, ensuring that all software development processes are conducted in a structured, secure, and efficient manner.

Scope:​

This policy applies to all employees, contractors, and third-party developers involved in the design, development, testing, deployment, and maintenance of software for the Pitaka platform.

Policy​

1. SDLC Phases:​

The SDLC consists of the following phases:​
  • Planning: Define project scope, objectives, and resource allocation.
  • Requirements Analysis: Gather and document functional and non-functional requirements from stakeholders.
  • Design: Create architectural and detailed design specifications for the software solution.
  • Development: Write and compile the code according to the design specifications, following coding standards and best practices.
  • Testing: Conduct various testing phases (unit testing, integration testing, user acceptance testing) to ensure the software meets the defined requirements and is free from defects.
  • Deployment: Release the software into the production environment, ensuring all stakeholders are informed and prepared for the change.
  • Maintenance: Provide ongoing support, including bug fixes, updates, and enhancements based on user feedback and changing requirements.

2. Security Considerations:​

  • Security must be integrated into every phase of the SDLC, following a “security by design” approach.
  • Developers must adhere to secure coding practices to mitigate vulnerabilities.
  • Regular security assessments (e.g., code reviews, penetration testing) should be conducted throughout the SDLC to identify and address potential security risks.

3. Documentation:​

All phases of the SDLC must be thoroughly documented, including:​
  • Project plans
  • Requirements specifications
  • Design documents
  • Testing plans and results
  • Deployment notes
  • Maintenance records
  • Documentation should be stored securely and made accessible to relevant stakeholders.

4. Change Management:​

  • Any changes to the software must follow a formal change management process, including impact assessment, approval, and communication to stakeholders.
  • Change requests must be documented and tracked throughout their lifecycle.

5. Version Control:​

  • All source code and related artifacts must be managed using a version control system.
  • Version control must include proper branching and merging strategies to facilitate collaboration and maintain code integrity.

6. Training and Awareness:​

  • All personnel involved in the SDLC must receive training on the policies, standards, and best practices related to software development.
  • Continuous education programs should be established to keep developers informed about emerging technologies and security threats.

This policy aligns with applicable laws and regulations, including the Data Privacy Act of 2012 and the Cybercrime Prevention Act of 2012 in the Philippines. Regular audits should be conducted to ensure compliance with this policy and assess the effectiveness of the SDLC processes.

8. Policy Enforcement:​

Violations of this policy may result in disciplinary actions, which may include revocation of access, termination of employment, or legal consequences, depending on the severity of the violation. The compliance officer is responsible for overseeing adherence to this policy and addressing any violations.