How to Model and Develop new Software & Hardware based Product & Solution

© BCausE Enterprise Pvt Ltd 2013

Apu Chandra SahaPMP,ITIL V3, Zachman EA

Founder & CEO BCausE Enterprise Pvt Ltd ,India

[email protected]@gmail.comPh: +91-9582158035

www.bcause.in

Process to Product Modeling : “First time Right” Method From Abstract Concept to Physical Product

A Consultant & Entrepreneur with more than 18 years of experience in Wireless carrier grade Telecom. Extensive exposure in telecom HW and SW Product and Solution & Service design, architecture, deployment in thetelecom OEM and Operator Industry. He has held leadership positions in global organisations both in Technology Practice and Business in British Telecom, Uninor, Alcatel Lucent & Siemens.

mailto:[email protected]

mailto:[email protected]

http://www.bcause.in/


ENTERPRISE DESIGN Delivering Changes - A Guideline “There is nothing permanent, except change” - Heraclitus

Approach to define the product /service model as Top Down or Bottom Up only is not correct approach

Confluence of both and collaboration at early stage is key - to reduce time to deliver - to reduce the sunk cost and risk cost

Requirement generation and requirement Analysis is key

At intersection of each layer, there is an abstract language of communication to the next layer

An Unified interactive requirement meta language is the first step

Multiple PDCA Cycle during the Product/Software Development life cycle


ENTERPRISE DESIGN Change & Transformation Life Cycle – Define , Design & Develop

TIME

COSTRISK


ENTERPRISE DESIGN Change & Transformation Life Cycle – Stage 1:Define


ENTERPRISE DESIGN Change & Transformation Life Cycle – Stage 2: Design


ENTERPRISE DESIGN Change & Transformation Life Cycle – Stage 3 : Develop


ENTERPRISE DESIGN Unified Requirement Generation Technique

Construct : Unified Requirement Model


ENTERPRISE DESIGN Unified Requirement Modeling – A Procedure for Successful Change

A Telecom Operator business includes various functional department

Many functional departments are non engineers and non technical

They are the primary stakeholder /sponsor of various IT Application

Collaboration with an Intuitive and Visual Notation helps easy and early comprehension

Unified requirement modeling is the best and effective way of Design & Development.


ENTERPRISE DESIGN Unified Requirement Modeling Language(URML) – A Framework & Practice

URML helps in constructing solution independent , business application domain based Process model

Very effective technique for Hardware software based early requirement composition

Easy to build demarcation and decomposition to various HW/SW components & Sub Component

The extent and aspects of the various meta model depends on the detail of requirement queries from URGT (Slide 27)

Most popular tools used at this stage is Ms Visio and Unicase.


ENTERPRISE DESIGN URML – Meta Models in Telecom

Goal Modeling

Stakeholder N

Goal

Goal Dependency

Stakeholder B

Stakeholder AExpress

Feature Modeling Goal

Feature 1

Feature 2Feature 3

Feature X

Functional Requirement

Condition to The Functional

Requirement

Details Constraints

Business/Functional Requirement Specification



Product Line Modeling

Feature

Start End Classification& Composition

attributes

Product C

Product B

Service

Used Case Modeling

ActorRole Player Activity Actor

Role Player

Actor -Actor Model


ENTERPRISE DESIGN

Used Case Modeling

ActorRole Player Activity Actor

Role Player

Actor -Actor Model

State Start State Variable State End State

State Change Model

URML – Meta Models in Telecom



Exceptional Scenario Modeling

Danger Modeling

Risk Model

Threat Model

Completes the Stage 2 of Change/Transformation Life cycle

Design approval and feasibility acquired

Determine the Functional Points, enabling to better estimation of cost , time and skill resource.


ENTERPRISE DESIGN Development – Stage 3

The Technical low level Engineering starts at Stage 3

Abstraction notation to unified notation arrived at the end of Stage 2

Time to convert from Static representation to Dynamic Representation

Unified Modeling Language and EDA tools can help to develop virtual Dynamic visual representation

Helps to have Process performance Intelligence

Helps to determine the bottleneck and weak legs

Allows to determine the final iteration points and process


ENTERPRISE DESIGN Unified Modeling Language - Purpose

A Project for Each Product as identified is defined

Multi-Technical Engineering specific knowledge skill interplay commences

Product technology Building blocks Architected

Software based Application using UML tool for defining the various object model is an Interdisciplinary Play

UML is a modeling Notation managed by OMG (Object Management Group) with various technology domain library

Various standard tools are available in the market, where multiple user can work on a project

Conversion from UML tool to Program Codes – Reduces time and dependency to expert skill and Knowledge.


ENTERPRISE DESIGN Unified Modeling Language - Derivatives


ENTERPRISE DESIGN Stage 3 : Completion

Development

Coding with the most appropriate language each module Compiling the codes Simulation Porting the module in Test Platform

Testing

Developing Test Criteria and Test Procedure Unit Testing System Integration Testing User Acceptance Testing

The maker cannot be the checker, so Testing team is different to the development team.

It is a collaboration of the Key members from Stage 1 to Stage 3


ENTERPRISE DESIGN

IMPLEMENTATION : FINAL STAGE

Changes in Telecom Operator’s scenario are Classified as Minor Changes Major Changes Emergency Changes

Minor Changes : a) One that would not require any disruption of on going service b) Will improve the operational efficiency. eg: Database Purging, Alternate Route, Query Optimization

Major Changes: a) One that would have revenue impact and shutdown of service b) One that may change the user interface and user training. eg: Database migration, New feature/function incorporation

Emergency Changes: a) Module crash or system down. b) ~ 20% or above of the user cannot avail the service/system.


ENTERPRISE DESIGN IMPLEMENTATION of CHANGE – PREREQUISTE Detailed Project Implementation Plan jointly approved

Change Environment Impact Assessment Brownfield Greenfield

Release Management Release window approval taken HW/SW module in format available to be ported in Production environment Test Results approved by customer All Backup of current state in on going production environment taken. Associated and dependent element key resources intimated and secured Revert back standard operating procedure in place. Call back release trigger defined, Project manager authorized to take the call. Training imparted to user and operation team in advance.

Post Release Monitoring Window Performance measurement metric periodically to be prepared by Operation and user team representative.


ENTERPRISE DESIGN Summary – Delivery Changes in Telecom Smoothly

Representation of Participation Index of those vectors between Vendor & Operator

Key Business Vectors: People, Technology, Cost & Risk

VENDOR OPERATOR VENDOR OPERATOR VENDOR BUYER VENDOR OPERATORDEFINE 75 100 100 50 100 100 75 100DESIGN 100 25 100 12.5 100 12.5 100 50DEVELOP 100 12.5 100 12.5 100 12.5 100 12.5IMPLEMENT 100 100 100 50 100 100 100 100

PEOPLE TECHNOLOGY COST RISK


ENTERPRISE DESIGN

Date post:	13-Dec-2014
Category:	Technology
Upload:	apu-saha
View:	83 times
Download:	3 times