A Toolkit for SE for Sustainability A Design Fiction
|
|
- Sara Richardson
- 8 years ago
- Views:
Transcription
1 A Toolkit for SE for Sustainability A Design Fiction Birgit Penzenstadler Department of Computer Engineering and Computer Science California State University Long Beach birgit.penzenstadler@csulb.edu Abstract. This paper explores the what-ifs for a possible future scenario describing how to develop software systems for sustainability in different application domains in a generic software development setting. The design fiction we narrate is the following: Valery, a software developer at the fictitious software development company GreenCode, works on CodeFairy, an educational game targeted at attracting girls to computer science, and uses the software engineering toolkit GreenYaCode as development environment. This toolkit helps to translate domain-dependent, high-level sustainability goals into software-specific constraints - i.e. it helps design sustainability into the software system. This is achieved by an extensive knowledge base that allows making recommendations to the software developer, and by best practices from open sources software development and user experience best practices. Keywords: Education, information design, knowledge visualization, design fiction, future trends, storytelling, sustainability 1 Software Engineering for Sustainability Sustainability from the point of view of software systems has two major aspects: The software system as technical implementation independent of its purpose, and the software system as means of interaction between users and application context. To define what sustainability for any kind of system, exact scoping needs to be performed by answering the questions of what to sustain, for whom, over which time frame, and at what cost [15]. Once that is established, we can apply systems thinking [16] and follow sustainability principles, e.g. [3], while honoring the axioms defined by Heinberg [7], to improve the sustainability of the given system. This encompasses the individual, social, economic, environmental, and technical sustainability aspects of a system [10]. For a software system, there are two scopes that may be chosen for an analysis, domain-dependent and domain-independent. Scope (1): Domain-dependent Sustainability. The software system in its application context, under consideration of the purpose of the software system. This scoping includes an analysis of the economic, social, and environmental dimensions of sustainability on a higher level. This part of the analysis
2 is largely within the responsibility of business analysts and domain experts. Following the code of ethics [1], it is our responsibility to support in translating the arising demands into system-related requirements. This is what we call domain-dependent sustainability: The Sustainability of a Software System and its Surrounding Application Context, is characterized by the domain experts. This scoping is domain-dependent and we call it domain-dependent sustainability, software engineers can translate those requirements into constraints for the software system. Scope (2): Domain-independent Sustainability. The artifacts and implementation of a software system, without any consideration of the purpose of the software system. This scoping focuses on the technical characteristics of the system and its operational environment. All domain-relevant information has already been refined into domain-independent constraints for a technical solution by business analysts. This is the responsibility of the software engineers. This is what we call domain-independent sustainability: The Sustainability of a Software System is its capacity to endure, i.e. its energy efficiency, its maintainability over a long period of time, and its adherence to standards and laws. This scoping is independent of the application domain of the software system; therefore we call this domain-independent sustainability. In order to develop software systems that implement sustainability goals, we need the discipline of software engineering to embrace sustainability as major objective for systems development. Software Engineering for Sustainability (SE4S) denotes the concept of applying software engineering techniques to facilitate the refinement of higher level sustainability concerns as defined in the domain into lower level, technical requirements for the design and implementation of the system. This means the translation and refinement from domaindependent to domain-independent sustainability. In this paper, we present a design fiction of how SE4S can be supported in a toolkit. In more detail, the story line follows software developer Valery through her workday and points out open questions and research challenges by describing which inputs have to be made to implement the GreenYaCode toolkit system. We illustrate its usage with the support that it makes when Valery goes through the individual steps taken during software development. 2 Background This section provides background information on design fiction, on free open source software development, and on the Software Engineering for Sustainability (SE4S) research project. 2.1 Design Fiction Research is often inspired by visions of the future, for example the Vision 2050 [17]. These visions can take on various narrative forms, and can fall anywhere along the spectrum from utopian to dystopian [2]. Even though we recognize the importance of such visions to help us shape research questions and
3 inspire rich design spaces to be explored, the opportunity to discuss them is rarely given in a research context [12]. 2.2 Free Open Source Software Development and Open Innovation Open-source software development has been a large part of the creation of the World Wide Web as we know it, with Tim Berners-Lee contributing his HTML code development as the original platform upon which the internet is now built [4]. Free and open sources software (FOSS) are software products available with its source code under an open-source license to study, change, and improve its design. Examples of some popular open-source software products are Mozilla Firefox, Google Chromium, Android, LibreOffice and the Apache OpenOffice Suite. FOSS is said to reduce costs, avoid lock-in, ease use, and provide open security [13]. 2.3 SE4S Research Project The Software Engineering for Sustainability (SE4S) research project has developed a number of contributions with regard to how software engineers can include sustainability as major objective into software systems development [11]. Specifically requirements engineers have the means to establish designing for sustainability early on during the development process [10], and quality engineers help carry it through the rest of the development process [8]. This paper proposes the vision of a toolkit to support these concepts in practice, so that every software developer can easily apply them in their daily work. 3 Vision of the Toolkit and its Application It is the year 2020 and Valery has been working as software engineer at Green- Code for 5 years after graduating from California State University Long Beach with a Master s degree in Computer Science. She had been eager to find a software development company that would allow her to work on projects where she can foster environmental and social sustainability. When GreenCode emerged as an academic spin-off from the GreenIT lab at UC Irvine, she got in touch with their team and found an alike mindset of motivated software engineers who wanted to take their share of responsibility to make software systems that would improve the status quo in social responsibility and environmental protection. They mainly work on projects in two domains: scientific software to facilitate research in their local environment, the ocean and the mountains, and educational software to improve the access to knowledge for children of all ages. In that latter domain, Valery has been assigned to the CodeFairy project, an educational game targeted at attracting girls to computer science. Before GreenCode became an academic spin-off, the team had developed the SE4S toolkit GreenYaCode, a software development environment that helps to translate domain-dependent, high-level sustainability goals into domain-independent,
4 software-specific constraints i.e. it helps design sustainability into the software system. GreenCode is a web-based SE4S guide that provides easy access to the reference models and related examples in form of a knowledge database, see the wireframe in Fig. 2. This knowledge base can be extended over time with further examples from case studies and with recommender systems that actively guide the user, i.e., the requirements engineer. This is the most flexible way of accommodating the pace of change in popular programming languages and therefore provides the greatest possible outreach to the software development community. The toolkit ties together efforts in software engineering for sustainability, free open source software development, recommender systems, usability best practices, open innovation, and user engagement. SE4S starts with requirements engineering and determining the stakeholders for the system, which is the basis for being able to elicit requirements. In more detail, there are four elicitation and analysis steps that are preempted by guiding questions [10]. For CodeFairy, Valery develops a number of artifacts that document the information needed to start the actual design process. She composes a business case, stakeholder model, goal model, system vision, domain model, usage model, and non-functional requirements, all by using the guidance provided by GreenYaCode to make sure the sustainability goals issued by the stakeholders for CodeFairy are incorporated into the design process. These artifacts form the basis that allows to decide on the implementation platform and to start the design of CodeFairy. In the following, we will walk through those steps and their application for CodeFairy. 3.1 Scope System and Derive System Vision Fig. 1. CodeFairy Clear scoping lies the foundation for successful systems development. The scoping allows for deriving a system vision, a conception of what is to be developed commonly agreed upon by all stakeholders. Valery opens the GreenYaCode start page and the quick start guide provides the guiding question for the first step: Does the system under consideration have an explicit purpose towards environmental or social sustainability? If yes, this can be analyzed in depth. If no, it can be considered whether such an aspect is desirable and feasible to add. For CodeFairy, the purpose is to engage girls from the age of twelve to learn coding in a playful way. Inspired by The Hour of Code 1 and Alice 2, CodeFairy provides means to understand concepts in computer science and mathematics, and shows
5 how they are applied when making software. It promotes social sustainability in terms of education and gender equality in STEM. On this basis, Valery develops a system vision using an integrated diagraming tool that helps her define the system boundary, operational context and the most central user features of CodeFairy. 3.2 Analyse Sustainability of Context The second guiding question posed by GreenYaCode is: Does the system under consideration have an impact on the environment? We need to analyze what are the direct (first order), indirect (second order), and systemic as well as potential rebound effects (third order) [9]. GreenYaCode provides an analysis checklist of influencing factors for each of those orders of effect. Most obvious are the first order effects. First order effects are the resources that the system itself (the application on different devices and the database) consume. For software, that is predominantly the energy that a software consumes, which can be influenced by good design strategies and energyefficient code. For the hardware part of a system, measures include following green IT principles. The second order effects are the resources the system triggers in its application domain. That means, the developer has to look at how the software system interacts with its operational environment. Which processes are triggered, for example which machines are used or what do users do because of having this software system in place? The third order effects remain to be observed in the long run but can be predicted using future scenario techniques and extrapolation. In simple terms, imagine what could happen if the user base of this system increases dramatically and many people use the system over many years in high intensity. How could that affect overall resource consumption and how could that change behavior? For CodeFairy, the first order effects are the energy that the software uses and the usage of laptops or desktop machines to run the software. Second order effects are increased computer literacy and software engineering knowledge (education is part of individual sustainability), increased social skills in collaboration with other girls on teams (social sustainability) but also increased hardware usage in classroom and therefore e-waste (environmental impact). Third order effects might be increased rates of female students in computer science if outreach is successful (potential individual, social, and economic benefits) but also further environmental impact due to increased energy usage and e-waste production. However, as CodeFairy would not be the reason for ordering new hardware, but rather sharing common resources (laptops or computers that are used in class anyways), this environmental impact is comparatively small. 3.3 Find Sustainability Stakeholders THe third guiding question is: Is there an explicit stakeholder for sustainability? In case there is an explicit stakeholder who advocates for environmental sustainability, there is already a significant representative who issues objectives,
6 constraints and considerations to support that quality in the system under consideration. In case there is no such advocate, it can be decided to establish such a role. Otherwise, at the very least, a domain expert should be established as a representative for sustainability for providing information on applying environmental standards, legislation, and regulations. To find sustainability stakeholders, GreenYaCode provides a reference list of stakeholders who might have an interest in sustainability concerns. The reference list is ordered by sustainability aspect and describes for each stakeholder role that is common in software development, what their interest w.r.t. in a specific sustainability aspect is, for example a user is interested in their own individual sustainability, and a network administrator is mainly interested in the technical sustainability of the system they have to maintain. Furthermore, the list references dedicated sustainability stakeholders, for example legal representatives for environmental regulations. For CodeFairy, the usual software development stakeholders have to be considered. In addition, Valery might engage a sustainability consultant to, for example, add a case study system with environmental objectives, so the students can learn how software systems can support and help to protect the environment. 3.4 Elicit Sustainability Objectives, Goals and Constraints Fig. 2. Wireframe of the Reference Model Screen of the Toolkit
7 The fourth guiding question is: What are the sustainability goals and constraints for the system? Independent of whether the system has an explicit purpose for supporting environmental sustainability or not, there certainly are a number of objectives that pertain to the different dimensions of sustainability that may be chosen to apply. For example, a social network might not have an explicit environmental purpose, but it certainly has objectives supporting social sustainability. Furthermore, any system will at least have some constraints with respect to the environment, as stated in Q2. To elicit sustainability objectives, goals and constraints, GreenYaCode provides the sustainability reference model. Examples for instances are depicted in the wireframe on the right side in Fig. 2. It shows an example that distinguishes three levels of abstraction: The business goals (What benefits is this system going to bring?), the usage goals (What can the user do with the system?), and the system goals (How will the system provide that?). Each of those should be analyzed for the five sustainability aspects. For CodeFairy, a central business objective is to increase the education of girls in software engineering and thereby reach out early on to get them excited about STEM fields. A usage goal derived from this business objective is to have them interact with the system in a playful way so the intrinsical motivation remains high. A system goal deducted from that usage goal is that the user interface must be simple and intuitive enough so the target age group is addressed adequately. This way, Valery can develop a goal model that brings together the interests of the different stakeholders (who are the issuers of these objectives), that includes the different aspects of sustainability, and that uses continuous, integrated software engineering techniques for requirements that can be traced back to their originators. 4 Benefits and Challenges The development and evolution of the GreenYaCode toolkit brings with it a number of benefits and challenges, inter alia the transition from domain-dependent to domain-independent sustainability, the prioritization by stakeholders, economic return on investment, and the acceptance of the toolkit. 4.1 Domain-dependent Sustainability Sustainability is a very broad concept that is closely tied in with personal values. Consequently, it is used in very different forms. One end of the spectrum is the capacity to endure [14], which can be interpreted as survival of the fittest, and that leads to a concept of competence without considering values. The other end of the spectrum is life flourishing forever [5], where flourish needs interpretation that will include personal values. Consequently, domain-dependent sustainability is strongly dependent on the project context and tied in with the values of the stakeholders. This strong interdependence makes it impossible to clearly decompose domain-dependent sustainability for the general case.
8 4.2 Prioritization by Stakeholders There are potentially conflicting quality criteria, which again is tied to the specifics of the chosen definition for domain-dependent sustainability; for example sustainability and privacy: On one hand the absolute availability of information would make sustainability easier in many domains, and that is in conflict with privacy. For example, if companies had to provide all information on how green (environmentally sustainable) they really are with consumption of any type of resources, their processes, and their waste production. On the other hand, privacy can be understood as part of the individual sustainability of a person, for example security breaches in online banking. Consequently the occurrence of the conflict again depends on the definition of the domain-dependent sustainability and which values that definition is based on. Finally, how it is prioritized again depends on the importance that these stakeholders assign to it. 4.3 Economic Return on Investment For the economic perspective, (1) Valery can get credit for her company by contributing back into the knowledge base of GreenYaCode and (2) she can provide added value for her company by using GreenYaCode to demonstrate how sustainability is designed into the system. This is because the toolkit provides the traceability to prove the integration of sustainability throughout the development process and into the final product. The first point, the contribution back into the knowledge base, is a central principle in any open collaboration. For solving sustainability issues, sharing our knowledge and building up the databases that provide examples for best practices, is vital to success as there are so many different factors that have to be taken into account. A specific economic benefit of contributing back to the knowledge base will depend on the implementation of the tool. One way to imagine a win-win situation is to offer free use of the tool if the results that they were used for are contributed back to the knowledge base. In case of confidentiality issues, the contributions could be made more abstract or names and numbers could be modified and sources anonymized. The second point, providing added value to the company by demonstrating that sustainability was designed into the system, is relevant for marketing. As sustainability has received an increased awareness by companies in all application areas and business domains, it is likely that sustainability standards will develop that require the use of certain reference models to ensure compliance with such standards. In an ideal world, the GreenYaCode toolkit could become one of the toolkits to ensure this compliance. 4.4 Tool Acceptance To facilitate their application in practice for any proposed concept (including SE4S), it is necessary to provide adequate tooling to disseminate them. However, establishing new reference tools within a development company always
9 faces challenges of acceptance. It is easier to stick to established tools and avoid learning curves for new tools, unless the benefits early on significantly outweigh the initial effort. There are several open source development environments, for example Eclipse, that may welcome plug-ins that access GreenYaCode and use its reference models for provigin additional guidance within their programming environments. The availablility of such plug-ins is likely to increase application of SE4S in practice because the integration reduces the user effort for looking up yet another reference. Contributing to free open source software is an incentive to improve your coding skills and get familiar with large projects [6]. Therefore, students with interest in sustainability should be encouraged to engage in such activities. 5 Conclusion and Future Work As this is design fiction, we cannot present an evaluation of the concepts presented in this paper. However, the fiction is based on elements that have resulted from previous research and now have to be integrated into an encompassing guidance for software engineering for sustainability. The contribution of this paper is to provide a research roadmap for software engineers who aim at making our profession a part of the way of our society towards sustainability and to outline questions and challenges that have to be solved along that way. Future work includes: The iterative implementation of the proposed tool vision in increments with a growing list of features and capabilities. The qualitative evaluation of applicability and usability in feasibility studies in collaboration with software development companies in different contexts. The long-term evaluation of benefits for systems developmentin terms of the impact on the different dimensions of sustainability and the return on investment. Acknowledgements: This work is partially sponsored by the Deutsche Forschungsgemeinschaft under the EnviroSiSE project (grant number PE 2044/1-1). We would like to thank Ankita Raturi for feedback on an earlier version of this paper. References 1. ACM, Inc. Acm code of ethics Eric P. S. Baumer, June Ahn, Mei Bie, Beth Bonsignore, Ahmet Borutecene, Oguz Turan Buruk, Tamara Clegg, Allison Druin, Florian Echtler, Daniel Gruen, Mona Leigh Guha, Chelsea Hordatt, Antonio Kruger, Shachar Maidenbaum, Michael Muller, Leyla Norooz, Juliet Norton, Oguzhan Ozcan, Don Patterson, Andreas Riener, Steven Ross, Karen Rust, Johannes Schoening, Six Silberman, Bill Tomlinson, and Jason Yip. CHI 2039: Speculative Research Visions. In Proceedings of alt.chi of the ACM CHI Conference on Human Factors in Computing Systems, 2014.
10 3. Christoph Becker, Ruzanna Chitchyan, Leticia Duboc, Steve Easterbrook, Birgit Penzenstadler, Norbert Seyff, and Colin Venters. Sustainability Design and Software: The Karlskrona Manifesto. In Proceedings of the International Conference on Software Engineering, Tim Berners-Lee. Tim Berners-Lee on the Web at 25: the past, present and future. Wired UK, John R Ehrenfeld. The roots of sustainability. MIT Sloan Management Review, 46(2):23 25, Shlomi Fish. How to start contributing to or using Open Source Software. or_using_open_source_software, Richard Heinberg and Daniel Lerch. What is sustainability? The post carbon reader: managing the 21st century s sustainability crises, Patricia Lago, Akinli Kocak Sedef, Ivica Crnkovic, and Birgit Penzenstadler. Framing Sustainability as a Software Quality Property. Communications of the ACM, Current status: accepted for publication. 9. Donella Meadows. Leverage points places to intervene in a system. donellameadows.org/wp-content/userfiles/leverage_points.pdf, A shorter version of this paper appeared in Whole Earth, winter Birgit Penzenstadler. Infusing Green: Requirements Engineering for Green in and through software systems. In 3rd Intl. Workshop on Requirements Engineering for Sustainable Systems, Birgit Penzenstadler, Ankita Raturi, Debra Richardson, and Bill Tomlinson. Safety, Security, now Sustainability: The non-functional requirement of the 21st century. IEEE Software Special Issue on Green Software, Birgit Penzenstadler, Bill Tomlinson, Eric Baumer, Marcel Pufal, Ankita Raturi, Debra Richardson, Baki Cakici, Ruzanna Chitchyan, Georges Da Costa, Lynn Dombrowski, Malin Picha Edwardsson, Elina Eriksson, Xavier Franch, Gillian R. Hayes, Christina Herzog, Wolfgang Lohmann, Martin Mahaux, Alistair Mavin, Melissa Mazmanian, Sahand Nayebaziz, Juliet Norton, Daniel Pargman, Donald J. Patterson, Jean-Marc Pierson, Kristin Roher, M. Six Silberman, Kevin Simonson, Andrew W. Torrance, and Andre van der Hoek. ICT4S 2029: What will be the Systems Supporting Sustainability in 15 Years? In 2nd Intl Conf on ICT for Sustainability (ICT4S 2014) Stockholm, Sweden, August 2014, W. Stewart. Free Open Source Software Main Page. freeopensourcesoftware.org, SustainAbility. Sustainability: Can our society endure? sustainability.com/sustainability, Joseph Tainter. Sustainability. Personal communication, February 14, C.H. Waddington. Tools for Thought. Basic Books Inc., World Business Council for Sustainable Development. Vision 2050: A New Agenda for Business. VISION2050-FULLREPORT_FINAL.PDF, 2010.
RE4ES: Support Environmental Sustainability by Requirements Engineering
RE4ES: Support Environmental Sustainability by Requirements Engineering Birgit Penzenstadler 1, Bill Tomlinson 2 and Debra Richardson 2 1 Technische Universität München, Germany penzenst@in.tum.de 2 University
More informationSoftware Requirements Engineering for Sustainability. Debra Richardson* with Bill Tomlinson* and Birgit Penzenstadler** * UCIrvine, ** TUMünchen
Software Requirements Engineering for Sustainability Debra Richardson* with Bill Tomlinson* and Birgit Penzenstadler** * UCIrvine, ** TUMünchen Software Engineering has been Underutilized for Sustainability
More informationEffective Business Requirements (Virtual Classroom Edition)
Developing & Confirming Effective Business Requirements (Virtual Classroom Edition) Eliminate Costly Changes and Save Time by Nailing Down the Project Requirements the First Time! Pre-Workshop Preparation
More informationNASCIO EA Development Tool-Kit Solution Architecture. Version 3.0
NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5
More informationStory Card Based Agile Software Development
Story Card Based Agile Software Development Chetankumar Patel, and Muthu Ramachandran Leeds Metropolitan University, UK c.patel@leedsmet.ac.uk Abstract The use of story cards for user stories in many Extreme
More informationHow To Understand The Business Analysis Lifecycle
Business Analysis Lifecycle by Sergey Korban Aotea Studios Ltd November 2011 Contents Introduction... 3 Business Analysis Lifecycle... 4 Practical Application... 5 Start-Up Phase... 5 Initiation Phase...
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationThe role of integrated requirements management in software delivery.
Software development White paper October 2007 The role of integrated requirements Jim Heumann, requirements evangelist, IBM Rational 2 Contents 2 Introduction 2 What is integrated requirements management?
More informationExpert Reference Series of White Papers. Intersecting Project Management and Business Analysis
Expert Reference Series of White Papers Intersecting Project Management and Business Analysis 1-800-COURSES www.globalknowledge.com Intersecting Project Management and Business Analysis Daniel Stober,
More informationThe profile of your work on an Agile project will be very different. Agile projects have several things in common:
The Agile Business Analyst IT s all about being Agile? You re working as a Business Analyst in a traditional project environment, specifying the requirements for IT Developers to build. Suddenly everyone
More informationThe Role of Modelling in Teaching Formal Methods for Software Engineering
The Role of Modelling in Teaching Formal Methods for Software Engineering A. J. Cowling Department of Computer Science University of Sheffield Sheffield, England A.Cowling@dcs.shef.ac.uk Abstract. This
More informationAdopting Agile Project Management - Corporate Culture Must Match (Apr 15)
Adopting Agile Project Management - Corporate Culture Must Match (Apr 15) by Megan Torrance April 20, 2015 If you re contemplating adopting an agile approach, and the thought of implementing new project
More informationMENDIX FOR MOBILE APP DEVELOPMENT WHITE PAPER
MENDIX FOR MOBILE APP DEVELOPMENT WHITE PAPER TABLE OF CONTENTS Market Demand for Enterprise Mobile Mobile App Development Approaches Native Apps Mobile Web Apps Hybrid Apps Mendix Vision for Mobile App
More informationDEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES Robert M. Bruckner Vienna University of Technology bruckner@ifs.tuwien.ac.at Beate List Vienna University of Technology list@ifs.tuwien.ac.at
More informationListening to the Customer s Voice 1
Listening to the Customer s Voice 1 Karl E. Wiegers Process Impact 716-377-5110 www.processimpact.com Perhaps the greatest challenge facing the software developer is sharing the vision of the final product
More informationCLOUD MIGRATION STRATEGIES
CLOUD MIGRATION STRATEGIES Faculty Contributor: Dr. Rahul De Student Contributors: Mayur Agrawal, Sudheender S Abstract This article identifies the common challenges that typical IT managers face while
More informationWhite Paper. Business Analysis meets Business Information Management
White Paper BABOK v2 & BiSL Business Analysis meets Business Information Management Business Analysis (BA) and Business Information Management (BIM) are two highly-interconnected fields that contribute
More informationA Variability Viewpoint for Enterprise Software Systems
2012 Joint Working Conference on Software Architecture & 6th European Conference on Software Architecture A Variability Viewpoint for Enterprise Software Systems Matthias Galster University of Groningen,
More informationProject Cognatio: Developing a System for Medication Adherence (Evaluation of Requirements Engineering for Sustainability)
Institute for Software Research University of California, Irvine Project Cognatio: Developing a System for Medication Adherence (Evaluation of Requirements Engineering for Sustainability) Joseph Mehrabi
More informationRequirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationTowards Better Software Projects and Contracts: Commitment Specifications in Software Development Projects
Paper presented at the 20th International Conference on Software Engineering, April 19-25, 1998, Kyoto, JAPAN Towards Better Software Projects and Contracts: Commitment Specifications in Software Development
More informationComputing & Communications Services
2010 Computing & Communications Services 2010 / 10 / 04 Final Kent Percival, M.Sc., P.Eng. Defining the Value of the Business Analyst In achieving its vision, key CCS partnerships involve working directly
More informationSoftware development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali
Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 abb@cs.stir.ac.uk Spring 2014 (elicitation)
More information1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java. The Nature of Software...
1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering Software is intangible Hard to understand
More informationImproving Traceability of Requirements Through Qualitative Data Analysis
Improving Traceability of Requirements Through Qualitative Data Analysis Andreas Kaufmann, Dirk Riehle Open Source Research Group, Computer Science Department Friedrich-Alexander University Erlangen Nürnberg
More informationAs the use of agile approaches
What Does a Business Analyst Do on an Agile Project? By Kent J. McDonald Senior Instructor, B2T Training As the use of agile approaches increases, business analysts struggle to determine how their role
More informationImproving the visualisation of statistics: The use of SDMX as input for dynamic charts on the ECB website
Improving the visualisation of statistics: The use of SDMX as input for dynamic charts on the ECB website Xavier Sosnovsky, Gérard Salou European Central Bank Abstract The ECB has introduced a number of
More informationVAIL-Plant Asset Integrity Management System. Software Development Process
VAIL-Plant Asset Integrity Management System Software Development Process Document Number: VAIL/SDP/2008/008 Engineering For a Safer World P u b l i c Approved by : Ijaz Ul Karim Rao Revision: 0 Page:2-of-15
More informationExtended Enterprise Architecture Framework Essentials Guide
Extended Enterprise Architecture Framework Essentials Guide Editorial Writer: J. Schekkerman Version 1.5 2006 Preface An enterprise architecture (EA) establishes the organization-wide roadmap to achieve
More informationProcess Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
More informationCore Competencies for Public Health Professionals
Core Competencies for Public Health Professionals Revisions Adopted: May 2010 Available from: http://www.phf.org/programs/corecompetencies A collaborative activity of the Centers for Disease Control and
More informationBusiness Analysis Standardization & Maturity
Business Analysis Standardization & Maturity Contact Us: 210.399.4240 info@enfocussolutions.com Copyright 2014 Enfocus Solutions Inc. Enfocus Requirements Suite is a trademark of Enfocus Solutions Inc.
More information"A Role With No Edges": The Work Practices of Information Architects
Proceedings of HCI International 2003, vol 1, 22-27 June 2003, Crete, pp. 396-400. "A Role With No Edges": The Work Practices of Information Architects Toni Robertson, Cindy Hewlett, Sam Harvey and Jenny
More informationPartnering for Project Success: Project Manager and Business Analyst Collaboration
Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Definition and to describe the practice overview, requirements, best practices, activities, and key
More informationSoftware Requirements Specification of A University Class Scheduler
Software Requirements Specification of A University Class Scheduler Deanna M. Needell Jeff A. Stuart Tamara C. Thiel Sergiu M. Dascalu Frederick C. Harris, Jr. Department of Computer Science University
More informationRequirements Engineering Process
Software Engineering Requirements Engineering Process Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To describe the principal requirements engineering activities and d their
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationA Case Study on Benefits and Side-Effects of Agile Practices in Large-Scale Requirements Engineering
A Case Study on Benefits and Side-Effects of Agile Practices in Large-Scale Requirements Engineering Elizabeth Bjarnason, Krzysztof Wnuk, Björn Regnell Department of Computer Science, Lund University,
More informationStandardized software development model for SME software houses in Pakistan
Standardized software development model for SME software houses in Pakistan Abstract There are many software development models that exist for software development like Extreme Programming, Waterfall,
More informationIndustrial Engineering Definition of Tuning
Industrial Engineering Definition of Tuning Tuning is a faculty-led pilot project designed to define what students must know, understand, and be able to demonstrate after completing a degree in a specific
More informationFrom Capability-Based Planning to Competitive Advantage Assembling Your Business Transformation Value Network
From Capability-Based Planning to Competitive Advantage Assembling Your Business Transformation Value Network Marc Lankhorst, BiZZdesign Iver Band, Cambia Health Solutions INTRODUCTIONS 2 1 Marc Lankhorst
More informationContext Capture in Software Development
Context Capture in Software Development Bruno Antunes, Francisco Correia and Paulo Gomes Knowledge and Intelligent Systems Laboratory Cognitive and Media Systems Group Centre for Informatics and Systems
More informationEnterprise Architecture Assessment Guide
Enterprise Architecture Assessment Guide Editorial Writer: J. Schekkerman Version 2.2 2006 Preface An enterprise architecture (EA) establishes the organization-wide roadmap to achieve an organization s
More informationRequirements Engineering: Elicitation Techniques
2008:PR003 Requirements Engineering: Elicitation Techniques Sai Ganesh. Gunda Source:http://www.marcocioffi.com/archives/2005/04/requirements-engineering/ MASTER S THESIS Software Engineering, 2008 Department
More informationCybersecurity Framework. Executive Order 13636 Improving Critical Infrastructure Cybersecurity
Cybersecurity Framework Executive Order 13636 Improving Critical Infrastructure Cybersecurity National Institute of Standards and Technology (NIST) Mission To promote U.S. innovation and industrial competitiveness
More informationIndustry. Head of Research Service Desk Institute
Asset Management in the ITSM Industry Prepared by Daniel Wood Head of Research Service Desk Institute Sponsored by Declaration We believe the information in this document to be accurate, relevant and truthful
More informationNIST Cloud Computing Program Activities
NIST Cloud Computing Program Overview The NIST Cloud Computing Program includes Strategic and Tactical efforts which were initiated in parallel, and are integrated as shown below: NIST Cloud Computing
More informationSoftware Requirements Specification. For. Get Real Website. Version 0.2. Prepared by Ken Cone. OUS Industry Affairs <7/16/07> Page i of 10
Software Requirements Specification For Get Real Website Version 0.2 Prepared by Ken Cone OUS Industry Affairs Page i of 10 Page 1 Table of Contents Table of Contents... 1 Revision History...
More informationUNIVERSITY OF MIAMI SCHOOL OF BUSINESS ADMINISTRATION MISSION, VISION & STRATEGIC PRIORITIES. Approved by SBA General Faculty (April 2012)
UNIVERSITY OF MIAMI SCHOOL OF BUSINESS ADMINISTRATION MISSION, VISION & STRATEGIC PRIORITIES Approved by SBA General Faculty (April 2012) Introduction In 1926, we embarked on a noble experiment the creation
More informationRequirements in Functional IT Management
Requirements in Functional IT Floris Blaauboer University of Twente, Department of Computer Science, Chair of Information Systems, f.a.blaauboer@student.utwente.nl Abstract. Requirements engineering and
More informationMIPRO s Business Intelligence Manifesto: Six Requirements for an Effective BI Deployment
MIPRO s Business Intelligence Manifesto: Six Requirements for an Effective BI Deployment Contents Executive Summary Requirement #1: Execute Dashboards Effectively Requirement #2: Understand the BI Maturity
More informationCSC340: Information Systems Analysis and Design. About the Course
CSC340: Information Systems Analysis and Design Professor Jennifer Campbell campbell@cs.toronto.edu http://www.cs.toronto.edu/~csc340h/ Acknowledgement: Material Provided by Professor Steve Easterbrook
More informationEmployee Engagement Survey Toolkit
Employee Engagement Survey Toolkit Acknowledgements This document and this effort is the product of collaboration among a number of departments and individuals at Organization including: Placeholders Placeholders
More informationPosition Paper for Cognition and Collaboration Workshop: Analyzing Distributed Community Practices for Design
Position Paper for Cognition and Collaboration Workshop: Analyzing Distributed Community Practices for Design Jean Scholtz, Michelle Steves, and Emile Morse National Institute of Standards and Technology
More informationIntroduction. Contents. Introducing the DSDM Agile Project Framework. Introducing DSDM
Contents Introduction... 2 Introducing the DSDM Agile Project Framework... 2 Introducing DSDM... 2 Introducing Scrum... 3 The DSDM Agile Project Framework for Scrum... 4 Philosophy... 4 Values... 4 Principles...
More informationBusiness Process Modeling with Structured Scenarios
Business Process Modeling with Structured Scenarios Doug Rosenberg ICONIX Software Engineering, Inc. In 2008, based on our experience with a number of business process engineering projects over the last
More informationVALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
VALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Sub Code : CP7007 Sub Name: SOFTWARE REQUIREMENTS ENGINEERING Branch / Year : ME CSE / I Year
More information7 Habits for Effectively Leading Healthcare Interoperability Initiatives
Available at: http://www.corepointhealth.com/whitepapers/7-habits-effectively-leading-healthcare-interoperability-initiatives 7 Habits for Effectively Leading Healthcare Interoperability Initiatives What
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationWeb Team Roles & Responsibilities. This document defines the approved Roles & Responsibilities for the Web Team and related Job Descriptions.
Web Team Roles & Responsibilities This document defines the approved Roles & Responsibilities for the Web Team and related Job Descriptions. Table of Contents Introduction 1 1.1 Roles & responsibilities
More informationPROMOTION & TENURE SYMPOSIUM
PROMOTION & TENURE SYMPOSIUM DR. NICHOLAS P. JONES A Conversation with the Provost FRIDAY, OCTOBER 16, 2015 9:45 a.m. 10:30 a.m. FOSTER AUDITORIUM, PATERNO LIBRARY 2 Good morning! Thank you for the kind
More informationHow To Design An Information System
Information system for production and mounting of plastic windows MARCEL, MELIŠ Slovak University of Technology - Faculty of Material Sciences and Technology in Trnava, Paulínska 16 street, Trnava, 917
More informationPrivacy Engineering & Assurance. The Emerging Engineering Discipline for implementing Privacy by Design
Privacy Engineering & Assurance The Emerging Engineering Discipline for implementing Privacy by Design 2014-09-08 Position Paper - 1 / 10 Nokia 2014 Contents 1 Introduction... 3 2 The Discipline... 4 3
More informationAgile Project Management By Mark C. Layton
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
More informationBUSINESS RULES AS PART OF INFORMATION SYSTEMS LIFE CYCLE: POSSIBLE SCENARIOS Kestutis Kapocius 1,2,3, Gintautas Garsva 1,2,4
International Conference 20th EURO Mini Conference Continuous Optimization and Knowledge-Based Technologies (EurOPT-2008) May 20 23, 2008, Neringa, LITHUANIA ISBN 978-9955-28-283-9 L. Sakalauskas, G.W.
More informationMulti-Dimensional Success Factors of Agile Software Development Projects
Multi-Dimensional Success Factors of Agile Software Development Projects Nagy Ramadan Darwish Department of Computers and Information Sciences Institute of Statistical Studies and Research Cairo University
More informationFamily Evaluation Framework overview & introduction
A Family Evaluation Framework overview & introduction P B Frank van der Linden O Partner: Philips Medical Systems Veenpluis 4-6 5684 PC Best, the Netherlands Date: 29 August, 2005 Number: PH-0503-01 Version:
More informationCertifying Energy Efficiency of Android Applications
Proceedings of the 28th EnviroInfo 2014 Conference, Oldenburg, Germany September 10-12, 2014 Certifying Energy Efficiency of Android Applications Johannes Meier 1, Marie-Christin Ostendorp 1, Jan Jelschen
More informationThe CS Principles Project 1
The CS Principles Project 1 Owen Astrachan, Duke University Amy Briggs, Middlebury College Abstract The Computer Science Principles project is part of a national effort to reach a wide and diverse audience
More informationUsing i for Transformational Creativity in Requirements Engineering
Using i for Transformational Creativity in Requirements Engineering Sushma Rayasam and Nan Niu Department of EECS, University of Cincinnati Cincinnati, OH, USA 45221 rayasasa@mail.uc.edu, nan.niu@uc.edu
More informationPractice Overview. REQUIREMENTS DEFINITION Issue Date: <mm/dd/yyyy> Revision Date: <mm/dd/yyyy>
DEPARTMENT OF HEALTH AND HUMAN SERVICES ENTERPRISE PERFORMANCE LIFE CYCLE FRAMEWORK PRACTIICES GUIIDE REQUIREMENTS DEFINITION Issue Date: Revision Date: Document
More informationIDOL Outcomes and Competencies (ibstpi) 2
Instructional Design for Online Learning (IDOL) Specialization Outcomes and Specialization Competencies Updated January 2008 Table of Contents Outcomes-based curricula at Capella University...3 IDOL MS
More informationNorth Dakota PROGRAM REVIEW FOR SCHOOL COUNSELING PROGRAMS
North Dakota PROGRAM REVIEW FOR SCHOOL COUNSELING PROGRAMS District: Enrollment: Evaluator: School: Grades in School: Date of Evaluation: *Adapted from the American School Counseling Association National
More informationSoftware Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Not this life cycle SE, Software Lifecycle, Hans van Vliet, 2008 2 Introduction software development
More informationDo you know? "7 Practices" for a Reliable Requirements Management. by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd.
Do you know? "7 Practices" for a Reliable Requirements Management by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd. In this white paper, we focus on the "Requirements Management,"
More informationA Comparison of SOA Methodologies Analysis & Design Phases
202 A Comparison of SOA Methodologies Analysis & Design Phases Sandra SVANIDZAITĖ Institute of Mathematics and Informatics, Vilnius University Abstract. Service oriented computing is a new software engineering
More informationInteractive Enterprise Applications for Web, Social and Mobile Media
Interactive Enterprise Applications for Web, Social and Mobile Media Working with DOOR3 - About DOOR3 - Enterprise Practice & Business Apps - Microsoft Practice - Digital Strategy - User Experience & Design
More informationSoftware Engineering Reference Framework
Software Engineering Reference Framework Michel Chaudron, Jan Friso Groote, Kees van Hee, Kees Hemerik, Lou Somers, Tom Verhoeff. Department of Mathematics and Computer Science Eindhoven University of
More informationSystems Engineering Master Project
System 1 System n by Gerrit Muller HBV-NISE e-mail: gaudisite@gmail.com www.gaudisite.nl Abstract The master study Systems Engineering is completed by performing a thesis project. This document describes
More informationIncreasing Development Knowledge with EPFC
The Eclipse Process Framework Composer Increasing Development Knowledge with EPFC Are all your developers on the same page? Are they all using the best practices and the same best practices for agile,
More informationChapter 1 Introduction
Chapter 1 Introduction Chapter 1 Introduction Slide 1 Topics covered Professional software development What is meant by software engineering. Addendum to Sommerville s FAQs Software engineering ethics
More informationGreening Our Indian Business for Sustainability
Greening Our Indian Business for Sustainability Maulik K. Rathod 1, Mayank R. Rai 2 1 (Rai University, Dholka, Ahmedabad, Gujarat India.) 2 (Anand Law College, Anand, Gujarat India.) Abstract: Modern Corporates
More informationSLDS Workshop Summary: Data Use
SLDS Workshop Summary: Data Use Developing a Data Use Strategy This publication aims to help states detail the current status of their State Longitudinal Data System (SLDS) data use strategy and identify
More informationRequirements engineering and quality attributes
Open Learning Universiteit Unit 2 Learning Unit 2 Requirements engineering and quality attributes Contents Introduction............................................... 21 2.1 Important concepts........................................
More informationTable of Contents. CHAPTER 1 Web-Based Systems 1. CHAPTER 2 Web Engineering 12. CHAPTER 3 A Web Engineering Process 24
Table of Contents CHAPTER 1 Web-Based Systems 1 The Web 1 Web Applications 2 Let s Introduce a Case Study 3 Are WebApps Really Computer Software? 4 Are the Attributes of WebApps Different from the Attributes
More informationAgile Software Engineering, a proposed extension for in-house software development
Journal of Information & Communication Technology Vol. 5, No. 2, (Fall 2011) 61-73 Agile Software Engineering, a proposed extension for in-house software development Muhammad Misbahuddin * Institute of
More informationDSDM Case Study. An Agile Approach to Software Systems Development for the Highways Agency
DSDM Case Study An Agile Approach to Software Systems Development for the Highways Agency Government agencies are constantly striving to develop software systems that support business objectives, deliver
More informationAgile Extension to the BABOK Guide
Agile Extension to the BABOK Guide Version 1.0 Complimentary IIBA Member Copy. Not for Redistribution or Resale www.iiba.org International Institute of Business Analysis, Toronto, Ontario, Canada International
More informationInvestigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations
Investigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations Mennatallah H. Ibrahim Department of Computers and Information Sciences Institute
More informationCore Competencies for Public Health Professionals
Core Competencies for Public Health Professionals Introduction This document contains three different versions of the recently adopted Core Competencies for Public Health Professionals. Click on the name
More informationRequirements Engineering Process Models in Practice
AWRE 2002 141 Engineering Process Models in Practice Sacha Martin 1, Aybüke Aurum 1, Ross Jeffery 2, Barbara Paech 3 1 School of Information Systems, Technology and Management, University of New South
More informationInformation systems supported organizational learning as a competitive advantage
Journal of Industrial Engineering and Management JIEM, 2013 6(3): 702-708 Online ISSN: 2013-0953 Print ISSN: 2013-8423 http://dx.doi.org/10.3926/jiem.555 Information systems supported organizational learning
More informationA Study on RE Process Models for Offshore Software Development
J. Basic. Appl. Sci. Res., 4(4)114-119, 2014 2014, TextRoad Publication ISSN 2090-4304 Journal of Basic and Applied Scientific Research www.textroad.com A Study on RE Process Models for Offshore Software
More informationA new European approach toward Quality Assurance in Vocational Education
A new European approach toward Quality Assurance in Vocational Education I have been a teacher myself for over 15 years now. To keep developing myself as a teacher in my profession I signed in for a Masters
More informationSyllabus. REQB Certified Professional for Requirements Engineering. Foundation Level
Syllabus REQB Certified Professional for Requirements Engineering Version 2.1 2014 The copyright to this edition of the syllabus in all languages is held by the Global Association for Software Quality,
More information(Refer Slide Time: 01:52)
Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This
More informationThe Role of Design in the Design of EMR Systems
The Role of Design in the Design of EMR Systems By: Kevin Richardson, PhD The recent Healthcare Information and Management Systems Society (HIMSS) report, Defining and Testing EMR Usability: Principles
More information