Software engineering models, methods and tools for “post-crisis" lifecycle management

1

Software engineering models, Software engineering models, methods and tools for methods and tools for

“post-crisis" lifecycle management “post-crisis" lifecycle management

The 3d Conference on Information Technologies in Professional Activities (ITPA)

November 8–12, 2011, Izhevsk, Russia

Dr. Sergey V. Zykov, Ph.D.State University –

Higher School of Economics

2

Software engineering models, methods and tools for “post-crisis" lifecycle managementSoftware engineering models, methods and tools for “post-crisis" lifecycle management

Heterogeneous ESE: a challenge, esp. under the crisis The methodology combines formal models (incl. modified spiral

model) and SDK for class-level association-based relationships Problem domain features: heavy data burden - in 2005 total data size of Intel Corp. exceeded

3.2 petabytes (over 120,000 employees in 57 countries) - high object classes complexity - incomplete information on the structure of certain instantiations

of the classes; - the set of class attributes and operations can be determined

rigorously. Reasons for methodology application (besides crisis): - variety of heterogeneous classes, - importance of association-based inter-class relationships - class inference possible even under certain % of weak-structured

class instancesThe 3d Conference on Information Technologies in Professional Activities (ITPA)


3


Software production crisis and SE era advent 1960-s: the software production crisis begins Problems/Disproportions: - anarchic SDL vs. growing system complexity - no SDL methodologies (except “build-and fix” approach) - the crisis is in our minds, not just in economics - an adequate (R&D-based, adaptive) SDL methodology required!

SE – the sci-&-tech discipline to overcome the crisis

SE development stages: - 1960-s: “hand-made” art – unique and precious masterpieces - 1970-s: “manufacturing” – mission-critical systems - 1990-s: “machine-tool conveyor” – CASE + team development



4


Comparing SDL and material production 1967 - The NATO Conference on SE Q.: Can SW be constructed/produced as a physical/material

object? Analysis: - step-by-step elaboration - maintenance (bridges may cost $0 for years, not SW) - “intellectual degeneration” (complex SW platforms change fast) - prototype reliability - “brute force” / “bulletproof “ approach (a bridge twice thicker) - residual faults (NASA flight simulation) Conclusions: - SW production is similar to material one in certain aspects - SW production is entirely different from material one in others A.: NO, Lifecycles are fundamentally different



5


Optimizing lifecycle: the answer to the crisis Every SSDL stage can be optimized (analysis, req.spec., design,

implementation, maintenance, etc.) Documenting should be optimized as well Optimization basis = models + methods + tools integration: - discrete metrics (residual faults, KLOC, etc.) + heuristics - practical applicability vs. mathematically “single-best” solution SSDL model basic features: - iterative nature - sequential elaboration - incremental development - risk analysis - modified incremental/spiral model - best applicable for enterprise-level projects (CASE + risks)



6


The methodology vs. ontology-based approaches (OBA):

OBA (e.g. Cyc) efficiency is comparable only under a total class-level uncertainty, which is a different problem domain than ECM

Thesaurus needed for the OBA to meet the relevance required

The methodology uses similar foundations and tools as OBA (UML and XML-based tools, predicate calculus-based CycL, “conceptual model” etc.) for data modelling and integration

OBA lack a balanced combination of formal models and industry-level SDKs (incl. visualization) for ECM lifecycle, resulting in low scalability and non-suitability for the major enterprise-level tasks



7

Objective, tasks, theoretical background

Objective: to make a software development methodology, which supports entire lifecycle of the enterprise software in the global computational environment

Tasks: - formalizing stages and levels of the methodology; - mathematical modeling; - creating CASE- and RAD-tools ; - implementing the methodology (prototype, full-scale).

Background: finite sequence, category, computation (D.Scott), semantic networks.




8

Innovations – the integrate methodology includes :

1. a set of data models for problem domain objects and for computational environment (CM, AMCM);

2. algorithm of the new component integration into the software implemented;

3. personalization procedure for enterprise content access;

4. SDKs: ConceptModeller, Content Management System




9

EDW problems solved by the methodology




10

Enterprise software lifecycle support by the methodology




11

Problem domain modeling

Data object modeling: “class object value” Class – collection of data objects of the integrated problem domain; Object – class instantiation by CMS template (metadata partial evaluation); Value – static HTML page generated by CMS (full evaluation).

Benefits: - evolves from the object-oriented approach; - develops the existing models ([V.E.Wolfengagen’s CM] et al.) in relation to global computational environment




12

From problem domain to computational environmentSoftware engineering models, methods and tools for “post-crisis" lifecycle managementSoftware engineering models, methods and tools for “post-crisis" lifecycle management



a1

Value (portal )

Class (UML)

-Name : char-ColorDepth : int-Resolution : int-ID : long-Width : int-Height : int-TemplMask : long double

Photo

Object (CMS )

a2

13

Formal syntax of the CMS abstract machine

Let us collect all the CMS abstract machine language identifiers into Ide domain, commands – into Com domain, and expressions – into Exp domain:

Ide ={I | I – identifier}; Com ={C | C – command}; Exp ={E | E – expression}.




14

Formal semantics of the CMS abstract machine (1)Order of construction:

– standard domains (most often used);– finite domains (including explicitly enumerable elements);– domain constructors – operations of building new domains out of

existing ones;– composite domain formalization based on standard domains and

domain constructors.

Domain constructors :

- functional space: [D1D2];

- Cartesian product: [D1D2…Dn]; - sequence: D*;

- disjunctive sum:[D1+ D2+… +Dn].




15

Bi-directional software development

in ConceptModeller CASE-toolkit


FO

RM

AL

IZA

TIO

NNATURAL

LANGUAGE

Business situations

in terms of

natural language

FORMAL LANGUAGEOF FRAME

DESCRIPTION(XML)

Visual frame

representation

C#.NET

FRAMETRANSLATION

INTO UML DIAGRAMS

Mapping

function from

frames to UML

diagrams

C#.NET

FORMAL LANGUAGEOF DIAGRAMS

(XML / RATIONAL)

UML diagrams

visualization

C#.NET

FORMAL LANGUAGEOF DIAGRAMS

(IBM RATIONAL / MS VISIO)

IBM RATIONAL,ORACLE DEVELOPER,

MS VISUAL STUDIO



VIS

UA

LIZ

AT

ION

TR

AN

SL

AT

ION

VIS

UA

LIZ

AT

ION

Business situations

in terms of

UML diagrams

16


Software Solution Arcitecture

в

Oracle InterOffice

Oracle Appls

Media

ArchiveOracleDBMS Cluster

WWW server

SD

Catalyst8500

Power Supply 0CISCO YSTEMSS Power Supply 1

SwitchProcessor

SERIES

Content DB

Notebook

Mobile phone

PocketPC /PDA

Home desktop PC

RS CS TR RD TD CDTALK / DATA

TALK

Enterprise LAN

Oracle Portal/Intranet server

Content DB



17


CMS logical structure

Keywords

IM

ImagesReferences, keywords

Image parameters

Special section parameters,

Message status

KeywordsModulePress Release

Module

Media News

NCNews Columns

Module

MenuModulePages

CMConfiguration management

ModuleEvents

ModuleSpeeches

SSSpecific Sections

ModuleSynchronize

ModulePublish Cycle

ADAdministration

Menu parameters

Keywords

Keywords

Page status, publishing cycle

params

Params and states for news pages

Page status, publishing cycle params

References, keywords

Menu items paramsMedia news parameters

(menu items, etc.)

Keywords

Image state

parameters

Special section parameters

(menu items etc.)



Params and states for menus and messages



18


Structure of the integrated enterprise program system

Deductions and Bonuses

Module

VacanciesModule

LeavesModule

Personnel Movement

ModuleAssets

Responsibility

Module

Appraisal and Testing

Module

Personal Data

Module

TrainingsModule

PR

Payroll Information System

FAFixed Assets Management

Information System

AP

Accounts Payable IS

DC

Document Control Information System

AR

Accounts Receivable IS

Deductions, payments

Address book , organization

structure

Asset Features

Параметры аттестации

Appraisal params

Appraisal reports

Параметры выплат

Responsibility Reports

Assets Refixed

Leave params Testing

params

NecessaryTrainings

Appraisal params

Appraisal params

Appraisal params



19


Comparing the software development methodology

to the commercial methodologies available



Methodology Mathematical model

Integrated methodology

20


Implementation features comparison



Software

ITERA CMS

Mu

lti-

lan

gu

age

pu

blic

atio

n

Java

ser

vlet

s

.NE

T w

eb s

ervi

ces

UM

L d

iag

ram

s

WY

SIW

YG

-map

pin

g

Inte

gra

ted

ER

P

info

rmat

ion

sys

tem

re

po

rts

Inte

gra

tio

n w

ith

leg

acy

info

rmat

ion

sys

tem

s

Sm

art,

tem

pla

te-

bas

ed d

esig

n

Co

mp

lex

dat

a o

bje

ct

emb

edd

ing

21


TCO comparison results



/person

CMS + ConceptModeller

22


ROI comparison results



CMS + ConceptModeller

, yrs

23


Implementation terms comparison results



CMS +

Conce

ptM

odell

er

Optimistic scenario

Pessimistic scenario

24

Theoretical results:

1) A system of formal models for problem domain and computational environment (rigorous semantics, entire lifecycle support, content management orientation);

2) Algorithm of integrating new components to the enterprise software system (problem-oriented, heterogeneous software architecture support);

3) personalization procedure for accessing enterprise content

(flexible, reliable)




25

Engineering results:

1) CASE- and RAD-toolkits: a) ConceptModeller (rigorous semantics; compatible to up-to-

date CASE-tools, ERP and и legacy systems; re-engineering; XML/BPR/UML standard support);

b) ITERA CMS (rigorous semantics; rapid publishing of complex content; WYSIWYG interface; office products integration).

2) Architecture (environment unification of heterogeneous enterprise

applications; role personalization with situation dynamics)




26

Practical value of the results obtained:

1) implementation term-and-cost reduction (TCO, ROI) as compared to commercially available

software by 30% (average);

2) major enterprise software features improvement:- scalability; - reliability; - ergonomics.




27


Research results approbation:

Over 30 presentations on international conferences,4 books and over 50 papers

Research grants: MSR (2002-2003), RFBR (1996-2006) and HSE (2008-2012).

ITERA implementation (150 companies, 10,000 employees): CMS (2002); Internet-portal (2003); Intranet-portal (2004)

Other implementations: ICP (RAS), Sterkh Foundation, Ashihara Karate Association, Russian Orthodox Church, etc.

Curricula (MSR, HSE, MEPhI, MIPT, MSUFI, INTUIT, LANIT, SoftLine, TEKAMA, CareerLab) – over 3000 graduates



Documents

Software engineering models, methods and tools for “post-crisis" lifecycle management