12/10/20081 Final Product Delivery and Demonstration Team 4 Mid-Atlantic Software CMSC 345 Software Design and Development December 10th, 2008.

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

Faculty LMS Orientation
INFO 425 Week 31 INFO 425 Design Problem I Week 3 – SDS Improvements Glenn Booker.
Detailed Design Presentation February 21, 2006 NSG Software DevelopmentFebruary 21, NSG Software Development.
Online School Registration System Solomon Ng Pei-Yu Wang Evan Chiu Curtis Wong.
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
16/27/2015 3:38 AM6/27/2015 3:38 AM6/27/2015 3:38 AMTesting and Debugging Testing The process of verifying the software performs to the specifications.
Pear Software e-SATA (The Electronic Spreadsheet Automated Teaching Assistant) Preliminary Design.
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 26 Delivering the System.
Chapter 3 Planning Your Solution
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
Chapter 24 - Quality Management Lecture 1 1Chapter 24 Quality management.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
1 ThinkLink Learning Online User Manual for Predictive Assessment Series Go to www2.thinklinklearning.com/pas4mlwk. Click Educator Login. Your username.
Planning Iteration Demo Suunto Training Program Planner.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
Presented by Janine Termine Welcome 095 Basic Algebra.
CMSC 345, Spring CMSC 345 Software Design and Development Spring 2003 Section 0101 Ms. Susan Mitchell “Welcome to the School of Hard Knocks”
Text 1 July, 2010 DCMS: Training Manual Interface and Master Data Management.
VistA Imaging Capture via Scanning. October VistA Imaging Capture via Scanning The information in this documentation includes only new and updated.
Leave Your Ego at the Door! CMSC 345 Software Design and Development Spring 2011 Ms. Susan Mitchell.
Software Development Process.  You should already know that any computer system is made up of hardware and software.  The term hardware is fairly easy.
1 Moodle Login Professional Development Training.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
CMSC 345, Fall CMSC 345 Software Design and Development Fall 2003 Section 0101 Ms. Susan Mitchell Leave Your Ego at the Door!
Cs413_design04.ppt Design and Software Development Design : to create a functional interface that has high usability Development : an organized approach.
CTP210 TERM PROJECT
The Software Development Process
Software Engineering 4, Julian Richardson, 30 April Static Analysis Software Engineering HX3 Julian Richardson
T Project Review RoadRunners [IM3] Iteration
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
Online Class tips & tricks Ms. Bennett Online Facilitator (Mentor /Administrator / Instructor)
Intermediate 2 Computing Unit 2 - Software Development.
D R A T D R A T ABSTRACT Every semester each department at Iowa State University has to assign its faculty members and teaching assistants (TAs) to the.
K-12 Teaching Application Support and Software Ongo-08 Client Dr. John Lamont Prof. Ralph Patterson Advisor Dr. Gregory Smith Team Members Sean Boyle Tony.
Lesson Format Good Teacher. Lesson Format Each “Lesson” has to be a stand alone activity in an LMS to be SCORM compliant. The Review questions can be.
Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.
Project CSTutor Group Leader:David Gurba Technical Leader: Tommy Tsan Librarian/Secretary: Nolan Marcy Documentation Specialist: Hiep Nguyen Aesthetic.
Functions Part I (Syntax). What is a function? A function is a set of statements which is split off into a separate entity that can be used like a “new.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
T Project Review Muuntaja I1 Iteration
Creating Your Own Online Classroom MOODLE. Welcome Amy Basket – 17 years with Bay City Public Schools – Gifted and Talented Program – Volunteer Program.
Matt Tempia Chris Thomas Thomas Taylor Jeffrey Tansey.
321 Calc! Login Instructions for Students. You will need the following items before logging into this course: An Access Code for 321 Calc! – You may have.
Team Layer 8 Shiny Widget Delivery Presentation Dec. 4th, 2008.
NAVSEA Liaison Scott Huseth Faculty Advisor Dr. Jiang Guo Team Members Areg Abcarians David Ballardo Niteen Borge Daniel Flores Constance Jiang June 3,
“Making Frames for given Predicate : An approach for Unification of knowledge”
CMPT 275 TEAM DIRECTORIES. One Sentence Summary The Study Buddy is: a tool to help users study to improve their grades by simulating a multiple choice.
1 Week 1 Introduction, Writing a Program, Building a System Software Engineering Fall Term 2015 Marymount University School of Business Administration.
Architecture Review 10/11/2004
STOCK TRADING SIMULATION SYSTEM
Software Testing.
System Design, Implementation and Review
Data Virtualization Tutorial: Introduction to SQL Script
Verification and Validation
ISBN of bookstore bundle
T Project Review Group: pdm I2 Iteration
About the Presentations
CSE784 – Software Studio Jim Fawcett Fall 2006.
Software Documentation
Documentation for Developers
Chapter 13: Construction
Project Closure And Termination
CMSC 345 Software Design and Development Spring 2004 Sections 0101 & 0201 Ms. Susan Mitchell Leave Your Ego at the Door! CMSC 345, Spring 2004.
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Our Process CMSC 345, Version 1/04.
Presentation transcript:

12/10/20081 Final Product Delivery and Demonstration Team 4 Mid-Atlantic Software CMSC 345 Software Design and Development December 10th, 2008

12/10/20082 Team Introduction Team Mid-Atlantic Software (MAS) Team members Justin Bucca - Design Leader Eugene Feldman - Implementation and Testing Leader Van Furrow - Requirements Leader Scott Walkup - Team Facilitator Dessislava Apostolova - Delivery Leader

12/10/20083 Agenda 2:30 – 2:35 (5 min) IntroductionDessislava Apostolova, Delivery Leader 2:35 – 2:45 (10 min) Product RequirementsVan Furrow, Requirements Leader 2:45 – 2:50 (5 min) Product DesignJustin Bucca, Design Leader 2:50 – 3:00 (10 min) Code Inspection and Testing Procedures Eugene Feldman, Implementation and Testing Leader 3:00 – 3:15 (15 min) Product DemonstrationScott Walkup, Team Facilitator 3:15 – 3:25 (10 min) Questions from the CustomerMs. Kamalika Das, Customer 3:25 – 3:35 (10 min) Questions from the Instructor for the Customer Ms. Susan Mitchell, Instructor Ms. Kamalika Das, Customer 3:35 – 3:50 (15 min) Questions from the Instructor for the Team Ms. Susan Mitchell, Instructor

12/10/20084 Product Description Python Online Introductory Course Teaches the basics of Python Different topics organized in Chapters Practice tests on every chapter

12/10/20085 Customer Requirements Python tutorial/GUI/Login based Hyperlinked TOC Admin/Student privileges Prev/Next Navigation on every page Course divided into Chapters/Topics Multiple choice quizzes – 5 questions 3 chances to clear quiz Confirmation

12/10/20086 Major Functional Requirements Top-Level Use Case Diagram

12/10/20087 Use Case: Create Account

12/10/20088 Use Case: View Learning Info

12/10/20089 Use Case: Quizzes

12/10/ Use Case: Grades

12/10/ Use Case: Admin

12/10/ Major Non-Functional Requirements The system shall be a GUI The system shall be accessed online The system shall be login based All the main tutorial content shall be independently navigational The system shall save the progress and the test scores of each user The system shall use a database

12/10/ Basic Design User Interface Design Screen Layout – Left Frame, Top Frame, Main Frame

12/10/ UI Design Standard (Screen Shot)

12/10/ Logical Design

12/10/ Technology Architecture

12/10/ Code Inspection Defect checklist CategoryInspection Check Data Are all variables initialized before they are used? Have all constants been named? Control For each conditional statement, is the condition correct? Will each loop terminate? In case statements, are all possible cases accounted for? Input/Output Are all input variables used? Are all output variables assigned a value before they are output? Interface Do formal and actual parameters match in: Number? Data Type? What they represent? Exception Management Have all possible error conditions been taken into account?

12/10/ Code Inspection (Cont.) Inspection based on different modules Modules inspected: Basic.css, Index.php,Top.php, Left.php, Main.php, Admin.php, Grades.php, Login.php, CreateAccount.php, Toc.php

12/10/ Testing Procedures System Testing Process – Black Box Testing Followed Use Cases from SRS Tested on Internet Explorer and Mozilla Firefox

12/10/ Changes Since Last Update 3 chances to take a quiz Fixed a bug in the admin. account – limited number of chapters can be added Added 2 more sections to chapter 3 Formatted the chapter contents

12/10/ Product Demonstration How to install the product?

12/10/ References Mitchell, S. (2008) Final Product Delivery and Demonstration, Retrieved December 7, 2008 from Mid-Atlantic Software (2008) System Requirements Specification, Retrieved December 8, 2008 from Mid-Atlantic Software (2008) System Design Document, Retrieved December 8, 2008 from Mid-Atlantic Software (2008) User interface Design Document, Retrieved December 8, 2008 from

12/10/ References (Cont.) Mid-Atlantic Software (2008) Code Inspection Report, Retrieved December 8, 2008 from doc doc Mid-Atlantic Software (2008) Testing Report, Retrieved December 8, 2008 from oc oc Mid-Atlantic Software (2008) Administrator Manual, Retrieved December 8, 2008 from doc doc