Compare and contrast software analysis techniques Essay

Compare and contrast software analysis techniques - Essay Example After the detection of that fault in the fifth month, a software programmer was contacted and briefed with the entire story. Even a small miscalculation can lead to a bad reputation and penalties from regulatory authorities that may lead to business loss. Similarly, a software malfunction was detected in November 1979, where the strategic air commander receives an alert scramble. The scramble alarm indicated that the Worldwide military Command and Control System (WWMCCS) reported that the Soviet Union has launched missiles that are moving towards the United States of America (Software engineering (sie) 7E). Likewise, later it was found that the simulated attack was considered as a real attack, however, the U.S department of defense has not provided the details of that incident as it was marked as confidential. Conclusively, it was also a software fault that may have intimated U.S to launch a counter attack. With these two examples of billing a customer or getting false alarms in air defense, the completion time of software is always late, over budgeted or with many faults and may not cope with clients requirements. To overcome, these issues, software engineering methods are invented. Likewise, it is an attempt to provide a solution of these problems. In this brief, we will discuss two software engineering techniques i.e. formal software engineering and semi-formal software engineering. 2 Formal Software Engineering Techniques There are various formal software engineering techniques available; however, they are exceedingly diverse. For instance, Anna is considered to be a formal specification language pertaining to Ada (Luckham, von Henke, Krieg-Brueckner, & Owe, 1987). Likewise, some of the formal techniques are based on knowledge such as Gist, as it was designed for describing processes aligned with user friendliness i.e. the closest alignment of describing the process. Likewise, this is only achievable by formulating the constructs that are utilized in natura l languages. The Gist specifications are very difficult to read in practice, a separate paraphrasing tool has been deployed from Gist to English. Moreover, one more formal software engineering technique known as (Schach, 1993) Vienna definition method (VDM) is also invented. Likewise, this technique is based on DE notational semantics (Fitzgerald & Larsen, 2009). Moreover, one remarkable factor of this technique encompasses not only on the application but the design and deployment, as well. The VDM technique has been successfully applied in many projects, most amazingly on the ‘Datamatik Center development’ that was integrated with DDC AdaCompiler System (Diaz & Orejas, 1989). A unique perspective of reviewing specifications is to analyze them in the context of sequences of events. Likewise, an event can be an ordinary action or a communication signal that transmits data inward or outward of the system. For instance, a case study related to an elevator, where one event comprises of pressing the button of the elevator for floor f on elevator e along with its consequential illumination. Similarly, another event comprises of elevator e that is leaving the floor f downwards along with cancellation of illumination that is associated with conforming floor button. The CSP language abbreviated as the Communication Sequential Processes (CSP) is invented by Hoare in