PI2134 Software Engineering IT Telkom

 Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic Framework Software Engineering

 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)

 Pressman: “Software is (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures that enable the programs to adequately manipulate information; and (3) documents that describer the operation and use of the programs.”  Sommerville: “Computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market.”

 Software is developed or engineered; it is not manufactured in the classical sense. The cost of developing software is focused in engineering process, so the software project cant be managed as in manufacturing project  Software doesn’t “wear out”.  Although the industry is moving toward component-based construction, most software continues to be custom built. a software component should be designed and implemented so that it can be reused.

 Definition: beliefs about software and the process used to build it – can be traced to the earliest days of computing.  The myths affect : ◦ managers, ◦ customers (and other non-technical stakeholders), ◦ and practitioners

 The book of standards can answer all the questions ◦ No! unless it is used, reflect modern SW engineering practice, complete, and adaptable  If we get behind schedule, we can add more programmers and catch up ◦ Adding people to a late SW project makes it later!  Outsourcing the project, so I can relax ◦ Of course not!

 A general statement of objective is sufficient to begin writing programs – we can fill in the details later. ◦ An ambiguous statement of objectives is a recipe for disaster!  Change can be easily accommodated because software is flexible ◦ Yes! But it will impact the cost, time, resource, and etc..

 Once we write the program and get it to work, our job is done ◦ Between 60-80% of all effort expended on software will be expended after it is delivered  Until I get the program running, I have no way of assessing its quality ◦ Software quality assurance mechanisms are important!

 The only deliverable work product for a successful project is the working program ◦ Documentation is need as guidance for software support  Software engineering will make us create voluminous and unnecessary documentation and will invariably slow us down ◦ Software engineering is not about creating document!

Software engineering is an engineering discipline which is concerned with all aspect of software production from the early stages of system specification through to maintaining the system after it has gone into use.

 Software definition  Characteristic of software  Software myths  Software Engineering definition