1. HNDIT23082– Principals of Software Engineering
Week 1: Introduction to Software Engineering

2. Software Engineering Overall Objectives:
 After successfully completing this module, students should be able to:
 Explain the principles of software engineering and appreciate the need for engineered process in software development
Understand and be fluent in the use of software engineering terminology and nomenclature
Be capable of intelligently communicating with most members in a software development organization (management, analysts, architects, developers, ...)

3. Be able to create and use planning, requirements analysis, domain analysis and design artifacts and carry them into code.
Be capable of taking on the role of systems analyst in a software development organization
Be able to document all phases of the software development processes 

4. Outline Syllabus Introduction to software engineering
Software development life cycle – from requirements analysis to software design, Coding, testing, maintenance etc.
Software requirement specification – different models for identifying software requirements

5. Software design methodologies
Coding and documentation
Software Testing
Software Project Management
Software Configuration Management

7. Main References
Ian Sommerville, Software Engineering, 6th Edition, Addison Wesley, 2000.
R Pressman, Software Engineering - A Practitioners Approach, 5th Edition, McGraw Hill.

8. Software Engineering Introduction
Learning Outcomes
Appreciate the problems associated with developing software
Understanding the need for a managed approach to software development
Be able to define the term ‘Software Engineering’
Identify software quality attributes and their classification

9. Student Center Activity with First Chapter
Goal 1
Activites
Assess
The student will know the fundamentals of Software Engineering process
Define software and software Engineering.
Knowledge and Analysis
Analysis
Differentiate SE and computer Science
3. List various cost associated with SE
Knowledge
4. List attributes of good SW
Discuss key challenges in SE
Explain CASE with examples
Application , Synthesis

10. Software Instructions given to a computer (computer programs)
 Systems software
 Application software

11. Types of software System Software:
System software is a collection of programs written to service the other programs.
eg. Operating systems, drivers, compilers communication software.

12. Types of software… Web-based software:
The network becomes a massive computer providing an almost unlimited software resources that can be accessed by anyone with a modem.
Artificial intelligence software:
All software makes use of non numerical algorithms to solve the complex problems that are not amenable to computing or straightforward analysis.

13. Hardware vs Software
cost
software
hardware
Time
1960
2002

14. Failure curve for hardware [Pressman]
Failure rate
Wear out
Infant
mortality
Time

15. Failure curves for software -Pressman
Failure rate
Failure curves for software -Pressman
Increase failure rates due to side effects
change
Actual curve
Idealized curve
Time

16. Development Failures
Examples
IBM Survey, 2000
55% of systems cost more than expected
68% overran the schedules
88% had to be substantially redesigned
Bureau of Labour Statistics (2001)
for every 6 new systems put into operation, 2 cancelled
probability of cancellation is about 50% for large systems
average project overshoots schedule by 50%

17. The Statistics

18. Distribution of software cost over life cycle
Requirements capture
Requirement specification 14%
Design
Implementation
Testing 6%
Maintenance 60%
40%

19. Software Problems 3. The quality of software is not satisfactory.
Time Schedules and cost estimates of many software projects are grossly inaccurate.
2. Software is costly.
3. The quality of software is not satisfactory.
4. Software is difficult to maintain.
5. The productivity of software people is not
satisfactory to meet the demand.

20. What makes software special?
The main difference in software engineering compared to other engineering disciplines are listed below.
It is difficult for a customer to specify requirements completely.
It is difficult for the developer to understand fully the customer needs.
Software requirements change regularly.
Software is primarily intangible; much of the process of creating software is also intangible, involving experience, thought and imagination.
It is difficult to test software exhaustively.

21. A Solution – Software Engineering
Greater emphasis on systematic , scientific development.
Computer assistance in software development (CASE)
A concentration on finding out the user’s requirements
Formal/Semi Formal specification of the requirements of a system.
Demonstration of early version of a system (prototyping)
Grater emphasis on development of error free easy to understand code.

22. Software engineering approach
What is the software engineering?
Software engineering is an engineering discipline which is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use. In this definition there are two key phrases.
What is the difference between software engineering and computer science?
Computer science is theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software.
What is the difference between software engineering and system engineering?
System engineering is concerned with all aspects of computer-based system development, including hardware, software and processor engineering. Software engineering is a part of this process

23. Evolution of software engineering
Software development began as a single person activity in 1940s and 1950s.
Software engineering was considered a new scientific discipline in 1960s and 1970s.
In 1980s and 1990s engineering ideas dominated software development

24. Software Engineering Simple definition :
Designing, building and maintaining large software systems.
Others
=> ‘Software engineering is concerned with the theories, methods and tools for developing, managing and evolving software products’ - I Sommerville

25. => ‘The practical application of scientific knowledge in the design and construction of computer programs and the associated documentation required to develop, operate and maintain them’
- B.W.Bohem
=> ‘ The establishment and use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines’
- F.L. Bauer
=> ‘The application of systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software’
- IEEE Standard

26. Software Engineering – Definition
‘Use of systematic, engineering approach in all stages of software development and project management to develop high quality and economical software using appropriate software tools.’

27. Software engineering approach
What is the software engineering?
Software engineering is an engineering discipline which is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use. In this definition there are two key phrases.
What is the difference between software engineering and computer science?
Computer science is theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software.
What is the difference between software engineering and system engineering?
System engineering is concerned with all aspects of computer-based system development, including hardware, software and processor engineering. Software engineering is a part of this process

28. Software Quality Attributes
Bohem’s Classification
Current usefulness
- The qualities expected from a software system in user’s point of view.
Potential Usefulness
- The qualities expected from a software system in developer’s point of view.

29. Current usefulness Reliability Usability Correctness User friendliness
Efficiency
Reliability
Usability
Correctness
User friendliness
Robustness

30. Potential usefulness Modularity Reusability Portability
Maintainability
Modularity
Reusability
Portability

31. McCall’s Classification
Product operation
Product revision
Product transition

32. Product Operation Correctness User friendliness Usability Reliability
Efficiency
Correctness
User friendliness
Usability
Reliability
Robustness

33. Product Revision Product Transition Flexibility Testability
Maintainability
Flexibility
Testability
Product Transition
Interoperability
Reusability
Portability

34. Changes in the user requirements Availability of new technology
Software Maintenance
Any software system needs to be changed. Maintenance is the costliest operation in the software development process (about 60%). Software need to be changed due to various reasons.
Errors in the system.
Changes in the user requirements
Availability of new technology
Changes in the enterprise or Govt. policy.

35. Review Questions Look at the following list of goals of software
a) Meeting the user’s needs
b) Low cost of production
c) High Performance
d) Portability
e) Low cost of maintenance
f) High Reliability
e) Delivery on time

36. For each of the following systems choose the two most important
goals.
A system to manage student fees – to track whether they have paid, calculate the correct amount, issue invoices, send out reminders etc.
A system to manage the temperature of a nuclear reactor core.
An experimental program to test the efficiency of an algorithm for some mathematical theory.
A program that allows viewing of cricket scores on mobile phones.

37. 3. Where are the most errors introduced in software projects?
2. Which stage of software development is most expensive?
3. Where are the most errors introduced in software projects?
4. What do project managers say is the worst problem (consequence) in software projects?
5. ‘All Microsoft software is bug free ‘ – Bill Gates
Is he correct?
6. Define the term ‘Software Engineering’.

38. Multiple choice quiz