Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.

Slides:



Advertisements
Similar presentations
Formal Specifications
Advertisements

1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Component-Based Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
What is software? Computer programs and associated documentation
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Jordan - Amman Tel: Fax: P.O.Box : 166 Copyright © 2011 Applied Science University. All Rights Reserved ASU Open Course.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Software Reuse Building software from reusable components Objectives
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 19 Slide 1 Component-based software engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
- 1 - Component Based Development R&D SDM Theo Schouten.
©Ian Sommerville 2000 Software Engineering, 6th edition Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 91 Formal Specification l Techniques for the unambiguous specification of software.
Building software from reusable components.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 10 Slide 1 Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
MCA –Software Engineering Kantipur City College. Topics include  Formal Methods Concept  Formal Specification Language Test plan creation Test-case.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Critical Systems Specification 3 Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
Chapter 3 Software Processes.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 19 Slide 1 Component-based software engineering 1.
Topic 6 Component-based software engineering
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 9 Slide 1 Formal Specification l Techniques for the unambiguous specification of software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Lecture 3 Software Engineering Models (Cont.)
WXGE6103 Software Engineering Process and Practice Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Lecture 21 Enterprise Systems Development ( CSC447 ) COMSATS Islamabad Muhammad Usman, Assistant Professor.
Chapter 17 Component-based software engineering 1Chapter 17 Software reuse CS 425 November 20, 2014 Ian Sommerville, Software Engineering, 9 th Edition.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 19 Slide 1 Component-based software engineering.
An Introduction to Software Engineering
Component Oriented Programming 1 Introduction to COP.
©Ian Sommerville 2000 Software Engineering. Chapter 18Slide 1 Chapters 18/19 Software Reuse / CBSE.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor.
Software Engineering Chapter 10 Formal Specification Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
CBSE Component Based Software Engineering cs. upt
Chapter 16 - Component-based software engineering Chapter 16 Component-based software engineering119/11/2014.
Chapter 16 Component-based software engineering 1 CS 425 November 19, 2015 Ian Sommerville, Software Engineering, 10 th Edition Pearson Education, Addison-Wesley.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2006MSc module: Advanced Software Engineering Slide 1 Component-based software engineering.
Component-based Software Engineering CBSE seminar, Oslo, 4 Feb Christian Bunse
Component-based software engineering (Sommervile chapter 17) 1Chapter 17 Software reuse.
1 SYS366 Week 2 - Lecture Visual Modeling and Process.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVII. Verification and Validation.
Chapter 17 - Component-based software engineering
IS301 – Software Engineering V:
Formal Specification.
Chapter3:Software Processes
Software Process Activities.
Chapter 17 - Component-based software engineering
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Component-Based Software Engineering
Component--based development
Formal Specifications
Chapter 17 - Component-based software engineering
COMPONENT – BASED SOFTWARE ENGINEERING MODULE 2 – SECOND SEMESTER MKHIZE, BSC HONS COMPUTER SCIENCES, DIP IT, ICDL.
Activities of Formal Methods
Presentation transcript:

Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model

Objectives To explain that CBSE is concerned with developing standardised components and composing these into applications To describe components and component models To show the principal activities in the CBSE process To discuss approaches to component composition and problems that may arise 9/22/2015ICS 413 – Software Engineering2

Topics covered Components and component models The CBSE process Component composition 9/22/2015ICS 413 – Software Engineering3

Component-based development Component-based software engineering (CBSE) is an approach to software development that relies on software reuse. It emerged from the failure of object-oriented development to support effective reuse. Single object classes are too detailed and specific. Components are more abstract than object classes and can be considered to be stand- alone service providers. 9/22/2015ICS 413 – Software Engineering4

CBSE essentials Independent components specified by their interfaces. Component standards to facilitate component integration. Middleware that provides support for component inter-operability. A development process that is geared to reuse. 9/22/2015ICS 413 – Software Engineering5

CBSE and design principles Apart from the benefits of reuse, CBSE is based on sound software engineering design principles: – Components are independent so do not interfere with each other; – Component implementations are hidden; – Communication is through well-defined interfaces; – Component platforms are shared and reduce development costs. 9/22/2015ICS 413 – Software Engineering6

CBSE problems Component trustworthiness - how can a component with no available source code be trusted? Component certification - who will certify the quality of components? Emergent property prediction - how can the emergent properties of component compositions be predicted? Requirements trade-offs - how do we do trade-off analysis between the features of one component and another? 9/22/2015ICS 413 – Software Engineering7

Components Components provide a service without regard to where the component is executing or its programming language – A component is an independent executable entity that can be made up of one or more executable objects; – The component interface is published and all interactions are through the published interface; 9/22/2015ICS 413 – Software Engineering8

Component definitions Councill and Heinmann: – A software component is a software element that conforms to a component model and can be independently deployed and composed without modification according to a composition standard. Szyperski: – A software component is a unit of composition with contractually specified interfaces and explicit context dependencies only. A software component can be deployed independently and is subject to composition by third-parties. 9/22/2015ICS 413 – Software Engineering9

Component as a service provider The component is an independent, executable entity. It does not have to be compiled before it is used with other components. The services offered by a component are made available through an interface and all component interactions take place through that interface. 9/22/2015ICS 413 – Software Engineering10

Component characteristics 1 9/22/2015ICS 413 – Software Engineering11

Component characteristics 2 9/22/2015ICS 413 – Software Engineering12

Formal Specification 9/22/2015ICS 413 – Software Engineering13

Objectives To explain why formal specification techniques help discover problems in system requirements 9/22/2015ICS 413 – Software Engineering14

Topics covered Formal specification in the software process 9/22/2015ICS 413 – Software Engineering15

Formal methods Formal specification is part of a more general collection of techniques that are known as ‘formal methods’. These are all based on mathematical representation and analysis of software. Formal methods include – Formal specification; – Specification analysis and proof; – Transformational development; – Program verification. 9/22/2015ICS 413 – Software Engineering16

Acceptance of formal methods Formal methods have not become mainstream software development techniques as was once predicted – Other software engineering techniques have been successful at increasing system quality. Hence the need for formal methods has been reduced; – Market changes have made time-to-market rather than software with a low error count the key factor. Formal methods do not reduce time to market; – The scope of formal methods is limited. They are not well-suited to specifying and analysing user interfaces and user interaction; – Formal methods are still hard to scale up to large systems. 9/22/2015ICS 413 – Software Engineering17

Use of formal methods The principal benefits of formal methods are in reducing the number of faults in systems. Consequently, their main area of applicability is in critical systems engineering. There have been several successful projects where formal methods have been used in this area. In this area, the use of formal methods is most likely to be cost-effective because high system failure costs must be avoided. 9/22/2015ICS 413 – Software Engineering18

Specification in the software process Specification and design are inextricably intermingled. Architectural design is essential to structure a specification and the specification process. Formal specifications are expressed in a mathematical notation with precisely defined vocabulary, syntax and semantics. 9/22/2015ICS 413 – Software Engineering19

Specification and design 9/22/2015ICS 413 – Software Engineering20

Specification in the software process 9/22/2015ICS 413 – Software Engineering21

Use of formal specification Formal specification involves investing more effort in the early phases of software development. This reduces requirements errors as it forces a detailed analysis of the requirements. Incompleteness and inconsistencies can be discovered and resolved. Hence, savings as made as the amount of rework due to requirements problems is reduced. 9/22/2015ICS 413 – Software Engineering22

Cost profile The use of formal specification means that the cost profile of a project changes – There are greater up front costs as more time and effort are spent developing the specification; – However, implementation and validation costs should be reduced as the specification process reduces errors and ambiguities in the requirements. 9/22/2015ICS 413 – Software Engineering23

Development costs with formal specification 9/22/2015ICS 413 – Software Engineering24

Specification techniques Algebraic specification – The system is specified in terms of its operations and their relationships. Model-based specification – The system is specified in terms of a state model that is constructed using mathematical constructs such as sets and sequences. Operations are defined by modifications to the system’s state. 9/22/2015ICS 413 – Software Engineering25

Formal specification languages 9/22/2015ICS 413 – Software Engineering26