Question

• Why do we need Subcontractor in Software and System Integration process? How does it help to ensure quality of integrated system?
• How do we Improve the quality and productivity during the software and system integration process?

Answer 1

Software Subcontractor
The roles and responsibilities of the software subcontractor describe how a program and projects can benefit and rely on outside companies’ resources to provide required software and hardware products to be under contract and effective. A customer must understand the subcontractor’s presentation, in which the subcontractor presents his expertise in supporting the lifecycle activities and how companies can use his knowledge. During the presentation, the subcontractor should allow the customer to ask any questions in order for the subcontractor to provide answers that meet the customer’s needs for reliability and support. The software subcontractor provides the necessary support and employment that benefits military and aerospace programs and projects. The software subcontractor can be hired for program and project planning, configuration management, quality, software design and development, testing, and the execution of activities or tasks related to the delivery of software work products to customers. The activities performed are in accordance with a purchase contract and the software work products are delivered to satisfy and comply with specified acceptance and delivery requirements.

A list of requirements, expectations, and interfaces between the program and project are documented in a SOW. The goals of selected software processes are given to the subcontractor per the direction of program and project managers in order to provide plans for required tasks during a software lifecycle. This permits the software subcontractor to abide by internal software processes that require objective evidence to be reviewed and ensure goals are being accomplished.

Software and Systems Integration
The software and systems integration method provides a consistent approach to effective integration activities. The software units, components, and sub-systems are assembled by the software designers and test teams to ensure the software and systems elements are created properly. The integration levels and the development plan (DP) for software determine if constructed elements are ready and subject to verification or validation activities. The development plan establishes the plan for development of software during the phase of the program. This plan establishes system level engineering standards, practices, and guidelines for development of CI and non-CI system software.

The effective methods and processes for software and systems integration require disciplined software design and development practices, including test planning, test execution, configuration control, quality, and reporting to management and the customer of the work product being tested inside integration facilities. Software technology books, magazines, and articles all over the world are intended to reflect "best practices" from various integration facilities supporting software companies, military, and aerospace programs and projects. It is the responsibility of management to select effective and responsible test conductors and teams. Successful software and systems integration objectives are accomplished by:

• Agreeing and identifying blocking issues
• Assigning responsibility to fixing blocking issues
• Scheduling dates from responsible teams
• Holding periodic meetings until issues and concerns are closed out
• Evaluating current integration facilities schedules