The product has had changes made which have then been removed a few months later. It's had new features added, and likewise, old and unused features removed. It's been all sorts of colours and patterns. Its also crashed a few times. But these are all in the natural timeline of a big development.
This is currently EISNet Management Studio and is likely to be exactly the same when you used it.
 |
| Main Window |
 |
| Package Manager |
The next step is to fix the few remaining application bugs. Once these are fixed and confirmed, we move into deployment testing. This is where we build a new EISNet network from scratch direct to v1.7. We emulate the same scenario we would have at a customer site. This is likely to raise a number of packaging issues which will be addressed. This testing is scheduled to start in late June.
Then, in early July, we start doing upgrade testing. This is where we use an image of an EISNet v1.6 network and run the upgrade, once again emulating a real scenario.
Shortly after that, we then hit the packaging phase of the product where everything we have learn from the two previous tests is encapsulated into deployment services.
In late-July, we then start a short field test. If the field test shows no major issues, we will then start fresh builds in schools from August. Schools currently running v1.6 will then be optionally upgrades in the months that follow (we are unable to plan for any EISNet development or installations during the first few weeks in September due to the start of term)
In between April and June, it is full steam ahead for document writing, installation guides, management guides, help content, like web content and training EIS staff.
Exciting times ahead!
No comments:
Post a Comment