Ijcsns international journal of computer science and network security

Applying Virtual Team Process Methodology

In Business Process Reengineering

Software Development

El Shaymaa Mohamad Nassar ,Prof. Dr. Ramadan Moawad

IntroductionBusiness Process Reengineering Team Software ProcesseXtreme Programming Virtual Team Software ProcessResultsConclusions

Agenda

2Wednesday, April 12, 2023

Our presentation introduces deployment of Team Software Process and eXtreme Programming within “Virtual Environment” in Business Process Reengineering Project.

We aim to decrease cost of changes plus implementing frequent requirements of different and incompatible platforms.

This paper also concerns customer ‘end-user’ satisfaction ‘motivation – and – trust’ to use primitive project decreasing their resistance and training requirements

3

Introduction

Wednesday, April 12, 2023

BPR is the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements of cost, quality, service, and speed.“ (Hammer & Champy 1993). A consolidated BPR approach has two phases:

Reverse engineering: Rational and Unify Processes (RUP) by frequent process refactoring

( Vishanth Weerakkody et al, 2003). Forward engineering: Integrate Unified Processes: 1) Removing unnecessary processes,2) Integrating small releases into final business process

(Edward, 2008)

Business Process Reengineering


What to Change? Isolated Business Processes and

What to Change to? Automated Integrated WFMS

What are the Constrains?Strengths, Weakness, Opportunities and Threatens

(SWOT) analysisSWOT Analysis Prioritization

What are the Resources? Cross Functional Department Distribution Virtual cross functional teams

Business Process Reengineering Phases


Isolated Business Processes

Wednesday, April 12, 2023 6

Strengths, Weakness, Opportunities and Threatens (SWOT) Aanalysis



SWOT Analysis Prioritization

Voting ratio using histogram

Rearrangement using pareto

I1: VTMS tracking processes

I1.1: Monitoring and acquiring RADAR scanning vessel transits

I1.2: Comparison of Transit data to vessel data

I1.3: Attachment of dummy label to vessel (file-no, type, etc.)

I1.4: Rearrangement convoy-id (N1, N2, S) and order

I1.5: Addition of tugs, pilotage to vessels transit

I2: ADM Financial SystemI2.1: Matching of vessel reserve card to VTMS booking recordI2.2: Data collection to form reports and billing printoutI2.3: Data processing into information with complete data sheet

I2.4: Review of Business Rules

I2.5: Mapping of transit data to business rules

I2.6: Billing estimation

I2.7: Data inspection

I2.8: Billing archiving

I3: Marketing and Economic Decision

I3.1: Statistical data filtering

I3.2: Comparison to international registration

I3.3: Flat file transfer and tables filling

I3.4: Vessel relationship management decision

Manual Workflow Management



Rational Unified Process (RUP)

Class Diagram


Business Process Reengineering Application

Integrated Business Process Modeling


O1: VTMS tracking processesO1.1: Monitoring and acquiring RADAR scanning vessel transits O1.2: Comparison of Transit data to vessel data.O1.3: Attachment of dummy label to vessel (file-no, type, etc.)O1.4: Rearrange convoy-id (N1, N2, S) and orderO1.5: Addition of tugs, pilotage to vessels transit

O2: ADM Financial SystemO2.1: data query to form reports and billing printoutO2.2: data processing into information with complete data sheetO2.3: Mapping of transit data to business rulesO2.4: Billing estimationO2.5: Archiving

O3: Marketing and Economic DecisionO3.1: Statistical data filteringO3.2: Comparison to international registrationO3.3: Vessel relationship management decision

Automated Workflow Management System



Team Software ProcessThe plan-driven TSP offers good results for large enterprises But in small firms, plan-driven TSP may fail due to : 1) Frequent changes, 2) Heavy weight documentation, 3) People and employee resistance, 4) Overrun expected funds and time, 5) Sudden disturbance of organization, 6) Dependency on PSP individuals,7) Excessive meetings,

Requirement

high level design

implementation

Integration and test

Level 3 Defined

Level 2 Managed

Level 1 Initial

Level 4Quantitative

Managed

Level 5 Optimizing


eXtreme Programming (XP)


eXtreme Programming (XP) Values Greatest Agile

Return of InvestmentFlatten

Cost of Change


Virtual Team Structure and Practices

Virtual Team StructureOnline Representative CustomerDistributed Pair ProgrammersCoordinate Interaction and CommunicationSustain Organizational Hierarchical Systems

(Sub Team A/ Sub Team B/ Sub Team C)

GSD

Workforce needed

Effort Remaining

Coordinator

Workforce Available

Workforce Available

AEUB/CEU

B/CDEV ADEV

B/CBO ABO

Planning

Control

Sub team ASub team B/C

Interactions

ADHMXP

EU: End User BO: Business Owner DEV: DEVlopper18Wednesday, April 12, 2023


Virtual Team Process Activities

VTSP Interface screenUser StoryProject ManagementConfigure Change ManagementAutomated Monitoring & Test CMMI KPA ChecklistCollective Ownership

Virtual Team Process Interface Screen

Distributed pair programming

Online Customer

Customer Story

CMMI KPA - VTSP

SQA Check List

Social factor detection



Hierarchy Object Oriented Team Design

Team members Location Count Sub Team Members

Symbol Count

Site A Developers

VTS 5Project Leader PL 6

Site B Developers

ADM 5Developers DEV 15

Site C Developers

P&R 5Business owners BO 100

Site A users VTS 12 End Users EU 39

Site B users ADM 20 Marketing Manager

MM 7

Site C users P&R 7

Site A customers

VTS 24+ site C

Site B customers

ADM 10 + site A

Site C customers

P&R Overall

Virtual Team Member Roles



VTSP Technical PracticesItems Release 1 Release 2 Release 3

Language C/C++ C/C++ C/C++ADM Database

MySQL-Server-5.1.8.glibc-i368.rpm

Sybase Database server MySQL Database server to Flat File transmission

Development Environment

KDE Developer v1.3 /Linux Virtual Improvement Editor

(VIM)Unix Virtual Editor

KDE Developer v1.3 /Linux Virtual Improvement Editor

(VIM)

Software Configuration Management

(SCM)

Linux OS. Security Shell Control and Configuration

Linux OS. Security Shell Control and Configuration.

Crontab schedule transmission time

Linux OS. Security Shell Control and Configuration.

Crontab schedule transmission time. Samba

Server Connection to Window. Configuration of

secure account and control

Unit testing Customer Acceptance Test ADM Customer Acceptance Test

FTP fulfillment for requirements and temporary

log files

Documents MS Office 2010User, Test, Maintenance Manuals (out sources)

User, Test, Maintenance Manuals (out sources)

Application Server Text User Interface (TUI) Application Interface (API) Application Interface (API)

Subversion Repository

SVN and http server SVN and http server


Release 1 TeamSchedule Time /day

(8hours*E)

Task/No Task Follower Task Mem./No Job P N O E

1 Plan New ADMSys A001 ATL 10 6 7 6.8

2 Design draft RDBMS ER 1 A002-to A005 ADEV 3 2 1 2.0

3 Display to online customer 2 A001+AC01 ABO 1 0.25 0.75 0.5

4 Investigate for legacy stories 3 A001toA005+AC01

ADEV+ABO

4 3 2 3.0

5 Develop small release 4 A002toA05 ADEV 5 4 2 3.8

6 Metaphor for mockup screens 5 A001toA005+AC01

ADEV+AEU

2 0.5 1.5 0.9

7 Factorize Modules 6 A001to A005 ADEV 3 2 1 2.0

8 Create BPR BPMS+WFMS 7+6+5 A002 toA005 ADEV 6 4 3 4.2

9 Design OO Class in (C++) 8 A002 to A005 ADEV 15 10 6 10.2

10 Run unit test 9 A002 to A005 ADEV 4 3 2 3.0

11 Test for First Development 10 A001 +AC01ADEV+AEU

3 2 1 2.0

SUBTEAM A WORK BREAK DOWN SYSTEM


Release 2 Sub-Team (A+B) Schedule Time /day (8hours*E)

Task/No Task Follower Task Mem./No Job P N O E

1 Plan New VTS_ADM_Sys

A001toA005+ B01toB05 ADEV+ BDEV

9 6 5 6.3

2 Design draft shared RDBMS

1 A002toB03 ADEV+ BDEV

5 3.6 2 3.6

3 Display to onsite customer

2 AC01+BC01 BBO 1 0.25 0.75 0.5

4 Investigate for legacy stories

3 A001toA005+AC01B001toB005+BC01

ADEV+BBO

4 3 2 3.0

5 Develop small release

4 A002toA05+B01toB05

ADEV+ BDEV

5 4 2 3.8

6 Create BPR BPMS+WFMS

5 A002 toA005 ADEV 6 4 3 4.2

7 Design UNIX/Linux VTMS/ADM script

6 A002 to A005+B01toB05

ADEV+ BDEV

15 10 6 10.2

8 Design schedule for file transfer

7 A002 to A005+B01toB05

ADEV+BDEV

4 3 2 3.0

9 Test for First Development

8 A002 to A005+B01toB05

ADEV+ BDEV

3 2 1 2.0

SUBTEAMS A,B WORK BREAK DOWN SYSTEM


Release 3 Sub-Teams (A+C) Schedule Time /day

(8hours*E)

Task/No TaskFollower

TaskMem./No Job P N O E

1 Plan New PR_ADM_Sys A001+ C01 ADEV+ CDEV

9 6 5 6.3

2 Specify fields of flat file 1 A002toC01ADEV+ CDEV

5 3.6 2 3.6

3Display mockup screen for flat file retrieve

2+3 C01toCC01CDEV+

CEU2 1 0.5 1.1

4Verify Database Compatibility

2 C01toC03 CDEV 4 2 1 2.2

5 Verify Networking connectivity

1 C01 + A002CDEV+ADEV

1 0.5 0.3 0.6

6 Test data consistency 2+3 C01 CDEV 5 3 1 3.0

7Test validity of data for marketing decisions

1+6 M01+C01+A01 ML+AL+CL 3 2 1 2.0

SUBTEAMS A,C WORK BREAK DOWN SYSTEM

Results


OLD I1 I4 I7 I100%

20%

40%

60%

80%

100%

120%

100%

22%

89%

22%

91%

40% 40%

60%70%

75%

11- Attendance Rate of end users 5- online customer

Results (Cont.)

OLD I1 I4 I7 I100

0.10.20.30.40.50.60.70.80.9

1- Defect Rate (%) 6- collective ownership

Iterations and Release

Rela

tive C

han

ge

Results (Cont.)

OLD I1 I4 I7 I100%

10%

20%

30%

40%

50%

60%

5- Additional Asset Costs (subscriptions, spares)12- Delta Maintenance Time Per Iteration

Virtual Team software process (VTSP) introduces a good solution for eXtreme Programming (XP) deployment within sophisticated software development.

VTSP approach defines, manages and optimizes quickly for all frequent requirements of an online customer ‘end-user’ ,

VTSP improves quality of software upon distributed pair programmers and online collective ownership and coding standard with low training time, and requirement of PSP individuals.

VTSP minimizes meeting times and funds of strategic-plan-driven process.

VTSP Interface screen coordinate team work and simplifies project documentation.

Conclusion


1) Edward J. Barkmeyer (2003b),” Model-Driven Integration Using Existing Models: IEEE Software, vol. 20, no. 5, pp. 59

2) Farid A. (2008), “Business Process Reengineering by Rational Unified Process”, World Applied Sciences Journal Supplier 2 ,33-42

3) Fatima C. (2011), “Online Collaborative behavior patterns and factors affecting distributed team performance” : Computers in Human Behavior

4) Hamid M. and Hassan A. (2009), “Alternating Group Coordinator (AGC) An approach to improve eXtreme Programming”, The Open Software Engineering , vol. 3,pp1-8

5) Hans S. et al,” Software Improvement through Benchmarking”,2009

References


5) Helen Sharp et al (2008), “Collaboration and co-ordination in mature eXtreme programming teams”: International Journal Human-Computer Studies 66 506-518

6) Hilma R. Z. (2005), “The Integration of Total Quality Management (TQM) and Theory Of Constraints (TOC): Implementation In Malaysian Automotive Supplier

7) Minna P. et al, (2006). ”An Approach for using CMMI in Agile Software Development Assessment Experiences from Three Case Studies”, SPICE 2006 Conference 4-5

8) Mohamed H., (2011). “Analysis of the collaborative activities in software development processes”

9) Nader A. et al (2009),” Virtual Teams Product Development - An Innovative Experience R&D Engineers”, European Journal of Educational Studies


References

QUESTIONS


THANKS


Ijcsns international journal of computer science and network security

Documents

Transcript of Ijcsns international journal of computer science and network security