MavHome Software Development Guidelines G. Michael Youngblood Chief Scientist, MavHome The University of Texas at Arlington June 8, 2003.

Slides:

Advertisements

Similar presentations

Commenting and Naming Conventions

Advertisements

1 ICS103 Programming in C Lecture 4: Data Types, Operators & Expressions.

Juan Carlos Flores 10/20/2011. Outline Introduction Centralized Revision Control Systems Subversion Overview Distributed Revision Control Systems Network.

Data Linkage Graphical User Interface for Febrl Author: Changyang Li Student ID:u Supervisor: Peter Christen Faculty of Engineering and Information.

The Basic Tools Presented by: Robert E., & Jonathan Chase.

CS565 Advanced Software Development Lecture 23, 2006 CASE.

Kurt Menke, GISP GRASS GIS Geographic Resources Analysis Support System.

Time Domain Analysis Tool Semester Project Presentation Ehsan Ghaneie Ken Waller EEL 6883 – Software Engineering II Spring 2007.

Version Enterprise Architect Redefines Modeling in 2006 An Agile and Scalable modeling solution Provides Full Lifecycle.

Computer Programming and Problem Solving Ke shuwei.

- Chaitanya Krishna Pappala Enterprise Architect- a tool for Business process modelling.

Stanford University StanfordNetDB Stanford NetDB- An Open Source Network Management Application for DNS, DHCP, IP Address Spaces, etc.

Doxygen: Source Code Documentation Generator John Tully.

Norwegian Meteorological Institute met.no Recent development at met.no EGOWS 2008, Ljubljana Michael O. Akinde Martin L. Sætra Bjørn K. Larsen.

Introduction of Some Useful Free Software Cheng-Han Du.

SPI Software Process & Infrastructure GRIDPP Collaboration Meeting - 3 June 2004 Jakub MOSCICKI

UML Tools ● UML is a language, not a tool ● UML tools make use of UML possible ● Choice of tools, for individual or group use, has a large affect on acceptance.

Technical Overview.

SPI Software Process & Infrastructure EGEE France - 11 June 2004 Yannick Patois

Subversion, an Open Source Version Control System An Introduction.

18 March Implementation. Tools Do you need them? When do you need them? What can they do better then you?

Open Source The Future of Software What’s Open Source Open-source software is computer software whose source code is available under a copyright license.

CSE 219 Computer Science III Testing. Testing vs. Debugging Testing: Create and use scenarios which reveal incorrect behaviors –Design of test cases:

The Basics of Javadoc Presented By: Wes Toland. Outline  Overview  Background  Environment  Features Javadoc Comment Format Javadoc Program HTML API.

Taverna and my Grid Open Workflow for Life Sciences Tom Oinn

1 SEG4912 University of Ottawa by Jason Kealey Software Engineering Capstone Project Tools and Technologies.

Old Chapter 10: Programming Tools A Developer’s Candy Store.

Short Status Report: Documentation Geant4 Workshop at Noorwijk 4 October, 2010 Dennis Wright (for Katsuya Amako)

L. Mancera IT/API LCG SPI project: Code documentation1 Code Documentation Luis Mancera LCG Software Process & Infrastructure (CERN, 10/23/02)

1 1 Software Documentation David Geldreich (DREAM)

Introduction to Version Control SE-2030 Dr. Rob Hasker 1 Based on material at and slides written.

Java Coding Standards and Best Practices Coding Standards Introduction: After completing this chapter, you will able to keep your code up to standards.

Distributed Java Programming Distributed Java Programming Setting up a Java Development Environment.

Productivity Tools Ken Nguyen Department of Information Technology Clayton State University.

AP Computer Science Programming Conventions. Why coding conventions? 80% of the lifetime cost of a piece of software goes to maintenance. Hardly any.

CASE Tools Union Palenshus. In the early days… ► Software engineering tools consisted solely of translators, compilers, assemblers, linkers, loaders,

Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.

Code Conventions Tonga Institute of Higher Education.

JAVA Programming “When you are willing to make sacrifices for a great cause, you will never be alone.” Instructor: รัฐภูมิ เถื่อนถนอม

CONTENT 1.Software Process 2.Object Technology 3.UML 4.UML For Java.

KUFA UNIVERSITY Department of Computer Science 09/12/2015.

© 2008 by Shawn Spiars; made available under the EPL v1.0 | March 17, 2008 Case Study – Phurnace Software and RCP Shawn Spiars Lead UI Developer Phurnace.

GLite build and integration system Building and Packaging Robert HARAKALY

National Portals Project 2001 Create software package Define channel areas Promote transparancy Streamline many portal initiatives Make use of available.

 Programming - the process of creating computer programs.

Software Engineering Overview DTI International Technology Service-Global Watch Mission “Mission to CERN in Distributed IT Applications” June 2004.

December 5, 2005 Documentation and Project Organization Software Engineering Workshop, December 5-6, 2005 Jan Beutel ETH Zürich, Institut TIK.

Yannick Patois - Datagrid Software Repository Presentation - March, n° 1 Datagrid Software Repository Presentation CVS, packages and automatic.

GLAST LAT Project Science Tools - 12 June 2002 T. Burnett 1 The Science Analysis Software Development Environment -- for tools too! T. Burnett.

CASE Tools CSC 532 : Advance Topics CSC 532 : Advance Topics Software Engineering Software Engineering Dr. box Dr. box Moayad Almohaishi Moayad Almohaishi.

Software Deployment & Release 26/03/2015 1EN-ICE.

Technical Overview. What Is MagicDraw?  Business Analysts  Software Analysts  Programmers  QA Engineers  Documentation Writers MagicDraw is a powerful.

SPI Software Process & Infrastructure Project Plan 2004 H1 LCG-PEB Meeting - 06 April 2004 Alberto AIMAR

Outline Announcements: –HW II due today! –HW III on web CVS.

CODERS ADJUNCTION POINT Presented by, Rumana Ahmed Deeba Tazeen CSE final year.

PAPYRUS Tutorial CSOS 손 태 용.

Maite Barroso – WP4 Workshop – 10/12/ n° 1 -WP4 Workshop- Developers’ Guide Maite Barroso 10/12/2002

Use of SVN as lattice repository Andrea Latina Common paths for CLIC and ILC BDS – Friday, 30 August 2013 – CERN.

Free Software for Engineers Indian GNU/Linux Users' Group, Chennai Shakthi Kannan MS October 29, 2007 Version 1.1 presents by.

Programming C++ in Linux by various IDEs and editors by: Danial Khashabi Master: Dr.B.Taheri November 2008.

Version Control and Source Code Control Systems

SE goes software engineering; (practically) managing the Compose

Documentation Generators

Component and Deployment Diagrams

SE goes software engineering; managing the Compose* project.

SE goes software engineering; managing the Compose* project.

SE goes software engineering; managing the Compose* project.

SE goes software engineering; (practically) managing the Compose

Tonga Institute of Higher Education

The Ultimate Dataflex Source Code Editor!

Presentation transcript:

MavHome Software Development Guidelines G. Michael Youngblood Chief Scientist, MavHome The University of Texas at Arlington June 8, 2003

Overview " Project Structure " Development Environment (GNU Linux/GCC/Anjuta)  Project Building Makefiles/Autotools " Coding Standard (C++/Java/Scripts) " Documentation " Design UML (dia) " API (doxygen) " User Manual (html) " Repository (CVS)

Project Structure " Tree Structure " " Example Project " " Warning! This is a 24MB file!

Development Environment " RedHat GNU Linux 8.0 " GCC 3.2 " Java " FLTK  CORBA Orbacus " WindowsXP " M$ Visual Studio 7 " Java " FLTK  CORBA Orbacus 4.1.2

Development Environment " Eclipse " " Anjuta "

Project Building " Make " " htm htm " " Autotools " " / /

Coding Standard " Why have Code Conventions? " Code conventions are important to programmers for a number of reasons: " 80% of the lifetime cost of a piece of software goes to maintenance. " Hardly any software is maintained for its whole life by the original author. " Code conventions improve the readability of the software, allowing engineers to understand new code more quickly and thoroughly. If you ship your source code as a product, you need to make sure it is as well packaged and clean as any other product you create. Source: Gallery Coding Standards, SourceForge

MavHome Coding Standards " C/C " Java " Scripts (Shell, Perl, Python, etc)

Documentation - Design " UML " " " Useful " Class Diagram " Sequence Diagram " Dia

Documentation - API " doxygen " "

Documentation - Users " HTML " "

Documentation - Reports " Latex or M$ Word " "

Repository - CVS " Concurrent Versions System " " " Cervisia "

Additional Information " Contributing to OpenSource Projects "

Questions?

Thank You!