What is Software? Computer Software is the product that software professional design and built.

. It includes Programs Content Documents What is software engineering? Your thoughts here Related to the process: a systematic procedure used for the analysis, design, implementation, test and maintenance of software. Related to the product: the software should be efficient, reliable, usable, modifiable, portable, testable, reusable, maintainable, interoperable, and correct.

The definition in IEEE Standard: The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, that is, the application of engineering to software. The study of approaches as in 1993: The Joint IEEE Computer Society and ACM Steering Committee for the establishment of software engineering as a profession. What is important and what are the steps?

Software affects nearly every aspect of our lives. (data). You build software like you build any successful product, by applying a process that leads to a high-quality result. You apply a software engineering approach. What is the work Product? From the point of view of a software engineer, the work product is the programs, documents, and content. From the users viewpoint, the work product is the resultant information that somehow makes the users world better. The Product Is the engine that drives business decision making. Software serves as the basis for modern scientific investigation and engineering problem solving. It is embedded in systems of all kinds: transportation, medical, telecommunications, military, industrial processes, entertainment, office products Softwares Dual Role

1.1 THE EVOLVING ROLE OF SOFTWARE

Software is a product

Delivers computing potential Produces, manages, acquires, modifies, displays, or transmits information.

Software is a vehicle for delivering a product Supports or directly provides system functionality Controls other programs (e.g., an operating system) Effects communications (e.g., networking software) Helps build other software (e.g., software tools) The Law of Continuing Change (1974): E-type systems must be continually adapted else they become progressively less satisfactory. The Law of Increasing Complexity (1974): As an E-type system evolves its complexity increases unless work is done to maintain or reduce it. The Law of Self Regulation (1974): The E-type system evolution process is selfregulating with distribution of product and process measures close to normal. The Law of Conservation of Organizational Stability (1980): The average effective global activity rate in an evolving E-type system is invariant over product lifetime. The Law of Conservation of Familiarity (1980): As an E-type system evolves all associated with it, developers, sales personnel, users, for example, must maintain mastery of its content and behavior to achieve satisfactory evolution. The Law of Continuing Growth (1980): The functional content of E-type systems must be continually increased to maintain user satisfaction over their lifetime. The Law of Declining Quality (1996): The quality of E-type systems will appear to be declining unless they are rigorously maintained and adapted to operational environment changes. The Feedback System Law (1996): E-type evolution processes constitute multi-level, multi-loop, multi-agent feedback systems and must be treated as such to achieve significant improvement over any reasonable base.