Identify and briefly discuss the implications to a project team of classifying a piece of software as safety critical

When developing safety-critical systems, a key assumption must be that safety will not automatically result from following an organization’s standard development methodology. Safety-critical software must go through a much more rigorous and time-consuming development process than other kinds of software. All tasks—including requirement definition, systems analysis, design, coding, fault analysis, testing, implementation, and change control—require additional steps, more thorough documentation, and vigilant checking and rechecking. As a result, safety-critical software takes much longer to complete and is much more expensive to develop.