MODEL BASED SOFTWARE ENGINEERING

1. MODEL BASED SOFTWARE ENGINEERING PRESENTED BY USHA GHIMIRE

2. OVERVIEW Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages Required architecture characteristics summary

3. WHY MBSE? Modern projects are now evolving as a totally different projects compared to those from earlier times in following respects: --Increase in system size, complexity and cost --Requirements/operating environments change throughout the system lifetime --quality of software at delivery is becoming more important. --Assessing quality through testing is becoming more difficult. It is critical to be able to simulate these systems before we build them. A MBSE approach promise to address those issues.

4. INTRODUCTION TO MBSE? • In short Model-Based Software Engineering (MBSE) is the idea of achieving code reuse and perform maintenance and product development through the use of software modeling technology and by splitting the production of software into two parallel engineering processes namely domain engineering and application engineering. • Uses software reusability • MBSE is a program for adopting systematic reuse that is centered on software modeling technology.

5. INTRODUCTION TO MBSE(Contd..) • MBSE consists of the following elements: • product families - domains • a production system • software assets • engineering processes

6. DOMAIN ENGINEERING • It is a process of analysis, specification and implementation of software assets in a domain which are used in the development of multiple software products.

7. APPLICATION ENGINEERING • It is an engineering change process that develops software products from software assets. • It runs in parallel with domain engineering.

8. SOFTWARE ASSETS • Are the reusable resources used in application engineering. • Examples include domain models, software architectures, design standards, communication protocols, code components and application generators.

9. WHAT IS A MODEL THEN………………………..

10. A MODEL • To document, to communicate, to investigate, to predict-----we will need map or models. • Plays the analogous role as the blueprint plays in building the skyscraper. • Models help us by letting us work at a higher level of abstraction. A model may do this by hiding or masking details, bringing out the big picture, or by focusing on different aspects of the prototype.

11. MODELLING LANGUAGE • UML Notation Class Diagram State Diagram Activity Diagram Sequence Diagram • Will have issue like compositionality,formality,encapsuation

12. MODELING LANGUAGE • A class diagram to introduce various kinds of objects. • A object diagram describing the initial state. • A state diagram for each class, to show how each kind of object will behave. • A sequence diagram to show the message exchange between different objects. • An activity diagram to show the overall flow of control.

13. MBSE IN THE FUTURE • We want our MBSE environment to provide capability for: --Simulation of Hardware --Simulation of Software --Simulations of humans in the system environment --Simulations of the system environment itself • The key concept of MBSE should be to develop fully executable model.

14. MBSE IN THE FUTURE(Contd..) • Key advantages --The approach inherently leads to the better understanding of the system. --Money spend on modeling and simulation upfront will reduce in networking later in the development process. • Key Disadvantages --The level of complexity can be extreme so as the time and cost is high

15. REFERENCES • www.sei.cmu.edu/mbse/is.html • xxx.lanl.gov/pdf/cs/0201023 • web.comlab.ox.ac.uk/oucl/research/areas/softeng/imbusQCday.pdf