Suunto 2.0 web - Quality Assurance Plan
|
|
- Asher Gardner
- 8 years ago
- Views:
Transcription
1 Suunto 2.0 web - Quality Assurance Plan T Software Development Project: Iteration 2 Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for - P. Drucker
2 Table 1. Document changelog. Version Date Done Author First draft Häppölä Second draft Häppölä First release Häppölä Additional details Seppälä Updates for I1 Häppölä Post I1-updates Häppölä Updates for I2 Häppölä Reviewed and approved Häppölä, Palomäki, Seppälä
3 Table of Contents 1 Introduction Details concerning the project Quality Assurance Framework and Goals Quality goals Testing levels Quality Assurance Practices Quality and testing practices Unit testing Test cases Explorative testing Coding standards Side-by-side programming Code reviews and change of ideas Heuristics Documentation General Project management Dialogue with the customer Summary of testing practices Testing Environments and Software Stress testing and scalability Summary of QA activities Deliverables and QA Feedback Quality assurance documentation Quality of QA material Test cases and defect tracking Quality feedback...9
4 1 Introduction This document describes quality assurance strategies and practices of Suunto 2.0 Web project. The document is part of the requirements of T Software Development Project course of Helsinki University of Technology. The proposed audience of this document is listed in table 2. First part of this document describes the goals of overall quality process and conceptual framework of this project, second chapter quality practices and their connection to quality goals at different levels of software design. Thirdly, this plan discusses on planned effects and resulting documentation of the quality assurance. This document will be updated during the project as needed. Table 2. Audience of the document. Audience Customer Mentor Team Neula Tester Purpose of the document Describe the planned Quality Assurance practices and frameworks to give an overview of quality management and planned testing methods of the whole project. Communicate the scope and context of the QA and respective practices. Work as a guideline for planned practices and their effect on software development and testing as well as project management. Guide through testing and give information of most important testing goals and practices. 1.1 Details concerning the project The Suunto 2.0 web project consists of several autonomous and functionally separate small applications that are built for different social platforms with different programming languages. Some work server side, most on the user s computer. The only actual interconnecting link between all applications is the MySuunto database that provides the user s training data that is then visualized by the application. Applications will conceptually work as a middleware between their platform and MySuunto database, delivering aggregated simple information through attractive, convenient and light user interfaces, gadgets. This detachment and multiplicity informs quality assurance as well as general software development but is discussed in more detail in the separate architectural technical specification document, requirements document and general project plan. Noteworthy, however is that individual applications can be de facto delivered at different times at they are developed simultaneously. We are multitasking development and design: There are constantly two applications under development and new prototypes designed at the end of every sprint. For additional information, reader should refer the project plan. Also Iteration 1 QA report describes emergent quality practices and overall framework used in course of the project. 1
5 2 Quality Assurance Framework and Goals 2.1 Quality goals Quality goals of the project are derived primarily from non-functional requirements and are mostly qualitative by nature (Table 3). Table 3. Quality goals ID Quality goal Description Verification QG 1 Compatibility Applications developed in this project must be seamlessly compatible with the platform they are developed for and Suunto DB. Will be ensured by extensive testing and following platform development instructions. Meanwhile, the customer s DB deployment is delayed so this integration may not be feasible at all during the project. QG 2 Layout Especially commercial marketing attractiveness and visual compliance with the Suunto brand guidelines. Approval and dialogue with the customer s design team and possibly also testing with external reference groups (like peer group) with this perspective in mind. QG 3 Usability Must be simple for the user to use and add to his/her platform. Applications should work with virtually no technical knowhow. Lightweight appearance and intuitive user interface. Feedback from customers and reference groups. QG 4 Localization Several different languages must be supported. Aspect will be brought along through the whole design and development process. QG 5 Innovativeness Innovative approaches to gadget design. Large role in design has been given to the team. Process is iterative and requirements refined with ongoing development. Brainstorming sessions. Evolutionary and iterative idea development and updating of requirements throughout the project by using feedback from the customer. 2
6 QG 6 Exploration Gadgets must provide the customer with new technological insight into emerging social technologies and platforms. QG 7 Variety In total 2 commercial quality, 2 working quality, 1 prototype applications and 10 descriptions will be delivered to the customer by the end. Documentation of learning and continuous bilateral idea exchange. Emphasis on project planning and time tracking. 2.2 Testing levels There are four testing levels according to the V-model of software development. Figure 1 shows their respective links to different design levels and phases of the software development process. In our project, however, there is practically no integration testing level since the modules are autonomous applications and due to their small size usually do not consist of reasonable smaller submodules. Also the implementation of the customer s database is delayed, so it may not be available for testing at all during the project. Figure 1. V-model of software development [Wikimedia Commons] 3
7 3 Quality Assurance Practices Quality strategies and their implementation are updated during the Iteration when needed and the quality practice adaptation could be described as a trial-and-error learning process after the Deming wheel (Figure 1). Act Plan Check Do Figure 2 The Deming PDCA-cycle Taken that project consists of several totally autonomous applications, many originally planned high level quality practices can t be really used for value-adding purposes in reality as became apparent during the Iteration 1. Several approaches were done as an exercise and their actual realized practicability and usability for the project were evaluated at the end of iteration. Please refer to QA report for details. The development process of individual application with respective quality goals and levels are described in the framework of Figure 2. Reader should note that only fraction of finally delivered applications are required to reach the commercial quality. Customer Feedback Requirements Cycle Prototype Description (Level 0) Prototype (Level 1) Working Quality (Level 2) Commercial Quality (Level 3) Delivery Main Focus Innovating Platform Learning Coding Testing & UI finalizing Figure 3 Application development process and three levels of quality. 4
8 As we re developing several applications simultaneously and waiting comments from the customer, the status of development and required quality was divided into four levels (Table 2). Table 4 Levels of quality Level of quality Prototype Description Prototype Working Quality Commercial Quality Description Written document and visual presentation of the gadget idea. Includes also a small user story. No actual technical implementation yet. First working visual representation and technical implementation of the idea under the platform after exploration of its technical specifications, possibilities and limitations. Application that has the most important functions described in the description implemented and usable (but not yet finalized) user interface. Some minor additional features requested by the customer. Also finished user interface after customer s wishes and comments from the design team. Thoroughly tested according to the test cases. 3.1 Quality and testing practices Unit testing Unit testing is the lowest level of white box testing and the primary element in the quality assurance chain. The developer is responsible for writing unit tests. Regular runs and automatic unit testing make sure that the code base doesn t break. Unit testing will be performed throughout the project where possible. Different platforms and programming languages give certain limitations to the tools available. Given that the applications are small and they are run through web platforms, unit testing is mainly limited to database interfaces and will be done mostly as an academic exercise Test cases Test cases will be written in compliance with functional requirements and most important requirements. These are based on our prototype definitions, their user stories 1 and customer feedback received during the development process. Functional testing will be mostly done at the end, prior delivery due to customer s focusing wishes: altering requirements, altering level of quality and changes in the actual development process. Reader should refer to the user requirements document and QA report for deeper reasoning. 1 This creative and iterative requirement design process is presented in the project plan and requirements document in more detail. 5
9 3.1.3 Explorative testing After each sprint the customer will be given a prototype to test. Application can be later enhanced and requirements altered to meet new emergent ideas. Also our team and peer group will be given opportunity to play around with the applications to find potential caveats as well as potential enhancement ideas (given the NDA restrictions). Explorative testing also gets important role before delivering prototypes for customer. Charters and logs will be written Coding standards Coding standards are described in the project plan. They, however, needed some reviewing to better meet project needs Side-by-side programming As a main practice, we will be having two developers working on one application. Therefore side-by-side programming is a definition. We have weekly coding sessions in which nearly all team members are present. Strong emphasis is on continuous communication and mutual sanity checking of the code Code reviews and change of ideas Code reviews will be arranged at the end of each sprint at least. This also serves the purpose of mutual learning of different technologies as we have two teams working on two different applications Heuristics More abstract goals regarding usability and visual layout are to be measured by constant feedback from the customer and using external reference groups (e.g. the peer group) for testing and new ideas Documentation Documentation includes both internal documentation as well as research documentation concerning findings, opportunities and technical issues of new platforms and technologies. The latter will be passed on to the customer as well General Project management As the project consists of 18 separate applications and functional requirements can be heavily altered during iterations, emphasis must be all times on overall project management, tracking and - above all - big picture. As been discovered during the first iteration, platform learning takes more time than was expected. Also the customer s needs for variety and level of quality might change during the project Dialogue with the customer Constant dialogue with the customer is a must due to the iterative application design and building process. New prototypes will be sketched as first applications reach the prototype phase. Thus customer feedback is of enormous importance. Please refer to the user requirements document. 3.2 Summary of testing practices Planned testing practices at each testing level with planned tools are summarized in the Table 4. 6
10 Table 5. Testing levels, planned practices and tools Testing level Practices Tools Unit level Unit level testing will be performed where applicable. JUnit, PHPUnit, GWT Integration testing System testing Compatibility with the platforms and Suunto database will be tested with test cases and explorative testing. Database connection will hopefully be available by the end of the project. Explorative testing Meetings at the end of sprints and constant feedback from the customer Bugzilla Bugzilla, Testopia Code reviews at the end of sprints and constant side-by-side programming. Acceptance testing Compatibility with functional requirements will be ensured by test cases and explorative acceptance session with the customer. Bugzilla, Testopia 3.3 Testing Environments and Software In addition to tools described in the Table 5, testing will be done mainly in real environments except for Facebook applications which will be tested non-publicly in the developer area. The Facebook server application will run on a rented Debian Linux virtual server. Thus, after our delivery it still needs further development and larger scale server architecture considerations if going to be released into production as it s going to be delivered mainly as a proof-of-concept artifact. The defect tracking system used in this project is Bugzilla. It has been enhanced with Testopia test case management suite that integrates into Bugzilla s tracking system seamlessly and runs inside it. Some additional QA tools, like CruiseControl, were set up for exercise, but their fit in this project is debatable and were abandoned at the beginning of the second iteration. 3.4 Stress testing and scalability Apart from Facebook, applications run on the client side and restricting elements are thus the user s computer and Suunto database. The prior shouldn t be an issue since the main target is to make applications as lightweight as possible and individual computer performance doesn t affect the system as a whole. The latter element is out of scope of this project. 7
11 Facebook application may need some focus on scalability in communities with several users. However, the optimization possibilities under this project are very limited since the Facebook application won t likely be commercialized as such. The final public version would need a further consideration of the customer s own future large scale server architecture as currently it will be built to a custom rented server running only that application. 3.5 Summary of QA activities QA practices and according goals are visualized in the quality palette of Table 6. Table 6. Quality palette Quality Goal vs. Quality Practice (effect 1-3) Unit testing QG 1 Compatibility X QG 2 Layout QG 3 Usability QG 4 Localization Test cases X X X Explorative testing X X X X QG5 Innovativeness Coding standards X Side-by-side X X X X programming Code reviews X X Heuristics X X Documentation X X X General project management Dialogue with the customer QG 6 Exploration X X X X X X X QG 7 Variety 4 Deliverables and QA Feedback 4.1 Quality assurance documentation Quality assurance plan will be updated as needed to clarify details and better match empirically found best practices. Other quality documentation will be delivered given the course framework and as described in the project plan schedule. 4.2 Quality of QA material One of the issues to track is the quality, repeatability and consistency of bug reports and other quality related material. 8
12 4.3 Test cases and defect tracking Our defect tracking system Bugzilla has been enhanced with Testopia test case management suite which manages test plans, test cases, test runs and gives extensive reports with different views. This gives us an opportunity to conveniently avoid hassle of sharing Excel sheets with test cases and matrices. We can get the big picture of overall project even with 5 separate applications in development by consolidating these as separate products under this environment. Test case management tool can be also seen as an exercise for larger development projects. 4.4 Quality feedback The primary source of quality feedback and awareness is the feedback from the customer at the end of every sprint. This gives us an opportunity to correct our steering, development and quality practices if needed. Also it s the responsibility of Quality Manager to follow the status of quality of the entire project as whole. We also try to keep quality praxis as transparent as possible to make it easily communicable to customer as well. 9
Custom Software Development Approach
Custom Software Development Approach Our approach to custom software development combines benefits from several standard development process models. We tend to have a well-defined, predictable and highly
More informationQuality Assurance Plan
CloudSizzle : Quality Assurance Plan Quality Assurance Plan General info Changelog 1. Introduction 2. Quality goals and risks 3. Quality Assurance practices 3.1 Testing levels 3.2 Testing - 3.2.1 Test
More informationeorgette ullivan Portfolio
Portfolio Experience Designer: Design Research, Interaction and Visual Design georgettes.com georgette@georgettes.com 512-362-8078 Innovating Enterprise IT Management Software Description Create a reference
More informationE-vote 2011 Version: 1.0 Testing and Approval Date: 26/10/2009. E-vote 2011. SSA-U Appendix 5 Testing and Approval Project: E-vote 2011
E-vote 2011 SSA-U Appendix 5 Testing and Approval Project: E-vote 2011 Change log Version Date Author Description/changes 0.1 26.10.09 First version Page 1 CONTENT 1. INTRODUCTION 3 2. TESTING PROCESS
More informationTime Monitoring Tool Software Development Plan. Version <1.1>
Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page
More informationISTQB Certified Tester. Foundation Level. Sample Exam 1
ISTQB Certified Tester Foundation Level Version 2015 American Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged. #1 When test cases are designed
More informationHP Agile Manager What we do
HP Agile Manager What we do Release planning Sprint planning Sprint execution Visibility and insight Structure release Define teams Define release scope Manage team capacity Define team backlog Manage
More informationNova Software Quality Assurance Process
Nova Software Quality Assurance Process White Paper Atlantic International Building 15F No.2 Ke Yuan Yi Road, Shiqiaopu, Chongqing, P.R.C. 400039 Tel: 86-23- 68795169 Fax: 86-23- 68795169 Quality Assurance
More informationMANUAL TESTING. (Complete Package) We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info
MANUAL TESTING (Complete Package) WEB APP TESTING DB TESTING MOBILE APP TESTING We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info START DATE : TIMINGS : DURATION :
More informationAnnouncements. Project status demo in class
Web Design cs465 Announcements Project status demo in class Why? You will likely be involved in Web design You have many of the skills necessary Understand similarities and differences between GUI design
More informationDevelopment Methodologies Compared
N CYCLES software solutions Development Methodologies Compared Why different projects require different development methodologies. December 2002 Dan Marks 65 Germantown Court 1616 West Gate Circle Suite
More informationRelative cost of fixing bugs
Code Review Tool Introduction Code review is a systematic examination of source code with an intention to find and fix bugs. Code reviews are primarily done during development phase to improve the quality
More informationHow we work. Digital Natives working methods
How we work Digital Natives working methods 22 October 2014 (C) Copyright 2014 Digital Natives LTD All rights reserved. 1 How we work Digital Natives (DiNa) s business goal is to take part in and support
More informationTest Driven Development Part III: Continuous Integration Venkat Subramaniam venkats@agiledeveloper.com http://www.agiledeveloper.com/download.
Test Driven Development Part III: Continuous Integration Venkat Subramaniam venkats@agiledeveloper.com http://www.agiledeveloper.com/download.aspx Abstract In this final part of the three part series on
More informationAUTOMATED TESTING and SPI. Brian Lynch
AUTOMATED TESTING and SPI Brian Lynch 1 Introduction The following document explains the purpose and benefits for having an Automation Test Team, the strategy/approach taken by an Automation Test Team
More informationAGILE SOFTWARE TESTING
AGILE SOFTWARE TESTING Business environments continue to rapidly evolve, leaving many IT organizations struggling to keep up. This need for speed has led to an increased interest in the Agile software
More informationBuilding Software in an Agile Manner
Building Software in an Agile Manner Abstract The technology industry continues to evolve with new products and category innovations defining and then redefining this sector's shifting landscape. Over
More informationWebsite design & development process
Website design & development process Key stages of the process 9 1 Support, development and maintenance Competitor and audience analysis 8 Training IMPROVE THINK Wireframe and prototype (UX) 2 7 User testing
More informationRe: RFP # 08-X-39202 MOTOR VEHICLE AUTOMATED TRANSACTION SYSTEM (MATRX) FOR MVC ADDENDUM #10
State of New Jersey DEPARTMENT OF THE TREASURY JON S. CORZINE DIVISION OF PURCHASE AND PROPERTY BRADLEY I. ABELOW Governor PURCHASE BUREAU State Treasurer P.O. BOX 230 TRENTON, NEW JERSEY 08625-0230 September
More informationDigital Marketplace Services Service Definition
Digital Marketplace Services Service Definition Arrk Limited Manchester Science Park Pencroft Way Manchester M15 6JJ Tel: +44 161 227 9900 Fax: +44 016 227 9966 www.arrkgroup.com Registered In England
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 informationWhat is a life cycle model?
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
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 informationGroup18-CUCE2012. Mr. Mobile Project. Software Testing Plan (STP) Version: 4.0. CM Identifier: G18_SE004
Group18-CUCE2012 Mr. Mobile Project Software Testing Plan (STP) Version: 4.0 CM Identifier: G18_SE004 26 April 2010 Revision History Prepared/ Modified by Ahmed Adel Ahmed Abdullah, Ahmed Hafez and Sheriff
More informationTWX-21 Business System Cloud for Global Corporations
TWX-21 Business System Cloud for Global Corporations 8 TWX-21 Business System Cloud for Global Corporations Hidenori Kiuchi Yasuyuki Suzuki Sho Obayashi Manabu Naganuma Seiichiro Hayashi Taku Tozawa OVERVIEW:
More informationAgile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
More informationUsing Use Cases on Agile Projects
Using Use Cases on Agile Projects Ivar Jacobson with Ian Spence Agenda What are agile teams looking for? Cards, conversations, and confirmations Knowing what to do and when it s done Being agile with use
More informationThe Quality Assurance Centre of Excellence
The Quality Assurance Centre of Excellence A X I S T E C H N I C A L G R O U P A N A H E I M H E A D Q U A R T E R S, 300 S. H A R B O R, B L V D. S U I T E 904, A N A H E I M, CA 92805 PHONE :( 714) 491-2636
More informationXtreme RUP. Ne t BJECTIVES. Lightening Up the Rational Unified Process. 2/9/2001 Copyright 2001 Net Objectives 1. Agenda
Xtreme RUP by Ne t BJECTIVES Lightening Up the Rational Unified Process 2/9/2001 Copyright 2001 Net Objectives 1 RUP Overview Agenda Typical RUP Challenges Xtreme Programming Paradigm Document driven or
More informationHow Silk Central brings flexibility to agile development
How Silk Central brings flexibility to agile development The name agile development is perhaps slightly misleading as it is by its very nature, a carefully structured environment of rigorous procedures.
More informationSmarter Balanced Assessment Consortium. Recommendation
Smarter Balanced Assessment Consortium Recommendation Smarter Balanced Quality Assurance Approach Recommendation for the Smarter Balanced Assessment Consortium 20 July 2012 Summary When this document was
More informationEducational Collaborative Develops Big Data Solution with MongoDB
CASE STUDY OVERVIEW Educational Collaborative Develops Big Data Solution with MongoDB INDUSTRIES Education, Nonprofit LOCATION Durham, NC PROJECT LENGTH 1 year, 5 months APPLICATION SUPPORTED Data driven
More informationCopyrighted www.eh1infotech.com +919780265007, 0172-5098107 Address :- EH1-Infotech, SCF 69, Top Floor, Phase 3B-2, Sector 60, Mohali (Chandigarh),
Content of 6 Months Software Testing Training at EH1-Infotech Module 1: Introduction to Software Testing Basics of S/W testing Module 2: SQA Basics Testing introduction and terminology Verification and
More informationTest Automation: A Project Management Perspective
Test Automation: A Project Management Perspective Abstract Amith Pulla amith.pulla@intel.com For most QA leads or managers, it s always difficult to get the project manager (PM) to invest in test automation.
More informationSoftware Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
More informationOutline. Introduction. WebQuilt and Mobile Devices: A Web Usability Testing and Analysis Tool for the Mobile Internet
WebQuilt and Mobile Devices: A Web Usability Testing and Analysis Tool for the Mobile Internet Tara Matthews Seattle University April 5, 001 Outline 1. Introduction. Motivation. Usability Testing and WebQuilt
More information7 KEYS TO DELIVER BETTER APPS FASTER
7 KEYS TO DELIVER BETTER APPS FASTER Through Effective IT/Business Collaboration There s a rift between IT & Business Poor IT-business collaboration is a key reason for misalignment 50% According to the
More informationImplementing Continuous Integration Testing Prepared by:
Implementing Continuous Integration Testing Prepared by: Mr Sandeep M Table of Contents 1. ABSTRACT... 2 2. INTRODUCTION TO CONTINUOUS INTEGRATION (CI)... 3 3. CI FOR AGILE METHODOLOGY... 4 4. WORK FLOW...
More informationWHITE PAPER. The 7 Deadly Sins of. Dashboard Design
WHITE PAPER The 7 Deadly Sins of Dashboard Design Overview In the new world of business intelligence (BI), the front end of an executive management platform, or dashboard, is one of several critical elements
More informationTerrace Consulting Services
Terrace Consulting Services Overview: Every project will require some degree of Planning before Implementation can begin. Analysis and Planning are essential in order to confirm requirements, define the
More informationExploratory Testing Dynamics
Exploratory Testing Dynamics Created by James and Jonathan Bach 1 v1.6 Copyright 2005-2006, Satisfice, Inc. Exploratory testing is the opposite of scripted testing. Both scripted and exploratory testing
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 informationLevels of Software Testing. Functional Testing
Levels of Software Testing There are different levels during the process of Testing. In this chapter a brief description is provided about these levels. Levels of testing include the different methodologies
More information2003 Patricia Ensworth Page 1
1 1 Sample software development project 2 1.1 Start project 3 1.2 Initiation phase 4 1.2.1 Develop project charter 5 1.2.2 Project charter approved 6 1.3 Planning phase 7 1.3.1 Product activities 8 1.3.1.1
More informationLean Software Development
Lean Software Development Alexandre Boutin Responsable Stratégie International Développement Logiciel chez Yahoo Scrum Master & Practitioner Certifié Coach Agile Blog : www.agilex.fr Président du Club
More informationAgile Software Development
Agile Software Development Use case for Agile Software Development Methodology in an Oil and Gas Exploration environment. White Paper Introduction No matter what business you are in, there are critical
More informationThe Design and Improvement of a Software Project Management System Based on CMMI
Intelligent Information Management, 2012, 4, 330-337 http://dx.doi.org/10.4236/iim.2012.46037 Published Online November 2012 (http://www.scirp.org/journal/iim) The Design and Improvement of a Software
More information2. Analysis, Design and Implementation
2. Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Individual Programs to Complete Application Systems Software Development: Goals, Tasks, Actors,
More informationProject Lifecycle Management (PLM)
Project Lifecycle Management (PLM) Process or Tool? Why PLM? Project Definition Project Management NEW REQUEST/ INITIATIVES SUPPORT (Quick fixes) PROJECT (Start Finish) ONGOING WORK (Continuous) ENHANCEMENTS
More informationA Software Engineering Model for Mobile App Development
APPENDIX C A Software Engineering Model for Mobile App Development As we mentioned early in the book (see Chapter 1), to successfully develop a mobile software solution you should follow an engineering
More informationHow To Write An Slcm Project Plan
SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) Project Development Phases Pension Benefit Guaranty Corporation s (PBGC) System Life Cycle Methodology (SLCM) is comprised of five project development
More informationA Practical Guide to implementing Agile QA process on Scrum Projects
Agile QA A Practical Guide to implementing Agile QA process on Scrum Projects Syed Rayhan Co-founder, Code71, Inc. Contact: srayhan@code71.com Blog: http://blog.syedrayhan.com Company: http://www.code71.com
More informationTeaching an Elephant to Dance. Patterns and Practices for Scaling Agility
Teaching an Elephant to Dance Patterns and Practices for Scaling Agility Steve Povilaitis Enterprise Agile Coach LeadingAgile steve@leadingagile.com http://www.linkedin.com/in/stevepov/ Twitter: @stevepov
More informationSoftware Process Models. Xin Feng
Software Process Models Xin Feng Questions to Answer in Software Engineering? Questions to answer in software engineering What is the problem to be solved? Definition What are the characteristics of the
More informationRFP Attachment C Classifications
RFP 1. Applications IT Architect Analyzes and designs the architecture for software applications and enhancements, including the appropriate application of frameworks and design patterns and the interrelationships
More informationEngineering Process Software Qualities Software Architectural Design
Engineering Process We need to understand the steps that take us from an idea to a product. What do we do? In what order do we do it? How do we know when we re finished each step? Production process Typical
More informationLEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) Project Status Report Week Ending: 09-19-2012 Page - 1 Executive Summary The Executive Summary provides an executive level review of general project activities,
More informationKeywords document, agile documentation, documentation, Techno functional expert, Team Collaboration, document selection;
Volume 4, Issue 4, April 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com A Document Driven
More information2. Analysis, Design and Implementation
2. Analysis, Design and Implementation Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Programs to Application Systems Products Software Development:
More informationPROJECT AUDIT METHODOLOGY
PROJECT AUDIT METHODOLOGY 1 "Your career as a project manager begins here!" Content Introduction... 3 1. Definition of the project audit... 3 2. Objectives of the project audit... 3 3. Benefit of the audit
More informationSoftware Engineering. Christopher Simpkins chris.simpkins@gatech.edu. Chris Simpkins (Georgia Tech) CS 2340 Objects and Design CS 1331 1 / 16
Software Engineering Christopher Simpkins chris.simpkins@gatech.edu Chris Simpkins (Georgia Tech) CS 2340 Objects and Design CS 1331 1 / 16 Software Engineering Definition 3.2760 from ISO/IEC/IEEE 24765:2010(E)
More informationA DIGITAL SOLUTIONS AGENCY. 2212 Queen Anne Ave N. Ste. 337 Seattle WA, 98109 206.280.3422 info@peelinteractive.com www.peelinteractive.
A DIGITAL SOLUTIONS AGENCY We are an Enteractive Agency! We are a full service digital production agency located in Seattle Washington. We specialize in developing digital marketing for the entertainment
More informationExploratory Testing Dynamics
Exploratory Testing Dynamics Created by James Bach, Jonathan Bach, and Michael Bolton 1 v2.2 Copyright 2005-2009, Satisfice, Inc. Exploratory testing is the opposite of scripted testing. Both scripted
More informationThe IconProcess: A Web Development Process Based on RUP
The IconProcess: A Web Development Process Based on RUP Katherine Marshak IconMedialab, Director of Process Development Katherine.Marshak@IconMedialab.com Agenda» The legacy of web development processes
More informationApplying Agile Methods in Rapidly Changing Environments
Applying Agile Methods in Changing Environments 7/23/2002 1 Applying Agile Methods in Rapidly Changing Environments Peter Kutschera IBM Unternehmensberatung GmbH Am Fichtenberg 1, D-71803 Herrenberg Steffen
More informationUI Designer JOB SPECIFICATION. Get in touch hello@foundation-sp.com
UI Designer JOB SPECIFICATION Get in touch hello@foundation-sp.com Role Overview The UI Designer will be able to take functional and branding requirements and turning it into an amazing user experience.
More informationBest Practices, Process
Best Practices, Process Nathaniel Osgood MIT 15.879 May 16, 2012 Recall: Process Suggestions Use discovery of bugs & oversights to find opportunities to improve Q & A and broader modeling process Use peer
More informationApplying Lean on Agile Scrum Development Methodology
ISSN:2320-0790 Applying Lean on Agile Scrum Development Methodology SurendRaj Dharmapal, Dr. K. Thirunadana Sikamani Department of Computer Science, St. Peter University St. Peter s College of Engineering
More informationMicrosoft Modern ALM. Gilad Levy Baruch Frei
Microsoft Modern ALM Gilad Levy Baruch Frei Every app Every developer Any platform Achieve more Team agility The Open Cloud Open, broad, and flexible cloud across the stack Web App Gallery Dozens of.net
More informationBUSINESS RULES AND GAP ANALYSIS
Leading the Evolution WHITE PAPER BUSINESS RULES AND GAP ANALYSIS Discovery and management of business rules avoids business disruptions WHITE PAPER BUSINESS RULES AND GAP ANALYSIS Business Situation More
More informationDriving Quality Improvement and Reducing Technical Debt with the Definition of Done
Driving Quality Improvement and Reducing Technical Debt with the Definition of Done Noopur Davis Principal, Davis Systems Pittsburgh, PA NDavis@DavisSys.com Abstract This paper describes our experiences
More informationICAgile Learning Roadmap Agile Testing Track
International Consortium for Agile ICAgile Learning Roadmap Agile Testing Track Learning Objectives Licensing Information The work in this document was facilitated by the International Consortium for Agile
More informationWhitepaper. Agile Methodology: An Airline Business Case YOUR SUCCESS IS OUR FOCUS. Published on: Jun-09 Author: Ramesh & Lakshmi Narasimhan
YOUR SUCCESS IS OUR FOCUS Whitepaper Published on: Jun-09 Author: Ramesh & Lakshmi Narasimhan 2009 Hexaware Technologies. All rights reserved. Table of Contents 1. Introduction 2. Subject Clarity 3. Agile
More informationTowards Collaborative Requirements Engineering Tool for ERP product customization
Towards Collaborative Requirements Engineering Tool for ERP product customization Boban Celebic, Ruth Breu, Michael Felderer, Florian Häser Institute of Computer Science, University of Innsbruck 6020 Innsbruck,
More informationThe Role of the Software Architect
IBM Software Group The Role of the Software Architect Peter Eeles peter.eeles@uk.ibm.com 2004 IBM Corporation Agenda Architecture Architect Architecting Requirements Analysis and design Implementation
More informationThe Definitive Guide to Data Blending. White Paper
The Definitive Guide to Data Blending White Paper Leveraging Alteryx Analytics for data blending you can: Gather and blend data from virtually any data source including local, third-party, and cloud/ social
More informationBest-Practice Software Engineering: Software Processes to Support Project Success. Dietmar Winkler
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
More informationD25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
More informationMobile App Proposal 0-000-000-000. - Magazine company- email@address.com. January 12, y. Direct Contact. Email
Mobile App Proposal - Magazine company- January 12, y Direct Contact 0-000-000-000 Email email@address.com TABLE OF CONTENTS 1. Introduction 2. Project Overview & Objectives 3. About Newsboard 4. Analytics
More informationPRACTICE GUIDE FOR AGILE SOFTWARE DEVELOPMENT [G62]
PRACTICE GUIDE FOR AGILE SOFTWARE DEVELOPMENT [G62] Version: 1.0 March 2015 The Government of the Hong Kong Special Administrative Region The contents of this document remain the property of the Office
More information7/24/2015. Blackstone Drupal Team
7/24/2015 Drupal to Agile Drupal Blackstone Drupal Team 1 Agenda What We Will Present Today 1:00 PM 1:15 PM Introduction Why Apply Agile to Drupal Development Sprint 0 Model Sprint Cadence Definition of
More informationSoftware Requirements Specification
Software Requirements Specification Project Name: DocPlus Project Members: Dorothy Mtaty Justin Esau Abstract: This Software Requirements Specification (SRS) describes the system requirements, and system
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationControlling Change on Agile Software Development Projects
Universal Journal of Management 4(1): 42-49, 2016 DOI: 10.13189/ujm.2016.040106 http://www.hrpub.org Controlling Change on Agile Software Development Projects Andrew L Ecuyer 1, Syed Adeel Ahmed 2,* 1
More informationSoftware Quality Assurance Plan
For Database Applications Document ID: Version: 2.1a Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 54 Copyright 2000-2006 Digital Publications LLC.
More informationA Tailored Approach to Effective and Efficient Software Process Maturity Improvement
A Tailored Approach to Effective and Efficient Software Process Maturity Improvement Richard Léveillé Synopsys Inc. Mountain View, California, USA Richard.Leveille@synopsys.com Abstract A well defined
More informationSolr Cloud vs Replication
Solr Cloud vs Replication vs Solr Cloud implementation Single point of failure Single point of failure Data Sources 4 x Solr Servers (Windows) 3 x Zookeeper Servers (Linux) Load Balancer Server (Mule -
More informationChange Management Best Practices
General Change Management Best Practices Practice Area Best Practice Criteria Organization Change management policy, procedures, and standards are integrated with and communicated to IT and business management
More informationEssentials of the Quality Assurance Practice Principles of Testing Test Documentation Techniques. Target Audience: Prerequisites:
Curriculum Certified Software Tester (CST) Common Body of Knowledge Control Procedures Problem Resolution Reports Requirements Test Builds Test Cases Test Execution Test Plans Test Planning Testing Concepts
More informationSuccessful Strategies for Custom Software Development
A MYTEK Whitepaper Successful Strategies for Custom Software Development ADDRESS 2225 W. Whispering Wind Drive #100 Phoenix, AZ 85085 CUSTOMER SERVICE Tel. 1.877.236.8583 FIND US HERE: www.mytek.net Custom
More informationFive questions to ask your data integration provider
Five questions to ask your data integration provider You ve taken the steps to prepare for your data integration project, you have identified the vital metrics that will drive the process, and armed with
More informationIssue in Focus: Consolidating Design Software. Extending Value Beyond 3D CAD Consolidation
Issue in Focus: Consolidating Design Software Extending Value Beyond 3D CAD Consolidation Tech-Clarity, Inc. 2012 Table of Contents Introducing the Issue... 3 Consolidate Upstream from Detailed Design...
More informationHow To Improve User Interface Design In An Ema System
Human-Centered Design in Medical Fields V Noriyoshi Ando V Naoki Nakano V Natsuko Tohyama (Manuscript received November 7, 2008) This paper introduces Fujitsu s human-centered design approaches to reduce
More informationBridging the Gap Between Acceptance Criteria and Definition of Done
Bridging the Gap Between Acceptance Criteria and Definition of Done Sowmya Purushotham, Amith Pulla sowmya.sudha@gmail.com, amith.pulla@intel.com Abstract With the onset of Scrum and as many organizations
More informationBAILEY LAUERMAN AD AGENCY RELIES ON KEY SURVEY
BAILEY LAUERMAN AD AGENCY RELIES ON KEY SURVEY TO DELIVER RAPID SOLUTIONS TO ITS CLIENTS AND ADD SUPERIOR VALUE TO ITS SERVICES ONE OF THE TOP ADVERTISING AGENCIES IN THE USA Bailey Lauerman is a full
More informationCHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology
CHAPTER 3 : AGILE METHODOLOGIES 3.1Introductions 3.2 Main Stages in Agile project 3.3 Various Agile Software development methodologies 3.4 Advantage and Disadvantage of Agile Methodology 3.1Introductions
More informationTop 10 Skills and Knowledge Set Every User Experience (UX) Professional Needs
Top 10 Skills and Knowledge Set Every User Experience (UX) Professional Needs The user experience (UX) of your products is only as good as the knowledge and skills of your UX staff. Here are the top 10
More informationAgile Metrics. It s Not All That Complicated
Agile Metrics It s Not All That Complicated Welcome About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach Certified Scrum Master Certified Scrum Product Owner Led teams/org s to
More informationANATOMY OF A WEBSITE PROJECT Jasper Ditton, Head of Digital 21.03.14
ANATOMY OF A WEBSITE PROJECT Jasper Ditton, Head of Digital 21.03.14 INTRODUCTION The 7Ps is a British Army adage for: Proper Planning and Preparation Prevents P*** Poor Performance. This statement can
More information