100%(2)2 out of 2 people found this document helpful
This preview shows page 3 - 5 out of 5 pages.
Development – All previously planned documents so far are now implemented into actualphysical hardware and software. Just as this step supports the IT infrastructure, it also supports the EA; this is where the EA and the SDLC start to really correlate with each other. Coding is written to meet specifications to create relational databases and become functional systems to utilize throughout the EA, allowing users to train and test the product (Alwan, Motea, 2017).Integration & Testing – Innovative Architects explain how Quality Assurance (QA) professionals are responsible for determining if the proposed system meets the business requirements and the functionality of the integration of the system (2017). This step is exponentially important to an EA because security and performance will make or break any 3
EA ENABLING SDLCorganization. The EA must effectively structure all sub-departments to operate together, but if the new system integration does not meet those requirements, it will lead to project failure.Implementation – Phase G in the change management model for an EA aligns with this step when the product has been officially implemented. Whether the system is new or improved, the system will need to be governed in order to sustain operations. Alwan mentions that maintenance intervals will need to be completed to avoid system isolation by cultivating new hardware and continuously monitoring system performances (2017).Operations & Maintenance – This seventh step falls in line with the sixth SDLC step, but the main reason for this step is to align it with the EA change management models last phase,H. As technology improves throughout time, operating systems will become outdated and
You've reached the end of your free preview.
Want to read all 5 pages?
Systems Development Life Cycle, ea, EA ENABLING SDLC