1. USER & CUSTOMER 2.BASING DEVELOPMENT ON SOLID PRINCIPALS AND REUSABLE TECH.

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

Winston W. Royce (1929–1995) American leader computer scientist & Engineer of software development in the second half of the 20th century. B.Sc. in physics,
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
© AgiliX Agile Development Consulting Agile Software Architecture Cesario Ramos.
SERL - Software Engineering Research Labslide1 Frameworks and Hooks by Garry Froehlich Paul Sorenson SERL (Software Engineering Research Lab)
Basic Concepts in Component-Based Software Engineering
CBSD – Component Based Software Development - Introduction -
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Analysis Modeling Over view of today’s lesson T he analysis model is the first technical representation of a system. Analysis modeling uses a combination.
7M822 Software Engineering Introduction 7 September 2010.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
Software Engineering Incorporating Interface Design Into Software Engineering.
Managing Reuse Presented by: Aisha Al-Hammadi. Outline Introduction History. The technical and managerial advantages of Reusing Solutions. The main challenges.
May-June 2001 ISISTAN Research Institute – Tandil, Argentina Software Design Methodologies: UML in Action Dr. Mohamed Fayad, J.D. Edwards Professor Department.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
© M.E. Fayad SJSU -- CmpE Analysis Heuristics Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 3: Basing Software Development on Reusable Technology.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.
7M822 Software Requirements Introduction 7 September 2010.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
OOP- OBJECT OBJECT PROGRAMMING By KRATI SHARMA 02 XI-B ✏✏✏✏ ☺☻☺☻☺☻☺ ✏✏✏✏
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
Software Engineering Reuse.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering1 Warm Up Question: What do you think are the most important attributes of a piece.
Software Requirements Engineering CSE 305 Lecture-2.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
CSE 219 Computer Science III Program Design Principles.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
12.1 Introduction Checklists are used as a technique to give status information in a formalized manner about all aspects of the test process. This chapter.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 3: Basing Software Development on Reusable Technology.
Software Engineering, Lecture 4 Mohamed Elshaikh.
SOFTWARE MAINTENANCE 1. TOPICS TO BE DISCUSSED.. Definition of Maintenance Software Maintenance Types of Maintenance Maintenance Process Need of Maintenance.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering 1.
K. Ingram (with thanks to A. Seddon) Staffordshire UNIVERSITY School of Computing Introduction to Software System Design.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Chapter 10 Basic Skills Count Chapter 10 Basic Skills Count Lesson 10.2 Applying Other Skills Lesson 10.2 Applying Other Skills.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 3: Basing Software Development on Reusable Technology.
IS444: Modern tools for applications development Dr. Azeddine Chikh.
Object-Oriented Software Engineering Chapter 1 Software and Software Engineering.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Chapter 10: Software Size Estimation Omar Meqdadi SE 273 Lecture 10 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Developing Requirements. 1. Domain Analysis Domain: The general field of business or technology in which the customers expect to be using software Domain.
Software. Introduction n A computer can’t do anything without a program of instructions. n A program is a set of instructions a computer carries out.
Chapter 1: Software and Software Engineering The Nature of Software... Software is intangible  Hard to understand development effort Software.
16CS202 & Software Engineering
ITEC 370 Lecture 13 Design.
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
Software Design and Architecture
CS 641 – Requirements Engineering
CS 641 – Requirements Engineering
State of the art We still have problem using 3D – There are no standard of how to make the modelling, so we can’t benefit from each other. There are not.
Software Engineering (CSE 314)
Creating Custom Workflow Activities with Windows Workflow Foundation
Product Name.
Monday 9th April – Friday 13th April 2018
CS310 Software Engineering Lecturer Dr.Doaa Sami
Product Name.
What is Software? Software is: (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures.
Chapter 1: Software and Software Engineering
Chapter 1: Software and Software Engineering
Presentation transcript:

1. USER & CUSTOMER 2.BASING DEVELOPMENT ON SOLID PRINCIPALS AND REUSABLE TECH.

Someone doing ‘real work’ with the computer software A person or group of person that uses the software for their daily or specific work

one who uses a computer software

A customer is a person or organization that a software developer believes will benefit from the software and services offered by software developer’s organization. A customer is a person who purchasing or paying for the software program

One who have Purchased The software

WHEN A PERSON PURCHASE A SOFTWARE AND USE IT HIMSELF

THE SOFTWARE ENGINEERING IS AN ENGINEERING ACTIVITY LIKE OTHER ENGINEER A SOFTWARE ENGINEER SOLVE PROBLEM BY APPLYING WELL UNDERSTOOD KNOWLEDGE AND TECHNOLOGY IN A WELL MANNERED WAY. SOFTWARE ENGINEER DESIGNS ARE SUBJECT TO THE PRINCIPLES OF LOGIC AND HUMAN PSYCHOLOGY

SOFTWARE ENGINEERING PRINCIPLES

 PRINCIPLE FOR GATHERING GOOD REQUIREMENTS  PRINCIPLE FOR WRITING GOOD REQUIREMENTS DOCUMENTS  PRINCIPLE OF USER CENTERED DESIGN  PRINCIPLE THAT LEAD TO GOOD USABILITY  PRINCIPLE FOR MAKING GOOD DESIGN DECISIONS  PRINCIPLE OF EFFECTIVE DESIGN  PRINCIPLE OF TESTING  PRINCIPLE OF INSPECTING PRINCIPLES FOR GOOD SOFTWARE ENGINEERING

REUSABLE TECH. WHEN WE USE A PRECREATED SOFTWARE OR IT’S PART TO MAKE ANOTHER NEW SOFTWARE CALLED REUSABLE TECH.

FRAMEWORKS Frameworks are skeletal applications or subsystems on which many different applications can be built. They contain the essentials services needed by a class of systems. Software engineers adapt than to the needs of a particular system by writing code that fills slots [required functionality mining from the framework) or hooks (places where the system explicitly anticipates you may want to add extensions). The code written to fill slots and hooks will call the services of the framework.

REUSE OF SOFTWARE IN ANOTHER SOFTWARE If you are going to making two or more financial software then you need a calculator program in each software. In such condition you have not need to write separate code for calculator in each software. You have to write it once and then you can reuse it in another software.

THANKS