Enterprise Architecture and Development Strategy

Business Case:

A major government client was in the process of transitioning their development processes and staff from legacy environments to a Web based architecture. Existing development processes were rigid and inflexible, configuration management and change control were non-existent, an Enterprise Architecture definition approach had not been defined, tools and technologies had not been selected, and staff was in need of training.

Solution: 

CapTech consultants stepped in to lead and manage the client’s efforts and to assist on-site staff with making the right decisions, establishing needed processes, and preparing the proper infrastructure.

CapTech’s efforts included:

  • Designing improvements to the client’s Software Development Lifecycle Methodology to support iterative and agile approaches to solving project needs
  • Selection and establishment of technology standards in the areas of development language, runtime platform, development frameworks, and supporting infrastructure
  • Definition of an Enterprise Architecture management process to identify and close gaps, as well as manage change over time as technologies evolve or as needs become more complex
  • Development and implementation of a Software Configuration Management plan
  • Definition of ownership for processes such as QA, testing, runtime infrastructure support and hosting, Software Configuration Management administration, and tools championship and training
Tools: 
  • IBM/Rational ClearCase
  • IBM/Rational Functional Tester
  • IBM/Rational Software Architect
  • Unified Modeling Language v2.0
  • IBM Websphere MQ
  • IBM/Rational Performance Tester
  • IBM/Rational Software Modeler
  • IBM Websphere Application Server
  • IBM/Rational Requisite Pro
Results: 
  • Software development processes have become more flexible and adaptable, leading to more successful project outcomes
  • Change in systems has been managed, resulting in traceability from requirements to implemented systems, enhanced stability, and elimination of unwanted or unneeded change
  • The “To-Be” Enterprise Architecture has been defined and a process for managing change in the Architecture has been implemented, leading to reduced uncertainty and risk, better decision-making and investment in technology, and increased project speed due to the availability of standards
  • Ownership of critical roles and processes is defined, and staff teams clearly understand their tasks and expectations