Analysis Design and Modeling

This article discusses the testing process, data conversion plans, changeover methods, and investigation techniques for analysis design and modeling. It covers unit testing, integration testing, and system testing, as well as options for changeover methods such as parallel changeover, direct changeover, phased changeover, or pilot changeover. The article also recommends involving employees and IT professionals in the post-implementation evaluation process and using investigation techniques like observation, interviews, questionnaires, sampling, and examination.

Running head: Analysis design and modeling
Analysis design and modeling

Analysis design and modeling
1.) Type of testing to be performed
Testing is nothing but a verification of the software if it is working according to the expected
result. Usually, there can be ample amount of testing that is performed to test the developed
software, but the major three tests include Unit testing, Integration testing, and system testing.
Unit testing is the first major and basic step of testing performed by the developer himself, where
tests are taken of every program data to be ensured whether the program is executing the desired
results or not.
Next stage of testing involves integration testing, in which the links checked between different
function can together generate a required program file. The main program file is not a particular
file which can be developed alone to generate desired results, it is actually an integration of
functions and other programs which works collectively to generate the desired results.
Now after performing integration testing, the final software can be attained which is an
integration of different modules. This final software developed is now further tested to get
ensured whether it is working as per the user requirements. At this stage, the end to end testing of
the software is performed to ensure that the software is ready to deploy.
The test data which includes positive test case generates the expected results and negative test
cases which are used to test the unhandled conditions should also be considered. Test data should
be designed in such a way that it should cover all the possible test scenarios, which ultimately
results in the best quality application.
2.) Data Conversion plans
Data conversion plan that results in minimum system problems while converting to the new
system is most recommended.
While converting data into the new system in a test environment, a batch of test data is most
likely to be created. It is important to retain all the documents of the previous system, so as to
cope up with any failure in the new system. Also, the process which includes hardware backup
and recovery of disaster should have been tested properly and thoroughly.
1

Analysis design and modeling
3.) Options for changeover methods
Options for changeover over methods that cornucopia can consider are parallel changeover,
direct changeover, phased changeover or pilot changeover.
If we consider phased changeover operation, the order of implementation of module has to be
determined. If pilot operation is considered, then the test site or department has to be determined
first, and also justification has to be provided as per the selection. If direct or parallel operations
are selected, then there are many chances of arguments to arise.
A proper discussion in which the advantages and disadvantages about the operation is discussed,
has to be provided by the student for the operation they have selected.
4.) Investigation techniques to be used: -
Employees of cornucopia should be involved in the process to perform a post-implementation
evaluation and to assess the quality of the system. An IT Professional, who is much familiar with
the company, should be called as well for the proper assistance during evaluation because
cornucopia does not have many employees with IT background.
The investigation techniques like, observation, interviews, questionnaires, sampling, and
examination should be used. The observation technique involves observing the user and the
computer operators.
All the documents, reports and schedules are to be examined properly, and then the
questionnaires have to be created in order to have feedback from the user. The survey has to be
done at the end in order to ensure whether the customers are satisfied or not or what is the level
of satisfaction and what changes might bring the best satisfaction level.
2