Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.

Slides:



Advertisements
Similar presentations
Requirements Specification and Management
Advertisements

Ch 3: Unified Process CSCI 4320: Software Engineering.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
Indistar: Updates, Additions, and Coming Soon Stephanie Benedict, ADI.
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Planning. SDLC Planning Analysis Design Implementation.
CHAPTER 19 Building Software.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Mobile Application for SAT Preparation Preliminary Project Plan By Project Team: Hi5 Anant Kambli Amit Shukla Ajaykumar Aswathappa Prabin Gautam Rama K.
Karl Banks Aaron Birencwaig Andrew Harmic Jason Heintz Stephen Rodriguez Tyler Zaino.
Introduction to Information System Development.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Web Development Process Description
AJAX Chat Analysis and Design Rui Zhao CS SPG UCCS.
Virtual Mechanics Fall Semester 2009
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
ABSTRACT Zirous Inc. is a growing company and they need a new way to track who their employees working on various different projects. To solve the issue.
About Dynamic Sites (Front End / Back End Implementations) by Janssen & Associates Affordable Website Solutions for Individuals and Small Businesses.
Software Testing Life Cycle
Group 8: Shenanigans Mike Ostrowski Josh Patsey Michelle Boomer Tom Parks Levent Niazi.
RUP Implementation and Testing
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
Understand Application Lifecycle Management
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Medium Size Software, Inc. SQA Plan: The Batch Processing Application.
Course Presentation EEL5881, Fall, 2003 Project: Network Reliability Tests Project: Network Reliability Tests Team: Gladiator Team: Gladiator Shuxin Li.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Tunis International Centre for Environmental Technologies Small Seminar on Networking Technology Information Centers UNFCCC secretariat offices Bonn, Germany.
Software Engineering Management Lecture 1 The Software Process.
PROJECT SECME1 Carthik A. Sharma Juan Carlos Vivanco Majid Ali Khan Santhosh Kumar Grandai Software Engineering Fall 2002.
Computer Emergency Notification System (CENS)
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Distributed Software Development QR Marks The Spot Beta Prototype Vadym Khatsanovskyy, Nicolas Jacquemoud.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
REAL TIME GPS TRACKING SYSTEM MSE PROJECT PHASE I PRESENTATION Bakor Kamal CIS 895.
Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
MSE Presentation 1 By Padmaja Havaldar- Graduate Student Under the guidance of Dr. Daniel Andresen – Major Advisor Dr. Scott Deloach-Committee Member Dr.
Request for Proposal (RFP)
Chapter 3: Software Project Management Metrics
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
HR for XML WebService -- Week 2 System Design Phase Smartest Fish.
Members: Adam Lee, Kartik Subbu, Nick Oakman, and Gabriel Semonis Advisor: Professor Daji Qiao.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Chapter 12 Implementation and Maintenance
 SAP AG 2007, SAP CSUN 2007 Conference Presentation / 1 Presented by Team “Call of Duty” 29 th April 2010 CS 6361, University of Texas At Dallas.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Web-based Front End for Kraken Jing Ai Jingfei Kong Yinghua Hu.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Statistics Monitor of SPMSII -High level and detailed design Warrior Team Pu Su Heng Tan Kening Zhang.
Word Guess Team (Team #4) October 8, Word Guess Team  Team Members  Chakib Kouhel:  Steve Mattingley:
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Online Newspaper CMS 1 Date: 27/12/2012. Contents Introduction Project Management Requirement Specifications Design Description Test Documentation Summary.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Milestone Two – Reach Across Houston (RAH) Tuesday, June 14, Team:Matthew Edwards Thomasina Coates Michelle Graham James Henrydoss James McNicholas.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
PROJECT SECME Carthik A. Sharma Juan Carlos Vivanco Majid Khan Santhosh Kumar Grandai. Software Engineering Fall 2002.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Architecture Review 10/11/2004
Software Engineering Management
T Project Review Group: pdm I2 Iteration
Request for Proposal (RFP)
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang

Overview Background Proposed System Requirement Specification Project Management Plan Testing Future

Background Current System Features –Similar with Source Forge system ( ) Project hosting Version control Bug and issue tracking Project management Backups and archives Communication and collaboration resources Current System Shortcoming –Lack of statistic information for the project progress monitor. ( )

Proposed System Based on SPMSI, monitor statistics module is added to provide function of tracing the activities of projects Similar with Source Forge system ( ) –Overall Statistics –Separate Detailed Statistics

System Environment & Tools All software components are Open Source Apache Web Server MySQL or greater PHP4 Scripting Language Linux Debian 3.0 System Processor PII/233Mhz or above System Memory 128MB or greater Internet connection

Requirement Specification Requirement Specification Functional Requirements Interface Requirements Physical Environment Requirements Users and Human Factors Requirements Documentation Requirements Resource Requirements Security Requirements Quality Assurance Requirements

Event Table Event NameExternal StimuliExternal ResponsesInternal data and state Overall Statistics Page Request User types HTTP address of Overall Statistics Webpage and IP packets signal server to send user this webpage Page sentApache server logs user IP address, and HTTP request Seperate Statistics Page Request User types HTTP address of Separate Statistics Webpage and IP packets signal server to send user this webpage Page sentApache server logs user IP address, and HTTP request

Use Case Diagram

Use Case Descriptions Use cases from the overall projects' statistics pages and associated pages –Display the overall statistics of all projects after inquiry (Primary: Display) 1. Execute inquiry action 2. Display result as a ranking list with percentage (detailed activity data with forms) 3. Update the ranking list with the latest data under updating inquiry Alternative: Inquiry action not accepted Display an error message page if exceptions happen during inquiry

Use Case Descriptions (contd) Use cases from the each project's statistics pages and associated pages –Display the separate statistics of each project after inquiry (Primary: Display) 1.Execute inquiry action 2.Display result as a ranking list with percentage (detailed activity data with forms) 3.Update the ranking list with the latest data under updating inquiry Alternative: Inquiry action not accepted –Display an error message page if exceptions happen during inquiry

Project Team Organization Team will use a democratic organization to carry out development of SPMSII project. This will allow everyone to have equal input in decision making and allow the group to make decisions based on the majority rules principle. However, the team do have a team manager to accommodate all the non-technique affairs. –Pu Su, Kening Zhang, Heng Tan are in the team. –All the technique decisions will be discussed and finally made democratically. –Communication will be handled through and scheduled face-to- face meetings when ideas and design need to be decided.

Deliverables Timetable Artifact Due Dates Meeting MinutesIn maintenance. Update approximately once every two week Individual Logs In maintenance. Update when necessary Group Project Management Reports N/A ConOps 10/01/02 Project Plan 10/01/02 SRS 10/01/02 High-Level Design 10/22/02 Detailed Design 10/22/02 Test Plan 10/01/02 User's Manual 11/19/02 Final Test Results 11/19/02 Source, Executable, Build Instructions 11/19/02 Project Legacy 11/19/02

Software Life Cycle Basically,waterfall model is used in this project Rapid prototype may be used in requirement phase.

Quality Assurance QA is group effort in the final days of each phase testing. The group will decide unanimously if the project satisfies the requirements and if it does so accurately

Risk Management Inability to coordinate three different developers in the group due to the different schedules –Suggested solution: Utilize and instant messaging to overcome scheduling errors Inability to coordinate between the client and developers –Suggested solution: Fully used the loop back of the waterfall model Limited time of developers –Suggested solution: improve our work efficiency

Technical Progress Metrics For requirements phase, the total number of requirements, the number of requirements changes is used For OO analysis and design, the number of UML diagrams completed is used. For detailed design and code, the number of web pages, classes, and methods is used

Plan for tracking, control, and reporting of progress Tracking and control will be handled by a website where all group members can keep track of the progress of the pages and upload updates to the development of the web pages. –Each team member will post the following information weekly –Each week, the project manager will: read and analyze the logs –The project manager will issue a Project Management Report on the schedule as indicated in the deliverables section above

Overall Objective for Software Test Activity Using non-execute test to specification Using execute test to the software production Using different test cases to test

Test case I Test Objective: Test the over all project statistics Test Description: Test whether the over all project statistics is correct reflected in the monitor. Operate the all monitor operation in all projects, and see whether the monitor can get a reasonable result. Test Conditions: See test environment Expected Results: the project statistics can be recorded by the monitor correctly

Test case II Test Objective: Test the single project statistics Test Description: Operate the single project in all possible operation, and see whether the monitor can reflect the change. Test Conditions: See test environment Expected Results: the change can reflect in the monitor statistics

Test stopping criteria The software qualify assurance policy Test cases The object of software qualify assurance

Future Details of Design Implementation of Statistics Monitor Integration with SPMSII Maintenance