Process
STiGZ Infinity’ follows the defined set process for each activity. The typical cycle starts with system requirements followed with traceability of each requirement. The business cases are converted in to software, mechanical and automation functional requirements. The architectural design phase follows by the freezing of functional requirements.
The architectural design brings out Interface requirements and getting in to conceptual models would further augment the entire solution structure.
The detailed design follows with the requirements traceability and the reviews at each stage ensures that the deviation from the original track is minimal. The overall design is shared with the customer to get the feeling of how the solutions looks like and any changes are recorded. The change management process is followed for the changes.
The configuration management practices ensure the proper visioning and control. The design cycle goes for the review cycle at each and every phase and the practice goes on till the mapping between the actual requirement and design representation matches with each other. The design is verified for fail proof mechanisms and wherever required the FEMA is done.
The design phase is followed by execution phase with strict control over each activity being mapped through the design. The quality testing requirements evolved during design phase gets implemented in execution stage with real time inspection of components / sub-assemblies. The assemblies get tested for functional requirements followed by performance tests. The test reports are properly reviewed for deviation and unless the set standards are reached the iteration goes on.
The required performance test result ensures that the iteration stops and each time the regression tests ensure that the solution flows the documented design cycle.
The Gantt chart is followed from the beginning and project management is done for proper time and resource management. The deviation in plan is recorded and whenever required additional resources are pooled to ensure the schedule lapses are avoided. The weekly reviews are submitted to client for the critical feedback system where in client gets real feedback on the progress.
The R&R study is conducted at the end of performance testing and client is called for the FAT trails at the end of R&R successful internal trails. I most cased the FAT trails being the formality as everything gets internally verified any changes as per the environment at client end or calling for new changes requires further iteration.