Subsequent to the plan and design requirements, the implementation phase takes the blueprints of efficient, maintenance, and training requirements and transforms them into detailed pilot designs. System functionality is addressed and determined to satisfy functional requirements. Emphasizing the functional characteristics of the system, a pilot (general) system design produces an advanced guide. Conclusively, a finished (detailed) system design is developed, broadening the design by identifying all the technical specifics involved to advance the system. “Screen layouts, business rules, process diagrams, pseudocode and other documentation” (Kay, 2002) are involved to ensure a clear and distinct framework through Software Requirement Specification (SRS). The third phase of SDLC transforms the conceptual, logical, and physical design components into an operational application.

Now it’s time to test the developed data! Through data loading, various degrees of validation occur based on design requirements for “units, integration, performance, system, and acceptance testing. System functionality is verified for business requirements in which each system element, communication, application, process, and related records are developed/acquired, tested, and integrated.” (Steinbach, 2013) Teams across an enterprise collaborate to facilitate this function in which robust user contribution is vital as “genuine code is composed and populated in a table structure at this juncture.” (Kay, 2002)

After the data has been loaded and verified; evaluation tests then modifies the database’s process and plan. This testing permits the plan to be improved and debugged before deployment. During this implementation phase, the final system is installed in the production environment. “Users are then tutored and data is converted. The business procedures are later assessed after being relinquished to the benefactor. “(Steinbach, 2013) Implementation deploys implementation, system problem resolution, and interoperability.

The database is finally released for deployment at this sixth phase. The system’s operation is maintained in accordance to business requirements and the needs of benefactors are also consistently met. An effective system operation consists of upgrades; furthermore, to habitually maintain hardware/software. User support remains strong with perpetual training ensues for both new and seasoned users in the event new system features are initiated and to resolve any system bugs encountered. This is the beta testing phase which runs on an actual business platform.

The last and final phase in the SDLC model emphasizes on the consistent update and maintenance of the database system. This is usually performed at an operational level to analyze and monitor the performance of the database system. Any modifications, corrections, additions, and transporting to another platform occurs. Dispositions may be determined at this phase to terminate the system. The lifecycle comes full circle at the phase of maintenance in which it continues in an infinite loop or terminates in accordance to business needs, regulations, and the benefactors who support them.

Copyright © 2014 Margaret Hillary. All Rights Reserved.

References:

Kay, Russell (2002) ComputerWorld. QuickStudy: System Development Life Cycle.

http://www.computerworld.com/s/article/71151/System_Development_Life_Cycle?taxonomyId=011

Steinbach, Chris (2013) C2. Systems Development Life Cycle.

http://c2.com/cgi/wiki?SystemsDevelopmentLifeCycle

 

error: Content is protected !!