Framtagning av prototyp för att läsa och dokumentera kundspecifikationer

To increase the quality in their products ABB is working towards a cleared order concept. That means that all customer specified options are to be known before they start with order calculations and construction. As it is today they use paper checklists to achieve this. One order may have several reactors, and for a reactor there can be several different alternatives. For each alternative a new checklist must be filled out.As of today all reading of the customer specification and checklist fill in with is done by hand by different persons, and sometimes the same data is read more than one time. All data is also manually inserted into the calculation tools.To decrease the risk that data is left out or gets distorted they want to have a tool to aid with the reading of the specification and the documentation of that work. Already read data can be copied over to another alternative so that it not must be read one more time. The read data are to be stored in a database so that it easily can be per automation inserted into the different design tools.

En beskrivning av manuellt test : Svagheter och styrkor med och utan stöd avett testverktyg

Test is an area in system development. Test can be performed manually or automated. Test activities can be supported by Word documents and Excel sheets for documenting and executing test cases and as well for follow up, but there are also new test tools designed to support and facilitate the testing process and the activities of the test. This study has described manual test and identified strengths and weaknesses of manual testing with a testing tool called Microsoft Test Manager (MTM) and of manual testing using test cases and test log templates developed by the testers at Sogeti. The result that emerged from the problem and strength analysis and the analysis of literature studies and firsthand experiences (in terms of creating, documenting and executing test cases) addresses the issue of the following weaknesses and strengths. Strengths of the test tool is that it contains needed functionality all in one place and it is available when needed without having to open up other programs which saves many steps of activity. Strengths with test without the support of test tools is mainly that it is easy to learn and gives a good overview, easy to format text as desired and flexible to changes during execution of a test case. Weaknesses in test with the support of test tools include that it is difficult to get a good overview of the entire test case, that it is not possible to format the text in the test steps. It is as well not possible to modify the test steps during execution. It is also difficult to use some of the test design techniques of TMap, for example a checklist, when using the test tool MTM. Weaknesses with test without the support of the testing tool MTM is that the tester gets many more steps of activities to do compared to doing the same activities with the support of the testing tool MTM. There is more to remember because the documents the tester use are not directly linked. Altogether the strengths of the test tool stands out when it comes to supporting the testing process.