People who make art or practice of software craft or discipline for software engineering. But what is software engineering "practice"? included in the broader sense practice is a collection of concepts, principles, methods and tools, a software engineer calls on a daily basis. Practice allows executives to software project management and software engineers to construct computer programs. Practice responds to a model of software process with the technical and management procedures to do the job. Practice transforms a fuzzy random approach to something that is more organized, more efficient and more likely to succeed.
Basic Principles
The dictionary defines the word principle as "an important law underlying or assumption required in a system of thought" throughout this book, we discuss the principles at different levels of abstraction. Some focus on software engineering as a whole, while others believe a generic framework specific activity (such as client communications), and others focus on software engineering activities (eg architectural design) or technical tasks (eg, write a scenario of use). Whatever their orientation, principles to help us create a state of mind of solid software engineering practices. They are important for this reason.
First principle: why do not all
Software exists for one reason: to deliver value to its users. All decisions must be taken in this direction. Before specifying a system requirement, before any part of the functionality of a system before determining the hardware platforms or development processes, ask questions like: Is this a real value to the system? If the answer is no, no. All other principles support.
