Get Instant Help From 5000+ Experts For
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing:Proofread your work by experts and improve grade at Lowest cost

And Improve Your Grades
myassignmenthelp.com
loader
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Guaranteed Higher Grade!
Free Quote
wave

 What is your project going to accomplish How does this project relate to overall goals and objectives of the company It is part of a program or larger project

What will this project create What is the product of the project At a high level, how do you plan on doing the work of the project What are the high-level deliverables for this project

Objectives

What objectives, if any, of the company is this project designed to meet

Business Need

Why should we do this project What will be gained, changed, or modified Is there a financial or business reason to do this project This area should contain any feasibility studies, NPV, PI, PB, or PBD used to advance the project.

Project Manager and Stakeholders

Who will lead this project Who are the major stakeholders

Milestones

What are the key milestone dates associated with the project

Budget

What is the order-of-magnitude budget for this project

User Acceptance Criteria/Quality

What are the minimum success criteria as defined by the key stakeholders

What are the major risks affecting the project.

Objectives

After successful completion of the project the company would be able to create high quality cloud based software for the accounting companies to avoid the security level risks.The products of the project are cloud based server for storing and managing information in an advanced way rather than manual data management.

 In order to complete and execute the project successfully it is necessary for the project manager to plan accurately. As, it is regarding development of a cloud based software thus at the very initial phase the project team members should be selected and recruited carefully considering their knowledge and professional skills. Then the requirement of the accounting companies and the current issues they have been facing due to lack of technical failure and application level errors. In order to mitigate these issues, proper technical requirements should be adopted. Then, based on the type of accounting organizational applications platform for software and hardware should be hired by the software developer.

The high level deliverable of the project is to complete the project within estimated time phase, budget allotted by the project developer. In order to develop such project it is necessary to consider accurate hardware and software platform. Another deliverable of the project is to consider proper resources those are required for the project development so that during the project development phase, the developers could avoid the resource level issues. Another important deliverable of the project is to deliver security to the accounting companies.

Objectives

Ø To understand current application level issues facing by the accounting companies of United States.

Ø To develop a cloud based software for United States based  accounting companies

Ø To analyze the detail requirements of accounting company’s software

Business Need

This particular software project is required to be developed for resolving the issues of United States based accounting companies. After successful completion of the project, the project manager would be able to gain competitive advantages for Abacus Data System Company. In addition to this, the company would also gain effective and structured revenue regardless of the input to the processes such as information, documents, panning, equipments, money software etc. Manual information is referred to as one of the most issues and with the help of this particular software the data could be managed mush efficiently. However, the expected outcomes from this project include consultation, project plan, tools, software, results from the testing etc. the security aspects would be modified.

The reasons behind the development of this particular project are both financial and business based. If this particular project is completed successfully then, Abacus Data System would gain measurable revenue and the accounting companies would be able to secure the confidential information from the external attackers. In order to complete this particular software development project, NPV feasibility calculation has been done.

Project Manager and Stakeholders

Name of the project manager

Apart from project manager the other project stakeholders associated to the project are the finance manager, software developer, and tester, application programming manager, coder, program analyst, business analyst and HR manager. For completing this project, all the stakeholders should take part actively in the project development.  

Milestones

WBS

Task Name

Duration

Start

Finish

0

Schedule for cloud based software development

185 days

Tue 10/24/17

Mon 7/9/18

1

   Project initiation

105 days

Tue 10/24/17

Mon 3/19/18

1.1

      Understanding the details of cloud based software

14 days

Tue 10/24/17

Fri 11/10/17

1.2

      Understanding the issues of accounting companies

7 days

Mon 11/13/17

Tue 11/21/17

1.3

      Feasibility testing

11 days

Mon 2/26/18

Mon 3/12/18

1.4

      Identifying the issues with traditional system

6 days

Fri 2/16/18

Fri 2/23/18

1.5

      Identification of risks

15 days

Wed 11/22/17

Tue 12/12/17

1.6

      Vendor selection

16 days

Wed 12/13/17

Wed 1/3/18

1.7

      Project kick off

8 days

Fri 1/19/18

Tue 1/30/18

1.8

      Specification on the software requirements

5 days

Tue 3/13/18

Mon 3/19/18

1.9

      Milestone 1: Completion of project initiation phase

0 days

Mon 3/19/18

Mon 3/19/18

2

   Project planning

64 days

Wed 12/13/17

Mon 3/12/18

2.1

      Budget estimation

15 days

Thu 1/4/18

Wed 1/24/18

2.2

      Preparation of software project tender

32 days

Wed 12/13/17

Thu 1/25/18

2.3

      Software requirement workshop specification

10 days

Thu 1/25/18

Wed 2/7/18

2.4

      Identification of project stakeholders

12 days

Fri 2/23/18

Mon 3/12/18

2.5

      Software design entry

11 days

Thu 2/8/18

Thu 2/22/18

2.6

      Time estimation for the project

14 days

Wed 12/13/17

Mon 1/1/18

2.7

      Adoption of software requirement standard

11 days

Thu 1/4/18

Thu 1/18/18

2.8

      Milestone 2: Completion of project planning phase

0 days

Thu 1/18/18

Thu 1/18/18

3

   Project development

62 days

Fri 1/26/18

Mon 4/23/18

3.1

      Understanding the details of software architecture

12 days

Wed 1/31/18

Thu 2/15/18

3.2

      Requirement elicitation

7 days

Mon 2/26/18

Tue 3/6/18

3.3

      Understanding architectural view of the system

5 days

Wed 3/7/18

Tue 3/13/18

3.4

      Developing the design view

5 days

Tue 3/13/18

Mon 3/19/18

3.5

      Developing design entity

10 days

Fri 1/26/18

Thu 2/8/18

3.6

      Development of quality matter

11 days

Tue 3/20/18

Tue 4/3/18

3.7

      Development of functional safety management

6 days

Fri 2/9/18

Fri 2/16/18

3.8

      Development of system architecture

14 days

Wed 4/4/18

Mon 4/23/18

3.9

      Milestone 3: Completion of project development phase

0 days

Mon 4/23/18

Mon 4/23/18

4

   Project testing

38 days

Tue 4/24/18

Thu 6/14/18

4.1

      Review project requirement

10 days

Tue 4/24/18

Mon 5/7/18

4.2

      Development of Critical design

6 days

Fri 5/25/18

Fri 6/1/18

4.3

      Developing test planning

9 days

Mon 6/4/18

Thu 6/14/18

4.4

      Review operational activities

3 days

Mon 6/4/18

Wed 6/6/18

4.5

      Design modeling

4 days

Mon 5/21/18

Thu 5/24/18

4.6

      Coding

6 days

Fri 5/11/18

Fri 5/18/18

4.7

      Quality control

8 days

Tue 5/8/18

Thu 5/17/18

4.8

      User acceptance criteria testing

9 days

Tue 4/24/18

Fri 5/4/18

4.9

      Unit testing

4 days

Mon 5/7/18

Thu 5/10/18

4.10

      Integration testing

5 days

Mon 6/4/18

Fri 6/8/18

4.11

      Final field testing

6 days

Fri 5/18/18

Fri 5/25/18

4.12

      Milestone 4: Completion of project testing phase

0 days

Fri 5/25/18

Fri 5/25/18

5

   Project execution

25 days

Mon 5/28/18

Fri 6/29/18

5.1

      Process refinement

4 days

Mon 6/11/18

Thu 6/14/18

5.2

      Program implementation

5 days

Fri 6/15/18

Thu 6/21/18

5.3

      Considering options for data capture resources

8 days

Mon 5/28/18

Wed 6/6/18

5.4

      Program controlling

9 days

Fri 6/15/18

Wed 6/27/18

5.5

      Approval process development

6 days

Fri 6/22/18

Fri 6/29/18

5.6

      SaaS plan form incorporation

10 days

Thu 6/7/18

Wed 6/20/18

5.7

      Milestone 5: completion of project execution phase

0 days

Wed 6/20/18

Wed 6/20/18

6

   Project closure

6 days

Mon 7/2/18

Mon 7/9/18

6.1

      Stakeholder signoff

2 days

Mon 7/2/18

Tue 7/3/18

6.2

      Prost project evaluation

2 days

Wed 7/4/18

Thu 7/5/18

6.3

      Long term maintenance planning development

1 day

Fri 7/6/18

Fri 7/6/18

6.4

      Final documentation

1 day

Mon 7/9/18

Mon 7/9/18

6.5

      Milestone 6: Completion of project closure phase

0 days

Mon 7/9/18

Mon 7/9/18

WBS

Task Name

Duration

Start

Finish

Cost Variance

0

Schedule for cloud based software development

185 days

Tue 10/24/17

Mon 7/9/18

$74,232.00

1

   Project initiation

105 days

Tue 10/24/17

Mon 3/19/18

$16,400.00

1.1

      Understanding the details of cloud based software

14 days

Tue 10/24/17

Fri 11/10/17

$3,808.00

1.2

      Understanding the issues of accounting companies

7 days

Mon 11/13/17

Tue 11/21/17

$1,064.00

1.3

      Feasibility testing

11 days

Mon 2/26/18

Mon 3/12/18

$1,320.00

1.4

      Identifying the issues with traditional system

6 days

Fri 2/16/18

Fri 2/23/18

$1,632.00

1.5

      Identification of risks

15 days

Wed 11/22/17

Tue 12/12/17

$3,720.00

1.6

      Vendor selection

16 days

Wed 12/13/17

Wed 1/3/18

$2,560.00

1.7

      Project kick off

8 days

Fri 1/19/18

Tue 1/30/18

$896.00

1.8

      Specification on the software requirements

5 days

Tue 3/13/18

Mon 3/19/18

$1,400.00

1.9

      Milestone 1: Completion of project initiation phase

0 days

Mon 3/19/18

Mon 3/19/18

$0.00

2

   Project planning

64 days

Wed 12/13/17

Mon 3/12/18

$24,392.00

2.1

      Budget estimation

15 days

Thu 1/4/18

Wed 1/24/18

$1,800.00

2.2

      Preparation of software project tender

32 days

Wed 12/13/17

Thu 1/25/18

$7,424.00

2.3

      Software requirement workshop specification

10 days

Thu 1/25/18

Wed 2/7/18

$3,120.00

2.4

      Identification of project stakeholders

12 days

Fri 2/23/18

Mon 3/12/18

$3,648.00

2.5

      Software design entry

11 days

Thu 2/8/18

Thu 2/22/18

$2,992.00

2.6

      Time estimation for the project

14 days

Wed 12/13/17

Mon 1/1/18

$2,240.00

2.7

      Adoption of software requirement standard

11 days

Thu 1/4/18

Thu 1/18/18

$3,168.00

2.8

      Milestone 2: Completion of project planning phase

0 days

Thu 1/18/18

Thu 1/18/18

$0.00

3

   Project development

62 days

Fri 1/26/18

Mon 4/23/18

$9,408.00

3.1

      Understanding the details of software architecture

12 days

Wed 1/31/18

Thu 2/15/18

$0.00

3.2

      Requirement elicitation

7 days

Mon 2/26/18

Tue 3/6/18

$784.00

3.3

      Understanding architectural view of the system

5 days

Wed 3/7/18

Tue 3/13/18

$560.00

3.4

      Developing the design view

5 days

Tue 3/13/18

Mon 3/19/18

$1,160.00

3.5

      Developing design entity

10 days

Fri 1/26/18

Thu 2/8/18

$1,120.00

3.6

      Development of quality matter

11 days

Tue 3/20/18

Tue 4/3/18

$1,496.00

3.7

      Development of functional safety management

6 days

Fri 2/9/18

Fri 2/16/18

$816.00

3.8

      Development of system architecture

14 days

Wed 4/4/18

Mon 4/23/18

$3,472.00

3.9

      Milestone 3: Completion of project development phase

0 days

Mon 4/23/18

Mon 4/23/18

$0.00

4

   Project testing

38 days

Tue 4/24/18

Thu 6/14/18

$12,304.00

4.1

      Review project requirement

10 days

Tue 4/24/18

Mon 5/7/18

$2,960.00

4.2

      Development of Critical design

6 days

Fri 5/25/18

Fri 6/1/18

$1,632.00

4.3

      Developing test planning

9 days

Mon 6/4/18

Thu 6/14/18

$2,448.00

4.4

      Review operational activities

3 days

Mon 6/4/18

Wed 6/6/18

$888.00

4.5

      Design modeling

4 days

Mon 5/21/18

Thu 5/24/18

$1,184.00

4.6

      Coding

6 days

Fri 5/11/18

Fri 5/18/18

$864.00

4.7

      Quality control

8 days

Tue 5/8/18

Thu 5/17/18

$960.00

4.8

      User acceptance criteria testing

9 days

Tue 4/24/18

Fri 5/4/18

$1,368.00

4.9

      Unit testing

4 days

Mon 5/7/18

Thu 5/10/18

$0.00

4.10

      Integration testing

5 days

Mon 6/4/18

Fri 6/8/18

$0.00

4.11

      Final field testing

6 days

Fri 5/18/18

Fri 5/25/18

$0.00

4.12

      Milestone 4: Completion of project testing phase

0 days

Fri 5/25/18

Fri 5/25/18

$0.00

5

   Project execution

25 days

Mon 5/28/18

Fri 6/29/18

$10,256.00

5.1

      Process refinement

4 days

Mon 6/11/18

Thu 6/14/18

$544.00

5.2

      Program implementation

5 days

Fri 6/15/18

Thu 6/21/18

$680.00

5.3

      Considering options for data capture resources

8 days

Mon 5/28/18

Wed 6/6/18

$1,216.00

5.4

      Program controlling

9 days

Fri 6/15/18

Wed 6/27/18

$3,528.00

5.5

      Approval process development

6 days

Fri 6/22/18

Fri 6/29/18

$1,728.00

5.6

      SaaS plan form incorporation

10 days

Thu 6/7/18

Wed 6/20/18

$2,560.00

5.7

      Milestone 5: completion of project execution phase

0 days

Wed 6/20/18

Wed 6/20/18

$0.00

6

   Project closure

6 days

Mon 7/2/18

Mon 7/9/18

$1,472.00

6.1

      Stakeholder signoff

2 days

Mon 7/2/18

Tue 7/3/18

$592.00

6.2

      Prost project evaluation

2 days

Wed 7/4/18

Thu 7/5/18

$320.00

6.3

      Long term maintenance planning development

1 day

Fri 7/6/18

Fri 7/6/18

$304.00

6.4

      Final documentation

1 day

Mon 7/9/18

Mon 7/9/18

$256.00

6.5

      Milestone 6: Completion of project closure phase

0 days

Mon 7/9/18

Mon 7/9/18

$0.00

User Acceptance Criteria/Quality

For success of the software project the stakeholders defined certain key factors in terms of acceptance criteria. For this particular project the minimum success criteria are as follows:

Success criteria

Success factor

Commercial success

Project mission

Meeting the requirement of the users

Support from the management authority

Meeting the project budget

Project planning and scheduling

Satisfied users

Client consultation

Purpose achievement

Personnel

Meeting to project timescale

Technical tasks

Meeting the project quality

Project monitoring and feedback

Development of co ordinate project team

Accurate communication

Achieving the project safety standards

Troubleshooting

Acceptance criteria from the client perspectives

Stakeholder management

Long term success

Constant  training and development program

Major Risks

Poor leadership: One of the common problems in project management implies lack of leadership and motivation of the project manager. The project manager fails to manage the project team members properly and as a result the team co ordination is getting contradicted and due to intra team and inter team conflict the project fails to meet to meet the objectives.

Lack of resources: In the project initiation phase the project head fails to identify all the required resources, thus during the execution phase the project manager is facing major issues throughout.

Changing business strategies: Due to continuous technical development the project manager and technical head are incorporating technical components to the project. As a result the business strategies of the software project also keep on changing. The project team members fail to adopt those frequently changing strategies which are another major risk for the project. 

Continuity failure: If the project manager fails to consider accurate activity linking aspects then the flow of the project will be interrupted which is another project risk.

Project Manager Authority Level

The project manager is responsible to control and monitor the project details properly. It will help the project team members to identify the details and complete the project within estimated times phase and budget as well. Not only this but also, the strategies and business components could be effectively executed with the help of the project manager.

Project Core Team

Finance manager: The finance manager is responsible to estimate the project budget.

HR manager: Responsible to manage the human resources associated to the project

Coder: Responsible to develop the code for the cloud based software

Tester: Whether the codes are correctly executed or not is tested by the project tester

Program analysts: The program analysts analyzes the project

Business analyst: The business analyst analyzes the business details that is whether the software will be beneficial for the company or not.

Operation manager: The operational and functional components of the system are measured by the operation manager.

Subject Matter Experts (SMEs) (include company and channel designations if applicable)

NA

Ahern, T., Leavy, B., & Byrne, P. J. (2014). Complex project management as complex problem solving: A distributed knowledge management perspective. International Journal of Project Management, 32(8), 1371-1381.

Boud, D., Cohen, R., & Sampson, J. (Eds.). (2014). Peer learning in higher education: Learning from and with each other. Routledge.

Browning, T.R. &Ramasesh, R.V., (2015). Reducing unwelcome surprises in project management. MIT Sloan Management Review, 56(3), p.53.

Burke, R., (2013). Project management: planning and control techniques. New Jersey, USA.

Conforto, E. C., Salum, F., Amaral, D. C., da Silva, S. L., & de Almeida, L. F. M. (2014). Can agile project management be adopted by industries other than software development?. Project Management Journal, 45(3), 21-34.

Drury-Grogan, M.L., (2014). Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors. Information and Software Technology, 56(5), pp.506-515.

Fleming, Q.W. &Koppelman, J.M., ((2016)), December. Earned value project management. Project Management Institute.

Heldman, K. (2015). PMP project management professional exam deluxe study guide: updated for the 2015 Exam. John Wiley & Sons.

Hornstein, H. A. (2015). The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), 291-298.

Jalal, M.P. &Koosha, S.M., (2015). Identifying organizational variables affecting project management office characteristics and analyzing their correlations in the Iranian project-oriented organizations of the construction industry. International Journal of Project Management, 33(2), pp.458-466.

Joslin, R., & Müller, R. (2015). Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), 1377-1392.

Kerzner, H., (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Kwak, Y.H., Walewski, J., Sleeper, D. &Sadatsafavi, H., (2014). What can we learn from the Hoover Dam project that influenced modern project management?. International Journal of Project Management, 32(2), pp.256-264.

Larson, E. W., & Gray, C. (2013). Project Management: The Managerial Process with MS Project. McGraw-Hill.

Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project risk management methodology for small firms. International Journal of Project Management, 32(2), 327-340.

Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), 202-217.

Pemsel, S., & Wiewiora, A. (2013). Project management office a knowledge broker in project-based organisations. International Journal of Project Management, 31(1), 31-42.

Sanchez, M. A. (2015). Integrating sustainability issues into project management. Journal of Cleaner Production, 96, 319-330.

Schwalbe, K. (2015). Information technology project management. Cengage Learning.

Todorovic, M. L., Petrovi?, D. ?., Mihic, M. M., Obradovic, V. L., & Bushuyev, S. D. (2015). Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), 772-783.

Turner, R. (2016). Gower handbook of project management. Routledge.

Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.

Walker, A. (2015). Project management in construction. John Wiley & Sons.

Cite This Work

To export a reference to this article please select a referencing stye below:

My Assignment Help. (2021). Cloud-Based Software Development For Accounting Companies - An Essay.. Retrieved from https://myassignmenthelp.com/free-samples/proj586-project-management-systems/data-management.html.

"Cloud-Based Software Development For Accounting Companies - An Essay.." My Assignment Help, 2021, https://myassignmenthelp.com/free-samples/proj586-project-management-systems/data-management.html.

My Assignment Help (2021) Cloud-Based Software Development For Accounting Companies - An Essay. [Online]. Available from: https://myassignmenthelp.com/free-samples/proj586-project-management-systems/data-management.html
[Accessed 29 March 2024].

My Assignment Help. 'Cloud-Based Software Development For Accounting Companies - An Essay.' (My Assignment Help, 2021) <https://myassignmenthelp.com/free-samples/proj586-project-management-systems/data-management.html> accessed 29 March 2024.

My Assignment Help. Cloud-Based Software Development For Accounting Companies - An Essay. [Internet]. My Assignment Help. 2021 [cited 29 March 2024]. Available from: https://myassignmenthelp.com/free-samples/proj586-project-management-systems/data-management.html.

Get instant help from 5000+ experts for
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing: Proofread your work by experts and improve grade at Lowest cost

loader
250 words
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Plagiarism checker
Verify originality of an essay
essay
Generate unique essays in a jiffy
Plagiarism checker
Cite sources with ease
support
Whatsapp
callback
sales
sales chat
Whatsapp
callback
sales chat
close