I have been assigned as CM on an OTA project or Other Than Authority Project, very similar to IR&D or prototype. I have written a cm plan based on a department cm plan and modified for the project. But after discussion with the project lead today, and answered responses to a review of drafted CM plan. They want little to no CM support, not even recording or archiving their CDRLs. They would much rather rely on each area to draft, review, and provide CDRLs to customer early on, plus they are using Sharepoint as well to allow customer to review their CDRLs.
here is a definition of an OTA found on the web. What is Other Transaction Authority (OTA)?
what is the role of software builds like private, integration and release builds in software development life cycle? What kind of documentation is required at build level? Can i allocate version no to a build and when version allocation came into action?
Ryan Kenney, senior consultant at Coveros, chats with TechWell community manager Owen Gotimer about the difference between containers, container engines, and container orchestration; using containers in your CI/CD pipelines; and the cost of security.
We may need to switch from our long standing, 20+ years use of PVCS VM to GIT. CM would like to maintain a Master repository with no branching but allow the developers the freedon to do so bur then merge back into the master. Also are their resources available on pulling information from GIT repository for reports as in a list of files, revisions and change dates for each baseline? Is their any formal training available for GIT and setting it up? Thanks for any guidance on this.
If you want to trigger long-running, end-to-end automated tests, you must integrate the test execution system with the continuous integration system. But this job falls in a fuzzy area that meets at the nexus of feature development, test automation development, quality assurance, and build and release engineering. Here's how to decide who should be responsible for the setup.
Tools like JIRA, Service Now for Incident management, I'm looking for a software platform that will keep track of all related documentation, test plans, user sign offs etc... But what I have not been able to find and is critical for me is a Parent - Child, Child - Child relationship of all changes.
I'm the Configuration Manager for a large enterprise project. I was added to the team after around 8 months worth of developement/staging had already taken place. We're working toward a short-term ATO, and PMO is looking to baseline our applications. My argument is that we're not ready to baseline, as we're still in developemnt. No configuation items are recorded in Remedy, the Change Managemnet process isn't fleshed out (as that is also my tasking), and we have no historical records that I can find for how are architecture came to this point. Simply, here, this is version one, and now start documenting from this point forward. Am I worng in my push-back on this stance? Shouldn't I first work to identify the CIs and their historical changes (as best as I can documnet)? Further info: this system will be the subject of an offical audit, not just my configuration audit.