DOCSLIB.ORG

A Refinement Based Methodology for Software Process Modeling Fahad Rafique Golra

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Refinement Based Methodology for Software Process Modeling Fahad Rafique Golra A Refinement based methodology for software process modeling Fahad Rafique Golra To cite this version: Fahad Rafique Golra. A Refinement based methodology for software process modeling. Software Engineering [cs.SE]. Télécom Bretagne, Université de Rennes 1, 2014. English. tel-00978732 HAL Id: tel-00978732 https://tel.archives-ouvertes.fr/tel-00978732 Submitted on 14 Apr 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. N° d’ordre : 2014telb0304 Sous le sceau de l’Université européenne de Bretagne Télécom Bretagne En habilitation conjointe avec l’Université de Rennes 1 Ecole Doctorale – MATISSE A REFINEMENT BASED METHODOLOGY FOR SOFTWARE PROCESS MODELING Thèse de Doctorat Mention : Informatique Présentée par Fahad Rafique – GOLRA Département : Informatique Laboratoire : IRISA Directeur de thèse : Antoine Beugnard Soutenue le 08 janvier 2014 Jury : M. Bernard Coulette + Professeur à l’université de Toulouse (Rapporteur) Mme Sophie Dupuy-Chessa Maître de conférence à UPMF-Grenoble 2 (Rapporteur) M. Christophe Dony + Professeur à Université Montpellier II (Examinateur) M. Reda Bendraou + Maître de conférence l’université Pierre & Marie Curie (Examinateur) M. Fabien Dagnat + Maître de conférence à Télécom Bretagne (Encadrant) M. Antoine Beugnard + Professeur à Télécom Bretagne (Directeur de thèse) Essentially, all models are wrong, but some are useful. George E. P. Box Acknowledgments I would like to gratefully and sincerely thank Fabien Dagnat for his guidance, understanding, patience, and most importantly, his friendship during my graduate studies at Telecom Bretagne. His mentorship was paramount in providing a well- rounded experience consistent to my long-term career goals. He encouraged me to not only grow my expertise in my research domain but also as an independent thinker. Not only did he ignite my imaginations, he also stimulated the thirst and the desire to know. I would like to thank Antoine Beugnard for his constant guidance and the liberty to explore the domain with his constant support. I am not sure many graduate students are given the opportunity to develop their own individuality and self-sufficiency by being allowed to work with such independence. I would also like to thank all of the members of PASS research team at Tele- com Bretagne, especially Maria-Teresa Segarra and Julien Mallet and all other fellow doctoral/post-doctoral researchers for giving me the opportunity to discuss and evolve this research project. Additionally, I am very grateful for the friendship of all of the members of his research group, especially Aladin, Jean Baptiste, Thang, Ali and An Phung, with whom I worked closely and puzzled over many similar problems. I would also like to thank my colleagues in office and Serge Garlatti who provided for some much needed humor and entertainment in what could have otherwise been a somew- hat stressful laboratory environment. I specially want to thank Armelle Lannuzel, who has helped me through all administrative procedures during my stay. I would like to thank the members of my defense jury for their input, valuable discussions and proposed corrections, that shall guide me further to improve my professional skills. Finally, and most importantly, I would like to thank my wife Asfia Firduas. Her support, encouragement, quiet patience and unwavering love were undeniably the foundations upon which the past six years of my life have been built. I thank my parents, Rafique Golra and Nusrat Shaheen, for their faith in me and allowing me to be as ambitious as I wanted. It was under their watchful eye that I gained so much drive and an ability to tackle challenges head on. Also, I thank my brothers Asad and Shoaib who provided me with unending encouragement and support. Abstract There is an increasing trend to consider the processes of an organization as one of its highly valuable assets. Processes are the reusable assets of an organization which define the procedures of routine working for accomplishing its goals. The software in- dustry has the potential to become one of the most internationally dispersed high-tech industry. With growing importance of software and services sector, standardization of processes is also becoming crucial to maintain credibility in the market. Software development processes follow a lifecycle that is very similar to the software develop- ment lifecycle. Similarly, multiple phases of a process development lifecycle follow an iterative/incremental approach that leads to continuous process improvement. This incremental approach calls for a refinement based strategy to develop, execute and maintain software development processes. This thesis develops a conceptual foundation for refinement based development of software processes keeping in view the precise requirements for each individual phase of process development lifecycle. It exploits model driven engineering to present a multi-metamodel framework for the development of software processes, where each metamodel corresponds to a different phase of a process. A process undergoes a series of refinements till it is enriched with execution capabilities. Keeping in view the need to comply with the adopted standards, the architecture of process modeling approach exploits the concept of abstraction. This mechanism also caters for special circumstances where a software enterprise needs to follow multiple process standards for the same project. On the basis of the insights gained from the examination of contemporary offe- rings in this domain, the proposed process modeling framework tends to foster an architecture that is developed around the concepts of “design by contract" and “de- sign for reuse". This allows to develop a process model that is modular in structure and guarantees the correctness of interactions between the constituent activities. Se- paration of concerns being the motivation, data-flow within a process is handled at a different abstraction level than the control-flow. Conformance between these levels allows to offer a bi-layered architecture that handles the flow of data through an un- derlying event management system. An assessment of the capabilities of the proposed approach is provided through a comprehensive patterns-based analysis, which allows a direct comparison of its functionality with other process modeling approaches. Keywords : Process Modeling, Software Development, Metamodels, Model Driven Architecture, Process Refinement, Component-oriented Process Modeling Framework (CPMF) Résumé Il y a une tendance croissante à considérer les processus d’une organisation comme l’une de ses grandes forces. Les processus sont des ressources réutilisables d’une orga- nisation qui définissent les procédures de travail pour la réalisation de ses objectifs. Avec l’importance croissante du secteur des logiciels et des services, la standardisation des processus devient indispensable pour maintenir sa crédibilité. Le développement de processus suit un cycle de vie très similaire à celui du développement logiciel. Par exemple, il se compose de plusieurs phases et suit une approche incrémentale qui mène à son amélioration continue. Cette approche incrémentale peut être complétée par une stratégie basée sur le raffinement pour développer, exécuter et maintenir les processus de développement de logiciels. Cette thèse propose une base conceptuelle pour le développement de processus logiciels par raffinement, sans perdre de vue les exigences spécifiques de chaque phase du cycle de vie d’un tel processus. Elle utilise l’ingénierie dirigée par les modèles pour présenter un ensemble de méta-modèles pour le développement de processus logiciels où chaque méta-modèle correspond à une phase différente d’un processus (spécifica- tion, implémentation et instanciation). Le modèle d’un processus traverse une série de raffinement jusqu’à ce qu’elle soit enrichie par des capacités d’exécution. Le dé- veloppement d’un interpréteur permet d’exécuter ce modèle. Il donne la possibilité de relier les modèles des differentes phases par des liens de traçabilité. Les inter- venants peuvent interagir avec le processus en exécution à l’aide d’une interface de supervision. Un niveau de variabilité incluse dans les modèles de processus permet leur adaptation pendant l’exécution. Tout en prenant en compte la nécessité de se conformer aux standards adoptés par l’organisation, l’architecture de l’approche de modélisation proposée exploite le concept d’abstraction en s’inspirant de la notion de composant logiciel pour aider à la réutilisation de modèles de processus. Notre mé- thode est également prévue pour les entreprises qui veulent suivre plusieurs standards pour le même projet. Sur la base des connaissances acquises grâce à l’étude des langages de modélisation actuels du domaine, le cadre proposé pour la modélisation de processus présente une architecture qui se développe autour des concepts de «conception par contrat» et «conception pour et par la réutilisation». Ceci permet de construire un modèle de processus qui a une structure modulaire et garantit la correction des interactions entre
Load more

Recommended publications
  • Software Architecture: the Next Step for Object Technology (PANEL)
    Software Architecture: The Next Step for Object Technology (PANEL) Bruce Anderson, University of ESSPX (moderator) Mary Shaw, Carnegie-Mellon University Larry Best, American Management Systems Kent Beck, First Class Software What is the next step for you? Progress comes Abstract from taking aware steps, but what steps are those? Architectures are the structuring paradigms, styles They could be in attempting to discover and and patterns that make up our software systems. catalogue architectures; creating awareness of this They are important in many ways: they allow us to level of product envisioning; doing design more talk usefully about systems without talking about consciously; finding ways of describing systems; their detail; a knowledge of them gives us design consolidating legacy code; abandoning legacy code; choices; attention to this level can make systems and making new software lifecycles. families of systems have the non-functional What is the next step for the community? Are there properties we want, especially changeability. ways to work that go beyond projects and Each panelist will address the following issues: companies? Will there be focus on the community, l What is architecture? which suggests cooperation, learning, divergence l What is the value you have had so far from and empowerment; or on the marketplace, which this concept? suggests competition, confidentiality, convergence l What is the next step for you? and dependence? l What is the next step for the community? 2 Mary Shaw 1 Background Software architecture is concerned with the What is architecture? We all have experience of organization of software systems: the selection of systems of great conceptual clarity and integrity.
    [Show full text]
  • The Great Methodologies Debate: Part 1
    ACCESS TO THE EXPERTS The Journal of Information Technology Management December 2001 Vol. 14, No. 12 The Great Methodologies Debate: Part 1 Resolved “Today, a new debate rages: agile software Traditional methodologists development versus rigorous software are a bunch of process- development.” dependent stick-in-the-muds who’d rather produce flawless Jim Highsmith, Guest Editor documentation than a working system that meets business needs. Opening Statement Jim Highsmith 2 Rebuttal Lightweight, er, “agile” Agile Can Scale: Inventing and Reinventing methodologists are a bunch of SCRUM in Five Companies glorified hackers who are going to be in for a heck of a surprise Jeff Sutherland 5 when they try to scale up their “toys” into enterprise-level software. Agile Versus Traditional: Make Love, Not War! Robert L. Glass 12 Business Intelligence Methodologies: Agile with Rigor? Larissa T. Moss 19 Agility with the RUP Philippe Kruchten 27 Extreme Requirements Engineering Larry Wagner 34 Exclusion, Assumptions, and Misinterpretation: Foes of Collaboration Lou Russell 39 Opening Statement by Jim Highsmith In the early 1980s, I participated in rigorous software development. others be able to understand the one round of methodology debate. Agile approaches (Extreme similarities and differences and be Structured analysis and design Programming, Crystal Methods, able to apply the right mix to their champions such as Tom DeMarco, Lean Development, Feature-Driven own organization. Both the SEI and Ed Yourdon, and Tim Lister were Development, Adaptive Software Rational have made wonderful on one side of the debate, while Development, SCRUM, and contributions to software develop- data-driven design aficionados like Dynamic Systems Development ment, but it is important to Ken Orr, Jean-Dominique Warnier, Methodology) populate one camp.
    [Show full text]
  • Facilitating Dynamic Flexibility and Exception Handling for Workflows
    Facilitating Dynamic Flexibility and Exception Handling for Workflows by Michael James Adams B.Comp (Hons) A dissertation submitted for the degree of IF49 Doctor of Philosophy Principal Supervisor: Associate Professor Arthur H.M. ter Hofstede Associate Supervisors: Dr David Edmond & Professor Wil M.P. van der Aalst Faculty of Information Technology Queensland University of Technology Brisbane, Australia 14 November 2007 Certificate of Acceptance i Keywords workflow exception handling, workflow flexibility, adaptive workflow, service oriented architecture, Activity Theory, Ripple-Down Rules, worklet, exlet, YAWL ii Abstract Workflow Management Systems (WfMSs) are used to support the modelling, analysis, and enactment of business processes. The key benefits WfMSs seek to bring to an or- ganisation include improved efficiency, better process control and improved customer service, which are realised by modelling rigidly structured business processes that in turn derive well-defined workflow process instances. However, the proprietary process definition frameworks imposed by WfMSs make it difficult to support (i) dynamic evo- lution and adaptation (i.e. modifying process definitions during execution) following unexpected or developmental change in the business processes being modelled; and (ii) exceptions, or deviations from the prescribed process model at runtime, even though it has been shown that such deviations are a common occurrence for almost all processes. These limitations imply that a large subset of business processes do not easily translate to the ‘system-centric’ modelling frameworks imposed. This research re-examines the fundamental theoretical principles that underpin workflow technologies to derive an approach that moves forward from the production- line paradigm and thereby offers workflow management support for a wider range of work environments.
    [Show full text]
  • Extreme Programming from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit View history Search Extreme programming From Wikipedia, the free encyclopedia Main page Extreme programming (XP) is a software development methodology which is Contents intended to improve software quality and responsiveness to changing customer Featured content requirements. As a type of agile software development,[1][2][3] it advocates frequent Current events "releases" in short development cycles, which is intended to improve productivity Random article and introduce checkpoints at which new customer requirements can be adopted. Donate to Wikipedia Wikipedia store Other elements of extreme programming include: programming in pairs or doing Interaction extensive code review, unit testing of all code, avoiding programming of features Help until they are actually needed, a flat management structure, simplicity and clarity in About Wikipedia code, expecting changes in the customer's requirements as time passes and the Community portal problem is better understood, and frequent communication with the customer and Recent changes among programmers.[2][3][4] The methodology takes its name from the idea that the Contact page Planning and feedback loops in beneficial elements of traditional software engineering practices are taken to extreme programming. Tools "extreme" levels. As an example, code reviews are considered a beneficial What links here practice; taken to the extreme, code can be reviewed continuously, i.e. the practice Related changes Software development of pair programming. Upload file process Special pages Critics have noted several potential drawbacks,[5] including problems with Core activities Permanent link unstable requirements, no documented compromises of user conflicts, and a Requirements · Design · Construction · Testing · Debugging · Deployment · Page information lack of an overall design specification or document.
    [Show full text]
  • Programming Design Patterns
    Programming Design Patterns Patterns for High Performance Computing Marc Snir/Tim Mattson Feb 2006 Dagstuhl Marc Snir Design Pattern High quality solution to frequently recurring problem in some domain Each pattern has a name, providing a vocabulary for discussing the solutions Written in prescribed format to allow the reader to quickly understand the solution and its context 2 Dagstuhl Feb 2006 Marc Snir History ‘60s and ‘70s Berkeley architecture professor Christopher Alexander 253 patterns for city planning, landscaping, and architecture Attempted to capture principles for “living” design. Published in 1977 3 Dagstuhl Feb 2006 Marc Snir Patterns in Object-oriented Programming OOPSLA’87 Kent Beck and Ward Cunningham Design Patterns: Elements of Reusable Object-Oriented Software By the “Gang of Four (GOF)”: Gamma, Helm, Johnson, Vlissides Catalog of patterns Creation, structural, behavioral Published in 1995 4 Dagstuhl Feb 2006 Marc Snir Impact of GOF book Good solutions to frequently recurring problems Pattern catalog Significant influence on object-oriented programming! Created a new vocabulary for software designers. 5 Dagstuhl Feb 2006 Marc Snir The Task Parallelism Pattern Problem: How do you exploit concurrency expressed in terms of a set of distinct tasks? Forces Size of task – small size to balance load vs. large size to reduce scheduling overhead Managing dependencies without destroying efficiency. Solution Schedule tasks for execution with balanced load – use master worker, loop parallelism, or SPMD patterns. Manage dependencies by: removing them (replicating data), transforming induction variables, exposing reductions explicitly protecting (shared data pattern). Intrusion of shared memory model… 6 Dagstuhl Feb 2006 Marc Snir Pattern Languages: A new approach to design Not just a collection of patterns, but a pattern language: Patterns lead to other patterns creating a design as a network of patterns.
    [Show full text]
  • Two Reengineering Patterns
    Type-Check Elimination: Two Reengineering Patterns Stephane´ Ducasse, Robb Nebbe, Tamar Richner Software Composition Group, Universitat¨ Bern g fducasse,nebbe,richner @iam.unibe.ch http://www.iam.unibe.ch/scg/ Abstract A reengineering pattern describes how to go from an existing legacy solution to a new refactored solution. In this paper we discuss the role of reengineering patterns and contrast them with design patterns and antipatterns. We then highlight the structure of a reengineering pattern and present two simple, related patterns for type-check elimination. 1 Reengineering Patterns When important legacy software can no longer gracefully evolve to meet changing requirements it is often reengineered. Reengineering patterns codify and record knowledge about modifying legacy software: they help in diagnosing problems and identifying weaknesses which hinder further development of the system and aid in finding solutions which are more appropriate to the new requirements. Reengineering patterns differ from Design Patterns [GHJV95] in their emphasis on the pro- cess of moving from an existing legacy solution to a new refactored solution. Whereas a design pattern presents a solution for a recurring design problem, a reengineering pattern presents a refactored solution for a recurring legacy solution which is no longer appropriate, and describes how to move from the legacy solution to the refactored solution. The mark of a good reengineer- ing pattern is (a) the clarity with which it exposes the advantages, the cost and the consequences of the target solution with respect to the existing solution, and not how elegant the target solution is, (b) the description of the change process: how to get from one state of the system to another.
    [Show full text]
  • Summary of Extreme Programming by Marc Novakouski Description Extreme Programming (Also Known As “XP”) Is a Popular Software
    Summary of Extreme Programming By Marc Novakouski Description Extreme Programming (also known as “XP”) is a popular software development process which grew out of the growing movement towards Agile processes[1]. The basic idea behind Extreme Programming is to strip out virtually all of the elements of the traditional software process to get to streamline development[1]. As a result, an XP project usually results in a software project in which software development is begun immediately, virtually no documentation artifacts are created, other than “user stories” which are written on index cards, and the project proceeds in an iterative fashion in which prototypes are created with the direct input (and sometimes help) of the stakeholders on a daily basis until the desired effect is created[1]. Finally, a key principle of XP is to expect and even “embrace” change, and XP does this by encouraging “refactoring,” or restructuring of the code on the fly on an as-needed basis. Extreme Programming is essentially a conglomeration of a number of specific “Agile” software development practices and concepts[2] in an attempt to remove the non-essential parts of the development process[3]. There are 12 “core” practices that make up XP, which are separated into 4 key areas: Planning, Design, Coding, and Testing[3][4]. Some practices are considered to be “best practices” of the software industry, such as Continuous Integration and Test Driven Development[4]. However, several practices such as Pair Programming and the System Metaphor are more controversial, and are often excluded in practice[5][7]. Extreme Programming is considered to be a development method suitable for only certain types of projects, such as small projects, research projects, and projects dealing with new technology[4].
    [Show full text]
  • Devops Advantages for Testing
    INTEGRATION AND INTEROPERABILITY Labs found that teams using DevOps experience “60 times fewer failures and recover from failures 168 times faster than DevOps Advantages their lower-performing peers. They also deploy 30 times more frequently with 200 times shorter lead times [2].” The choices of tools and frameworks for all of this automation for Testing has grown dramatically in recent years, with options available for almost any operating system, any programming language, open source or commercial, hosted or as-a-service. Active communi- Increasing Quality through ties surround many of these tools, making it easy to find help to start using them and to resolve issues. Continuous Delivery Continuous Integration Building a CD process starts with building a Continuous Integra- Gene Gotimer, Coveros tion (CI) process. In CI developers frequently integrate other de- Thomas Stiehm, Coveros veloper’s code changes, often multiple times a day. The integrated code is committed to source control then automatically built and Abstract. DevOps and continuous delivery can improve software quality and unit tested. Developers get into the rhythm of a rapid “edit-compile- reduce risk by offering opportunities for testing and some non-obvious benefits test” feedback loop. Integration errors are discovered quickly, to the software development cycle. By taking advantage of cloud computing and usually within minutes or hours of the integration being performed, automated deployment, throughput can be improved while increasing the amount while the changes are fresh on the developer’s minds. of testing and ensuring high quality. This article points out some of these oppor- A CI engine, such as Jenkins [3], is often used to schedule tunities and offers suggestions for making the most of them.
    [Show full text]
  • A Brief History of Devops by Alek Sharma Introduction: History in Progress
    A Brief History of DevOps by Alek Sharma Introduction: History in Progress Software engineers spend most of their waking hours wading George Santayana wrote that “those who cannot remember the through the mud of their predecessors. Only a few are lucky past are condemned to repeat it.” He was definitely not thinking enough to see green fields before conflict transforms the about software when he wrote this, but he’s dead now, which terrain; the rest are shipped to the front (end). There, they means he can be quoted out of context. Oh, the joys of public languish in trenches as shells of outages explode around them. domain! Progress is usually glacial, though ground can be covered This ebook will be about the history of software development through heroic sprints. methodologies — especially where they intersect with traditional best practices. Think of it as The Silmarillion of Silicon Valley, But veterans do emerge, scarred and battle-hardened. They except shorter and with more pictures. Before plunging into this revel in relating their most daring exploits and bug fixes to new rushing river of time, please note that the presented chronology recruits. And just as individuals have learned individual lessons is both theoretically complete and practically in progress. In other about writing code, our industry has learned collective lessons words, even though a term or process might have been coined, it about software development at scale. It’s not always easy to always takes more time for Best Practices to trickle down to Real see these larger trends when you’re on the ground — buried in Products.
    [Show full text]
  • Agile Practices
    Founda'ons of Soware Engineering Process: Agile Prac.ces Claire Le Goues 1 Learning goals • Define agile as both a set of iterave process prac.ces and a business approach for aligning customer needs with development. • Explain the mo.vaon behind and reason about the tradeoffs presented by several common agile prac.ces. • Summarize both scrum and extreme programming, and provide mo.vaon and tradeoffs behind their prac.ces. • Iden.fy and jus.fy the process prac.ces from the agile tradi.on that are most appropriate in a given modern development process. 2 What problems are there in soware development? 3 Agile So,ware Development Is … Both: • a set of soMware engineering best prac.ces (allowing for rapid delivery of high quality soMware) • a business approach (aligning development with customer needs and goals) 4 Brief History of Agile XP reified: Kent Beck Incepon of Iterave and released Extreme Incremental Development (IID): Introducon of Scrum: Programming Explained: Walter Shewhart (Bell Labs, Jeff Sutherland and Ken Embrace Change signal transmission) proposed a Schwaber presented a paper Introduc&on of “Agile”: series of “plan-do-study- describing the Scrum The Agile Manifesto act” (PDSA) cycles methodology at a conference wri[en by 17 soMware workshop developers Introducon of the waterfall: Winston Royce’s ar.cle Managing the Development of Large So<ware Systems 1930s 1970 1995 1999 2001 5 Agile in a nutshell • A project management approach that seeks to respond to change and unpredictability, primarily using incremental, iterave work sequences (oMen called “sprints”). • Also: a collec.on of prac.ces to facility that approach.
    [Show full text]
  • Architecture of Information Systems
    Technische Universiteit Eindhoven University of Technology Architecture of Information Systems Full title Architecture of Information Systems Programme leader prof.dr.ir. W.M.P. van der Aalst (from September 2006) prof.dr. K.M. van Hee (until September 2006) Starting date before 1996 Research area Information systems CR-classification H. Information Systems D.2.2 Design Tools and Techniques H.4.1 Office Automation H.2.8 Database Applications Affiliations research school SIKS (Research School for Information and Knowledge Sys- tems) BETA (Research School for Operations Management and Lo- gistics) TU/e LOIS (Logistics, Operations and their Information Systems) Cooperations (at most five per category are listed) national prof. Geert-Jan Houben (Delft) prof. Roel Wieringa (Twente) prof. Farhad Arbab (CWI) prof. Rinus Plasmeijer (Radboud University Nijmegen) international prof. Wolfgang Reisig and prof. Jan Mendling (Humboldt- Universität zu Berlin ) prof. Arthur ter Hofstede and prof. Michael Rosemann (Queensland University of Technology) prof. Karsten Wolf (Universität Rostock) prof. Mathias Weske (Hasso Plattner Institute) prof. Kurt Jensen (University of Aarhus) 25 Research Evaluation Computer Science 2009 * Part B: AIS Technische Universiteit Eindhoven University of Technology Mission statement The Architecture of Information Systems (AIS) research group investigates methods, techniques and tools for the design and analysis of Process-Aware Information Systems (PAIS), i.e., systems that support business processes (workflows) inside and between organizations. We are not only interested in these information systems and their architecture, but also model and analyze the business processes and organizations they support. Our mission is to be one of the worldwide leading research groups in process modeling and analysis, process mining, and PAIS technology.
    [Show full text]
  • Extreme Programming Explained Embrace Change Kent Beck With
    Extreme Programming Explained Embrace Change Kent Beck with Cynthia Andres What is XP? • XP is about: • social change. • letting go of old habits and patterns that limit us. • giving up defenses that protect us but interfere with our productivity • being open about what we are capable of doing. • allowing others to do the same. • the process of becoming more of our best selves • the process of becoming our best as programmers. • Good relationships lead to good business. • Productivity and confidence are related to our human relationships in the workplace as well as our coding ability • XP addresses both What is XP? • Prepare for success. • Don’t protect yourself from success by holding back. • Do your best and then deal with the consequences. • That’s extreme – you leave yourself exposed. • This can be as scary as it is exciting and liberating. • XP focuses on: • excellent application of programming techniques • clear communication • teamwork What is XP? • XP Includes: • A philosophy of software development based on the values of communication, feedback, simplicity, courage, and respect. • A body of practices proven useful in improving software development • The practices complement each other, amplifying their effects. • The practices are chosen as expressions of the values. • A set of complementary principles, intellectual techniques for translating the values into practice • A community that shares these values and practices. What is XP? • XP is a path to improvement to excellence for people coming together to develop software. • It is distinguished from other software engineering methodologies by: • Short development cycles, resulting in early, concrete, and continuing feedback. • An incremental planning approach, which quickly comes up with an overall plan that is expected to evolve over time.
    [Show full text]