The Charlatans Mid-Semester Presentation Spring 2003 Lalit Jina April Navarro Dawei Gu Matt Bass Wei Zhang.

Slides:



Advertisements
Similar presentations
ATAM Architecture Tradeoff Analysis Method
Advertisements

C2-SENSE WP2 Bojan Božić, Gerald Schimak, Refiz Duro C2-SENSE WP2 Meeting Paris
Lecture # 2 : Process Models
CSE 470 : Software Engineering The Software Process.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
SYSC System Analysis and Design
Online School Registration System Solomon Ng Pei-Yu Wang Evan Chiu Curtis Wong.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
CS 5150 Software Engineering
02/12/00 E-Business Architecture
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Team Spider Interim Presentation. Team Spider Members Sponsor  Telecom Consulting Group N.E. Corp. (TCN) Advisor  Professor Raghu Reddy Students  Adam.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Software Performance Engineering Steve Chenoweth CSSE 375, Rose-Hulman Tues, Oct 23, 2007.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 8 Requirements I.
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
Software Architecture in Practice
0-1 Team 1 Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auto-Owners.
0-1 Team ?? Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auraria.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Chapter : Software Process
System Analysis and Project Management Key terms and definitions Presentation.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
T Project Review RoadRunners [PP] Iteration
Design Development Image credit:
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
May 6, 2002 PUMA SPRING 2002 EOSP PUMA. 2Agenda Introduction Project organization Process Benefits from mini-SRE Architecture Achievements Project demonstration.
Software Engineering Management Lecture 1 The Software Process.
Basic of Project and Project Management Presentation.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
WEB BASED DATA TRANSFORMATION USING XML, JAVA Group members: Darius Balarashti & Matt Smith.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Example Template for Project Presentation
Project Methodology May 2, System Development Life Cycle Overview.
CS 5150 Software Engineering Lecture 3 Software Processes 2.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Chapter 5 Lecture 5: Understanding Requirements Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
ANKITHA CHOWDARY GARAPATI
The Charlatans EOSP Fall Charlatans – Fall 2002 EOSP2 11/25/2015 Agenda People Project Overview Key Requirements Process Description Risk Driven.
COMM89 Knowledge-Based Systems Engineering Lecture 8 Life-cycles and Methodologies
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a: Architectural Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a:
Developed by Reneta Barneva, SUNY Fredonia The Process.
Petals SAP Point Of Sale System Second Project Presentation M.Tech Team SE 15 (Saturday) Team Aug-2008.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CENG334 Introduction to Operating Systems 1 Erol Sahin Dept of Computer Eng. Middle East Technical University Ankara, TURKEY URL:
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
Software Engineering Management
CS4311 Spring 2011 Process Improvement Dr
Database Development Cycle
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
Requirements Development in CMMI
Presentation transcript:

The Charlatans Mid-Semester Presentation Spring 2003 Lalit Jina April Navarro Dawei Gu Matt Bass Wei Zhang

Charlatans Carnegie Mellon MEME S Master of Software Engineering 2 Agenda Project Overview Semester Goals Architecture Status Next Steps

Charlatans Carnegie Mellon MEME S Master of Software Engineering 3 Project Overview - I Sponsored by the SEI Team Objective Deliver companion applications for Casio wrist cameras Client Objective Provide insight into how teams make decisions and solve problems Project deliverables Software applications (Palm and PC)  Palm application over all PDAs supporting Palm OS 3.1 thru 4.1  PC application on platforms supporting Win9X, Win2000 and WinXP Design and implementation report

Charlatans Carnegie Mellon MEME S Master of Software Engineering 4 Project Overview - II BOB JILL

Charlatans Carnegie Mellon MEME S Master of Software Engineering 5 Previous Suggestions Focus development of prototypes Developing prototypes to define an architecture for the system Develop overall Architecture Defined a high level architecture Use of resources on campus Working with Ray Williams for risk management

Charlatans Carnegie Mellon MEME S Master of Software Engineering 6 Semester Goals Use a risk-driven approach to: Develop a system architecture Build a functional prototype of the minimal system on the most difficult platform The system with the capability for image transfers, minimal editing and display capabilities Palm OS 3.1, Handspring Visor monochrome display

Charlatans Carnegie Mellon MEME S Master of Software Engineering 7 Risk Management Identify issues during each cycle Enter the issues in the online risk database Group the issues into categories Identify the prototypes to be built or tasks to be done to mitigate the technical risks

Charlatans Carnegie Mellon MEME S Master of Software Engineering 8 Identified Risks Implemented functionalities may not work on all platforms IR-Communication Display mechanism Unknown portability issues Performance of the application may be below the level given in Requirements JPEG Compression-Decompression Possibility of requirements miscommunication with the clients Established the prototype driven requirements clarification methodology

Charlatans Carnegie Mellon MEME S Master of Software Engineering 9 Architecture development process Define an initial high level architecture Create a vertical use case touching on all the highest priority risks identified Exercise the architecture using the vertical use case Assign functionalities to the architectural components Identify “toys” to make design decisions Continuously refine architecture

Charlatans Carnegie Mellon MEME S Master of Software Engineering 10 Architecture Important quality attributes Portability Performance Portability Portability Layer abstracts OS and device specifics Rest of the functionality in Application Layer Performance JPEG Decompression Palm Hardware Palm OS Application Layer Portability Layer

Charlatans Carnegie Mellon MEME S Master of Software Engineering 11 Design Decisions Isolate platform dependent and the platform independent functionalities Layered approach Early identification of portable and non-portable functionalities Performance a constraint for JPEG compression – decompression Limited system resources CPU Memory

Charlatans Carnegie Mellon MEME S Master of Software Engineering 12 Semester Plan - I 3 Planned development cycles Cycle 1 – Short cycle to define a high-level architecture Cycle 2 – Risk based “toy” development leading to architecture refinement Cycle 3 – Development of the “integrated minimal system” leading to architecture definition

Charlatans Carnegie Mellon MEME S Master of Software Engineering 13 Semester Plan -II Design High-level Architecture Vertical prototype Identify components Assign tasks Refine Architecture Develop Toy Applications Individual development Prototype testing System integration Refine architecture Feedback Cycle 1Cycle 2Cycle 3

Charlatans Carnegie Mellon MEME S Master of Software Engineering 14 Current Status Technical Achievements JPEG compression Multiple-bit depth display prototype (monochrome, gray-scale, & color) Watch control using low level IRDA protocol Palm database access prototype Palm to Palm communication Architecture Being refined regularly depending on findings The “toys” are helping to answers to specific questions

Charlatans Carnegie Mellon MEME S Master of Software Engineering 15 Summer Plans Expand the "integrated minimal system" to work on other platforms (Palm OS 3.1 thru 4.1) Add the rest of the functionality as defined by requirements

Charlatans Carnegie Mellon MEME S Master of Software Engineering 16 For more information, please visit our web site at Questions?