Project Proposal-Part 3

Project Proposal-Part 2

CASE STUDY:

DATA MANAGEMENT SOFTWARE

Student’s Name

Institution Affiliation

Course Name

Professor’s Name

Date

CHAPTER 1 - INTRODUCTION

The world is becoming more and more technological with the majority of transactions applying the use of machines and computer-generated applications. For this reason, businesses require digitized methods of serving customers. This would ensure business processes serve customers in a effective and timely manner.

1.1 Operational Characteristics

Data management software is mandatory in any business since its main purpose is to collect data then convert it into meaningful form usable by business leaders. The data is stored in a database where different collection of similar data is aggregated. When a business provides its products and services, it is mandatory for them to monitor how customers receive and use the services. When there are many customers, it is mandatory for a business to have automatic methods of data getting transferred into the database. Since businesses have diverse methods of operating, it is a requirement to create a customized method of serving customers. The data management software proposed in this paper shall provide a clear step by step method of creating the software.

The fact that there are billions of bytes of data available on the internet every single day leads to the need of companies having proper technique of managing data (Naeem, 2020). Businesses that apply a data management software have a robust method of serving customers. It is easier to manage how customers respond to a particular product and service. This information is applicable for companies to develop strategic methods of gaining large market share. The return on investment realized when companies apply the software is high (Naeem, 2020). This proposal document shall provide a detailed work breakdown structure and project schedule which shall clearly explain how the data management software shall work.

1.2 Problem Description

This project proposal is aimed to identify various problems in customer service department of a company. There are companies that have been having operational issues in this sector yet tactics to implement the software lead to more vulnerabilities. These lead to issues with data security which is detrimental to a company’s operations.

Another problem discovered is that companies lack a proper technology team. This leads to improper technology implementation whereby software can be acquired but it is not suitable for the company’s business operations.

CHAPTER 2-OBJECTIVES

2.1 Objectives

Convenience – to provide convenience for employees with robust methods of performing small operational details of a company and to apply this to achieve mandated goals.

Revenue improvement – to use proper expertise a project manager to include IT support in the project so that all resources are used efficiently.

Great customer service – to provide customers with software that meets all their needs.

Versatility - to have a combatable data management software for the data available by using customized software that make work effective in an organization (Smith, 2020).

2.2 Proposed Software Solution

Data management software would improve organizational procedures to promote customer service. It would be easier to monitor business requirements since large volumes of data would be properly managed (Rogers et al., 2015).

CHAPTER 3 – METHODOLOGY

This section shall cover the steps to be taken to develop the system, data collection tools that will be used and why they shall be used; another component of this section is software and hardware requirements.

3.1 Data Collection Tools

The main methods to collect data shall be by conducting observations and documentation.

a) Observation

Observation as a data collection tool is a technique whereby the phenomena under study is monitored when it occurs. Since the phenomena under study is software, the major observation shall be by observing how users interact with the current point of sale software. The proposed project shall apply this technique because of the following reasons:

· -Observing allows an observer to use a simple technique of getting data which does not require much technical knowledge

· -a hypothesis can be formulated which creates an opportunity for the phenomena to be studied further. This shall thus result in new information about the phenomena being discovered.

· -This method shall provide an opportunity for innovation since upon studying the phenomena, various new ideas shall be discovered on how to improve the functional systems.

b) Documentation

Documentation is defined as “systematic procedure for reviewing or evaluating documents. It is a data collection tool which is concerned with documents that contain information about phenomena under study. The documents are retrieved from printed media, online repositories, websites and digital media. This method shall be suitable because of the following reasons:

· There exist variety of online repositories that contain information on how a point of sale system works.

· There are documents that provide information such as how a point of sale system log in interface shall appear to a user. With such documents as a reference only, the project shall be implemented to fit the proper format of a point of sale system.

· Information is readily available online and for free, thus it is unnecessary to interview very many people.

3.2 Work Breakdown Structure

The findings from all the data collection methods shall be analyzed and presented using graphics since the graphics shall display data collected under all topics. The most applicable graphics are bar graphs since they present concise trend in data that would not be apparent in other presentation methods such as tables.

3.2 Communication Plan

The deployment of the project would require incorporation of all participants of the organization. Quality assurance is an intricate step as it collects feedback for the implementation.

3.3 Software and Personnel Requirements

This section contains all software components and developers to be used to implement the project. There shall be IT staff, developers, and data specialists. The equipment required would be a resource center, internet connection, and computers.

CHAPTER 4-SCHEDULE AND BUDGET

4.1 Schedule

ScheduleMonth 1Month 2Month 3Month 4Month 5Month 6Month 7Month 8Month 9Month 10Month 11Month 12

Preparation

Brainstorming

Problem definition

Context and definitions

Establish goals

Document every requirement

Involve correct stakeholders

Active analysis of input

Create validation plan

Define system specifications

Test proposed modules

Develop accurate report

Market analysis

Environmental analysis

Setting development procedure

Conducting surveys

Trianing of employees

Installation of new software

Involvement of customers in testing

Final verification

Planning of tests

Design of tests

Execution of tests with developmnet team and customers

Defining key variables for development

Implement any changes after testing

Verification of customer engagement

Determine method of deployment

Monitoring employee and customer engagement

Fixing any usability issues

This section provides the concise list of activities that shall be conducted during the implementation period of the project.

4.2 Budget

This section provides the accurate amount of money required for the project’s development and deployment. The total money required to pay staff is $1,500,000 for the duration of 12 months where each gets $150,000. Purchase of resources would require $200,000. Total budget is $1,700,000.

Reference

Naeem, T. (2020). Data Management Software: A Beginner’s Guide. Retrieved 30 November 2020 from https://www.astera.com/type/blog/data-management-software/

Rogers, P., Pawlik, L., & Shwom, B. (2015). The Role of Deliverables in Project Work. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.2576748

Smith, T. (2020). What Are 8 Milestones Every Software Project Should Have? - SOLTECH. SOLTECH. Retrieved 16 November 2020, from https://soltech.net/what-are-8-milestones-every-software-project-should-have/ .

Sheet1

Schedule

Month 1

Month 2

Month 3

Month 4

Month 5

Month 6

Month 7

Month 8

Month 9

Month 10

Month 11

Month 12

Preparation

Brainstorming

Problem definition

Context and definitions

Establish goals

Document every requirement

Involve correct stakeholders

Active analysis of input

Create validation plan

Define system specifications

Test proposed modules

Develop accurate report

Market analysis

Environmental analysis

Setting development procedure

Conducting surveys

Trianing of employees

Installation of new software

Involvement of customers in testing

Final verification

Planning of tests

Design of tests

Execution of tests with developmnet team and customers

Defining key variables for development

Implement any changes after testing

Verification of customer engagement

Determine method of deployment

Monitoring employee and customer engagement

Fixing any usability issues