Achieving Better Buying Power through Acquisition of Open Architecture Software Systems. Volume 2 Understanding Open Architecture Software Systems: Licensing and Security Research and Recommendations
University of California, Irvine Irvine United States
Pagination or Media Count:
This research focuses on continuing investigation and refinement of techniques for identifying and reducing the costs, streamlining the process, and improving the readiness of future workforce for the acquisition of complex software systems. Emphasis was directed at identifying, tracking, and analyzing software component costs and cost reduction opportunities within the acquisition life cycle of open architecture OA systems for Web-based and mobile devices, where such systems combine best-of-breed software components and software products lines SPLs that are subject to different IP license and cybersecurity requirements. The investigation focuses on four project work activities Investigating the interactions between software system acquisition guidelines and processes, and the cost consequences of alternative software system architectures incorporating different mixes of OSS and CSS components subject to different licenses within secure OA SPLs ScA08, ScA12b, ScA13a, ScA13b, ScA13c. This entails exploring the balance between development, verification, and validation of software licenses and security rights, as well as the software componentlicense costs while managing the development and evolution of OA systems at design-time, build-time, and release and run-time. Developing formal foundations for establishing acquisition guidelines program managers can use in reduced cost acquisition of software-intensive systems that rely on development and deployment of secure OA systems using OSS and SPL technology and processes AlS10, AlS13, ScA11, ScA12a, ScA12b, ScA13a, ScA13b, ScA13c. Continuing to develop concepts contributing to the emerging design of an automated approach supporting acquisition of secure OA systems by a determining their conformance to acquisition guidelinespolicies, contracts, and related license management issues, and release and run-time.