1 / 16

WXGE6103 Software Engineering Process and Practice

WXGE6103 Software Engineering Process and Practice. Introduction to SE. References. Sommerville, I. 2007. Software engineering . Eighth Edition. Addison-Wesley. ( Available in UM Pekan Buku)

sydnee-barron
Download Presentation

WXGE6103 Software Engineering Process and Practice

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. WXGE6103Software Engineering Process and Practice Introduction to SE Lecture 1: Introduction to Software Engineering

  2. References • Sommerville, I. 2007. Software engineering. Eighth Edition. Addison-Wesley. (Available in UM Pekan Buku) • Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli. 2003. Fundamentals of Software Engineering. Second Edition. Prentice Hall. • Pfleeger, S. L. 2006. Software Engineering: Theory and Practice. Third Edition. Prentice Hall.

  3. Course Blog http://busyairah.wordpress.com/

  4. SW SE SW PROCESS WXGE6103 SE COSTS SW PROCESS MODEL GOOD SW SE METHODS CASE

  5. Software Engineering (SE) • Def: An engineering discipline concerned with all aspects of sw production • practicality of developing sw • delivering useful & high quality sw • cost effective • The field of Software Engineering (SE) was born to overcome “software crisis“ (1968) • failures of software projects to meet schedule and budget constraints • SE has many sw development approaches

  6. Software (SW) • What is SW? • Computer programs + associated documentation and configuration data • Characteristics of SW • Abstract & intangible • Not constrained by material • Not governed by physical laws /manufacturing process - computer programs - configuration files - system documentation - user documentation - website Software

  7. Software (SW) • Types of Software • Generic product • Stand-alone, sold in open market • Customised product • Custom-built for particular customer

  8. Software Process • A set of activities and associated results that produce a software product • Generic activities in all software processes are: • Specification - what the system should do and its development constraints • Development - production of the software system • Validation - checking that the software is what the customer wants • Evolution - changing the software in response to changing demands

  9. Software process model • A simplified representation of a software process, presented from a specific perspective: • Workflow model - sequence of activities • Data-flow model - information flow • Role/action model - who does what • Generic process models • Waterfall • Iterative Development • Component based Software Engineering

  10. Attributes of good software • Maintainability • evolve to meet changing needs • Dependability • Software must be trustworthy • Efficiency • Software should not make wasteful use of system resources • Usability • Software must be usable by the users for which it was designed

  11. Software Engineering Methods • Structured approaches to software development which include system models, notations, rules, design advice and process guidance • Model descriptions • Descriptions of graphical models which should be produced • Rules • Constraints applied to system models (e.g. every entity have a unique name) • Recommendations • Advice on good design practice • Process guidance • What activities to follow • 1970s – Structured Analysis (JSD) • 1980s - OO methods (Booch, Rumbaugh) • 1990s – Unified approach

  12. CASE (Computer-Aided Software Engineering) • Software tools which are intended to provide automated support for software process activities. • Upper-CASE (Tools to support the early process activities of requirements and design) • Lower-CASE (Tools to support later activities such as programming, debugging and testing)

  13. Key Challenges SW ENG • Heterogeneity • Delivery • Trust

  14. Professional Ethics of Software Engineer • Confidentiality • Should not misrepresent own level of competence • Intellectual property rights • Computer Misuse

More Related