Identification of problems, specifying solutions, and establishing information requirements
During systems design, the system analyst will model and document design specifications, select the hardware and software technologies for the solution, and present this to Kretsmart for business users’ approval of the specifications.
Programming
Translating design specifications into program code
The systems analyst delivers the requirements to the programmers to translate the design specifications into software.
Testing
Developing and executing test plans, unit testing, system testing, and acceptance testing.
The technical team will conduct unit, system, and acceptance tests. These tests will generate test data and scenarios and validate test results.
Unit testing: tests each program in the system separately.
System testing: test the functioning of the system as a whole.
Acceptance testing: ensure the system is ready to be used in the production setting.
Test plan: determine all preparations for a series of tests.
Conversion
Preparing and executing a conversion plan to transition from the old to the new system.
There is no right way or wrong way to implement the system; the strategy selection must be made in the context of the company.
Four main strategies Kretsmart:
The parallel strategy allows both systems to run simultaneously until there is confidence in the new systems.
The direct cutover strategy replaces the old system with the new system.
The pilot study strategy introduces the new system into one area of the organization.
If all goes well, the system will be rolled out to other areas of the organization.
The phased approach slowly integrates the new system into specific areas of the organization.
Production and Maintenance
Reviewing the system, ensuring it meets objectives, and on-going maintenance.
The next phase after the new system is installed and the conversion phase is completed.