LACK OF KNOWLEDGE WHEN CODING THE SOFTWARE ACCORDING TO THE ESTABLISHED DESIGN.

LACK OF KNOWLEDGE WHEN CODING THE SOFTWARE ACCORDING TO THE ESTABLISHED DESIGN.

1. 1. CONDITIONS THAT LED TO THE PROBLEM

   • 1. Project Requirements
     • 2. Required functionalities
       • 3. System constraints
         • 4. Performance requirements
           • 5. Tools and Technologies
             • 6. Programming languages
               • 7. Integrated development environments (IDE)
                 • 8. Libraries and frameworks
                   • 9. Development Team
                     • 10. Roles and responsibilities
                       • 11. Experience and skills
                         • 12. Development environment
                           • 13. Hardware configuration
                             • 14. Software and required dependencies
               • El problema es la falta de conocimiento al momento de elegir el lenguaje de programación
                 • ejemplo: python, javascrit, php, java.

2. 3. SOLUTION TO THE PROBLEM

   • develop flowcharts and UML
   • Use development methodology
   • review code and standards
   • Implement the waterfall model
   • document the code
   • implement good coding practices
   • develop coding
   • Analyze an agile approach

3. 2. NEGATIVE OUTCOMES OF THE PROBLEM PRESENTED.

   • Bugs and errors
   • Common problems during coding ()
   • Project delays
   • Impact on schedule
   • Cost overruns
   • Lack of compliance with requirements

4. 5. IMPORTANCE OF HAVING A CONTINGENCY PLAN

   • 5.1 continuous training
     • implement regular training programs
     • Organize workshops and seminars on the latest software development technologies and methodologies.
   • 5.2.Complete and Accessible Documentation
     • Maintain detailed and up-to-date documentation on software design.
     • Use tools such as internal wikis or document management systems to facilitate access.
   • 5.3 Code Review and Mentoring
     • Implement regular code reviews.
       • Assign experienced mentors or reviewers to less experienced developers.
   • 5.4 Planning and Prioritization Action:
     • Carry out detailed planning and establish clear priorities.
     • Divide work into manageable tasks and ensure a balanced distribution
   • 5.5 Simulation and Contingency Scenarios Action:
     • Carry out simulations and contingency scenarios to foresee possible problems.
     • Develop specific action plans for different types of problems.
   • 5.6 Testing and Validation
     • Implement a robust unit, integration and acceptance testing approach.
     • Perform regular validations against requirements and design.

5. 4. FACTORS THAT COULD AVOID THE PROBLEM.

   • 4.1 Documentation and Access Tools
     • Maintain detailed and easily accessible documentation of the design and development processes.
     • Use knowledge management and online collaboration tools.
   • 4.2 Review and Continuous Feedback
     • Implement periodic code reviews to ensure design adherence.
     • Foster a culture of constructive and continuous feedback.
   • 4.3 Facilitate updating and error correction
   • 4.4 Implement data protection measures