IOTAP Software Build Process Author: Aman Choudhary Draft Version – Work In Progress.

Slides:

Advertisements

Similar presentations

© 2007 IBM Corporation Demo Shimon Nir, Rational Technical & Service Manager, IBM Southwest Europe.

Advertisements

Configuration Management

JobTracker™ A Job Tracking System for Architects & Engineers Produced by LA Solutions.

Defect Tracking and Management

Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)

Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.

ACDM Focus 2 – Processes December 13, 2013 Diane Guerrero Principal SCM Engineer.

Agile development By Sam Chamberlain. First a bit of history..

CS 325: Software Engineering April 7, 2015 Software Configuration Management Task Scheduling & Prioritization Reporting Project Progress Configuration.

Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.

Mercury Quality Center Formerly Test Director. Topics Covered Testdirector Introduction Understanding the Testdirector Interface. Understanding Requirement.

Software Engineering Process and Tools in the Mozilla Project How open-source CM tools made Firefox the fastest and safest web browser.

Chapter 3: The Project Management Process Groups

Interface Programming 1 Week 15. Interface Programming 1 CALENDAR.

PowerPoint Presentation for IS-207 Copyright 2006 © Michael W. Schaffer. All rights reserved. Slide 1 System Analysis & Design Shrink-wrap Tools and Techniques.

Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.

Pedro Miguel Rosa Senior Software Engineer Developer Platform Group.

SAIC-F QA Internal Process (DRAFT ) Sudha Chudamani QA Team, Frederick National Lab Jan 2, 2013.

CBIIT Quality Assurance and Compliance Process August 8, 2012.

CONTINUOUS DELIVERY / CONTINUOUS INTEGRATION. IDEAS -> SOLUTIONS Time.

Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.

CaDSR Software Development Update Denise Warzel Semantic Infrastructure Operations Team Presented to caDSR Content team November 2012.

Software Testing Online Training DEFECT TRACKING & CORRECTION

Extreme Programming Software Developing Methodology.

Software Testing Life Cycle

& Dev Ops. Sherwin-Williams & DevOps Introduction to Sherwin-Williams.

Build Controller Build Controller – A Windows service that creates the name of the build, version control label, logging, and monitors status of the build.

The eHealth Services Capstone Project

Team Assignment 15 Team 04 Class K15T2. Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics.

Software Project Management

Sampleminded® Support Overview Last Updated: 1/22/

Viking Quality Report Team Assignment 9 Team 2-1.

C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009.

-1- Project Name Project Name Weekly Project Report Project Manager : __________________ Date : ___________________.

.com Software Testing Tutorials “Basics for beginners. Fundamentals for everyone.” Welcome to Day 4. We will start at 4:35 PM PST. Software Testing Tutorials.

Continuous Integration and Code Review: how IT can help Alex Lossent – IT/PES – Version Control Systems 29-Sep st Forum1.

Software Development Processes: How to create great software, doing it right the first time and keep your sanity Matt Howland Francesca Noli.

Project-X 3.0 Quality Criteria. QA Criteria Milestones Ø System Integration Complete (September) ùReady to start building production servers. Ø Project-X.

Theories of Agile, Fails of Security Daniel Liber CyberArk.

Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.

CSC 4700 Software Engineering

EMI INFSO-RI Guidelines and SQA Process Maria Alandes Pradillo (CERN) SA2.2 Task Leader.

Eriq Muhammad Adams J | 03 |QA and Testing (1) Eriq Muhammad Adams J |

Test Plan for Collaborative Server System Prashanth Vijayaraghavan (315) –

Practice Array Web Process By Shengli Hu. Wads Practice 1 review wads everyday morning. mail assignment everyday. keep the status of wads reflect.

Virtual techdays INDIA │ November 2010 Building Visual Studio LightSwitch Application Kunal Chowdhury │ Software Engineer, Silverlight MVP.

A way to develop software that emphasizes communication, collaboration, and integration between development and IT operations teams.

Texas Nodal Program ERCOT Readiness Update TPTF May 5, 2008.

JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.

Softheme Service Model Software Outsourcing Solutions.

Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.

Avoiding the Pitfalls of Database Change Automation Cindy Bean Sr. Software Consultant DBmaestro SQLSaturday #514 – Houston, May 14, 2016.

Version Control for PL/SQL

Implementing Cloud-based Agile Team Development - Lessons Learned

Implementing Cloud-based Agile Team Development - Lessons Learned

Project management Software development typically includes:

Chi Ben Jamilia Clary Jude Desti Sabrina Fontaine Preston Lucas

CS 325: Software Engineering

Building a Continuous Integration Pipeline using VSTS

Visual Studio 2005 “Personalized productivity”

Software Quality Engineering

Kickoff Presentation Date of Presentation Presenter Name

Software Quality Engineering

APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)

Dynamic Process for Source Control

APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)

LESSON 01 Hands-on Training Execution

Adaptive Product Development Process Framework

Setup QA Process Software Quality Assurance Telerik Software Academy

Software Development In Agile

Presentation transcript:

IOTAP Software Build Process Author: Aman Choudhary Draft Version – Work In Progress

Standards & Documentation A. Software Coding Standards A set of rules for writing software codes Generally defined by the customer B. UI Standards CSS Classes or Fonts, Table Sizes, etc which are defined by the UI Designer Generally defined by the customer C. Smoke Test A set of rules which the Project Lead needs to execute before the software is released to QA for it to starts its Testing Defined jointly by the customer and IOTAP Team Lead

Roles & Responsibilities (IOTAP) 1. Team Lead Overall Customer Satisfaction Monitor Software developed is meeting standards (UI & Software Coding) Enforce Development Release Process Time Sheets Are Being Entered Develop & Perform Smoke Test Automate Test Cases 2. Software Engineer Develop Software Per Decided Software Coding Standards & UI Standards 3. QA Engineer Test Software To Make Sure It Meets Specifications 4. Executive Sponsor Weekly Progress Report From Software Team Lead

Software Code Repository Current Software Branch Production Software Branch Sample Repositories IOTAP has used: - Source Safe - Sub Version - Team Foundation Services

Staged Test Instance: May 7 th, 2007 Build 5. Promote: Test To Prod 1. Promote: Dev To Test 2. Perform Smoke Test 3. Perform QA Staged Test Instance: May 20 th, 2007 Build 5. Promote: Test To Prod Development & Production Branch Current Software Branch May 3 rd, 2007 May 5 th, 2007 May 7 th, 2007 ….. …. ….. May 1 st,, 2007 Production Software Branch May 7 th, 2007 May 20th, 2007 …. ….. 1. Promote: Dev To Test 2. Perform Smoke Test 3. Perform QA Staged Test Instance: May 1 st, 2007 Build 5. Promote: Test To Prod 1. Promote: Dev To Test 2. Perform Smoke Test 3. Perform QA 4. Perform UAT May 20, 2007

QA Issue Tracking (Cont.) 1) Title 2) Status Open Need More Information Unable To Reproduce In Progress Ready For Testing Closed 3) Assigned To 4) Created By 5. Priority Show Stopper High Medium Low 6. Build Reported 7. Build Fixed 8. Comments 9. Attachments

QA Issue Tracking 1) Open 2) Work In Progress 1.b) Unable To Reproduce 1.a) Need More Information 3) Ready For Testing 4) Closed