Lessons learned Techniques Limitations of formal specifications - - PowerPoint PPT Presentation

lessons learned
SMART_READER_LITE
LIVE PREVIEW

Lessons learned Techniques Limitations of formal specifications - - PowerPoint PPT Presentation

CRIM Lessons learned Techniques Limitations of formal specifications Cost of technical staff training Ease of communication between different system stakeholders by using object- oriented modeling techniques and OMT as notational


slide-1
SLIDE 1

Amina BELKHELLADI 9

CRIM

Lessons learned

Techniques

  • Limitations of formal specifications
  • Cost of technical staff training
  • Ease of communication between different system stakeholders by using object-
  • riented modeling techniques and OMT as notational convention

Process

  • Importance of simplifying the development process

Products

  • Continuous evolution of current domain model
  • Reference architecture requires several iterations to be completed
slide-2
SLIDE 2

Amina BELKHELLADI 8

CRIM

  • Experience (3)

Keyboard Data Presentation Data Detector Trigger Code Page Translator OIA Data Data Emulation 3270 Comm. Manager Manager I/O Emulation Manager Data Emulation Subsystem Manager Data Conversion

slide-3
SLIDE 3

Amina BELKHELLADI 7

CRIM

  • Experience(2)

Emulator 5250 Emulator x Emulator 3270 Emulator 3270

Execution Architecture Conceptual Architecture Modular Partial Architecture Legacy Systems Object-oriented Emulation Systems System Models

OOCA OOEA OOMPA

OOCA (Object-oriented Conceptual Architecture) OOEA (Object-oriented Execution Architecture) OOMPA (Object-oriented Modular Partial Architecture) Real Systems

slide-4
SLIDE 4

Amina BELKHELLADI 6

CRIM

  • Experience(1)

X.25 SDLC link SNA PC Eicon (Unix 3270 access) Host asynchronous terminals

TCP/IP

Telnet TCP/IP workstations SNA for Eicon Cards

E

slide-5
SLIDE 5

Amina BELKHELLADI 5

CRIM

Process Overview

Requirements Analysis Domain Modelling Object-oriented Modelling Implementation Problem Understanding

Domain Engineering and Building Blocks Construction

slide-6
SLIDE 6

Amina BELKHELLADI 4

CRIM

MODL

Techniques

  • Object-oriented methods
  • Formal specification techniques and languages
  • Combination of both

Process

  • Development steps overview

Products

  • Domain engineering
  • Reference architecture
slide-7
SLIDE 7

Amina BELKHELLADI 3

CRIM

The Usefulness of Software Architecture

A software architecture (SWA) identifies a collection of functional modules shared by a family of products, and the relations between such modules. A SWA can me described using different views for capturing distinct properties

  • f a software system.

Our approach is based on two principal views:

  • Static
  • Dynamic
slide-8
SLIDE 8

Amina BELKHELLADI 2

CRIM

Why formal architectures? Legacy software systems reengineering problems:

  • Inability to recover design.
  • Inability to understand well large and complex systems.
  • Inability to modify, extend implemented software

systems.

  • Increased cost of software development .
  • Lack of high quality systems.
slide-9
SLIDE 9

Amina BELKHELLADI 1

CRIM

Formalizing Software Architectures: An Industrial Experience

Petre Dini, Amina Belkhelladi and Walcelio L. Melo (CRIM)