Software Engineering


Let’s Discuss

Windows Software

  • Stand-alone applications for Windows
  • Product support applications
    • Custom data analyzers
    • Simulators
    • Data logging
    • Development of rich, interactive GUIs for data visualization
  • Development languages, frameworks and environments
    • C, C++, C#
    • .NET
    • Visual Basic
    • PHP, SQL,
    • Python
    • Visual Studio
    • Labview
    • OpenCV

Android Software

  • Stand-alone applications for Android
  • Product support applications
    • Custom data analyzers
    • Simulators
    • Data logging
    • Development of rich, interactive GUIs for data visualization
  • Native and Hybrid applications
  • Bluetooth interfacing
  • Development languages, frameworks and environments
    • Java
    • C++
    • xamarin
    • Android Studio
    • Tensorflow
    • OpenCV

Development Methodology

  • Experience in planning and execution of projects with software and mechanical design inter-dependencies
  • Waterfall methodology
  • Scrum based Agile
    • Product backlog with priorities assigned
    • Scrum team with Product Owner, Scrum Master, Developers and QA
    • Release planning based on bi-weekly sprints
    • Daily stand-up Sprint-planning, Retrospect and Product Demo meetings
  • Collaboration Tools
    • CVS and SVN for version control
    • Redmine for issue management
    • Project collaboration tools
      • Active Collab for task assignment and tracking updates
      • Basecamp, JIRA
  • MS Project for project scheduling and tracking

Software Quality Assurance

  • Design reviews and code walkthrough and reviews
  • Developer Testing
    • Testing for low-level design issues such as memory overflow, memory leakage, boundary conditions, error handling etc. using various advanced tools such as debuggers, oscilloscopes, logic analyzers, communication protocol analyzers etc.
  • Testing by the Quality Assurance team
    • Feature & Functional Testing – Testing of newly released features. Test cases are created to cover all product functional requirements and different use case scenarios including boundary conditions and non-obvious use cases. A requirement traceability matrix is used to trace the requirements to the tests that are needed to verify whether the requirements are fulfilled. The QA team also focuses on reviewing the usability of the feature,
    • Regression testing – Tests are performed on the final software package as it is readied for release. The QA team focuses on testing of the integrated modules working together correctly and on ensuring that other functionality is not impacted. This testing includes a combination of automated test scripts and manual testing.

 

Let’s Discuss
Scroll to top