Mya is a programmer on the new inventory tracking system.She looks in the development library for a module that she needs to modify and changes a couple of lines in that module.BUT … at the same time Steve was also working on that module - getting it from the library before Mya did - and putting it back in the library after Mya made her changes and saved it.One common solution to this problem might be:
A)To hold weekly meetings so Mya and Steve could discuss this
B)To have all developers (including Mya and Steve)e-mail all other developers as they make changes to a module
C)Have a program log / check-out system which would show that the module was already checked out (in this case to Steve)and that modifications can not be made until he checks it back in
D)Have all developers call the Project Manager with any and all changes
E)Have a 'white board' in the development area, where a programmer can write down the modules he/she is working on - and ask all developers to check the white board before making changes

Question

Quizplus · Accepted Answer

Having a program log/check-out system ensures that developers are aware of who has checked out a module and prevents multiple developers from modifying the same module at the same time. This is a common practice in software development teams to avoid conflicts like the one described in the scenario. The other options may not be as effective in preventing conflicting edits or may be too time-consuming for daily use.

Mya Is a Programmer on the New Inventory Tracking System