Question

E. Explain Microsoft's conversion process. How does Microsoft plan conversion, prepare documentation, and train users and technical staff?

B. Explain Microsoft's systems design. How does Microsoft create design specifications? 

Answer 1

Before a package is converted into an application planning is essential that has a procedure that starts with the definition of a well-detailed conversion plan, which can be based on one of the two ways. A high-resource test environment and a small-test environment. The high-resource test environment is based on the fact more than enough resources are available at the disposal for the planning and testing, this is in terms of the test environment having the resources, permissions, and architecture similar to your production environment. The planning steps are as follows: Select the package to be converted. Migrate the packages for conversion into your test environment. Prepare the packages for conversion. Select test packages. Analyse, investigate, and convert the test packages. Test the converted applications. Analyse and convert the remaining (non-test) packages (Walsh). Export the applications from the test environment. Import them into your production environment.

The other plan, the limited-resource test environment is the exact opposite of the high-resource test environment by the basis of availing of types of resources, the test environment doesn't have the resources, permissions, and architecture similar to your production environment. Documentation is on the base of getting the requirements enlisted for the creation and having key features as a priority, by this they also have needs and for the perfection into a perfect plan, the readability, estimated reading time, content navigation. On the matter of training, Microsoft has a simple direct mode to train both the users of a product and the technicians, this can either be online or on physical terms. Physical training it's much simpler and faster to train, this is based on testing time where they will all be trained to use the product and deal with an issue in the software.

The other method, online works on the base that an online portal can be created to teach the use of the system. This has steps and requirements on the training, which include the process being easy to learn, accurate in the information and technically practical the requirements. The steps will be based on simplicity where they will start with having the system duplicated or have photos of the user interfaces as the educating samples, also draft the educating content, draft the check-up questions and quizzes, and also the drafting tips and additional information for clarity for the users to also know any information they may need to use in the actual use of the product most of this depends on the type of product in creation.

As the product requires system specification it is due to have a procedure and process to get it, with the software being created the specification will also be simple and direct but well detailed to avoid miscommunication so the inclusive should have enough information for developers to complete the software described. It not only lays out the description of the software under development but also the purpose it will serve: what the software is supposed to do and how it should perform (Pevtschin). the document typically includes The purpose of the software being developed. An overall description of the software. The functionality of the software or what it is supposed to do. Performance of the software in a production situation. Non-functional requirements. External interfaces or how the software will interact with hardware or other software it must connect to. Design constraints or the limitations of the environment that the software will run in.

References

Walsh, A. (n.d.). Microsoft v Commission: Interoperability, emerging standards and innovation in the software industry. Microsoft on Trial. https://doi.org/10.4337/9781849807142.00021

Taking your first steps. (n.d.). Foundations of Microsoft Expression Web, 25–46. https://doi.org/10.1007/978-1-4302-0392-6_2

Beegan, G. (2016). Microsoft. The Bloomsbury Encyclopedia of Design. https://doi.org/10.5040/9781472596161-bed-m052

Pevtschin, V. (n.d.). The Open Microprocessor Systems Initiative: A strategy towards Integrated System design. Proceedings Sixth IEEE International Workshop on Rapid System Prototyping. Shortening the Path from Specification to Prototype. https://doi.org/10.1109/iwrsp.1995.518564

 

 

 

Before a package is converted into an application planning is essential that has a procedure that starts with the definition of a well-detailed conversion plan, which can be based on one of the two ways.