COIT20248: Information Systems Analysis and Design Assessment 1 Report
VerifiedAdded on 2023/01/23
|12
|3080
|81
Report
AI Summary
This report analyzes the development of a hospital information system, addressing key aspects such as the project's aims and objectives, and the selection of an appropriate system development approach. The report compares Waterfall and Agile methodologies, ultimately advocating for the Agile approach due to its iterative nature and customer satisfaction benefits. It details the system's functional and non-functional requirements, including external interfaces, e-prescription facilities, performance, data security, and scalability. A cost-benefit analysis is presented, showing the project's financial viability and a return on investment. The report also includes a work breakdown structure and Gantt chart for project scheduling, emphasizing the importance of these tools for effective project management. Finally, it identifies stakeholders and system information investigation techniques like sampling documents, prototyping, and interviews used to gather requirements.

COIT 20248: Information Systems Analysis and Design
Term 1, 2019
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number
Term 1, 2019
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Table of Contents
1. Introduction.......................................................................................................................................1
2. Approach to Systems Development..................................................................................................1
3. Systems Requirements......................................................................................................................2
4. Project Cost Benefit Analysis.............................................................................................................3
5. Project Schedule................................................................................................................................4
6. System Information Requirement Investigation Techniques.............................................................7
7. Reflections and Conclusions..............................................................................................................7
References.............................................................................................................................................9
1. Introduction.......................................................................................................................................1
2. Approach to Systems Development..................................................................................................1
3. Systems Requirements......................................................................................................................2
4. Project Cost Benefit Analysis.............................................................................................................3
5. Project Schedule................................................................................................................................4
6. System Information Requirement Investigation Techniques.............................................................7
7. Reflections and Conclusions..............................................................................................................7
References.............................................................................................................................................9

1. Introduction
The paper mainly focuses on information system that is used in the hospitals. It is
found that the information system that is used in hospitals are unable to manage the data
as well as operations of the hospital in a very much efficient way but as the hospitals
generate huge amount of data as well as information therefore it is quite necessary to
develop a new information system that can be able to manage the flow of information quite
efficiently for providing interdependent support to the other functional and non –function
requirement. It is assumed that the entire system will be developed successfully within the
budget that is around $750,000.
Project aim
The main aim of the project is to analyze the issues that are present within the
present information system in order to develop a new information system so that current
issues ad challenges that the hospital is facing can get resolved.
Project objectives
The objectives of the project are mainly listed below:
To develop an information system for the hospital
To identify the issues that are mainly associated with the system
To resolve the problems that are mainly related with the current system
2. Approach to Systems Development
The information system will be developed by selecting proper system development
approach that is mainly suitable for the project. It is found that proper selection of the system
development approach is quite beneficial for developing the entire system quite successfully.
According to Chauhan, Rana and Sharma (2017) waterfall methodology is considered as one
of the traditional software development methodology. It is considered as one of the linear
methodology that mainly consists of number of different phases in sequence for accomplishing the
goals as well as objectives of the project. It is found that each phase of the project must be 100% be
complete before coming to the next phase of the project. It is found that the lean nature of the
methodology generally makes it simple as well as quite easy to understand. On the other hand, it is
stated by Patwardhan et al. (2016) that agile methodology is one of the iterative approach for
planning as well as guiding the entire procedures of the project. The main advantages that are
achieved by using the agile methodology is that it helps in providing higher customer satisfaction as
well as helps in keeping proper control on the project. Furthermore, it helps in minimizing the risks
and challenges that are mainly associated with the project. Furthermore, is considered as one of the
development procedure that helps in producing proper quality of the system with very much little
investment on the cost.
Page 1
The paper mainly focuses on information system that is used in the hospitals. It is
found that the information system that is used in hospitals are unable to manage the data
as well as operations of the hospital in a very much efficient way but as the hospitals
generate huge amount of data as well as information therefore it is quite necessary to
develop a new information system that can be able to manage the flow of information quite
efficiently for providing interdependent support to the other functional and non –function
requirement. It is assumed that the entire system will be developed successfully within the
budget that is around $750,000.
Project aim
The main aim of the project is to analyze the issues that are present within the
present information system in order to develop a new information system so that current
issues ad challenges that the hospital is facing can get resolved.
Project objectives
The objectives of the project are mainly listed below:
To develop an information system for the hospital
To identify the issues that are mainly associated with the system
To resolve the problems that are mainly related with the current system
2. Approach to Systems Development
The information system will be developed by selecting proper system development
approach that is mainly suitable for the project. It is found that proper selection of the system
development approach is quite beneficial for developing the entire system quite successfully.
According to Chauhan, Rana and Sharma (2017) waterfall methodology is considered as one
of the traditional software development methodology. It is considered as one of the linear
methodology that mainly consists of number of different phases in sequence for accomplishing the
goals as well as objectives of the project. It is found that each phase of the project must be 100% be
complete before coming to the next phase of the project. It is found that the lean nature of the
methodology generally makes it simple as well as quite easy to understand. On the other hand, it is
stated by Patwardhan et al. (2016) that agile methodology is one of the iterative approach for
planning as well as guiding the entire procedures of the project. The main advantages that are
achieved by using the agile methodology is that it helps in providing higher customer satisfaction as
well as helps in keeping proper control on the project. Furthermore, it helps in minimizing the risks
and challenges that are mainly associated with the project. Furthermore, is considered as one of the
development procedure that helps in producing proper quality of the system with very much little
investment on the cost.
Page 1
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

After analyzing all the system development methodology, it is found that agile system
development approach is mainly appropriate for the project. This is because, with the help of agile
approach is one of the practice that helps in promoting iteration of development as well as testing
within the entire software development lifecycle of the project. It is found that utilization of agile
project methodology helps in increasing customer satisfaction and assists in increasing control on
the entire project (Sanders et al. 2016). Furthermore, the risks that are mainly associated with the
project are generally identified so that the progress of the project does not get impacted.
3. Systems Requirements
The system requirements are mainly defined as the configuration that is generally
needed within the system in order to have a software and hardware application for running
the system smoothly as well as efficiently. The system requirements are generally
categorized into functional requirements as well as non-functional requirements.
Functional requirements: The functional requirements for the hospital information system are
generally elaborated below:
External interface: Proper external interface is needed that is helps in providing less
response time so that the customers can be able to get better experience while utilizing the
system.
Facility of E-prescription: E-prescription facility should be present within the system so that
the patients can be able to use the prospection whenever they need it by logging within the
system (Badewi 2016).
Business case: It is quite necessary to align the business requirements with the system
requirements so that the project goals and objectives of the project can be achieved quite
successfully.
Non-functional requirements: The non-functional requirements of the Hospital information
system are generally elaborated below:
Performance: It is identified that the response time should be kept minimum such that the
users of the system does not face any challenges while using the system and can be able to
work effectively within the system.
Data security: Proper security facility must be provided by the system such that the system
must be able to keep the various information as well as data of the patients confidential
such that the security issues and challenges that are associated with the system can
generally get resolved (Svejvig and Andersen 2015).
Scalability: The changes that is required in the system needs to be integrated with the new
system that is required to be developed for the hospital such that with the development of
the system, the project goals as well as objectives can be achieved quite successfully.
Page 2
development approach is mainly appropriate for the project. This is because, with the help of agile
approach is one of the practice that helps in promoting iteration of development as well as testing
within the entire software development lifecycle of the project. It is found that utilization of agile
project methodology helps in increasing customer satisfaction and assists in increasing control on
the entire project (Sanders et al. 2016). Furthermore, the risks that are mainly associated with the
project are generally identified so that the progress of the project does not get impacted.
3. Systems Requirements
The system requirements are mainly defined as the configuration that is generally
needed within the system in order to have a software and hardware application for running
the system smoothly as well as efficiently. The system requirements are generally
categorized into functional requirements as well as non-functional requirements.
Functional requirements: The functional requirements for the hospital information system are
generally elaborated below:
External interface: Proper external interface is needed that is helps in providing less
response time so that the customers can be able to get better experience while utilizing the
system.
Facility of E-prescription: E-prescription facility should be present within the system so that
the patients can be able to use the prospection whenever they need it by logging within the
system (Badewi 2016).
Business case: It is quite necessary to align the business requirements with the system
requirements so that the project goals and objectives of the project can be achieved quite
successfully.
Non-functional requirements: The non-functional requirements of the Hospital information
system are generally elaborated below:
Performance: It is identified that the response time should be kept minimum such that the
users of the system does not face any challenges while using the system and can be able to
work effectively within the system.
Data security: Proper security facility must be provided by the system such that the system
must be able to keep the various information as well as data of the patients confidential
such that the security issues and challenges that are associated with the system can
generally get resolved (Svejvig and Andersen 2015).
Scalability: The changes that is required in the system needs to be integrated with the new
system that is required to be developed for the hospital such that with the development of
the system, the project goals as well as objectives can be achieved quite successfully.
Page 2
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4. Project Cost Benefit Analysis
Cost benefit analysis is defined as one of the systematic approach that is mainly used in
order to estimate the strengths as weaknesses that are generally utilized for determining the
different options that are helpful in achieving proper benefits (Sanders et al. 2016). It is found that
in the project of information system development, it is quite necessary to undertake cost benefit
analysis in order to check the project feasibility and for making sure that the project that was
undertaken will bring benefit for the organization. It is found that by performing proper cost benefit
analysis helps in giving proper opportunity that delve for developing the information system
successfully. The table that is provided below reflects on the entire calculation that is used for
showcasing the cost benefit calculation and as per the calculation, the ROI that is achieved will be
around 0.1445.
Project
Cost-
Benefit
Analysis
Analysis
Variables:
Discount
Rate Used
8.00
%
Annual
Benefits
$
3,18,
000.0
0
Annual
Operation
al Costs
$
90,00
0.00
One-Time
Developm
ent Cost
$
7,50,
000.0
0
Year of
Project
0 1 2 3 4 5
TOTAL
S
Economic
Benefit $0.00
$
3,18,00
0.00
$
3,18,00
0.00
$
3,18,000
.00
$
3,18,00
0.00
$
3,18,00
0.00
Discount
Rate
1.000
0 0.9259 0.8573 0.7938 0.7350 0.6806
PV of
Benefits $0.00
$2,94,4
44.44
$2,72,6
33.74
$2,52,43
8.65
$2,33,7
39.49
$2,16,4
25.46
Page 3
Cost benefit analysis is defined as one of the systematic approach that is mainly used in
order to estimate the strengths as weaknesses that are generally utilized for determining the
different options that are helpful in achieving proper benefits (Sanders et al. 2016). It is found that
in the project of information system development, it is quite necessary to undertake cost benefit
analysis in order to check the project feasibility and for making sure that the project that was
undertaken will bring benefit for the organization. It is found that by performing proper cost benefit
analysis helps in giving proper opportunity that delve for developing the information system
successfully. The table that is provided below reflects on the entire calculation that is used for
showcasing the cost benefit calculation and as per the calculation, the ROI that is achieved will be
around 0.1445.
Project
Cost-
Benefit
Analysis
Analysis
Variables:
Discount
Rate Used
8.00
%
Annual
Benefits
$
3,18,
000.0
0
Annual
Operation
al Costs
$
90,00
0.00
One-Time
Developm
ent Cost
$
7,50,
000.0
0
Year of
Project
0 1 2 3 4 5
TOTAL
S
Economic
Benefit $0.00
$
3,18,00
0.00
$
3,18,00
0.00
$
3,18,000
.00
$
3,18,00
0.00
$
3,18,00
0.00
Discount
Rate
1.000
0 0.9259 0.8573 0.7938 0.7350 0.6806
PV of
Benefits $0.00
$2,94,4
44.44
$2,72,6
33.74
$2,52,43
8.65
$2,33,7
39.49
$2,16,4
25.46
Page 3

NPV of all
BENEFITS $0.00
$
2,94,44
4.44
$
5,67,07
8.19
$
8,19,516
.84
$
10,53,2
56.34
$
12,69,6
81.79
$
12,69,
681.79
One-Time
COSTS
$
(7,50,
000.0
0)
Recurring
Costs $0.00
$
(90,000.
00)
$
(90,000.
00)
$
(90,000.
00)
$
(90,000.
00)
$
(90,000
.00)
Discount
Rate
1.000
0 0.9259 0.8573 0.7938 0.7350 0.6806
PV of
Recurring
Costs $0.00
$
(83,333.
33)
$
(77,160.
49)
$
(71,444.
90)
$
(66,152.
69)
$
(61,252
.49)
NPV of all
COSTS
$
(7,50,
000.0
0)
$
(8,33,33
3.33)
$
(9,10,49
3.83)
$
(9,81,93
8.73)
$
(10,48,0
91.42)
$
(11,09,
343.90)
$
(11,09,
343.90
)
Overall
NPV
$
1,60,3
37.89
Overall
ROI
0.1445
Table 1: Cost benefit analysis
5. Project Schedule
Work breakdown structure is considered as one of the scheduling tool that is mainly
utilized for managing the projects tasks. It is found that the main reason of using the work
breakdown structure is that it helps in reducing the complicated project activities into a
number of tasks. In addition to this, it is found that the use of WBS is important for properly
overseeing the project tasks much more effectively than the project activities that are
complex (Fitzpatrick 2016). Furthermore, it is one of the essential tool that is mainly utilized
for defining the scope of the project properly. It is found that with the help of detailed work
breakdown structure, it is quite necessary to carry out bottom up estimation as well as
project costing in order to estimate the budget of the project.
Page 4
BENEFITS $0.00
$
2,94,44
4.44
$
5,67,07
8.19
$
8,19,516
.84
$
10,53,2
56.34
$
12,69,6
81.79
$
12,69,
681.79
One-Time
COSTS
$
(7,50,
000.0
0)
Recurring
Costs $0.00
$
(90,000.
00)
$
(90,000.
00)
$
(90,000.
00)
$
(90,000.
00)
$
(90,000
.00)
Discount
Rate
1.000
0 0.9259 0.8573 0.7938 0.7350 0.6806
PV of
Recurring
Costs $0.00
$
(83,333.
33)
$
(77,160.
49)
$
(71,444.
90)
$
(66,152.
69)
$
(61,252
.49)
NPV of all
COSTS
$
(7,50,
000.0
0)
$
(8,33,33
3.33)
$
(9,10,49
3.83)
$
(9,81,93
8.73)
$
(10,48,0
91.42)
$
(11,09,
343.90)
$
(11,09,
343.90
)
Overall
NPV
$
1,60,3
37.89
Overall
ROI
0.1445
Table 1: Cost benefit analysis
5. Project Schedule
Work breakdown structure is considered as one of the scheduling tool that is mainly
utilized for managing the projects tasks. It is found that the main reason of using the work
breakdown structure is that it helps in reducing the complicated project activities into a
number of tasks. In addition to this, it is found that the use of WBS is important for properly
overseeing the project tasks much more effectively than the project activities that are
complex (Fitzpatrick 2016). Furthermore, it is one of the essential tool that is mainly utilized
for defining the scope of the project properly. It is found that with the help of detailed work
breakdown structure, it is quite necessary to carry out bottom up estimation as well as
project costing in order to estimate the budget of the project.
Page 4
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Information system
development for hospital
Creating plan for the
project
Undertaking survey
Identyfying issues in
current system
Determining
solution to the
system
Understanding
functionalities of the
system
Project initiation
validation
Creating initiation plan
for the project
Developing project
team
Development of
project charter
Developing project
budget
Developing the
project schedule
Determining issues
within the system
Project
development
Budget procurement
Management of
resources
Hiring tester as well
as project developer
Assigning
responsibilities and
roles
Execution phase of the
project
Incorpotrating
feature of patient
identifier
Resigstration
procedure addition
Accessing control
facility
E-prescription for
the patients
Electronic media
integration
Facility of remote
access
Facility of adding
inventory
Bar coding facility
Information system
management
Customer chat
system
Testing the chat
procedure
Testing of the
system
Adding other
needed facilities
Development of final
version of the project
Handling the entire
project
Project Closing
Documentation of
the project
Project review
Project sign off
FIGURE 1: WBS
On the other hand, it is found that Gantt chart is one of the bar chart that helps in
illustrating the schedule of the project. The main purpose of using the project schedule is
that project Gantt chart helps in providing clear vision of the project ad further helps in
sequencing the events for reducing the poster that is mainly overburdened for the project
(Sequeira and Lopes 2015). Moreover, it also helps in managing the time of the project
effective in order to achieve success.
Page 5
development for hospital
Creating plan for the
project
Undertaking survey
Identyfying issues in
current system
Determining
solution to the
system
Understanding
functionalities of the
system
Project initiation
validation
Creating initiation plan
for the project
Developing project
team
Development of
project charter
Developing project
budget
Developing the
project schedule
Determining issues
within the system
Project
development
Budget procurement
Management of
resources
Hiring tester as well
as project developer
Assigning
responsibilities and
roles
Execution phase of the
project
Incorpotrating
feature of patient
identifier
Resigstration
procedure addition
Accessing control
facility
E-prescription for
the patients
Electronic media
integration
Facility of remote
access
Facility of adding
inventory
Bar coding facility
Information system
management
Customer chat
system
Testing the chat
procedure
Testing of the
system
Adding other
needed facilities
Development of final
version of the project
Handling the entire
project
Project Closing
Documentation of
the project
Project review
Project sign off
FIGURE 1: WBS
On the other hand, it is found that Gantt chart is one of the bar chart that helps in
illustrating the schedule of the project. The main purpose of using the project schedule is
that project Gantt chart helps in providing clear vision of the project ad further helps in
sequencing the events for reducing the poster that is mainly overburdened for the project
(Sequeira and Lopes 2015). Moreover, it also helps in managing the time of the project
effective in order to achieve success.
Page 5
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

FIGURE 2: Gantt chart
It is found that both work breakdown structure as well as schedule of the project are
related to each other. This is because an accurate project schedule can only be created with
the help of comprehensive project schedule which generally comprises of all the project
tasks. Furthermore, accurate scheduling general helps in improving the project profitability
that the entire project will get executed within the estimated time and budget.
It is found that after proper understanding of the various goals, requirements as well as
project scope, it is identified that the project is reasonable as the goal as well as objectives of the
project can be achieved quite effectively. It is found that with the project gaols, scope as well as
Page 6
It is found that both work breakdown structure as well as schedule of the project are
related to each other. This is because an accurate project schedule can only be created with
the help of comprehensive project schedule which generally comprises of all the project
tasks. Furthermore, accurate scheduling general helps in improving the project profitability
that the entire project will get executed within the estimated time and budget.
It is found that after proper understanding of the various goals, requirements as well as
project scope, it is identified that the project is reasonable as the goal as well as objectives of the
project can be achieved quite effectively. It is found that with the project gaols, scope as well as
Page 6

requirement, information system can be developed successfully such that project requirements are
met.
6. System Information Requirement Investigation Techniques
The stakeholders who are mainly involved within the project mainly includes:
Project manager
Financial manager
Workers
IT manger
Admin staffs
Technical staffs
Database manager
Vice chairman
The system information investigation technique that is mainly used within the project
are mainly elaborated below:
Sampling documents: This method of investigation is mainly needed in order to collect
proper information for the different documents of the hospitals. It is found that the various
sources of data that are mainly used for collecting information mainly include notes, reports
as well as different type of entries (Khare 2019).
Prototyping: It is one of the method where the basic project design is mainly showcases
after getting proper approval about the work of the project. Furthermore, it is identified
that the prototype of the project is generally applied within the initial stage in order to get
clear requirements about the project for reducing errors.
Interview: It is also considered as one of the investigation procedure that helps in
clarifying the project requirements as well as needs for the proper involvement of
stakeholders. Moreover, it is found that there a number of methods that are mainly used in
order to collect information successfully (Hu et al. 2016).
7. Reflections and Conclusions
After undertaking the project, I have identified that the information system for the
hospital have been developed successfully by accomplishing the project goals and objectives
without creating any financial issues. However, it is found that while progressing with the
project I have faced a lot of constraint including the inexperienced team members and as
result it is quite difficult to handle the project.
Page 7
met.
6. System Information Requirement Investigation Techniques
The stakeholders who are mainly involved within the project mainly includes:
Project manager
Financial manager
Workers
IT manger
Admin staffs
Technical staffs
Database manager
Vice chairman
The system information investigation technique that is mainly used within the project
are mainly elaborated below:
Sampling documents: This method of investigation is mainly needed in order to collect
proper information for the different documents of the hospitals. It is found that the various
sources of data that are mainly used for collecting information mainly include notes, reports
as well as different type of entries (Khare 2019).
Prototyping: It is one of the method where the basic project design is mainly showcases
after getting proper approval about the work of the project. Furthermore, it is identified
that the prototype of the project is generally applied within the initial stage in order to get
clear requirements about the project for reducing errors.
Interview: It is also considered as one of the investigation procedure that helps in
clarifying the project requirements as well as needs for the proper involvement of
stakeholders. Moreover, it is found that there a number of methods that are mainly used in
order to collect information successfully (Hu et al. 2016).
7. Reflections and Conclusions
After undertaking the project, I have identified that the information system for the
hospital have been developed successfully by accomplishing the project goals and objectives
without creating any financial issues. However, it is found that while progressing with the
project I have faced a lot of constraint including the inexperienced team members and as
result it is quite difficult to handle the project.
Page 7
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

From the entire project, it can be concluded that the system will be beneficial for
management of the operations of hospital. The paper develops proper schedule for the
project and also creates cost benefit analysis for analyzing the feasibility of the project. In
order to achieve success and for progressing successfully, it is found that agile system
development approach is mainly used within the project.
Page 8
management of the operations of hospital. The paper develops proper schedule for the
project and also creates cost benefit analysis for analyzing the feasibility of the project. In
order to achieve success and for progressing successfully, it is found that agile system
development approach is mainly used within the project.
Page 8
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

References
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), pp.761-778.
Bucero, A. and Englund, R.L., 2015, October. Project sponsorship: Achieving management
commitment for project success. Project Management Institute.
Chauhan, B.D., Rana, A. and Sharma, N.K., 2017, September. Impact of development
methodology on cost & risk for development projects. In 2017 6th International Conference
on Reliability, Infocom Technologies and Optimization (Trends and Future Directions)
(ICRITO) (pp. 267-272). IEEE.
Fitzpatrick, B.J., 2016. Determining the Optimal Work Breakdown Structure for Defense
Acquisition Contracts. Air Force Institute of Technology WPAFB United States.
Hu, X., Cui, N., Demeulemeester, E. and Bie, L., 2016. Incorporation of activity sensitivity
measures into buffer management to manage project schedule risk. European Journal of
Operational Research, 249(2), pp.717-727.
Kaiser, M.G., El Arbi, F. and Ahlemann, F., 2015. Successful project portfolio management
beyond project selection techniques: Understanding the role of structural
alignment. International Journal of Project Management, 33(1), pp.126-139.
Khare, V., 2019. Prediction, investigation, and assessment of novel tidal–solar hybrid
renewable energy system in India by different techniques. International Journal of
Sustainable Energy, 38(5), pp.447-468.
Kivilä, J., Martinsuo, M. and Vuorinen, L., 2017. Sustainable project management through
project control in infrastructure projects. International Journal of Project
Management, 35(6), pp.1167-1183.
Papke-Shields, K.E. and Boyer-Wright, K.M., 2017. Strategic planning characteristics applied
to project management. International Journal of Project Management, 35(2), pp.169-179.
Patwardhan, A., Kidd, J., Urena, T. and Rajgopalan, A., 2016. Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Ramazani, J. and Jergeas, G., 2015. Project managers and the journey from good to great:
The benefits of investment in project management training and education. International
Journal of Project Management, 33(1), pp.41-52.
Rui, Z., Peng, F., Ling, K., Chang, H., Chen, G. and Zhou, X., 2017. Investigation into the
performance of oil and gas projects. Journal of Natural Gas Science and Engineering, 38,
pp.12-20.
Sanders, G.D., Neumann, P.J., Basu, A., Brock, D.W., Feeny, D., Krahn, M., Kuntz, K.M.,
Meltzer, D.O., Owens, D.K., Prosser, L.A. and Salomon, J.A., 2016. Recommendations for
Page 9
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), pp.761-778.
Bucero, A. and Englund, R.L., 2015, October. Project sponsorship: Achieving management
commitment for project success. Project Management Institute.
Chauhan, B.D., Rana, A. and Sharma, N.K., 2017, September. Impact of development
methodology on cost & risk for development projects. In 2017 6th International Conference
on Reliability, Infocom Technologies and Optimization (Trends and Future Directions)
(ICRITO) (pp. 267-272). IEEE.
Fitzpatrick, B.J., 2016. Determining the Optimal Work Breakdown Structure for Defense
Acquisition Contracts. Air Force Institute of Technology WPAFB United States.
Hu, X., Cui, N., Demeulemeester, E. and Bie, L., 2016. Incorporation of activity sensitivity
measures into buffer management to manage project schedule risk. European Journal of
Operational Research, 249(2), pp.717-727.
Kaiser, M.G., El Arbi, F. and Ahlemann, F., 2015. Successful project portfolio management
beyond project selection techniques: Understanding the role of structural
alignment. International Journal of Project Management, 33(1), pp.126-139.
Khare, V., 2019. Prediction, investigation, and assessment of novel tidal–solar hybrid
renewable energy system in India by different techniques. International Journal of
Sustainable Energy, 38(5), pp.447-468.
Kivilä, J., Martinsuo, M. and Vuorinen, L., 2017. Sustainable project management through
project control in infrastructure projects. International Journal of Project
Management, 35(6), pp.1167-1183.
Papke-Shields, K.E. and Boyer-Wright, K.M., 2017. Strategic planning characteristics applied
to project management. International Journal of Project Management, 35(2), pp.169-179.
Patwardhan, A., Kidd, J., Urena, T. and Rajgopalan, A., 2016. Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Ramazani, J. and Jergeas, G., 2015. Project managers and the journey from good to great:
The benefits of investment in project management training and education. International
Journal of Project Management, 33(1), pp.41-52.
Rui, Z., Peng, F., Ling, K., Chang, H., Chen, G. and Zhou, X., 2017. Investigation into the
performance of oil and gas projects. Journal of Natural Gas Science and Engineering, 38,
pp.12-20.
Sanders, G.D., Neumann, P.J., Basu, A., Brock, D.W., Feeny, D., Krahn, M., Kuntz, K.M.,
Meltzer, D.O., Owens, D.K., Prosser, L.A. and Salomon, J.A., 2016. Recommendations for
Page 9

conduct, methodological practices, and reporting of cost-effectiveness analyses: second
panel on cost-effectiveness in health and medicine. Jama, 316(10), pp.1093-1103.
Sequeira, S. and Lopes, E., 2015. Simple Method Proposal for Cost Estimation from Work
Breakdown Structure. Procedia Computer Science, 64, pp.537-544.
Serra, C.E.M. and Kunc, M., 2015. Benefits realisation management and its influence on
project success and on the execution of business strategies. International Journal of Project
Management, 33(1), pp.53-66.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), pp.278-290.
Todorović, M.L., Petrović, D.Č., Mihić, M.M., Obradović, V.L. and Bushuyev, S.D., 2015.
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), pp.772-783.
Page 10
panel on cost-effectiveness in health and medicine. Jama, 316(10), pp.1093-1103.
Sequeira, S. and Lopes, E., 2015. Simple Method Proposal for Cost Estimation from Work
Breakdown Structure. Procedia Computer Science, 64, pp.537-544.
Serra, C.E.M. and Kunc, M., 2015. Benefits realisation management and its influence on
project success and on the execution of business strategies. International Journal of Project
Management, 33(1), pp.53-66.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), pp.278-290.
Todorović, M.L., Petrović, D.Č., Mihić, M.M., Obradović, V.L. and Bushuyev, S.D., 2015.
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), pp.772-783.
Page 10
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 12
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.