REAL TIME GPS TRACKING SYSTEM MSE PROJECT PHASE I PRESENTATION Bakor Kamal CIS 895

Outlines  Project Overview  Requirements  Project Plan  Cost Estimation  Software Quality Assurance Plan  Architecture Elaboration Plan  Standards, Practices, Conventions, and Metrics  Project Deliverables  Questions Department of Computing and Information Sciences - Kansas State University

Project Overview Department of Computing and Information Sciences - Kansas State University  Goal:  To develop an application for tracking mobile devices which came with GPS functionality with it.  Motivation:  The motivation of developing this project has been my desire of learning more about Mobile programming technology. Moreover, I want to apply what I learned about development lifecycle.

Project Overview (Cont.) Department of Computing and Information Sciences - Kansas State University

Requirements Department of Computing and Information Sciences - Kansas State University

Requirements (Cont.) Department of Computing and Information Sciences - Kansas State University  Track Connected Devices.  Purpose: The user can see a list of connected devices that are associated with his user ID.  Input: User credential.  Output: information about the connected devices and links that takes the user to more details and statistics about the devise position.

Requirements (Cont.) Department of Computing and Information Sciences - Kansas State University  View Statistics  Purpose: To let the user to see some statistics about the user position such as the average speed of the device movements, the path of the device moves and how many miles that device moved.  Input: Device ID.  Output: Mentioned statistics and information.

Requirements (Cont.) Department of Computing and Information Sciences - Kansas State University  Register Device  Purpose: to allow the user to add a new device under his account.  Input: Device type and device description.  Output: when the user successfully adds the device he will see “New Device Added Successfully” statement.

Requirements (Cont.) Department of Computing and Information Sciences - Kansas State University  Contact the System Administrator  Purpose: To provide a form for contacting the system admin to help the user in installing the client application in the device and to answer any questions regarding the system and to provide feedback.  Managing Accounts  Purpose: To give the user the ability to update his information including devices description, some of the tracking options, and his username and password.

Requirements (Cont.) Department of Computing and Information Sciences - Kansas State University  Signup  Login

Project Plan Department of Computing and Information Sciences - Kansas State University

Cost Estimate Department of Computing and Information Sciences - Kansas State University  Basic COCOMO Model  This project “Real Time GPS Tracking System” is an average complexity, thus it is classified as the first class of the COCOMO model the Organic Projects. Following is the formula for the cost estimation for the COCOMO Organic projects: Effort = 3.2*EAF (Size)^1.05 Time (in months) = 2.5(Effort)^0.38

Effort Adjustment Factor Department of Computing and Information Sciences - Kansas State University I classified the adjustment factors in the following way:  Computer turnaround time as low and a value of 0.9  Analyst capability as high and a value of 1.1  Applications experience as normal and a value of 1.0  Programmer capability as normal and a value of 1.0  Virtual machine experience as normal and a value of 1.0  Language experience as normal and a value of 1.0  Use of modern practices as normal and a value of 0.82  Use of software tools as high and a value of 0.83  Required development schedule as normal and a value of 1.10

Effort Adjustment Factor (Cont.) Department of Computing and Information Sciences - Kansas State University I classified the adjustment factors in the following way:  Required reliability as low and a value of 1.0.  Database size as low and a value of 1.0  Product complexity as normal and a value of 1.08  Execution time constraint as normal and a value of 1.2  Main storage constraint as low and a value of 1.1  Virtual machine volatility as low and a value of 0.95  Computer turnaround time as low and a value of 0.9

Calculations  The EAF value evaluated to 0.9. I estimated the size to be 2000 LOC based on the current prototype. The effort evaluates to:  Effort = 3.2*0.9*2.0^1.05 = 5.9 staff months  The time can now be calculated as:  Time = 2.5*5.9^0.38 = 4.9months Department of Computing and Information Sciences - Kansas State University

Architecture Elaboration Plan (phase2)  Revision of Vision Document:  After the first presentation, changes as required by the committee should be made in the Vision Document.  Revision of Project Plan:  According to the changes suggested by the committee after the first presentation, the project plan should be modified to include those changes. A section about the implementation plan should be added before the second presentation.  Architecture Design:  Based on the use case diagram in the vision document, an architecture design should be developed for the second phase.  Development of Prototype:  This prototype will include the demonstration of the critical requirements identified in the Vision Document. Department of Computing and Information Sciences - Kansas State University

Architecture Elaboration Plan (Cont.) Department of Computing and Information Sciences - Kansas State University  Test Plan:  A complete test plan will be developed indicating the testing techniques used and the way bugs will be reported and solved. This will be done to test whether all the requirements specified in the vision document are met or not.  Formal Technical Inspection:  Loai Zomlot and Waleed Al-Jandal will review the architecture design produced by the developer and submit a report on their findings.

Software Quality Assurance Plan Department of Computing and Information Sciences - Kansas State University  Reference Documents  Vision Document  Project Plan  IEEE Guide for Software Quality Assurance Planning  IEEE Standard for Software Quality Assurance Planning  Supervisory Committee  Dr. Daniel Andresen (Major Professor)  Dr. Gurdip Singh  Dr. Mitchell Neilsen  Developer  Bakor Kamal  Formal Technical Inspectors  Loai Zomlot  Waleed AlJandal

Documentation Department of Computing and Information Sciences - Kansas State University  The documentation will consist of a vision document, project plan, software quality assurance plan, formal requirements specification, architecture design, test plan, formal technical inspection, prototype, user manual, component design, source code, assessment evaluation, project evaluation, references, formal technical inspection letters.  All documentation will be posted on the developer’s web site at:

Standards, Practices, Conventions, and Metrics Department of Computing and Information Sciences - Kansas State University  Documentation Standard  IEEE standards will be used as a guideline to follow.  Coding Standard  The project will use traditional object oriented analysis and design methods. Recommended Java style guidelines will also be followed.  Documentation  JavaDoc will be used for documenting the complete API for the project.  Metrics  Basic COCOMO will be used to estimate the effort and time for the project.

Tools, Techniques, and Methodologies Department of Computing and Information Sciences - Kansas State University  The proposed software for this system was  Java ME (Java Platform, Micro Edition).  Eclipse – as the IDE for J2ME  PHP  Ajax  Dreamweaver – as IDE for PHP and Ajax  MySQL DB  Microsoft Software Project 2007 – Project Planning  OpenJMS – to implement JMS PTP (between the GPS client and the server) PTP will be used because the nature of this application considered as 1:1 application that is we have only one publisher and one subscriber all the time

Others Media Control  The software will be available on a CD-ROM ready for installation. The executable file will be recorded on it.  A user manual soft copy will also be saved in the CD to aid with the installation process and use of the software.  Documentation will be available from the developer’s website Records collection, maintenance and retention  The design documentation will be stored in the University library, the Major Professor and the developer.  Entire source code, documentation and web pages for the project website will be submitted to the Major Professor in the form of a CD. This will also be stored with the developer. Department of Computing and Information Sciences - Kansas State University

Project Deliverables Department of Computing and Information Sciences - Kansas State University  Phase I: Vision Document 1.0 Project Plan 1.0 Software Quality Assurance Plan 1.0 Presentation I

Project Deliverables (Cont.) Department of Computing and Information Sciences - Kansas State University  Phase II  Action items identified during Phase I  Vision Document 2.0  Project Plan 2.0  Formal Requirements Specification  Architecture Design  Test Plan  Formal Technical Inspection- by two MSE Students  Executable Architecture Prototype  Presentation II

Project Deliverables (Cont.) Department of Computing and Information Sciences - Kansas State University  Phase III  Action items identified during Phase II  User Manual  Component Design  Source Code  Assessment Evaluation  Project Evaluation  Test Results  References  Formal Technical Inspection- by two MSE students  Presentation III

Project Address Department of Computing and Information Sciences - Kansas State University  Project Address:   Documentation Address:  t.htm t.htm

Questions Department of Computing and Information Sciences - Kansas State University