1. An Introduction to Software Engineering (Chapter 1 from the textbook)

2. Objectives l To introduce software engineering and to explain its importance l To set out the answers to key questions about software engineering

3. Topics covered l FAQs about software engineering l Professional and ethical responsibility

4. Software engineering l The economies of ALL developed nations are dependent on software (as typical consumers of the software products). l More and more systems are software controlled ( The software is like the glue that is required to put the pieces together (new cars include 10’s of micro-programs) l Software engineering is concerned with theories, methods, practices and tools for professional software development. l Without complex software we would not have explore the space, or would not have the Internet, and modern telecommunication. Travel will be much harder, complex, inconvenient and dangerous.

5. Software costs l Software costs often dominate computer system costs. The costs of software on a PC are often greater than the hardware cost. l Software may cost more to maintain than it does to develop. For systems with a long life, maintenance costs may be several times development costs. l Software engineering is concerned with cost- effective software development.

6. FAQs about software engineering l What is software? l What is software engineering? l What is the difference between software engineering and computer science? l What is the difference between software engineering and system engineering? l What is a software process? l What is a software process model?

7. FAQs about software engineering l What are the costs of software engineering? l What are software engineering methods? l What is CASE (Computer-Aided Software Engineering) l What are the attributes of good software? l What are the key challenges facing software engineering?

8. What is a software? l A computer program and the associated documentation such as requirements, design models and user manuals. l Software products may be developed for a particular customer or may be developed for a general market. l Software products may be Generic - developed to be sold to a range of different customers such as the all PC software (e.g. Excel, Word, etc.). Bespoke (custom) - developed for a single customer according to their specification. Newer versions of an existed software. Updates, fixes and batches. Programming languages. Operating Systems.

9. What is Software? l New software can be created by developing new programs, configuring generic software systems or reusing existing software. l software is engineered (This means that it is like any other engineering discipline (e.g. civil engineering) requires plans, designs,..etc.). l software doesn’t wear out ( like an old building), but it may become obsolete, needs fixes, baths, upgrades. l software is complex ( For example it is not easy to evaluate a successful software as in evaluating a successful building as it has much more quality attributes).

10. Legacy Software Why must it change? Software must be adapted to meet the needs of new computing environments or technology ( such as richer GUIs, 3D, multi-threads, etc.). Software must be enhanced to implement new business requirements that are maybe required by customers. Software must be extended to make it interoperable with other more modern systems or databases. Software must be re-architected to make it viable within a new network environment.

11. What is software engineering? l Software engineering is an engineering discipline that is concerned with all aspects of software production (planning, design, coding, etc.). l Software engineers should adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available.

12. What is the difference between software engineering and computer science? l Computer science is concerned with theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software. l Computer science theories are still insufficient to act as a complete underpinning or infrastructure for software engineering (unlike e.g. physics and electrical engineering).

13. What is the difference between software engineering and system engineering? l System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. l Software engineering is part of this process concerned with developing the software infrastructure, control, applications and databases in the system. l System engineers are involved in system specification, architectural design, integration and deployment.

14. What is a software process? l A set of activities whose goal is the development or evolution of software. l Generic activities in all software processes are: Specification - what the system should do and its development constraints Development - production of the software system Validation and testing - checking that the software is what the customer wants and test it for errors. Evolution - changing the software in response to changing demands.

15. What is a software process model? l A simplified representation of a software process, presented from a specific perspective. l Examples of process perspectives are Workflow perspective - sequence of activities; Data-flow perspective - information flow; Role/action perspective - who does what. l Generic process models Waterfall; Iterative development; Agile development.

16. What are the costs of software engineering? l Roughly 60% of costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs. l Costs vary depending on the type of system being developed and the requirements of system attributes such as performance and system reliability. l Distribution of costs depends on the development model that is used.

17. Software Applications l system software such as Windows l application software such as Office l engineering/scientific software - AutoCAD l embedded software such as the BIOS l product-line software l WebApps (Web applications) l AI software

18. Activity cost distribution

19. What are software engineering methods? l Structured approaches to software development which include system models, notations, rules, design advice and process guidance. l Model descriptions Descriptions of graphical models which should be produced; l Rules Constraints applied to system models; l Recommendations Advice on good design practice; l Process guidance What activities to follow.

20. What is CASE (Computer-Aided Software Engineering) l Software systems that are intended to provide automated support for software process activities. l CASE systems are often used for method support. l Upper-CASE Tools to support the early process activities of requirements and design; l Lower-CASE Tools to support later activities such as programming, debugging and testing.

21. What are the attributes of good software? l The software should deliver the required functionalities and performance to the user and should be maintainable, dependable and acceptable. l Maintainability : The Software must evolve to meet changing needs; How much it is easy to maintain the software or keep it running as expected (i.e. the amount of effort required to keep the software running). l Dependability Software must be trustworthy; Can we depend on this software (i.e. reliability). l Efficiency Software should not make wasteful use of system resources; l Acceptability Software must be accepted by the users for which it was designed. This means it must be understandable, usable and compatible with other systems.

22. What are the key challenges facing software engineering? l Heterogeneity, delivery and trust. l Heterogeneity – Portability. Developing techniques for building software that can cope with heterogeneous platforms and execution environments; l Delivery Developing techniques that lead to faster delivery of software; l Trust – Through Validation and verification Developing techniques that demonstrate that software can be trusted by its users.

23. Key Constraints in a software projects The triple constraints l Resources: Which includes the humans or the employees such as developers, testers and equipments such as the PCs. l Time : The time to develop the software. This can be specified through a specific client, or in generally to reach the market early and have a bigger share than competitors. l Budget: Which include the amount of money allocated to the project.

24. Software’s Dual Role l Software is a product Delivers computing potential Produces, manages, acquires, modifies, displays, or transmits information l 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)

25. Key points l Software engineering is an engineering discipline that is concerned with all aspects of software production. l Software products consist of developed programs and associated documentation. Essential product attributes are maintainability, dependability, efficiency and usability. l The software process consists of activities that are involved in developing software products. Basic activities are software specification, development, validation and evolution. l Methods are organised ways of producing software. They include suggestions for the process to be followed, the notations to be used, rules governing the system descriptions which are produced and design guidelines.

26. Key points l CASE tools are software systems which are designed to support routine activities in the software process such as editing design diagrams, checking diagram consistency and keeping track of program tests which have been run.