Administrative Stuff.

Slides:



Advertisements
Similar presentations
Intro to Version Control Have you ever …? Had an application crash and lose ALL of your work Made changes to a file for the worse and wished you could.
Advertisements

By SAG Objectives Cross platform QA Automation for web applications Scheduling the automation Automatically build the test scripts Generate the.
Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.
Version Control 1.  Version control (or revision control) is the term for the management of source files, and all of the intermediate stages as development.
Tutorials Mid-Semester Fall ‘06 John Aitchison Josh Long Michael Bohn.
Source Control Repositories for Enabling Team Working Svetlin Nakov Telerik Corporation
Programming in Teams And how to manage your code.
COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.
Source Control Repositories for Team Collaboration: SVN, TFS, Git.
The new version control system. Kiril Karaatanasov, July 2006 What is Subversion Subversion is a newly developed open source version control system Subversion.
COMP 523 DIANE POZEFSKY 19 August CHAOS REIGNS.
To share information in four (4) critical areas for districts considering upgrading from the legacy STIOffice & STIDistrict applications to InformationNOW.
Lokesh Puppala. Introduction  Git - Distributed version control system  Initiated by Linus Torvalds  Strongly influenced by Linux kernel development.
Version Control Systems with Subversion (SVN) and Tortoise.
Introduction to Version Control SE-2030 Dr. Rob Hasker 1 Based on material at and slides written.
(Building the Presentation Layer - KISS). Figuring out what to do! Every was not learnt over night and certainly not without proper help and support.
Version Control with SVN Images from TortoiseSVN documentation
Version Control Systems. Version Control Manage changes to software code – Preserve history – Facilitate multiple users / versions.
WEEK INTRODUCTION CSC426 SOFTWARE ENGINEERING.
Policies and Processes Team meeting – February 2010.
Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.
L.T.E :: Learning Through Experimenting Using google-svn for MtM Docs Development Denis Thibault Version 3.2 Mar 12 th, 2009.
SW Development Project 2
INFO 344 Web Tools And Development CK Wang University of Washington Spring 2014.
Multi - Site Collaboration Systems Senior Design & Development - Spring 2016 Dan Jarvinen.
Subversion (SVN) Tutorial for CS421 Dan Fleck Spring 2010.
Geoff Davis Software Development Leader Software Development at eWater.
Source Control Repositories for Enabling Team Working Doncho Minkov Telerik Corporation
. SOEN 6481 SOFTWARE SYSTEMS REQUIRMENTS SPECIFICATION Summer 2016 / AA Team - F Patil Niketa (Primary) Patil Pooja (Secondary) Sangale Ninad Sanidhi Sanidhi.
. SOEN 6481 SOFTWARE SYSTEMS REQUIRMENTS SPECIFICATION Summer 2016 / AA Team - F Patil Niketa (Primary) Patil Pooja (Secondary) Sangale Ninad Sanidhi Sanidhi.
Version Control How and why to control changes in a software artifact.
L5 Computing Team Project Final Presentation Guidelines.
Software Documentation in an Agile Environment
HPE ALM Octane.
Introduction to Systems Analysis and Design
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Microsoft Virtual Academy
Getting Started on The Project Bank in Visual Studio
Version Control CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Improving quality and reproducibility of code
External Web Services Quick Start Guide
SVN intro (review).
The importance of being Connected
COMP 523 Diane pozefsky 24 August 2016.
Time Management and Teamwork (a.k.a. “Software Project”)
Chapter 1 The Systems Development Environment
Client communication.
Concurrent Version Control
System Development Life Cycle (SDLC)
Introduction to Team Foundation Server 2010
Systems Development and Documentation Techniques
Continuous Integration
CISC/CMPE320 - Prof. McLeod
Smoke and Mirrors Prototype
Git Version Control for Everyone
System Development Life Cycle (SDLC)
<<Project Name>>
Smoke and Mirrors Prototype
CISC/CMPE320 - Prof. McLeod
Continuous Integration Tool
Motion Capture and vr Frisbee Visualizer 2018.
CONTINUOUS INTEGRATION –WHY WE DO IT?
What is the name of your company? …by Monday…
By The way, Why Groups? OK every student hates group work
Version/revision control via git
Chapter 1 The Systems Development Environment
Documenting Accounting Information Systems
Federico Rojas Givaudan ESS Motion Control and Automation Group
Computational Environment Management
Presentation transcript:

Administrative Stuff

Sprint Grading Give teams a chance to make changes and get it right This weekend, requirements spring grading First development sprint will also be a bit delayed After that, grading will be immediate Remember grades include Process Code Documentation

Meetings Friday (travel) Monday (Rosh Hashonah) Monikos 9 am -> 9:30 phone Monday (Rosh Hashonah) Go.unc.edu 8 am -> 8 phone ITVS 10:10 am -> Wednesday at 10:10 Class: guest speakers: Cloud Apps and Kris Jordan on Vagrant Will be in for afternoon meetings

Business Process

Set of activities that will accomplish a specific goal Business Process Set of activities that will accomplish a specific goal Manual, computerized, or mix

Addresses What information is needed? Where does it come from? What needs to be done with it? Who has to process it? What is the flow of information? What is the expected output? How does it need to be presented? Is it a single process or multiple ones? What triggers the start(s)? What marks the end?

Why bring it up? Historically, 523 projects had a well designed or envisioned process USER STORIES are typically reflecting things that are already being done – just manually or inefficiently This year, I am seeing projects that do not understand their business process. This needs to be captured in order to build useful software

What are teams to do? Is the goal of your project to Create a new process? Automate an existing process? Improve a process? Is the business process you are part of well defined? Can you articulate it? Will your client agree with your description?

If there is a need for clarification Flowchart Follow the data Understand information transformations Inputs Outputs

Tools

Class list bitbucket codeshare.io github groupme jetbrains skype Slack tortoise/svn Trello

What Do You Need? Development Communication Repository Version control Editor Issue tracker Task management Communication

Repository and Version Control Backup Easy sharing Reversion Parallel development Git Parente Tools of the Trade SVN Tortoise Cross-platform GUI problems DIY