A PPARC funded project Architecture Appeal Guy Rixon AstroGrid Consortium meeting April 2004.

Slides:



Advertisements
Similar presentations
Use Case: Use case title Submitter(s) Submitting Company #1 – Submitter 1, Submitter 2 Supporters(s) Supporting Company #1 – Submitter 1, Submitter 2 Use.
Advertisements

Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
A PPARC funded project AstroGrid Framework Consortium meeting, Dec 14-15, 2004 Edinburgh Tony Linde Programme Manager.
A PPARC funded project Common Execution Architecture Paul Harrison AstroGrid consortium meeting Edinburgh UK Dec 2004.
assessed for quality before coding begins.
Technology readiness levels in a nutshell
Presentation by Prabhjot Singh
1 Software Testing and Quality Assurance Lecture 13 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
A PPARC funded project Tony Linde Programme Manager eScience meets eFrameworks 28 th April 2006 NeSC, Edinburgh.
An Integrated Approach to Enterprise Architecture LIACS, Martijn Wiering 23 juni ‘04.
May Archiving PAWN: A Policy-Driven Software Environment for Implementing Producer- Archive Interactions in Support of Long Term Digital.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Object Oriented Design. Goals  Levels of abstraction  Workshop: group meeting for Pragmatic Web homework.
Input Validation For Free Text Fields ADD Project Members: Hagar Offer & Ran Mor Academic Advisor: Dr Gera Weiss Technical Advisors: Raffi Lipkin & Nadav.
Residential Lending Property of Citigroup:Internal Document 0 Project Blacksmith Portal Server Investigation Prepared by: Technical Architecture & Strategy.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
AstroGrid Group 7: Teemu Toivola Tero Viitala. Problem several separate databases no common interface between databases difficulties of joining related.
Domain Modelling the upper levels of the eframework Yvonne Howard Hilary Dexter David Millard Learning Societies LabDistributed Learning, University of.
CRM WEB UI – ARCHITECTURE- DEFINITIONS For More details please go to
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Software Engineering 1 The Life Cicle of Software Lesson 5.
UML - Development Process 1 Software Development Process Using UML (2)
Team Awesome. The Five Ws of SUMS  What is SUMS? SUMS is a system designed to monitor sensors and display their information neatly.  Who is SUMS appealing.
RUP Fundamentals - Instructor Notes
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
A PPARC funded project AstroGrid: new technology for the virtual observatory SC2004 Pittsburgh, PA November 2004 Guy Rixon AstroGrid Technical Architect.
Understand Application Lifecycle Management
A PPARC funded project Review of architecture document Consortium meeting Edinburgh December 2004 Guy Rixon AstroGrid Technical Architect University of.
A PPARC funded project AstroGrid approach to the Virtual Observatory Architecture ADASS XIV Pasadena Oct-2004 Tony Linde Andrew Lawrence Keith Noddle.
The B uff. The Buffs Agenda 1. Recent iteration and Progress 2. Plan for next iteration 3. Prototype demonstration.
WordFreak A Language Independent, Extensible Annotation Tool.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
AstroGrid Overview AG-SAG Cambridge IoA 19 th June 2003 Tony Linde AstroGrid Project Manager University of Leicester, Dept. Physics & Astronomy.
1 Peter Allan14-15 Dec 2004AstroGrid Consortium Meeting: Architecture Discussion AstroGrid Architecture – the view from outside Is the description acceptable?
1 27-Apr-2004AstroGrid Consortium Meeting - PL talk Agenda Tuesday status review / goals / science Lunch + AGLI Itn-05 review Dinner at Coton (share.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
AstroGrid Oversight Committee MRC, London 30 July, 2002.
Budapest, September 5th, 2002 DataGrid Accounting System DGAS Current status & plans Stefano Barale INFN Budapest, September.
Course Conclusion. Agenda Summing up by Tom Handing over to Ellen Your presentations Typo3 // css stuff Information about exam.
A PPARC funded project VOTech AstroGrid DSA Update Kona Andrews Institute for Astronomy University of Edinburgh.
Deliverable 10. Deliverable #10 Class Design and Implementation #1 due 9 April Executive Summary and Statement of Work Iteration Plan (Updated) for remaining.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
1 Copyright 2010 NexJ Systems Inc. Confidential and Proprietary - Not for Distribution. OHT Platform Project.
The 9 steps to successful project implementation From BD to Operations.
A PPARC funded project Tony Linde Programme Manager AstroGrid in the wider world AstroGrid Consortium meeting Cambridge, UK 10-July-2005.
A PPARC funded project Common Execution Architecture Paul Harrison IVOA Interoperability Meeting Cambridge MA May 2004.
Java Software Solutions Lewis and Loftus Chapter 15 Copyright 1997 by John Lewis and William Loftus. All rights reserved. 1 Software Development Process.
Computer Science 340 Software Design & Testing Software Architecture.
Session 3 How to Approach the UML Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
AstroGrid consortium meeting, December 2005 Slide 1 Architecture review Guy Rixon AstroGrid consortium meeting Jodrell Bank, December 2005.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
4+1 View Model of Software Architecture
1 Using Rational Rose ® to construct UML diagrams.
Copyright © 2010 Obeo, Made available under the Eclipse Public License v SCA Tools (Helios) Release Review Planned Review Date: June 11, 2010.
WP1 Status and plans Francesco Prelz, Massimo Sgaravatto 4 th EDG Project Conference Paris, March 6 th, 2002.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
ONAP Usecase subcommittee July Virtual developers event
API Documentation Guidelines
Object Oriented Analysis and Design
Chapter 1 (pages 4-9); Overview of SDLC
Software Construction
Software Development Process
The 9 steps to successful project implementation
Chapter 7 –Implementation Issues
Name of Project Manager Date
The Fedora Project April 28-29, 2003 CNI, Washington DC
Software Construction
SDMX IT Tools SDMX Registry
Presentation transcript:

A PPARC funded project Architecture Appeal Guy Rixon AstroGrid Consortium meeting April 2004

AstroGrid architecture Current state We have an architecture It’s not written down coherently We all know and understand it We all disagree about details Disagreement hampers integration Need to document the architecture To focus iteration 6+ To plan AstroGrid 2 To help get the details right To help prove that AstroGrid 1 is a success

AstroGrid architecture Appeal for help Church architecture appeal Please give generously! We need your help to document the architecture. (And to keep the description up to date.) AstroGrid

AstroGrid architecture Your help needed Done In hand Required for I5 description ‘Requirements’ Science cases (on wiki already) Use cases (on wiki; may need updating) Implementation cases ‘Architecture’ Component lists (in RUP sense) (published) Java APIs W/S interfaces Deployment diagrams Semantic descriptions of components

AstroGrid architecture Three kinds of use case Science case Little/no (IT) technical detail Experiment leading to scientific publication For strategic planning Use case More technical detail Meaningful to end user For planning user interactions Implementation case Full technical detail Opaque to end user For planning development Science cases contain use cases contain implementation cases

AstroGrid architecture …and some questions Do you need an architecture doc to do Itn 6? If so, do you need it before or after planning? Do you need the Itn 6 architecture separately from the as-built description of Itn5? Do you need it for Itn 7 & 8? Current planning is to write up the AG-2 architecture before the current, as-built stuff. Is this a problem for you?