3
Download as PPT, PDF1 like513 views
Software Engineering involves developing software systems on time, on budget, with acceptable performance and correct operation. It is concerned with theories, methods and tools for professional software development. Software costs often dominate system costs and software is more expensive to maintain than develop. There are different types of software products and processes used for development.
3
- 1. Software Engineering Software Engineering is the science and art of building significant software systems that are: 1) on time 2) on budget 3) with acceptable performance 4) with correct operation.
- 2. Software Engineering The economies of all developed nations are dependent on software. More and more systems are software controlled. Software engineering is concerned with theories, methods and tools for professional software development. Software engineering expenditure represents a significant fraction of the GNP of developed countries.
- 3. Software Costs Software costs often dominate system costs. The costs of software on a PC are often greater than the hardware cost. Software costs more to maintain than it does to develop. Software engineering is concerned with cost-effective software development.
- 4. Software Products Generic products: Stand-alone systems which are produced by a development organization and sold on the open market to any customer. Customized products: Systems which are commissioned by a specific customer and developed specially by some contractor.
- 5. Software Product Attributes Maintainability Dependability Efficiency Usability
- 6. The Software Process Structured set of activities required to develop a software system Specification Design Validation Evolution Activities vary depending on the organization and the type of system being developed. Must be explicitly modeled if it is to be managed.
- 7. Engineering Process Model Specification : Set out the requirements and constraints on the system. Design : Produce a model of the system. Manufacture : Build the system. Test : Check the system meets the required specifications. Install : Deliver the system to the customer and ensure it is operational. Maintain : Repair faults in the system as they are discovered.
- 8. Generic Software Process Models Waterfall Separate and distinct phases of specification and development Evolutionary Specification and development are interleaved Formal Transformation A mathematical system model is formally transformed to an implementation Reuse-based The system is assembled from existing components
- 11. Process Model Problems Waterfall High risk for new systems because of specification and design problems. Low risk for well-understood developments using familiar technology. Prototyping Low risk for new applications because specification and program stay in step. High risk because of lack of process visibility. Transformational High risk because of need for advanced technology and staff skills.
- 12. Hybrid Process Models Large systems are usually made up of several sub-systems. The same process model need not be used for all subsystems. Prototyping for high-risk specifications. Waterfall model for well-understood developments.
- 14. Spiral Model Advantages Focuses attention on reuse options. Focuses attention on early error elimination. Puts quality objectives up front. Integrates development and maintenance. Provides a framework for hardware/software development.
- 15. Spiral Model Problems Contractual development often specifies process model and deliverables in advance. Requires risk assessment expertise.
- 16. 6.7. Rapid Prototyping Key idea : Customers are non-technical and usually don’t know what they want/can have. Rapid prototyping emphasises requirements analysis and validation, also called: customer oriented development , evolutionary prototyping
- 17. Requirements Capture Quick Design Build Prototype Customer Evaluation of Prototype Engineer Final Product The Rapid Prototype Workflow Iterate
- 18. Advantages Reduces risk of incorrect user requirements Good where requirements are changing/uncommitted Regular visible progress aids management Supports early product marketing
- 19. Disadvantages An unstable/badly implemented prototype often becomes the final product. Requires extensive customer collaboration Costs customers money Needs committed customers Difficult to finish if customer withdraws May be too customer specific, no broad market Difficult to know how long project will last Easy to fall back into code-and-fix without proper requirements analysis, design, customer evaluation and feedback.
- 20. Process Visibility Software systems are intangible so managers need documents to assess progress. Waterfall model is still the most widely used model.
- 23. Professional Responsibility Software engineers should not just be concerned with technical considerations. They have wider ethical, social and professional responsibilities. No clear rights and wrongs about many of these issues: Development of military systems Whistle blowing
- 24. Ethical Issues Confidentiality Competence Intellectual property rights Computer misuse