Final Project Plan

Business Requirement

Thien Thai

CIS599

Professor Wade M. Poole

Strayer University

Jan 31, 2020

Business Requirement

In order to secure information and database framework and achieve operational target, network base computing included IT framework has been continuing to develop. This paper will describe, analyze, and speculate the scope of the project. Important information about risks, constraints, and assumptions will also be discussed in this paper. Then it will talk about needed integration with other systems and infrastructure. The human capital and possible outsourcing or offshoring will be addressed to accomplish project. Finally, this paper will provide terms in the project and include cost projections.

1 Document Control

Change Record

Date	Author	Version	Change Reference
01/31/2019	Thien Thai	1.0	Review

Reviewers

Name	Position
Thien Thai	CIO

1 Business Requirements

1.1 Project Overview

The project entails development of a mobile application that will help the customers, find company’s information pertaining products and services, contact the company for assistance and perform self-care requests through their account area without customer service intervention.

1.2 Background including current process

This project is intended to ease the company’s display of information as well as access to service. Customers prefer a common area where all their company products and service subscriptions can be accessed without experiencing the limitations of a common web browser.

The project goal is to make an application that will log the customers to company personal account.

The IT role for this project is to ensure that the information updates and the application development is correct and to the desired security standards, layout and adhering to international standards.

1.3 Scope

1.3.1 Scope of Project

According to Kerzner in 2017, before the establishment of every project, the scope must be developed. This will act sat the guide throughout project development. The scope for this project will include the following items and holding a meeting with sponsors of the project. The project manager and the key development team shall conduct a meeting to discuss project support and finances. For each following item, there should be a corresponding strategy for incorporating these areas into the overall project.

Applications - we will use the mobile applications to meet the target production date.

Sites - the Google play store and the Appstore.

Process Re-engineering - Re-engineering will ensure that the application is user friendly to all the stakeholders and it’s completed on set time.

Customization - Customizations will be limited to the customer/public user interface, the client area dashboard and the staff backend dashboard.

Interfaces – it included customer/public user, the client dashboard, and the staff backend dashboard

Architecture – IT department will provide Application and Technical Architecture.

Conversion - Only the following data and volume will be considered for conversion: the company’s public data.

Testing - Testing will include only the compatibility of the application on various phone, tablets, and iPad models.

Funding It is limited to:

Staffing- $ 60000

Hosting – $ 5000

Computers - $10000

Data center - $5000

Training - Training will be conducted by the IT department to the customer service department.

Education - Education will include:

· Development of cross-platform applications

· Skills on UI/UX

· Any three of programming languages like C# and Java, API (Apple iOS, android & Windows Mobile), web development (HTML5 & CSS)

· Cross-platform suites for mobile (Antenna and AMP)

1.3.2 Constraints and Assumptions

The following constraints have been identified:

· The size of the screen, the sensors, as well as the interactions

· The storage sizes and the cache sizes

· Latencies

· Issues with network

· Requirements for use of data

· The type of fonts, the language to be used and the tome of the voice

The following assumptions have been made in defining the scope, objectives, and approach:

· The technology, as well as the toolset available, will be able to create the application till completion

· Enough financial and human resources set aside will be able to cater to the application’s development.

· Every item included in the development process will go according to the plan.

1.3.3 Risks

According to Muriana and Vizzini in 2017, during the development and implementation of any project, it is likely to encounter several risks. The following risks have been identified as possibly affecting the project during its progression:

· Building an application that is not wanted by the users

· Unsustainable growth in the number of users

· Choosing wrong task management partners

· Breaches in the application's security

· Risk of tying the development to one platform 

1.3.4 Scope Control

Change requests will be used in controlling the scope. This method is the requested changes emanating from the scope analysis that business owner representative will make approval for any changes that affect cost or timeline for the project. According to Johansson and Persson in 2019, we give high priority to outsourcing because it seems to be cheaper than offshoring due to differences in the values of currency. Another way in which project scope will be controlled is through the use of updates from the project management plan – the main areas in which the updates will likely emanate from includes the following; updates from scope baseline, the cost baseline, performance control baseline, and project schedule baseline. Of all these, change requests and work performance information will be given the highest priority during the control of the project scope.

1.3.5 Relationship to Other Systems/Projects

It is the responsibility of the business unit to inform IT of other business initiatives that may impact the project. The following are known business initiatives: the application will have a shared database with the website of the company. This will ensure that data provided by the company, requested, and received by the customers whether on web or mobile app is same at any given instance. The most important integration that the system will need to have is database integration – a proper integration with data storage is important because the system will perform Read-Write functions for data and information it requires for an effective business transaction.

1.3.6 Definition of Terms (if applicable)

The terms that will be used thought the project include the following:

i. SA – System Analyst. These are the people who work on system analysis.

ii. SD – System Developers. These are the people who work on system development (coding and documentation).

iii. DBA – Database Administrator. These are the individuals who work on the design and development of data databases.

iv. NE – Network Engineers (NE). Part of the development team that develope a secure network infrastructure for the system.

v. Application programming interface (API) - specifications of how the app interacts with other components of the software. 

vi. Business to customer – a mobile application that is built for an average customer

vii. Hybrid app- a mobo-app that has been coded in HTML, CSS, and JavaScript that makes use of the web to native abstraction layer.

Conclusion

Database is the the main key of an organization in order to meet business requirement. it keep organization protected. Itsfunction depends upon the safety specifications that are followed by the IT department and implemented inside the network of administration, further following the laid protocols.

References

Johansson, B., & Persson, R. (2019). Offshore Outsourcing: An IT-Manager Perspective on Cultural Differences. In 2019 Joint International Conference on Perspectives in Business Informatics Research Workshops and Doctoral Consortium, BIR-WS 2019 (Vol. 2443, pp. 140-152). CEUR.

Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.

Muriana, C., & Vizzini, G. (2017). Project risk management: A deterministic quantitative technique for assessment and mitigation. International Journal of Project Management, 35(3), 320-340.