1 Page 1 SECTION 2 PROGRAMMING & DEVELOPMENT DEVELOPMENT METHODOLOGY THE WATERFALL APPROACH The Waterfall model of software development is a top-down, sequential approach to the design, development, testing and deployment of commercial-grade technology solutions. The phases of the waterfall approach correspond to the phases of the software development lifecycle ( SDLC ) which include Requirements Definition, Enhancement Analysis and Corrective Analysis (collectively referred to as Scoping ), Architectural Design, Programming and Development, Validation and Testing, Compilation and, finally, Deployment. Each of these phases is defined below. REQUIREMENTS DEFINITION This phase of the SDLC is a big picture exercise that establishes the point, purpose and goals for the next product release. Questions that need to be answered during the requirements definition phase include but are not limited to: Is this upcoming release primarily a bug fix release where we fine-tune existing system features and possibly introduce a few new capabilities or is Copyright Bellateq, Ltd All Rights Reserved
2 Page 2 it a major functional release where we upgrade the user interface, introduce entirely new measures of functionality and seek to redefine the overall user experience while also addressing key algorithm errors and defects? Is this upcoming release targeted at our current customers with the goal of realizing deeper vertical market penetration or is it designed to enable the enterprise to attract customers in new markets thereby driving horizontal market expansion? Is this release expected to define (or further define) the enterprise as a thought leader or fast follower or is it expected to enable us to catch up to the competition and current functional standards and market expectations? What do our users expect this next release to do for them? What promises have we made and expectations have we set, as an organization, regarding this next product release? ENHANCEMENT ANALYSIS This phase of the SDLC is focused on what needs to be done to make the product more functionally capable. As opposed to deciding which bugs and defects will be addressed, the enhancement analysis phase seeks to answer the question what will users be able to do with this next version of our software that they cannot do with our current software? Examples of software fitness issues identified during the enhancement analysis phase include, but are not limited to: New or substantially modified user interface Support for new platforms (tablets, smart phones, additional operating systems, cloud computing, wireless services, etc.) Entirely new modules that expand the definition of purpose for which the software is intended
3 Page 3 CORRECTIVE ANALYSIS This phase of the SDLC is focused on existing features that may need to be improved and upgraded, known defects that need to be corrected and customer requests for the enhancement of currently available functionality. Functions and features of the current software release that require enhancement or programmatic correction drive the corrective analysis process. Examples of software fitness issues identified during the enhancement analysis phase include, but are not limited to: Fixing known defects that prevent users from engaging the software in the manner for which it was intended according to past Fitness-For-Use publications Expanding current functionality capacities Improving processing times and throughput Adding support for user compliance with new regulatory issues These Scoping and Analysis phases of the SDLC conclude with the release of the Fitness-For-Use documentation ( FFU ). The FFU details the improvements to be included in the next release, the target market (and target users) for the next release and the key business case issues that the next release will address on behalf of the target users. While the FFU details a technological commodity it is not a technical document. It should be written using business language that can be understood by end users and those who initiate, influence and approve purchasing decisions at the customer level. The FFU is critical in that it enables the testing and quality control group to begin development of the master test plan while providing the sales & marketing group with critical information regarding product positioning, market penetration strategy and sales collateral content development. ARCHITECTURAL DESIGN Up until now, the phases of the software development lifecycle have focused on what the next software release is going to do. In the Architectural Design phase, the enterprise begins to define how the software is going to do it. What languages, programming platforms and hardware tools are going to be used to enable programmers and developers to complete the software development lifecycle?
4 Page 4 What approaches and programmatic designs are required to create software that meets the functional user expectations set in the Fitness-For-Use document? These questions must be answered in this phase of the SDLC. The Architectural Design phase of the SDLC concludes with the release of the technical specifications documentation ( Tech Spec ). The tech spec is a technical document written by developers and architects for developers and architects. As such, it should include architectural design drawings, data flow maps, functional flow charts, underlying database table specifications and design standards for both the functional and user interface issues to be changed and/or introduced in the next release. The Tech Spec is critical in that it keeps the all members of the development team on the same page even if they are not working on the same function, feature or module. A well-written tech spec goes a long way towards ensuring a coordinated development effort and a resultant deliverable that is consistent in design, construction and programmatic style. With regards to the testing and quality control team, the technical specification document enables the test leader to begin defining the use cases, test scenarios and environmental configurations that will drive the tactical execution of the product testing lifecycle.
5 Page 5 DEVELOPMENT & TESTING FLOW CHART Copyright Bellateq, Ltd All Rights Reserved
6 Page 6 DEVELOPMENT & TESTING NARRATIVE The programming and development phase is beginning of software build and construction. It is during this phase of the SDLC that the programmers, architects, user interface designers, development leader and test leader all work together on the construction of the new software product. The programming & development phase temporarily concludes with the release of the first testable version of the product. While functional and UI testing may have already started prior to completion of the programming & development phase, the release of this first testable version the Alpha represents the first opportunity the testing team has to execute end-to-end testing on all functions, features, enhancements and corrections documented and called for in the FFU. With the commencement of end-to-end testing, the developers will re-start the programming and development phase of the SDLC with a focus on bug fixes and usability improvements found and reported by the testing team. This back-andforth process continues until the testing team completes all functional, usability, unit, integration, system and regression testing. This phase of the SDLC is again temporarily completed with the release of the second testable version the Beta1. The release of the Beta1 signals the commencement of user acceptance testing by the quality control team. As in the first round of testing, developers again re-start this phase of the SDLC with a focus on the usability improvements documented by the testing team and approved by the test leadership group (Development Leader, Test Leader, Sales Leader, Marketing Leader). With the completion of programming work on all reported usability improvement issues completed, the Programming & Development phase of the SDLC concluded and the Beta2 version of the software is released. (The Beta2 version is sometimes referred to as the Pre-release version.) Upon release of the Beta2, it is expected that all features and functions detailed in the FFU are ready for pre-sales evaluation by external third parties. The Beta2 is the first iteration of the software that will be seen and used by individuals who are employed by customers of the enterprise as opposed to the enterprise itself. With the Beta2 in test-users hands, the Business Acceptance phase of the testing lifecycle begins. By the time the enterprise is in Beta2 and external resources are testing and evaluating the software all defects should be corrected. Customer personnel should not be confirming that the products work. Business Acceptance Testing is Copyright Bellateq, Ltd All Rights Reserved
7 Page 7 when external users confirm that the new products work the way they expect it to work. It is during Business Acceptance Testing that the enterprise confirms that the next planned release will at minimum meet user expectations. COMPILATION Programming is now complete and the software does everything the FFU says it is supposed to do. Testing is finished and the enterprise has confirmed that the software meets or exceeds customer expectation. The Compilation phase of the software development lifecycle now begins and is focused on preparing the application for distribution to and use by paying customers. All distribution media (web download, CD installation, etc.) is prepared and tested. Collateral is required (labeled CD platters, users manuals, installation guides, user training and education collateral, etc.) is completed by the IT professional services team during this phase. The Compilation phase concludes with: Notification to the sales department that orders can now be taken (or preorders fulfilled) for the new version of the software Notification to the marketing department that they can publish press releases announcing the commercial availability of the new version Customer service personnel notifying Upgrade & Enhancement contract subscribers that a new version of their software is ready for download and/or installation Communication by Sales and Sales Support personnel to customers that if they have budgeted for system upgrades, user training, on-site installation and/or consulting services related to the next version of their software that those services are now available for purchase and if they haven t budgeted for those issues they may wish to consider them going into their next budgeting cycle.
8 Page 8 PROGRAMMING & DEVELOPMENT PROCESS DEFINITION This process definition section includes detailed process flow charts and RACI diagrams for the key deliverables, as defined in the Programming and Development group at Cott Systems. The flow charts in this section use graphic images that are defined in the tables below: Action, Work Stream and Executed function Symbols Symbol Name Description Process Predefined Process (Subroutine) Alternate Process Delay Preparation Manual Operation Represent a Process or action step. This is the most common symbol in both process flowcharts and process maps. A Predefined Process symbol is a marker for another process step or series of process flow steps that are formally defined elsewhere. This shape commonly depicts sub-processes (or subroutines in programming flowcharts). If the sub-process is considered "known" but not actually defined in a process procedure, work instruction, or some other process flowchart or documentation, then it is best not to use this symbol since it implies a formally defined process. This flowchart symbol is used when the process flow step is an alternate to the normal process step. Flow lines into an alternate process flow step are typically dashed. The Delay flowchart symbol depicts any waiting period that is part of a process. Delay shapes are common in process mapping and are often included in process flowcharts where periodic batch processes must be executed before the overall work stream can be completed. Any process step that is a Preparation process flow step including but not limited to a set-up operation, user login, or user-defined parameter definition. Manual Operations flowchart shapes show which process steps are not automated. In data processing flowcharts, this data flow shape indicates a looping operation along with a loop limit symbol. Copyright Bellateq, Ltd All Rights Reserved
9 Page 9 Branching and Control of Flow Symbols Symbol Name Description Flow Line Flow line connectors show the direction that the process flows. Flow charts in North America typically flow from top to bottom and left to right. Terminator Terminators show the start and stop points in a process. When used as a Start symbol, terminators depict a trigger action that sets the process flow into motion. Decision Connector (Inspection) Indicates a question, binomial response expectation or branch in the process flow. Typically, a Decision flowchart shape is used when there are 2 options (Yes/No, Go/No-Go, etc.) Flowchart Context: In flowcharts, this symbol is typically small and is used as a Connector to show a jump from one point in the process flow to another. Connectors are usually labeled with capital letters (A, B, AA) to show matching jump points. They are handy for avoiding flow lines that cross other shapes and flow lines. They are also handy for jumping to and from a sub-processes defined in an area other than the main flowchart. Process Mapping Context: In process maps, this symbol is full sized and shows an Inspection point in the process flow. Off-Page Connector Off-Page Connector shows continuation of a process flowchart onto another page. When using them in conjunction with Connectors, it's best to differentiate the labels, e.g. use numbers for Off-Page Connectors and capital letters for Connectors.
10 Page 10 Symbol Name Description Merge (Storage) Extract (Measurement) Or Flowchart Context: Shows the merging of and concatenation of multiple processes or process outputs into one piece of information or a single artifact. Process Mapping Context: commonly indicates storage of raw materials. Flowchart Context: Shows when a process splits into parallel paths. Also commonly indicates a Measurement, with a capital 'M' inside the symbol. Process Mapping Context: commonly indicates storage of finished goods. The logical Or symbol shows when a process diverges - usually for more than 2 branches. When using this symbol, it is important to label the out-going flow lines to indicate the criteria that must be met in order for process flow to follow each branch. Summing Junction The logical Summing Junction flowchart shape is shows when multiple branches converge into a single process.
11 Page 11 Input and Output Symbols Symbol Name Description Data (I/O) The Data flowchart shape indicates inputs to and outputs from a process. As such, the shape is often referred to as an I/O shape. Document Document flowchart symbol is for a process step that produces a document or artifact. Keep in mind that documents do not necessarily mean printed outputs. Display Indicates a process step where information is displayed to a person (e.g., PC user, machine operator, customer, etc.) Manual Input Manual Input flowchart shapes show process steps where the operator/ user is prompted for information that must be manually input into a system.
12 Page 12 File and Information Storage Symbols Symbol Name Description Stored Data A general Data Storage flowchart shape used for any process step that stores. Database This flowchart shape depicts a database consisting of columns corresponding to fields and rows corresponding to records. Direct Access Storage Direct Access Storage Hard Drive. Databases are usually stored on Direct Access Storage appliances. Internal Storage Used in programming flowcharts to represent information stored in memory, as opposed to on a file. Arrays are the most common internally stored artifact but this symbol may also be used to represent cookies stored locally on a web applet users machine or device.
13 Page 13 The RACI diagrams in this section use the following coding nomenclature: SCENARIO R Responsible A - Accountable C Consulted I Informed POTENTIAL RESOURCE ALLOCATION ISSUE Responsible parties own the project, work stream and/or deliverable assigned to them and are ultimately the point person for their quality and on-time delivery. Responsible parties, by definition are Accountable and must sign off on projects, work streams and deliverables before they can be considered complete Accountable parties must sign off on (approve) projects, work streams and or deliverables before than can be put into production or made available for external distribution Consulted parties have information, own content, have capabilities or are subject matter experts such that their contributions are necessary for successful completion of a project, work flow or deliverable Informed parties must be notified of the results and/or successful completion of projects and work streams and should be made aware of the availability of key deliverables
14 Page 14 PRODUCT FITNESS-FOR-USE RACI DIAGRAM Stakeholder Responsible Accountable Consulted Informed Development Team Development Lead Testing Team Test Lead Customer Service Team Customer Service Manager Sales Team Sales Manager Professional Services Team Professional Services Manager VP - Operations CFO CEO
15 Page 15 PRODUCT FITNESS-FOR-USE FLOW CHART Copyright Bellateq, Ltd All Rights Reserved
16 Page 16 PRODUCT TECHNICAL SPECIFICATION RACI DIAGRAM Stakeholder Responsible Accountable Consulted Informed Development Team Development Lead Testing Team & Test Lead Hosted Solutions Manager Customer Service Team Customer Service Manager Sales Team Sales Manager Professional Services Team Professional Services Manager VP - Operations CFO CEO
17 Page 17 PRODUCT TECHNICAL SPECIFICATION FLOW CHART Copyright Bellateq, Ltd All Rights Reserved
18 Page 18 SOFTWARE DEVELOPMENT LIFECYCLE RACI DIAGRAM SDLC Lifecycle Phase Responsible Accountable Consulted Informed Requirements Definition Dev Lead Test Lead, Pro Srvcs Lead Test Team, Cstmr Support Team, Sales Team, Mktg Team, Customers Senior Exec Team Enhancement Analysis Dev Lead Sales Lead, Mktg Lead Corrective Analysis Design & Architecture Dev Lead Dev Lead Test Lead, Cstmr Support Lead Dev Team, Hosted Solutions Lead Programming & Development Dev Lead Dev Team Validation & Testing Test Lead Dev Lead Dev Team, Senior Exec Team Compilation Dev Lead Hosted Solutions Lead Sales Lead, Mktg Lead Deployment Pro Srvcs Lead Dev Lead, Test Lead Senior Exec Team, Customers PROGRAMMING & DEVELOPMENT FLOW CHART
19 Page 19
20 Copyright Bellateq, Ltd All Rights Reserved Page 20
Page 1 SECTION 4 TESTING & QUALITY CONTROL TESTING METHODOLOGY & THE TESTING LIFECYCLE The stages of the Testing Life Cycle are: Requirements Analysis, Planning, Test Case Development, Test Environment
Flowchart s and Their Meanings Flowchart s Defined By Nicholas Hebb The following is a basic overview, with descriptions and meanings, of the most common flowchart symbols - also commonly called flowchart
Release management Release management process is a software engineering process intended to oversee the development, testing, deployment and support of software releases. A release is usually a named collection
Understanding Computers Today and Tomorrow 12 th Edition Chapter 13: Program Development and Programming Languages Learning Objectives Understand the differences between structured programming, object-oriented
15 th Edition Understanding Computers Today and Tomorrow Comprehensive Chapter 13: Program Development and Programming Languages Deborah Morley Charles S. Parker Copyright 2015 Cengage Learning Learning
BPMN by example Bizagi Suite Recruitment and Selection 1 Table of Contents Scope... 2 BPMN 2.0 Business Process Modeling Notation... 2 Why Is It Important To Model With Bpmn?... 2 Introduction to BPMN...
From Traditional Functional Testing to Enabling Continuous Quality in Mobile App Development Introduction Today s developers are under constant pressure to launch killer apps and release enhancements as
2 SYSTEM DESCRIPTION TECHNIQUES 2.1 INTRODUCTION Graphical representation of any process is always better and more meaningful than its representation in words. Moreover, it is very difficult to arrange
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
hapter 1 n Introduction to omputers and Problem Solving Section 1.1 n Introduction to omputers 1. Visual Basic is considered to be a () first-generation language. (B) package. () higher-level language.
CS/SWE 321 Sections -001 & -003 Software Project Management Copyright 2014 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written
UML Tutorials Using UML Part Two Behavioral Modeling Diagrams by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page 1 Trademarks Object Management Group, OMG, Unified Modeling Language,
Quick Guide Business Process Modeling Notation (BPMN) IDM Technical Team January 2007 Quick Guide: BPMN 2 of 14 The scope of this document is to provide a quick guide to the concepts and usage of the Business
Software Development In the Cloud Cloud management and ALM First published in Dr. Dobb's Journal, February 2009: http://www.ddj.com/development-tools/212900736 Nick Gulrajani is a Senior Solutions Architect
LECTURE 11: PROCESS MODELING Outline Logical modeling of processes Data Flow Diagram Elements Functional decomposition Data Flows Rules and Guidelines Structured Analysis with Use Cases Learning Objectives
Process Modeling Notations and Workflow Patterns Stephen A. White, IBM Corp., United States ABSTRACT The research work of Wil van der Aalst, Arthur ter Hofstede, Bartek Kiepuszewski, and Alistair Barros
Continuous Delivery Anatomy of the Deployment Pipeline (Free Chapter) by Jez Humble and David Farley Copyright 2011 ThoughtWorks Inc. All rights reserved www.thoughtworks-studios.com Introduction Continuous
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
Model Simulation in Rational Software Architect: Business Process Simulation Mattias Mohlin Senior Software Architect IBM The BPMN (Business Process Model and Notation) is the industry standard notation
What are Cognitive Radio and Dynamic Spectrum Access SDR can act as a key enabling technology for a variety of other reconfigurable radio equipments commonly discussed in the advanced wireless market 1.
Database Project Lifecycle Philippe Bonnet, 2006 2 Software Engineering The implementation of a database application is a significant engineering endeavor The project must complete On time On budget The
Testing Introduction IEEE Definitions Software testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the
Essential Visual Studio Team System Introduction This course helps software development teams successfully deliver complex software solutions with Microsoft Visual Studio Team System (VSTS). Discover how
The Business Process Model by Sparx Systems All material Sparx Systems 2007 Sparx Systems 2007 Page: 1 Table of Contents INTRODUCTION...3 BUSINESS PROCESS MODELING NOTATION (BPMN)...4 FLOW ELEMENTS...4
: Uniting business with technology to satisfy business process management needs A White Paper By Joby O Brien Vice President of Development What is Workflow? Workflow has been defined as the automation
Systems Analysis Pseudocoding & Flowcharting 1 Flowcharting, pseudocoding, and process design The purpose of flowcharts is to represent graphically the logical decisions and progression of steps in the
STLC-Software Testing Life Cycle SDLC Software Testing Lifecycle Software Testing Life Cycle (STLC) defines the steps/ stages/ phases in testing of software. However, there is no fixed standard STLC in
Chapter 5 5.1 Processor Memory Organization The memory structure for a PLC processor consists of several areas, some of these having specific roles. With rack-based memory structures addresses are derived
Software testing cmsc435-1 Objectives To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testing To describe strategies for generating
A discussion of information integration solutions November 2005 Deploying a Center of Excellence for data integration. Page 1 Contents Summary This paper describes: 1 Summary 1 Introduction 2 Mastering
ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition Version 0.6 - Page 3 / 43 Table of Contents 1. Process Introduction... 5 1.1. Process Scope... 5 1.2. Process Objectives and Benefits... 5
Accelerating Time to Market: Application Development and Test in the Cloud Paul Speciale, Savvis Symphony Product Marketing June 2010 HOS-20100608-GL-Accelerating-Time-to-Market-Dev-Test-Cloud 1 Software
Stephen A. White, IBM Corporation Abstract This paper is intended to provide a high-level overview and introduction to the Business Process Modeling Notation (BPMN). The context and general uses for BPMN
Textbook Correlation WESTMORELAND COUNTY PUBLIC SCHOOLS 2011 2012 Integrated Instructional Pacing Guide and Checklist Computer Math Following Directions Unit FIRST QUARTER AND SECOND QUARTER Logic Unit
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11, Testing, Part 2: Integration and System Testing Overview Integration testing Big bang Bottom up Top down Sandwich System testing
Business Process Standards and Modeling Janne J. Korhonen Helsinki University of Technology STANDARDS Standards Organizations Object Management Group (www.omg.org) Business Process Modeling Notation (BPMN)
CTI Higher Certificate in Information Systems (Engineering) Module Descriptions 2015 CTI is part of Pearson, the world s leading learning company. Pearson is the corporate owner, not a registered provider
SCALEOUT SOFTWARE How In-Memory Data Grids Can Analyze Fast-Changing Data in Real Time by Dr. William Bain and Dr. Mikhail Sobolev, ScaleOut Software, Inc. 2012 ScaleOut Software, Inc. 12/27/2012 T wenty-first
Software Development Lifecycle Steve Macbeth Group Program Manager Search Technology Center Microsoft Research Asia About Me Currently manage a team of 10 Program Managers at Microsoft Research Asia Over
3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification
Department of Health and Human Services Centers for Medicare & Medicaid Services Office of Information Services CMS Framework Overview Version 1.1 May 18, 2011 Table of Contents 1. Introduction... 1 1.1
Business Process Modeling with BPMN Dr. Darius Šilingas Head of Solutions Department email@example.com No Magic Europe, 2012 About Instructor Dr. Darius Šilingas q Principal Consultant and Head
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5, No. 6, July - August 2006 On Assuring Software Quality and Curbing Software
An introduction to the benefits of Application Lifecycle Management IKAN ALM increases team productivity, improves application quality, lowers the costs and speeds up the time-to-market of the entire application
Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems firstname.lastname@example.org
Process Mapping Guidelines FLOWCHART SYMBOLS The following are the primary symbols: SYMBOL NAME DESCRIPTION Activity/Processing Decision Document Direction of Flow Chart Connections Indicates that an activity
Section V: Object Oriented Programming Risk Management In theory, there is no difference between theory and practice. But, in practice, there is. - Jan van de Snepscheut 427 Chapter 21: Unified Modeling
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
XEGENCY ARTWORK PRODUCTION MANAGEMENT SYSTEM FOR AD AGENCIES An innovative workflow management solution for Ad agencies and Design agencies to efficiently manage the artwork production process. Right from
CROSS INDUSTRY PegaRULES Process Commander Bringing Insight and Streamlining Change with the PegaRULES Process Simulator Executive Summary All enterprises aim to increase revenues and drive down costs.
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
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
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
Modeling Guidelines Manual [Insert company name here] July 2014 Author: John Doe email@example.com Page 1 of 22 Table of Contents 1. Introduction... 3 2. Business Process Management (BPM)... 4 2.1.
CASE STUDY FROM THE FACTORY TO THE USER: STREAMLINING COMPUTER DELIVERY PROCESSES USING 1E SHOPPING AND SCCM By Gene Acker SCCM Architect, Project Manager, and Administrator We all come to rely on manufacturers.
A Fresh Graduate s Guide to Software Development Tools and Technologies Chapter 3 Testing CHAPTER AUTHORS Michael Atmadja Zhang Shuai Richard PREVIOUS CONTRIBUTORS : Ang Jin Juan Gabriel; Chen Shenglong
Automate Your BI Administration to Save Millions with Command Manager and System Manager Presented by: Dennis Liao Sr. Sales Engineer Date: 27 th January, 2015 Session 2 This Session is Part of MicroStrategy
DevOps for the Mainframe Rosalind Radcliffe IBM Distinguished Engineer, Enterprise Modernization Solution Architect firstname.lastname@example.org 1 Please note IBM s statements regarding its plans, directions, and
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
IBM Rational SCM solutions for distributed development August 2004 Successfully managing geographically distributed development Karen Wade SCM Product Marketing Manager IBM Software Group Page 2 Contents
USTC Course for students entering Clemson F2013 Equivalent Clemson Course Counts for Clemson MS Core Area 398 / SE05117 Advanced Cover software lifecycle: waterfall model, V model, spiral model, RUP and
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
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...
Siebel Business Process Framework: Workflow Guide Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013 Copyright 2005, 2013 Oracle and/or its affiliates. All rights reserved. This software and related
Recommendations for Performance Benchmarking Shikhar Puri Abstract Performance benchmarking of applications is increasingly becoming essential before deployment. This paper covers recommendations and best
The Real Challenges of Configuration Management McCabe & Associates Table of Contents The Real Challenges of CM 3 Introduction 3 Parallel Development 3 Maintaining Multiple Releases 3 Rapid Development
Performance testing in Agile environments Deliver quality software in less time Business white paper Table of contents Executive summary... 2 Why Agile? And, why now?... 2 Incorporating performance testing
Agile QA Process Anand Bagmar Anand.Bagmar@thoughtworks.com email@example.com http://www.essenceoftesting.blogspot.com Version 1.1 Agile QA Process 1 / 12 1. Objective QA is NOT the gatekeeper of the quality
Levels of Testing Patrick Oladimeji Advance topics in Computer Science Dr. Markus Roggenbach Prof. Dr. Holger Schlingloff University of Wales Swansea Computer Science Department Contents 1. Different levels
1 2 nd edition CC terms 50% task time estimate A task time estimate that has a 50% probability of being achieved. Perspective: The distribution of task times is generally viewed as an asymmetrical positive
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2007 Vol. 6, No. 1, January-February 2007 CM Configuration Change Management John D.
BPMN Business Process Modelling Notation Knut Hinkelmann This chapter is based on the BPMN Tutorial of Stephen A. White and the book White, S.A., Miers, D. (2008) BPMN - Modeling and Reference Guide. Future
Candle Plant process automation based on ABB 800xA Distributed Control Systems Yousef Iskandarani and Karina Nohammer Department of Engineering University of Agder Jon Lilletuns vei 9, 4879 Grimstad Norway
Course 10965B: IT Service Management with System Center Service Manager Page 1 of 9 IT Service Management with System Center Service Manager Course 10965B: 3 days; Instructor-Led Introduction This Three-day