Software What Is Software?

Slides:



Advertisements
Similar presentations
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided with permission by R.S.
Advertisements

Developed by Reneta Barneva, SUNY Fredonia
Ch.1 Introduction to Software Engineering The Evolution 1.1 The Evolving Role of Software 1/15 In the early days: User Computer Software = Place a sequence.
Lecture 2 1 Introduction to Software Engineering.
CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
Software Engineering Course Instructor: Aisha Azeem.
LECTURE-2. Software Is a Product Designed by software engineers. Consists of : –Programs - that execute within a computer and provides desired functions.
1 SWE Introduction to Software Engineering Lecture 3 Introduction to Software Engineering.
Software Engineering II
SWE Introduction to Software Engineering
1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Introduction Course outline / Recommended books Course objectives Marks distribution / Schedule Basic concepts of SE and PM Project management framework.
INTROSE Introduction to Software Engineering Raymund Sison, PhD College of Computer Studies De La Salle University Software: Definitions,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 1 Supplementary Slides for Software Engineering: A Practitioner's.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter : Introduction to Software Engineering Ref. book : Software Engineering by Roger Pressman.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
Software Engineering B.Tech Ii csE Sem-II Unit-1 PPT SLIDES By Hanumantha Rao.N Newton’s Institute of Engineering 1.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 1 Software and Software Engineering Discussion of the Software Product.
1.1 The Evolving Role of Software
Chapter 1 The Product. 2 Product  What is it?  Who does it?  Why is it important?  How to ensure it be done right?
INPUT#3 SOFTWARE ENGINEERING. QUALITY SOFTWARE?  Satisfies the needs of the users and programmers involved with it.
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
1M.Sc(I.T.) VNSGU, Surat. Software is instructions (computer programs) that when executed provide desired function and performance, data structures that.
1 Chapter 1 The Product. 2 What is Software?  Pressman Instruction (computer programs) Data Structures Documents  Sommerville Software is computer programs.
SWE311_Ch01 (071) Software & Software Engineering Slide 1 Chapter 1 Software and Software Engineering Chapter 1 Software and Software Engineering.
1 Chapter 1 Software and Software Engineering Chapter 1 Software and Software Engineering copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering (CSI 321) Introduction to Software Engineering 1.
CMSC 345 Fall 2000 Software Design and Development.
Overview: Software and Software Engineering n Software is used by virtually everyone in society. n Software engineers have a moral obligation to build.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
Software Engineering Text Books:1. Software Engineering, A practitioner’s approach Roger s. Pressman McGraw-Hill 2. Software Engineering Somerville 3.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Rekayasa Perangkat Lunak Kuliah 2. Outline of this presentation Attributes of Good Software Why Software Engineering ? What is Software Product ? Software.
Part 1 Introduction to Software Engineering 1 copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 1 Introduction to Software Engineering.
INTRODUCTION CSE 470 : Software Engineering. Goals of Software Engineering To produce software that is absolutely correct. To produce software with minimum.
Software Project Management Unit 1. Evolving role of software S/w now a days resides in the mobile, mainframes The main role of the s/w is to transform.
1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 7th edition by Roger S. Pressman.
Software Engineering.
Software Engineering B.Tech IT/II Sem-II
Rekayasa Perangkat Lunak Part-2
The Systems Engineering Context
The Product The Evolving Role of Software Dual role of software Product - It’s a information transformer producing, managing, acquiring, modifying, transmitting.
Chapter : Introduction to Software Engineering
Chapter : Introduction to Software Engineering
Rekayasa Perangkat Lunak Part-3
Software Engineering B.Tech IT/II Sem-II Term: Unit-1 PPT SLIDES Text Books:1.Software Engineering, A practitioner’s approach Roger s. Pressman.
Software Engineering B.E IT Sem-VII
Software Engineering (CSE 314)
Software Myths Deep Mann.
Software Engineering Rekayasa Perangkat Lunak
Chapter : Introduction to Software Engineering
Rekayasa Perangkat Lunak
Overview: Software and Software Engineering
Chapter : Introduction to Software Engineering
Chapter : Introduction to Software Engineering
Software Testing and Maintenance Maintenance and Evolution Overview
CMPE 412 Software Engineering
Software Engineering Rekayasa Perangkat Lunak
Software Engineering (CSI 321)
What is Software? Software is: (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures.
Rekayasa Perangkat Lunak
Software and Software Engineering
Introduction Software Engineering.
Software Engineering Rekayasa Perangkat Lunak
Presentation transcript:

Software What Is Software? Computer software is the product that software professionals design and build. It encompasses Programs Content Documents www.educlash.com

Vehicle to deliver the product Information Produces Modifies Manages Displays Software - the Product Acquires Transforms Software Vehicle to deliver the product Operating System Network Software Case tools www.educlash.com

What is Software Engineering Solving Problems Software products are large and complex Development requires analysis and synthesis Analysis: decompose a large problem into smaller, understandable pieces abstraction is the key Synthesis: build (compose) a software from smaller building blocks composition is challenging www.educlash.com

Con.. The analysis process www.educlash.com

Con.. The synthesis process www.educlash.com

What is Software Engineering Solving Problems (continued) Method: refers to a formal procedure; a formal “recipe” for accomplishing a goal that is typically independent of the tools used Tool: an instrument or automated system for accomplishing something in a better way Procedure: a combination of tools and techniques to produce a product Paradigm: philosophy or approach for building a product (e.g., OO vs structured approaches) www.educlash.com

What is Software Engineering Where Does the SW Engineer Fit in What is Software Engineering Where Does the SW Engineer Fit in? (continued) Relationship between computer science and software engineering www.educlash.com

Characteristics Software does not wear out It becomes reliable over time. It becomes obsolete based on new changes Software is not manufactured One time development efforts Continuous maintenance efforts. Reusability of components Not a single product as a whole Every component – Single process Component based Software Engineering Software is flexible Can be made flexible Leads to unpredictability www.educlash.com

The Evolving Role of Software Software takes on a dual role: A product Delivers the computing potential embodied by computer hardware The vehicle for delivering a product Acts as the basis for the control of the computer (OS), the communication of information (networks), and the creation and control of other programs (software tools and environments) The most important product: Information www.educlash.com

Changing Nature of Software System software Application software Engineering/scientific software Embedded software Product-line software (e.g., inventory control, word processing, multimedia) Web applications Artificial intelligence software Ubiquitous computing (small, wireless devices) Netsourcing (net-wide computing) Open source (operating systems, databases, development environments) The ".com" marketing applications www.educlash.com

Types of Software System software Real-time software Business software it services other programs heavy interaction with hardware, Real-time software data gathering component analysis component monitoring component Business software largest single software area MIS important component Engineering and scientific software number crunching numerical algorithms www.educlash.com

Types of Software Embedded software PC software Web-based software resides in read-only memory of any appliances controls products and system for consumers PC software several hundreds of applications available as software packages Web-based software unlimited software resource AI software makes use of non-numerical algorithms expert systems, pattern recognition, games www.educlash.com

Software Myths - Management "We already have a book that is full of standards and procedures for building software. Won't that provide my people with everything they need to know?" Not used, not up to date, not complete, not focused on quality, time, and money "If we get behind, we can add more programmers and catch up" Adding people to a late software project makes it later Training time, increased communication lines "If I decide to outsource the software project to a third party, I can just relax and let that firm build it" Software projects need to be controlled and managed www.educlash.com

Software Myths - Customer "A general statement of objectives is sufficient to begin writing programs – we can fill in the details later" Ambiguous statement of objectives spells disaster "Project requirements continually change, but change can be easily accommodated because software is flexible" Impact of change depends on where and when it occurs in the software life cycle (requirements analysis, design, code, test) www.educlash.com

Software Myths - Practitioner "Once we write the program and get it to work, our job is done" 60% to 80% of all effort expended on software occurs after it is delivered "Until I get the program running, I have no way of assessing its quality Formal technical reviews of requirements analysis documents, design documents, and source code (more effective than actual testing) "The only deliverable work product for a successful project is the working program" Software, documentation, test drivers, test results "Software engineering will make us create voluminous and unnecessary documentation and will invariably slow us down" Creates quality, not documents; quality reduces rework and provides software on time and within the budget  www.educlash.com