Package Development Model
- Offered bySalesforce
Package Development Model at Salesforce Overview
Duration | 1 hour |
Mode of learning | Online |
Official Website | Go to Website |
Credential | Certificate |
Package Development Model at Salesforce Highlights
- Earn a certification after completion
Package Development Model at Salesforce Course details
- Software developers interested in creating reusable and modular components
- Understand the key stages of the Package Development Model, including planning, design, implementation, testing, and deployment
- Gain proficiency in utilizing version control systems to manage package development iterations effectively
- Acquire skills in writing clear and concise package documentation to facilitate ease of use and adoption
- Develop strategies for conducting thorough testing to ensure package functionality, reliability, and compatibility
- The Package Development Model is a structured approach for creating software packages. It encompasses stages such as planning, design, implementation, testing, and deployment, ensuring systematic progression and quality control
- This model enhances collaboration, scalability, and maintainability, leading to efficient package development and streamlined software distribution processes
Package Development Model at Salesforce Curriculum
Imagine a New Source of Truth
Describe how the models for org development differ from modular package development
List the advantages of package development
Increase Productivity with Integrated Tools
Describe the ways in which the Salesforce Command Line Interface (CLI) can enhance productivity
Describe the role of version control systems, scratch orgs, and sandbox orgs in the package development model
Understand Source-Driven Development
Describe the purpose of a Salesforce DX project
Describe how the package development model helps you manage change tracking
Learn How to Test, Build, and Release
Describe how scratch orgs support various types of testing
Describe the role of sandboxes in deployment
Plan Your Move to Packages
Identify use cases where you can shift to a modular (package development) approach
Identify a scenario that doesn't lend itself to package development