A computer software engineer develops software systems to be used by their clients, such as a website used to sell the client's products. Although software engineers spend most of their time programming and testing software, a key component to a software engineer's success is the ability to write a thorough software requirements specification (SRS). An SRS documents the requirements and necessary dependencies for the software, before starting any programming. Therefore, a software engineer must know SRS is so important because engineers may have a wide range of clients that they work with on a regular basis. Public An SRS documents the requirements and necessary dependencies for the software, before starting any programming. This document requires a two-way understanding that ensures that both the customer and the engineer understand the needs and goals of the software. The first step in writing an SRS is to understand the customer's requirements and then clearly document them in terms the customer can relate to. This is where correctly analyzing the customer is very important on the part of the engineer because if the SRS is not correct and the engineer did not understand the customer, the program will not be what the customer wants, costing the company more time and money.Type of Writing and CommunicationAccording to the journal written by Lui et al., "correct understanding of user needs and appropriate design decisions almost always contribute considerably to the reliability of the software." Appendix A shows not only the importance of the specification document, but also the importance of the specification document being revised and developed several times before arriving at the final formal document… half of the document… Requirements Specification of ware." IEEE of software." International Journal Of Software Engineering & Knowledge Engineering 21.2 (2011): 259-288. Academic Search Premier. November 18, 2012. S. El-Kassas, et al. "Formal Analysis and Design for Automated Derivation of Engineering Security of formal software security specifications From goal-oriented security requirements." IET Software 4.2 (2010): 149-160. Academic Search Premier. Web. 18 November 2012. Wan-kadir and Pericles Loucopoulos. "Relating Evolving Business Rules to Software Design." Science Direct Department of Computing and Institute of Science and Technology, University of Manchester, July 2004. Web. . November 18. 2012.