Bugs vs. Feature Requests

User Generated

ehfgyrefuvqrnjnl

Writing

cmgt 410

Description

There is no such thing as a bug-free IT project. Because bugs are a fact of IT project life, IT project managers must articulate a process for identifying, tracking, and handling the bugs that will inevitably occur. In addition, because technical and business requirements change frequently, IT project managers must also plan to log and track requests for new features and functionality.

Read the following linked documents:

  • "Visual Studio - Manage Bugs": This article describes the process of tracking bugs in Visual Studio, a popular .NET development suite created by Microsoft®.
  • "What Is a Bug and Issue Tracking Tool?": This article describes the process of tracking bugs in Jira, a popular bug tracking and project management tool created by Atlassian.

Create a 3-page Microsoft® Word document of a bug tracking process for the project you created in the individual assignments in Weeks 2 and 3. Be sure to differentiate between bugs and feature requests. For this assignment, you will only be tracking bugs.

Your tracking process must include:

  • Description of software you propose using for bug tracking (in-house developed or third-party)
  • Description of issues that will be considered bugs (vs. feature requests)
  • Description of who will use the system to track bugs
  • Description of who will monitor the system, follow up with the requestor as necessary, and implement the bug fixes
  • Description of bug-related information (such as a unique tracking number, description, assignee, etc.) necessary to identify, fix, and log bugs

Submit your completed document.

Unformatted Attachment Preview

Running head: PROJECT DOCUMENTATION 1 PROJECT DOCUMENTATION (BRD) Amy Richardson Prof. Mark Stewart 9DEC2018 PROJECT DOCUMENTATION 2 BUSINESS REQUIREMENT TEMPLATE (BRD) A developed project is established to attain certain business objectives. The project will aimed at the development of an Android app designed to measure a patient’s heart rate by using sensors in the smartphone to determine the minute pulses in the blood flow through the fingers. Executive Summary 1.1 Create a project communication plan Communication needs delivers the purpose of the project to all stakeholders. It is an approach driven by policy to provide necessary information. 2. Product/service description 2.1 App preplanning This stage involves discussing fundamental parameters of the android app. On the same subject questions on what the app can do and what it is built on together with its function 2.2 Deploy module prototypes PROJECT DOCUMENTATION 3 The android app will enable a variety of processing that allows different modules in its strategies of implementation and deployment. 2.3 Create and update the app database The document presents project creation with a local database to allow addition, deletion and update of database. 2.4 Complete the final software development Completion is a set of activities that lead to the final outcome and final software development is important to enhance project delivery. 2.5 Confirm calibration of software Calibration entails ensuring that the software is up-to-date and conforms to basic standards. 3. Requirements 3.1 Review system requirements Review to ensure that the app system is ready to proceed into its initial designs, requirements and performance derived from the previous capabilities. 3.2 Make shareholder incorporation plan This phase involves making a list of important and manageable ownership changes. 3.3 Determine software requirements This part describes specifications on the software requirements that are to be developed. 3.4 Test ability to effectively detect the pulse and detect the heartbeat PROJECT DOCUMENTATION The aim of the phase is to test the android app designed to measure a patient’s heart rate. 4. Manageability/ maintainability 4.1 Information gathering These are techniques and tools used to gather information on the purpose of the project. 4.2 Testing This entails evaluating the app software to match the existing and required conditions. 4.3 Monitoring and evaluation Monitoring involves improvement of performance as a way to achieve results. 4.4 Testor sensor compatibility The part entails testing the app with compatibility test suits to determine its functionality. 5. Requirement confirmation 5.1 Completion Completion of project documentation will gather all records, distribution of information to formalize its acceptance to project sponsors and business analysts. 4 PROJECT DOCUMENTATION (WBS) Amy Richardson Prof. Mark Stewart 9DEC2018 WORK BREAKDOWN STRUCRURE (WBS) 1. Executive Summary – 3 days 1.1 Create a project communication plan – 3 days (software development team) 2. Production/service description – 50 days 2.1 App preplanning – 10 days (project manager/team) 2.2 Deploy module prototypes – 14 days (Lead developer) 2.3 Disable backward compatibility – 1 day (developer) Le 2.4 Create and update the app database – 6 days (UX designer) 2.5 Complete the final software development -18 days (Lead developer) 2.6 Confirm calibration of software – 1 day (Lead developer) 3. Requirements – 14 days 3.1 Review system requirement – 3 days (software development team 3.2Make shareholder incorporation plan – 1 day (human resource department) 3.3 Determine software requirements – 9 days (Lead developer) 3.4 Test ability to effectively determine heart rate – 1 day (Lead developer) 4. Manageability and maintainability – 91 days 4.1 Information gathering – 5 days (project manager/team) 4.2 Testing – 4 days (test engineer) 4.3 Monitoring and evaluation – 79 days (project manager/owner) 4.4 Test sensor compatibility -3 days (technical administrator) 5. Requirement confirmation 5.1 Completion (project manager) Project Kickoff Android app that measures patient heart rate CMGT/410 Project Planning & Implementation Amy Richardson 16DEC2018 Prof. Mark Stewart Project Definition ▪ The project involves developing an android app that would ensure caregivers have a better way to monitor their patients. ▪ The app will have the ability to collect sensor data from wearable sensors, process the data then analyze the same. ▪ The analyzed data will result in deciding the next step of action and may trigger warning messages to doctors and guardians. ▪ By involving doctors, we opt that the system will be more accurate and acceptable for health monitoring. Business case ▪ Ensure efficient and effective customer service through the development of an Android app designed to measure a patient’s heart rate by using sensors in the smartphone to determine the minute pulses in the blood flow through the fingers. ▪ The android app will ensure that the customer ▪ Measure the patient’s heart rate ▪ Monitor any abnormal heart rates ▪ Signal the patient of any abnormality ▪ Can press a panic button to call the health practitioner. Project Approach ▪ . In this project, the waterfall methodology of project management would be used ▪ This methodology is appropriate for this type of project due to the fact that traditionally, software development has been based on the waterfall method and it has been proven to fit well within the rigid structure of developing software in which modules must be developed separately and build upon one another. Project Scope ▪ ▪ In Scope: ▪ Support for Android and iOS ▪ Features: ▪ Wearable sensors ▪ Doctor message or notification ▪ Customer status Out of Scope: ▪ Support for Windows and Blackberry ▪ Features: ▪ Integration with website (future) Budget / Sponsor ▪ Approximate Cost – $150000 which involves hiring a consultant ▪ Our funds will be sourced from well wishers and shares collected from our shareholders. ▪ App improvements and modifications will be financed through profit ploughed back. Implementation Timeline ▪ Preplanning – 10 days(4th Nov – 14th Nov 2018) ▪ Resources ▪ ▪ Review system requirements -3 days( 15th -18th Nov 2018) ▪ Resources ▪ ▪ Software development team Make shareholder incorporation plans 1 day (19th -20th Nov 2018) ▪ Resources ▪ ▪ Project manager/team Human Resource department Communications plan – 3 days(25th Nov – 28th Nov 2018) ▪ Resources ▪ Project manager. Implementation Timeline (cont….) ▪ Determine software requirements -9 days( 28th -7th Dec 2018) ▪ Resources ▪ ▪ Deploy module prototypes-14 days(7th -21st Dec 2018) ▪ Resources ▪ ▪ Lead developer Disable backward compability 1 day(22nd -22nd Dec 2018) ▪ Resources ▪ ▪ Lead developer Lead developer Create and update app database 6 days(22nd -28th Dec 2018) ▪ Resources ▪ UX designer Implementation Timeline (cont….) ▪ Completion of final software development -18 days( 28th Dec -15th Jan 2019) ▪ Resources ▪ ▪ Testing and confirmation of calliberation software- 9 days(15th -23rd Jan 2019) ▪ ▪ Lead developer Resources ▪ Test engineer ▪ Technical administrator ▪ Lead developer Monitoring and evaluation- random continuous process ▪ Resources ▪ Project owner Risk Factors ▪ ▪ Resource risk factors ▪ Labor availability ▪ Convenience ▪ Updated support facilities Legal factors ▪ Compliance with relevant authorities Project Team Roles and Responsibilities ▪ Project manager-initiation, planning and overall coordination of the project ▪ Software development team-team responsible for development of the android app software and review software requirements ▪ Human Resource department-hiring, firing and incorporating shareholders ▪ Lead developer-in charge of system requirements, deploying module prototypes etc. ▪ UX designer-development and updating of app database ▪ Test engineer-General testing of the app ▪ Technical administrator-confirm calibration.
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

Running head: BUG TRACKING PROCESS

1

Bug Tracking Process

Institution Affiliation

Date

BUG TRACKING PROCESS

2
Introduction

The project aims to develop an Android application that would give caregivers a better
way to monitor their patients. The app will be designed to collect sensory data from the patient
using wearable sensors. Bugs in programming are problems that need to be fixed (Banjo, 2017).
Bugs are a fact in Information Technology (IT) projects. Features, on the other hand, are
capabilities of software that are beneficial (Microsoft, 2018). A key goal of an IT project
manager and developers is to try as much as possible to eliminate bugs that may hinder the
proper functioning of an application and ensure that all necessary features are in place. Several
programs have been developed to aid in the tracking and management of bugs (Banjo, 2017).
The tools help remind developers about the problems that need to be fixed. Such a software
program will be utilized in this project.
Proposed Bug Tracking Software
A bug tracking software developed by a third-party will be used to track and manage
bugs throughout the project. One reason for selecting a third-party program is that several such
programs in the market are very effective in the tracking and management of bugs. A second
reason is that developing an i...


Anonymous
I use Studypool every time I need help studying, and it never disappoints.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Related Tags