1 / 15

(Trimester I Session 2002/2003) foe.mmu.my/course/ecp4156

ECP 4156 SOFTWARE ENGINEERING. (Trimester I Session 2002/2003) http://foe.mmu.edu.my/course/ecp4156 Lecturer / Tutor Name : Mr. R. Logeswaran Email : loges@mmu.edu.my Room : CR4073 (FOE). Course Overview. Assessment Final Exam 60% Assignment / Project 20% Midterm Test 10%

Download Presentation

(Trimester I Session 2002/2003) foe.mmu.my/course/ecp4156

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. ECP 4156SOFTWARE ENGINEERING (Trimester I Session 2002/2003) http://foe.mmu.edu.my/course/ecp4156 Lecturer / TutorName : Mr. R. LogeswaranEmail : loges@mmu.edu.myRoom : CR4073 (FOE) Software Engineering

  2. Course Overview • Assessment • Final Exam 60% • Assignment / Project 20% • Midterm Test 10% • Tutorial 10% • Project (assessed as assignment, presentation, quiz) • Exercises • Reference Book : “Software Engineering: A Practitioner’s Approach”, 4th Ed., Roger S. Pressman, Mc-Graw-Hill, 1997 Software Engineering

  3. Lecture Objectives • To define the software engineering process • To understand the importance of software engineering • To discuss the important characteristics of software • To understand that the quality of different applications may be evaluated differently Software Engineering

  4. Introduction to Software Engineering Simple program : “Write a program to get a list of students’ test marks, calculate the grades and print a report of the results” What the customer wants What the software developer understands What the customer gets Software Engineering

  5. Typical Approaches • Go to the computer and immediately write the program • Find an old program and modify it • Discuss with friends on how to do it • Ask the lecturer for more information about the program Software Engineering

  6. What is Software Engineering • Software • programs that provide function & performance • data structures for information manipulation • documents that describe the operations and use of the programs • Engineering • A discipline that applies scientific and technical methods in the design and production of a product Software Engineering

  7. Definition of Software Engineering IEEE Definition : The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software --- 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 (Boehm) Software Engineering

  8. Objectives of Software Engineering • To improve quality of software products • To increase customer satisfaction • To increase productivity • To increase job satisfaction “This is not a programming course” Software Engineering

  9. Historical Background • Early days of computing, • programs were written to make hardware work • Programming was not a discipline, more like a hobby or “art form” • However, computer developments requires • larger programs to be developed e.g. compilers and operating systems • Programming became a profession Software Engineering

  10. Computer Expenditure 100% Hardware Maintenance Software Development Software Maintenance 1955 1980s Software Engineering

  11. Software Crisis • The large programming projects required many programmers working together • The projects were not delivered on time and costs more than initial budget - software crisis • Software Engineering methods were developed to overcome these problems Software Engineering

  12. The Systematic Process Problem Analysis Design Models Development Solution Testing Software Engineering

  13. Software Characteristics • Software is developed or engineered, not manufactured in the classical sense • Software doesn’t “wear out” • Most software is custom-built, rather than being assembled from existing components Software Engineering

  14. What Is A Good Software? • Software is intangible • Good software is subjective • Some qualities that is used to assess: - correctness - reliability - usability - integrity - reusability Software Engineering

  15. Software Applications • System Software • Real-time Software • Business Software • Engineering & Scientific Software • Embedded Software • Personal Computer Software • Artificial Intelligence Software Software Engineering

More Related