Straighten out the misguided Software Engineering by Romi Satria Wahono classdiagram.jpgRekayasa Software (Software Engineering), slightly shifting the meaning of the reality of the industrialized world, business, education and curriculum of the Information Technology (IT) in the country. In industry, the tester, debugger and programmer often mistakenly hold the title of Software Engineer. SMK in Indonesia too talkative by opening Software Engineering majors, although the curriculum to teach only the C language or Pascal (perhaps more fitting called computer programming majors) ;) This paper is trying to straighten out the misunderstanding that occurred on Software Engineering (Software Engineering) by agreement , reference, and standards that exist internationally. History of the emergence of Software Engineering is actually motivated by the crisis of software (the software crisis) in the era of the 1960s. Software crisis is a direct result of the birth of the computer generation of sophisticated 3, characterized by the use of Integrated Circuit (IC) to the computer. Increasing hardware performance, making the need to produce better software. As a result, the resulting software to be several times larger and more complex. Informal approach is used at the time in software development, to be not quite effective (in cost, time and quality). Began falling hardware costs and software costs to be rising rapidly. That's why the thought came to use the engineering approach is more definite, effective, and measurable standards in software development. From the literature, we can conclude that software engineering is: A discipline that addresses all aspects of software production, ranging from the early stages of requirement capturing (analysis of user requirements), specification (defining the specification of user requirements), design, coding, testing to maintenance of the system after use. The phrase "all aspects of software production" implies that that Software Engineering is not only related to the technical problems of software development but also the strategic activities such as project management software, the determination of the method and process development, as well as theoretical aspects, all of which support the production software. Then not be forgotten that the definition of the software not only to computer programs, but also includes documentation and configuration-related data necessary to make the program operate correctly. With this definition automatically output (output) production of computer software programs as well in addition to complete documentation associated with it. It is sometimes poorly understood by developers, so it considers sufficient to provide a road program (running program) to the user (customer). Software engineering is not a branch of Computer Science technical study of coding. It is often mistakenly understood, so that students, prospective students or even professors ;) shock when confronted with books on Software Engineering textbook which is always thick with extensive explanations of how software is produced, from the aspect of capturing requirements, design, architecture, testing, quality software, until the people / cost management. And this is an agreement that has been generally accepted on Software Engineering, from the time of Roger S Pressman wrote the book "Software Engineering: A Practitioner's Approach", until Ian Sommerville who then came up with the book "Software Engineering" which was to issue to 7, and Such newcomers Hans Van Vliet, Shari Lawrence Pfleeger and James F. Peters. And what if we want to deepen the technical problems of coding and programming? There are two other branches of science are discussed further in this matter, namely: Algorithms and Data Structures, and Programming Languages. How come so, basically where? So in essence, as a discipline, Computer Science also has a definition, scope, classification and categorization. The most well-known classification issued by the Task Force established by the IEEE (Institute of Electrical and Electronics Engineers) and ACM (Association for Computing Machinary (http://acm.org)), led by Peter J. Denning, who became known as the Matrix Denning . It is clear that the matrix Denning separate branch of Software Engineering with Algorithms and Data Structures, and Programming Languages. That was the beginning of the paragraph I mentioned that it is more appropriate vocational school, college or university using the name of the department (or courses): Computer Programming, Algorithms and Data Structures, or programming language, if that material is just learning a programming language problem technically. Well keep up the question again, so what is the actual scope of what science is Software Engineering? This question is a question many people, a growing number of researchers and practitioners to write, the more varied understanding of the emerging, more and more books are published increasingly confuse students and students in understanding what is a comprehensive software engineering. Anxiety is answered completely by the IEEE Computer Society (http://computer.org) by forming a team in 1998 when the team began to develop an understanding of standards (body of knowledge) about the field of Software Engineering, which was then known as the SWEBOK (Software Engineering Body of Knowledge). Already there are two versions of this SWEBOK, which is the last published in 1999 and 2004. There is no ivory that is not crack wise words, IEEE Computer Society project on SWEBOK is actually also widely criticized by other scholars. At least two of the great world of Software Engineering is Cem Kaner and Grady Booch do not necessarily agree with the material that is in the SWEBOK, and even called as a guide the misguided ;) Apart from that, so to speak SWEBOK quite acceptable for many. SWEBOK Besides, there are actually other similar project in an effort to develop an understanding of standards in the field of Software Engineering, the CCSE (Computing Curriculum Software Engineering). This project is also sponsored by the IEEE Computer Society and ACM, is only slightly different orientation, which is to establish a standard curriculum-related software engineering disciplines. This is in contrast with the more general orientation SWEBOK world surrounding academics and practitioners. Note: The complete edition of this paper can be read in a magazine June 2006 issue of Natural Resources Magazine. REFERENCES  Guide to the Software Engineering Body of Knowledge 2004 Version (SWEBOK), A Project of the IEEE Computer Society Professional Practices Committee, http://www.swebok.org, 2004.  IEEE Standard Glossary of Software Engineering Technology, IEEE Std 610.12- 1990, Institute of Electrical and Electronics Engineers, New York, 1990.  Hans Van Vliet, Software Engineering - Principles and Practice, John Wiley & Sons, 2000.  Peter J. Denning, Computer Science: the Discipline, In Encyclopedia of Computer Science (A. Ralston and D. Hemmendinger, Eds), 1999.  James F. Peters and Witold Pedrycz, Software Engineering: An Engineering Approach, John Wiley & Sons, 2000.  Roger S. Pressman, Software Engineering: A Practitioner's Approach Fifth Edition, McGraw-Hill, 2004.  Ian Sommerville, Software Engineering 7th Edition, Addison-Wesley, 2004.