An Agile Method for E-Service Composition Author : Pouya Fatehi, Seyyed Mohsen Hashemi Department of Computer Software, Science and Research Branch, Islamic.

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
Property Management Product Development Update Randy Lott Director, Development AMSI.
SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Alternate Software Development Methodologies
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Agile development By Sam Chamberlain. First a bit of history..
Chapter 6 Prototyping, RAD, and Extreme Programming
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 CMSC 132: Object-Oriented Programming II Software Development I Department of Computer Science University of Maryland, College Park.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
An Agile View of Process
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Rapid Prototyping Model
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Chapter 1 The Systems Development Environment
Ontologies Reasoning Components Agents Simulations The Eclipse Process Framework Breno Machado.
Current Trends in Systems Develpment
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
SYSTEM DYNAMICS MODELING OF AGILE CONTINUOUS DELIVERY PROCESS 資工 4A 鄭鈞輿.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Introduction to Systems Analysis and Design
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Agile Methods Presentation By: Jason Abbett. Definition A process to rapidly develop software Many kinds of agile methods but few are practiced.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
CS223: Software Engineering Lecture 18: The XP. Recap Introduction to Agile Methodology Customer centric approach Issues of Agile methodology Where to.
1 Requirements Engineering for Agile Methods Lecture # 41.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Software Engineering Salihu Ibrahim Dasuki (PhD) CSC102 INTRODUCTION TO COMPUTER SCIENCE.
Project Management Software development models & methodologies
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Appendix B Agile Methodologies
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Fundamentals of Information Systems, Sixth Edition
Chapter 1 The Systems Development Environment
Software Development methodologies
Chapter 1 The Systems Development Environment
Introduction to Software Engineering
Documentation in Continuous Delivery Model and DevOps
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Appendix B Agile Methodologies
Extreme Programming.
System Development Methods
Presentation transcript:

An Agile Method for E-Service Composition Author : Pouya Fatehi, Seyyed Mohsen Hashemi Department of Computer Software, Science and Research Branch, Islamic Azad university Tehran, Iran Reporter : Calvin Chang

OUTLINE Introduction Agile Model for Service Composition Second level of AM4SC Comparison of AM4SC with other Service Composition Methods

Introduction E-services more popular today Develop composite service – The composability feature of services leads to lowcost development of high quality services reason Software as a Service (SaaS) model which is a rapidly growing model of software licensing Under SaaS, the software publisher (seller) runs and maintains all necessary hardware and software and buyers obtain access using the Internet Software as a Service (SaaS) model which is a rapidly growing model of software licensing Under SaaS, the software publisher (seller) runs and maintains all necessary hardware and software and buyers obtain access using the Internet

Agile methodologies is more useful for developing services. In this paper try to represent a new agile methodology for services The Impact of Methods and Techniques on Outcomes from Agile Software Development Projects using two agile methods is better in productivity rather than using only one method. No significant further advantage in increasing the number of methods used beyond two. Significant difference between the eXtreme Programming/Scrum combination. using two agile methods is better in productivity rather than using only one method. No significant further advantage in increasing the number of methods used beyond two. Significant difference between the eXtreme Programming/Scrum combination. Which agile methods are the most effective for composite service development ?

Changing development process can not implemented in a single shot  Defined two implementation levels Scrum eXtreme Programming (XP)  Focused on agile project management aspects  Scrum is a wrapper around other engineering approaches  Focused on agile project management aspects  Scrum is a wrapper around other engineering approaches  Very much oriented towards technology  Practices and programmer activity  Very much oriented towards technology  Practices and programmer activity complem entarity

Agile Model for Service Composition 4 activities  Scrum methodology 6 practices  XP method (AM4SC)

4 activites 1- Planning process  According to agile manifesto, proposed model would not be a complete model but it is started with a simple model and will be finalized with iteration and incremental in later evolves. 2-Arrangement process  This process will be done at a periodical session  Output of services and features that should be included in next iteration  Expected input, expected output and requirement list determined  This process will be done at a periodical session  Output of services and features that should be included in next iteration  Expected input, expected output and requirement list determined 3-Modeling process  Done with any available service modeling tools 4- Implementation Process  The platform of independent model for composite service that offered in previous step mapped to platform of specific model

life cycle will be continued till getting customers feedback and their new requirements

6 practices Collaborative programming  Developers of services share their experiences for modeling and implementing composite service in low cost at easiest way Iterative and Incremental development  Main features developed in first iteration then with refactoring other features would be inserted to composite service incrementally Online customers  Feedbacks will be used to increase quality and acceptance of developed service  Release beta versions in web  Feedbacks will be used to increase quality and acceptance of developed service  Release beta versions in web Continues integration  Whole service model should be integrated to implement composite service, this makes model more reliable Reusability through design  Ensuring that a piece of functionality is implemented in a single place  Services which used in composite service, implement functionality once  Ensuring that a piece of functionality is implemented in a single place  Services which used in composite service, implement functionality once Service model refactoring  Logics of model sections must stay unchanged  useful for decreasing cost and time to apply changes that consumer expects  Logics of model sections must stay unchanged  useful for decreasing cost and time to apply changes that consumer expects

Second level of AM4SC Six agents collaborate together to achieve model goals

Feature selector  Select features by pairs that service requester sent as an input  customer’s requests should be categorized across the developer’s policies and their priorities which provided by requester  Output of this agent, also is useful tool for accessing progress of development process  Select features by pairs that service requester sent as an input  customer’s requests should be categorized across the developer’s policies and their priorities which provided by requester  Output of this agent, also is useful tool for accessing progress of development process Unit test maker  Searches among reference models for defined problem domain that described by service requester requirements Automated refactor/modeler agent  Creates requests for binding required service based on selected features and artifacts that defined by unit test maker agent. Model refactoring  When unit tests fails or in next iteration of service development, cycles to add more features in composed service Service creator  Binds services and creates needed relationship designed in service model between input and outputs of services Tester agent  Tests composed service with created unit tests and surveys the results. The composed service delivers to service requester Xmodel with failed unit tests delivered to automated modeler for refactoring and changing model to satisfy all unit tests  Tests composed service with created unit tests and surveys the results. The composed service delivers to service requester Xmodel with failed unit tests delivered to automated modeler for refactoring and changing model to satisfy all unit tests

Comparison of AM4SC with other Service Composition Methods

THANKS