SWIM-Suite Final Product Demo Team members: Abhishek Bindiganavile Robert Greenberg Sedat Ozer Jay Takle Swimming Meet Management Software.

Slides:



Advertisements
Similar presentations
Applicatieplatform congres 12 & 13 maart. Modeling that works with code Preview VSTS Architect edition 2010 Marcel de Vries IT- Architect Info Support.
Advertisements

MAPPING DATA FLOW DIAGRAMS INTO STRUCTURE CHARTS
Ch 3 System Development Environment
4+1 View Model of Software Architecture “Software architecture” course Presented By: Mazeiar Salehie October 2004.
Traditional Approach to Design
Outline About author. The problem that discussed in the article.
A Brief Introduction to Software Design and Design Quality By Laura Leventhal.
Oct. 9, 2003CS WPI1 CS 509 Design of Software Systems Lecture #6 Thursday, Oct. 9, 2003.
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.
Feb. 20, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #11 Tuesday, Feb. 20, 2001.
Handling Large Projects  Project Decomposition  Stepwise Refinement Functional Decomposition Design Decomposition  Work Breakdown Structures (WBS)
CMPT 370: Information Systems Design Instructor: Curtis Cartmill, Simon Fraser University – Summer 2003 Lecture Topic: Layered Architecture Class Exercise:
Logical Architecture and UML Package Diagrams
System Design Decomposing the System. Sequence diagram changes UML 2.x specifications tells that Sequence diagrams now support if-conditions, loops and.
MODEL VIEW CONTROLLER A Technical Seminar Report submitted to
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Requirement Analysis Functional & Non-Functional Requirements Scenarios Use cases: – View Fixtures – Manage Tournament – Register Team – Report Discrepancy.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
Design Dan Fleck CS 421 George Mason University. What is the design phase? Analysis phase describes what the system should do Analysis has provided a.
An Introduction to Software Architecture
CS 160: Software Engineering October 8 Class Meeting
 Chapter 6 Architecture 1. What is Architecture?  Overall Structure of system  First Stage in Design process 2.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
Nicolas Teirlinckx Made for Software Engineering Groep 1 (2009 – 2010)
Chapter 9 Moving to Design
Chapter 6 – Architectural Design CSE-411, Dr. Shamim H Ripon.
Chapter 13 Logical Architecture and UML Package Diagrams 1CS6359 Fall 2012 John Cole.
TCS2411 Software Engineering1 Data-Flow Oriented Design “From DFD to Structure Chart”
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
UML-1 4. Architecture. UML-2 Artifact: Analysis Class Abstraction of one or several classes or subsystems –Focuses on handling functional requirements.
Request for Proposal (RFP)
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
Lecture 18: Object-Oriented Design
Arch-1 9.Architecture. Arch-2 What’s Architecture? Description of sub-system –Components/sub-systems –Their interaction Framework for communication.
Computer Science 340 Software Design & Testing Software Architecture.
TK2023 Object-Oriented Software Engineering CHAPTER 8 LOGICAL ARCHITECTURE.
KEY PERSONNEL Dr. Bob Schutz, GLAS Science Team Leader Dr. Jay Zwally, ICESat Project Scientist, GLAS Team Member Mr. David Hancock, Science Software Development.
Curriculum Project for Information Extraction. Task definitions Task 1: Entity detection and recognition Task 2: Relation detection and recognition Both.
Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
BTS430 Systems Analysis and Design using UML
Introduction. System Design Hardware/Software Platform Selection Software Architectures Database Design Human-Computer Interaction (HCI) Interface Object.
CSE784 – Software Studio Jim Fawcett Fall 2002.
Introduction to MVC SoftUni Team Introduction to MVC
Software Design.
Introduction to .NET Florin Olariu
ITEC 370 Lecture 13 Design.
Review for Final, Fall 2010 Close book, Close notes
Software Design & Documentation
<<Project Name>> <<Team Members>>
CSE784 – Software Studio Jim Fawcett Fall 2006.
STARS Project Management
BTS530: Major Project Planning and Design
Chapter 13 Logical Architecture.
Software Engineering Lecture #45
Starting Design: Logical Architecture and UML Package Diagrams
Chapter 13 Logical Architecture.
Software Design Lecture : 8
An Introduction to Software Architecture
4+1 View Model of Software Architecture
Project Prototype Demo 1 Grading Rubric
PPT and video are due no later than February 15, 2019
4+1 View Model of Software Architecture
CMPE/SE 131 Software Engineering March 7 Class Meeting
Chapter 13 Logical Architecture.
Logical Architecture & UML Package Diagrams
Presentation transcript:

SWIM-Suite Final Product Demo Team members: Abhishek Bindiganavile Robert Greenberg Sedat Ozer Jay Takle Swimming Meet Management Software

Motivation - Write about swim meets

Requirements - Requirements

Class Diagram - Class Diagram

Software Architecture - Used a MVC architecture pattern. - Isolates the application logic from the user(Separation of concern). - Advantages: Independent development, testing and maintenance.

Subsystem Decomposition - 3 layered system with 7 subsystems - Higher cohesion and minimum coupling possible.

Hardware/software Mapping

Testing - Write about the test cases

Team Responsibilities Jay Takle: Requirements Analysis. Abhishek Bindiganavile: System Designing. Sedat Ozer: Algorithm Designing. Robert Greenberg: Testing. - Each member was allotted at least one sub-system to code and write at least one document throughout the process. - Helped in recognizing individual strengths.

Project Status & Demo - Write about what you will show at the demo

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2024 SlidePlayer.com. Inc. All rights reserved.