• Location:

    Omaha, Nebraska

  • Category:

    Transportation

  • Case Study:

    Product Engineering

Addressing Non-Functional Requirements in a Transportation Company Project :

A transportation company faced significant challenges in the productivity of resources allocated to handle non-functional requirements. Frequent rotation of resources and low productivity prompted SG to conduct a comprehensive 360-degree analysis of the product. Several critical gaps were identified, contributing to the inefficiencies and overall project delays.

Identified Gaps and Their Implications :

Code Quality issues:
  • Symptoms: Highly complex, leaky, and error-prone code; reliance on deprecated libraries; absence of static code analysis; poor adherence to coding standards.
  • Implications: Late detection of bugs and performance issues, increased time and effort in maintenance, and decreased system reliability.
Delayed Access to Crucial Documents
  • Symptoms: Limited or no timely access to system, functional, use case, and architecture documents.
  • Implications: Extended learning curves for new resources, decreased productivity, and slower project progression.
Lack of Proper Test Cases
  • Symptoms: Insufficient or inadequate test cases.
  • Implications: Ineffective testing leading to undetected bugs, lower product quality, and increased time to market.
Regulated Communication
  • Symptoms: Communication between functional and non-functional teams mediated by intermediaries, leading to reduced direct teamwork.
  • Implications: Miscommunications, delays in issue resolution, and decreased collaborative problem-solving.
Lack of process
  • Symptoms: Absence of streamlined processes leading to repeated work and communication issues.
  • Implications: Inefficiencies, duplication of efforts, and inconsistent project execution.
Architecture / Technology selection issues
  • Symptoms: Poor initial decisions regarding architecture and technology.
  • Implications: Rework, increased costs, and potential project derailment due to unsuitable technology choices.

Customer Response and Outcomes

Upon reviewing the analysis, the customer acknowledged the identified gaps and took corrective actions to address them. This proactive approach led to significant improvements in resource productivity and project deliverables. The key actions included:

Improving Code Quality
  • Implementing static code analysis tools and enforcing coding standards.
  • Refactoring code to eliminate deprecated libraries and reduce complexity.
Ensuring Timely Access to Documentation
  • Establishing a centralized repository for all crucial documents.
  • Ensuring timely updates and accessibility for all team members.
Enhancing Test Case Development
  • Developing comprehensive test cases to cover all critical functionalities.
  • Regularly updating and reviewing test cases to match evolving requirements.
Streamlining Communication
  • Facilitating direct communication channels between functional and non-functional teams.
  • Encouraging regular meetings and collaborative tools to enhance teamwork.
Implementing Robust Processes
  • Establishing clear processes and protocols for project execution.
  • Regularly reviewing and refining processes to eliminate inefficiencies.
Optimizing Architecture and Technology Selection
  • Conducting thorough evaluations and risk assessments before finalizing technology choices.
  • Engaging in continuous monitoring and adjustments based on project needs.

Code Quality Issues

  • Ability to introduce bugs is higher

  • Code quality

  • Code complexity issues

  • Code duplication

  • Hardcoded values

  • Usage of Deprecated Classes

  • Unused code

  • High Maintenance

  • Lack of coding best practices

Conclusion

The 360-degree analysis conducted by SG was instrumental in identifying and addressing critical gaps that hampered the productivity and efficiency of the transportation company’s project. By systematically addressing these issues, the company achieved better resource productivity and enhanced project outcomes. This case study underscores the importance of comprehensive project evaluation and proactive management in overcoming non-functional requirements challenges.