Running code
The stalled system regained a functioning development and test foundation.
Education & EdTech · Student management
Recovering a student-management product for school pilots
An education-software project recovered from a stalled handoff through code analysis, a shared requirements review, and completion of student, course, assessment, and reporting functions before school pilots.
The business context
The customer had code, but no usable development path.
The original development team had left a partially completed student-management system. Documentation was incomplete, and the customer did not have the technical knowledge to deploy or maintain what remained. Earlier investment was trapped in a project that could not move forward.
The intended product had a clear business purpose: support an education provider's own student and course administration, then offer those capabilities to other institutions. Restoring the environment was only the first step toward a product that schools could try.
System view
Make the assessment record useful to the people preparing reports.
Original reconstruction using fictional student references and course units. No real school records or official approval marks are shown. View full-size interface (new tab)
The operating challenge
Recovery required both technical understanding and agreed scope.
The new team needed to determine what the existing code did, which parts could be retained, and which essential functions were missing. Without that assessment, a new feature list would have rested on an uncertain foundation.
The product also needed coherent student records, assessment information, and reports for its intended education setting. Those requirements had to be discussed with a customer who could explain the business but could not supply a complete technical specification.
The delivery decisions
Make the inherited project understandable before rebuilding it.
Restore a working environment
The team gathered the available code and materials, investigated dependencies and configuration, and recovered the ability to run and develop the system. This created a practical basis for testing the inherited work.
Turn code analysis into a shared requirements record
Existing functions, data structures, and business logic were reviewed to identify implemented behavior and gaps. The resulting assessment gave the customer a concrete description of the project rather than an assumed completion percentage.
Review scope together, then retain useful work
An intensive workshop used that assessment to agree priorities and the remaining product scope. The team kept usable code and reworked the parts that needed improvement, then completed student, course, assessment, and reporting capabilities.
Support review and school pilots
Development, testing, and customer feedback continued through product completion. The team supported the required review work and prepared the system for use in real education settings.
The working detail
The assessment became a decision document.
From unknown code to agreed work
The project team reports completing the initial analysis in about a week and producing more than one hundred pages of system and requirements findings. Its value was the shared understanding it created: the customer could discuss known functions and missing work instead of restarting from vague expectations.
A subsequent workshop translated that understanding into a delivery plan. This kept the recovery connected to a usable student-management product, with school records and reporting as the core workflow.
The delivered result
The recovered product reached school pilots.
Completed core
The agreed student, course, assessment, and reporting functions were completed.
Four schools
The project team reports pilot deployment at four schools after the relevant review was completed.
The school-pilot and review outcomes are historical project-team reports. They are not a claim of current certification, continuing regulatory approval, or subsequent commercial scale.
Case taxonomy
Searchable by industry, technology, product, and business need.
Industry and product
- Education & EdTech
- Student management
Technology and delivery
- .NET Core
- Azure
- Web application
Business need
- Product rescue
- Student records
- Assessment reporting
- School pilots
- Requirements recovery
- Legacy modernization
Discuss your project
Can your stalled education product be recovered into something schools can use?
Tell us how your business works and where your software needs to change.
Get in touch
Ready to build software that fits your business?
Tell us what you need to build, modernize, automate, or augment with AI. We can start with a focused discussion or a no-risk 1-week trial.
“A fantastic company to work with.” After the initial rapid development project, American Shipping Co. kept two Shinetech developers embedded for nearly four years, supporting internal and external tools and new AI initiatives.
CEO, American Shipping Co. - 5-star Google Review