Project Management Research Literature Review

Verified

Added on  2021/04/21

|21
|5084
|25
AI Summary
This assignment involves a thorough examination of existing research papers and case studies related to project management. The provided references include articles and books that cover topics such as risk analysis, quality management systems, sustainability, optimism bias, and more. Students are expected to analyze these sources, identify key findings, and provide a detailed report on the status update and future directions of project management research. This assignment is suitable for students in business or engineering programs who need to demonstrate their understanding of project management principles and practices.

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: QUALITY SYSTEMS IN IT
Quality Systems in IT
Name of the Student
Name of the University

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1QUALITY SYSTEMS IN IT
Table of Contents
Task 1: Quality Assurance 2
ISO 31000 and ISO 9001: 2
Risk Assessment: 4
Quality Assurance Practices: 5
Task 2: Standard Quality Control Documentation 6
Questionnaires: 8
Interview Transcript: 9
Task 3: Project Management Tools 11
System Development Life Cycle: 11
Gantt Chart: 11
CPM: 14
PERT: 15
References: 17
Document Page
2QUALITY SYSTEMS IN IT
Task 1: Quality Assurance
ISO 31000 and ISO 9001:
Risk management refers to the procedure that is underpinned by several principles. In
addition to that, the risk management process is supported by a specific structure, adequate
enough to integrate the enterprise objectives and environment of external context. It is essential
to note that success of the project management process is directly proportional to the risk in the
project of UK Library System Development remaining in the organization. The risk management
approach is taken for delivering outputs in additional with compliance to appropriate governance
perquisites of UK Library System Development. In 2004, the Committee of Sponsoring
Organizations of the Treadway Commission introduced an Enterprise Risk management
standard. Based on this standard, the committee again, in 2009, published standard named ISO
31000. This standard guides the organization to implement the risk management approach
organization wide (Brogan and Galata 2015). In ISO 31000, the framework of risk management
is implemented first. Based on this framework, the whole risk management of UK Library
System Development is implemented. The framework is not for supporting the risk management
framework rather it must be viewed as the risk management (Batuwangala et al. 2017). The risk
management framework is not designed by following the ISO 31000 standard, rather it is
depended on the risk architecture, risk protocol for the organization and risk strategy that
organization wants to follow.
The risk management framework of UK Library System Development would be
consisting of risk identification, risk analysis, risk evaluation and risk treatment. In the risk
identification, the risks will be identified. Moreover, the nature of the risk will be recognized in
Document Page
3QUALITY SYSTEMS IN IT
this section too. The consequence of the risk investigation can be utilized to deliver a risk profile
that gives a rating of noteworthiness to each risk and gives a device to organizing risk treatment
endeavors. This positions the relative significance of each distinguished risk (Brogan and Galata
2015). This procedure enables the risks to be mapped to the business zone influenced, depicts the
essential control instruments set up and shows where the level of interest in controls may be
expanded, diminished or divided in terms of UK Library System Development. The ISO 31000
standard present the risk treatment process as the approach of choosing a risk and developing a
risk control measurement for the risk. The risk control or mitigation strategies within the project
of UK Library System Development can be risk avoidance, acceptance, financing or many
others. The standard guides the organization to implement the risk as per the applicable law for
achieving compliance.
Seven quality management principles are demonstrated in the ISO 9001.These principles
are customer focus, leadership, engagement of people, process approach, improvement,
evidencebased decision making and relationship management. In order to certifying to ISO 9001,
there is not specific obligation (Korenko et al. 2015). Only it is required to understand that the
certification should bring some meaning to the organization. For the selected project, the
customer focus, leadership, process approach, evidence based decision making and leadership
principles are appropriate.
i. Customer Focus: The business analyst and project manager of UK Library
System Development project will attend meeting and interview several end users
or audience of the final product. This way they can identify the needs of the end
users from the system. The project manager must be able to not only attract the
end users but also maintain their confidence.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4QUALITY SYSTEMS IN IT
ii. Leadership: The project manager of UK Library System Development along with
the project sponsor define the aims and objectives of the project. These aims and
objectives guides the project from the beginning to the end. The project manager
will carry out the act of leadership in the project to ensure everyone understand
what is needed to be achieved and everyone works in the right way.
iii. Process Approach: The project manager of UK Library System Development
defines the activities which functions for aching a goal. These processes or
activates are interconnected and have different objectives to fulfill (Shaari et al.
2015). Different team members can be responsible for executing different works.
iv. Evidence Based Decision Making: The ISO 9001 will ensure that the decision
making process within the selected project is made based on raw data and
findings.
Risk Assessment:
Financial Risk: It is among the high priority risk types regarding the selected project.
The financial risks occur because of the movements in the market. The movements in the market
is able to integrate host of factors. The financial risk can be of four types such as market risk,
credit risk, liquidity risk an operational risk (Marcelino et al. 2014). In the selected project,
online library system implementation, the operational risk can occur. This risk can occur due to
issue in managing the project or failure in technology. In order to manage the operational risk,
the project manager will implement proper control methods. All the activities will be closely
monitored. The project manager will inform the stakeholders if any issues occurs and mitigate
issue immediately.
Document Page
5QUALITY SYSTEMS IN IT
Project Risk: The project risk can be schedule risk, cost risk, governance risk and many
more. For the selected project, the schedule risk has the most potentiality to occur. The schedule
risk occurs due to inappropriate risk scheduling in the planning phase. The project manager is
responsible for handling this risk (Turner 2016). It can happen due to inadequate time allocation
to each of the activities associated with the project. The project manager must identify the needs
of the activities and its complexity level. Based on the collected data, the schedule of the project
will be developed.
Legal Risk: This risk rises due to regulatory and legal obligations. This risk includes
contracts made with various contractors and suppliers. Various commercial contracts integrate
provisions associated with the alteration in the risk laws. These changes are often neglected by
the organization or project manager (Dwivedi et al. 2015). In order to be ready for handling
risks, the project manager and client organization needs to be assessing all the legal implications
applicable to the project and abide by the law.
Disaster Risk: Disaster risks are very essential for the selected project. The project
manager will implement various approaches within the risk assessment framework for mitigating
the disaster risks (Silvius and Schipper 2014).
Quality Assurance Practices:
Budget: In order to control the budget of the project, the project manager will understand
the true requirements and wants of the stakeholders from the project. The project manager must
collect data from the stakeholders through information collection approaches (Sowunmi et al.
2016). This information will be examined properly to understand their needs. The selected
project may face various issues and challenges. Considering this fact, the project manager will
Document Page
6QUALITY SYSTEMS IN IT
create a budget for handling the sudden drawbacks in the project. The project manager will also
develop the appropriate key performance indicators for quality budgeting. The essential aspects
of the KPI are actual cost, cost variance, earned value, planned value and many more.
Monitoring: In order to track the progress of the project, the project manager will imply
various protocols to the working environment. Each of the employees will send their executed
work related information to the project manager (Montenegro and Flores 2015). The project
manager will check the progress of the project against the developed objectives. Each time an
issue or challenge occurs, the project manager will send detailed report to the stakeholders. This
process will also be done for risk occurrence. Each week team meeting will be held for better
team member mentality understanding purpose.
Work Plan: The project manager will define the work plan of the project. Each of the
team members will attend meeting with the project manager to understand their roles and
responsibilities (Odeck, Welde and Volden 2015). Each of the activity will have appropriate
objective linked with it. The team members will execute their work as per this objective.
Critical Path Analysis or CPA: First of all, the entire list of activities will be created
within the planning phase. The earliest start date, probable length of the activity, potential end
date and if the activity is parallel will be registered against each activity (Lock 2017). The
connection between the activities will be done. Such as from moving to task 1 to task 2, high
level analysis is required to done.
Task 2: Standard Quality Control Documentation
Techniques: Above all else, it is assumed that projects take more time to finish, invade
their financial plans, and convey less than impressive items not in view of seismic tremor, fire, or

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7QUALITY SYSTEMS IN IT
surge events outside the ability to control of the project director but instead, through absence of
vision, comprehension, knowledge, or examination at the beginning of the project (Kerzner and
Kerzner 2017). It is trusted that the greater part of the reasons for project delays are the
consequence of certainties that were knowable right on time in the project on the off chance that
somebody had been sufficiently shrewd to reveal and follow up on them before they progressed
toward becoming "centerpieces." This disclosure procedure could be considered piece of this
arranging procedure in that adequate time ought to be took into account this "revelation"
movement ahead of schedule in the project before a lot of time and cash are contributed.
Completing a project within allotted time a budget is a very hard task.
Cause Effect Matrix: At the time when the selected project will be in the design phase,
the problem analysis should be initiated. In order to perform the problem analysis, the
cause/effect matrix is an effective tool. It is proposed that the circumstances and end results be
masterminded in a two dimensional cluster with all the framework or item traits, segments, or
execution components recorded in one dimension; all the conceivable irritating causes recorded
in another. Into each cell is space for a sign of the likelihood of each reason adversy affecting the
framework work (Lock 2017). These probabilities (extending from 0 to 1.0) ought to be provided
by knowledgeable plan, generation, quality control, or deals engineers, and, potentially, by an
example of clients. They would demonstrate the likelihood that a specific reason over the span of
generation or item utilize would have a recognizable unfriendly impact on the framework work.
Every single high likelihood, no doubt, are terrible, and the condition making the high likelihood
ought to be amended.
The cause/effect analysis will be applied in the selected project for any fresh process. The
main problem the online system can have is server and website connection failure. This will
Document Page
8QUALITY SYSTEMS IN IT
result into data storing and retrieval failure. The end users will not be able to connect to the
system functions. Another problem can be data theft. The tremendous practice of cyberattacks in
recent days has put all the ICT systems in grave danger (Turner 2016). The online system will
have member’s personal information, account information and sensitive information of UK
library. If any of the data is stolen, then the hackers can use the data for illegal activities.
Creative Methods: Creativity is normally connected with developments and novel
arrangements. Preparation of the reason/impact network, graph, or stream outline may require a
decent arrangement of hypothesis or creativity. There are a few methods that are valuable. Most
importantly, through meetings of specialists directed by the project analyst, the reason/impact
graph ought to be set up as totally as conceivable on the main pass. The outline or grid should
then be utilized to "start the creative ability" of the members in a "moment round." The
procedure might be rehashed for third and extra adjusts. This procedure might be led by means
of occasional gatherings of the members, by individual meetings of the members, or even via
mail or a mix thereof (Verzuh 2015).
Process Mapping: Mapping is the method by which a procedure is deliberately subjected
to varieties in the control factors so as to describe the procedure. There are three purposes behind
doing this work: (1) so the procedure can be displayed and advanced, (2) so its affectability can
be resolved (Is the reaction a shallow dish or a blade edge?), (3) to better see how to rectify the
procedure on the off chance that it is exasperates by wild or unknown factors. Mapping is expert
by a plan of examinations and an investigation of the subsequent changes. In the tests, each
controllable variable is set at two to four levels.
Document Page
9QUALITY SYSTEMS IN IT
Questionnaires:
The questionnaires are created for collecting information from different audiences of the
system. The online system of UK Library has three major audiences like members, staff and
management. For each of the end users, different set of questions are created.
The members will be asked the following questions.
i. Do you want to have a login function in the system?
ii. Do you want to mark a book as wish to read?
iii. Do you want to read books online?
iv. How would you like to participate in the project?
The staff will be asked the following questions.
i. How would you like to interact with the system?
ii. Do you prefer filling up forms automatically?
iii. Do you want the system to register the members through yourself?
iv. Do you want the system to provide you searching which user has borrowed which
books?
v. Do you want to see notification to your mobile phone?
The management will be asked the following questions.
i. Do you want to see notification to your mobile phone?
ii. How much authority you want to give to the staff?
iii. Do you want different authorization levels for different staff?
iv. How would you prefer seeing a report?

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10QUALITY SYSTEMS IN IT
v. Do you want a chatting option in the system?
Interview Transcript:
Interviewer: Project Manager
Interviewee: Member
Interview Setting: The interview is done at the project working area. The interview
starts at 3:00 P.M. and duration is almost two hours.
(Start of Interview)
Interviewer: How often do you visit UK Library?
Interviewee: Twice a week.
Interviewer: Have you used any online library?
Interviewee: Yes.
Interviewer: Did you like accessing the website?
Interviewee: Yes.
Interviewer: Why did you like it?
Interviewee: Because I could have all the required information with my range.
Interviewer: Did you like reading EBook or Paper?
Interviewee: I like both. When I am at home, I read hard copy books.
Interviewer: Do you want to recharge your membership online?
Document Page
11QUALITY SYSTEMS IN IT
Interviewee: Yes. It will save a lot of time.
Interviewer: Would you prefer coming to the Library after online system is available?
Interviewee: Yes. I love the ambience.
Task 3: Project Management Tools
System Development Life Cycle:
The System Development will be separated into five sections. Every one of the stages
will be controlled by the project supervisor. In the arranging stage, the framework targets, project
plan, group choice, asset recognizable proof and numerous more different undertakings will be
finished. The project director will start the following stage after the first is finished. In the second
stage, the framework prerequisites will be distinguished, assessed and put away. The business
analyst will gather the information from librarian and management (Alshamrani and Bahattab
2015). These sets of information will be given to the system analyst for creating framework
prerequisites. In the design stage, the necessities will be utilized as a manual for framework
UML and Database design. The interface of the framework will likewise be designed in this
design stage. After every one of the designs are finished, the framework advancement process
will start. In this stage, the genuine frameworks are created. As the chose SDLC strategy is
waterfall, a regular and one of the most seasoned philosophy, it is basic that each business related
to a stage must be finished before starting the following stage (Madgunda et al. 2015). The
testing stage is for assessing the created unit and recognizing bugs or holes in them. At the last
stage, support, the framework will be sent in nature of the library.
Document Page
12QUALITY SYSTEMS IN IT
Gantt Chart:
WBS Task Name Duration Start Finish Predecessors Resource
Names
0 UK Library System
Development 70 days Sun
4/22/18
Fri
7/27/18
1 Planning 12 days Mon
4/23/18
Tue
5/8/18
1.1 Problem Definition 1 day Mon
4/23/18
Mon
4/23/18
Project
Manager
1.2 Project Charter
Development 1 day Tue
4/24/18
Tue
4/24/18 2 Project
Manager
1.3 Project Staff Employment 1 day Wed
4/25/18
Wed
4/25/18 3 Project
Manager
1.4
Selection of SDLC Model
or Software Development
Life Cycle
2 days Thu
4/26/18
Fri
4/27/18 4
Analyst,
Project
Manager
1.5 Project Schedule
Development 3 days Mon
4/30/18
Wed
5/2/18 5 Project
Manager
1.6 Project Budgeting 2 days Thu
5/3/18 Fri 5/4/18 6 Project
Manager
1.7 Allocate Resources
Planning 2 days Mon
5/7/18
Tue
5/8/18 7 Project
Manager
1.8 Planning Phase Complete 0 days Tue
5/8/18
Tue
5/8/18 8
2 System Analysis and
Requirements 12 days Wed
5/9/18
Thu
5/24/18
2.1 Identification of Business
Requirements 3 days Wed
5/9/18
Fri
5/11/18 9 Analyst
2.2 Identification of System
Requirement 2 days Mon
5/14/18
Tue
5/15/18 11 Analyst
2.3 Identification of User
Requirement 2 days Wed
5/16/18
Thu
5/17/18 12 Analyst
2.4 Verify Requirements 1 day Fri
5/18/18
Fri
5/18/18 13
Analyst,
Project
Manager
2.5 Evaluating Requirement 2 days Mon
5/21/18
Tue
5/22/18 14 Analyst
2.6 Documentation of
Requirement 2 days Wed
5/23/18
Thu
5/24/18 15 Analyst
2.7 System Analysis Phase
Complete 0 days Thu
5/24/18
Thu
5/24/18 16
3 System Design 20 days Fri Thu

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
13QUALITY SYSTEMS IN IT
5/25/18 6/21/18
3.1 Architecture Designing of
UK Library Online System 2 days Fri
5/25/18
Mon
5/28/18 17 Designer
3.2 UML Diagrams Designing 2 days Tue
5/29/18
Wed
5/30/18 19 Designer
3.3 Unit Design 2 days Tue
5/29/18
Wed
5/30/18 19
3.4 Database Design 6 days Thu
5/31/18
Thu
6/7/18
3.4.1 Selection of Attributes
and Entities 2 days Thu
5/31/18 Fri 6/1/18 20
Database
Developer,
Designer
3.4.2 Schema Diagram
Creation 2 days Mon
6/4/18
Tue
6/5/18 23 Designer
3.4.3 Generate Entity
Relationship Diagram or ERD 1 day Wed
6/6/18
Wed
6/6/18 24 Designer
3.4.4 Database Normalization 1 day Thu
6/7/18
Thu
6/7/18 25
Database
Developer,
Designer
3.5 Website Design 6 days Fri 6/8/18 Fri
6/15/18
3.5.1 User Interaction
Designing 2 days Fri 6/8/18 Mon
6/11/18 26 Web
Designer
3.5.2 User Interface
Designing 2 days Tue
6/12/18
Wed
6/13/18 28 Web
Designer
3.5.3 Functionality
Confirmation 2 days Thu
6/14/18
Fri
6/15/18 29 Web
Developer
3.6 Network Diagram
Designing 2 days Mon
6/18/18
Tue
6/19/18 30 Designer
3.7 Network Design 2 days Wed
6/20/18
Thu
6/21/18 31 Designer
3.8 Completion of Designing
Phase 0 days Thu
6/21/18
Thu
6/21/18 32
4 Development 25 days Fri
6/22/18
Thu
7/26/18
4.1 Implement Website 6 days Fri
6/22/18
Fri
6/29/18 33 Web
Developer
4.2 Implement Unit
Application 12 days Mon
7/2/18
Tue
7/17/18 35 Coder
4.3 Implement Database 3 days Wed
7/18/18
Fri
7/20/18 36 Database
Developer
4.4 Implement Network 4 days Mon
7/23/18
Thu
7/26/18 37 Web
Developer
Document Page
14QUALITY SYSTEMS IN IT
4.5 Complete of Development 0 days Thu
7/26/18
Thu
7/26/18 38
5 Deployment 70 days Sun
4/22/18
Fri
7/27/18
5.1 Go Live 1 day Fri
7/27/18
Fri
7/27/18 39
Analyst,
Project
Manager
5.2 Deployment Completion 0 days Sun
4/22/18
Sun
4/22/18
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 UK Library System Development 70 days Sun 4/22/18 Fri 7/27/18
1 1 Planning 12 days Mon 4/23/18 Tue 5/8/18
2 1.1 Problem Definition 1 day Mon 4/23/18 Mon 4/23/18
3 1.2 Project Charter Development 1 day Tue 4/24/18 Tue 4/24/18 2
4 1.3 Project Staff Employment 1 day Wed 4/25/18 Wed 4/25/18 3
5 1.4 Selection of SDLC Model or Software Development Life Cycle2 days Thu 4/26/18 Fri 4/27/18 4
6 1.5 Project Schedule Development 3 days Mon 4/30/18 Wed 5/2/18 5
7 1.6 Project Budgeting 2 days Thu 5/3/18 Fri 5/4/18 6
8 1.7 Allocate Resoruces Planning 2 days Mon 5/7/18 Tue 5/8/18 7
9 1.8 Planning Phase Complete 0 days Tue 5/8/18 Tue 5/8/18 8
10 2 System Analysis and Requirements 12 days Wed 5/9/18 Thu 5/24/18
11 2.1 Identification of Business Requirements 3 days Wed 5/9/18 Fri 5/11/18 9
12 2.2 Identification of System Requirement 2 days Mon 5/14/18 Tue 5/15/18 11
13 2.3 Identification of User Requirement 2 days Wed 5/16/18 Thu 5/17/18 12
14 2.4 Verify Requirements 1 day Fri 5/18/18 Fri 5/18/18 13
15 2.5 Evaluating Requirement 2 days Mon 5/21/18 Tue 5/22/18 14
16 2.6 Documentation of Requirement 2 days Wed 5/23/18 Thu 5/24/18 15
17 2.7 System Analysis Phase Complete 0 days Thu 5/24/18 Thu 5/24/18 16
18 3 System Design 20 days Fri 5/25/18 Thu 6/21/18
19 3.1 Architecture Designing of UK Library Online System 2 days Fri 5/25/18 Mon 5/28/18 17
20 3.2 UML Diagrams Designing 2 days Tue 5/29/18 Wed 5/30/18 19
21 3.3 Unit Design 2 days Tue 5/29/18 Wed 5/30/18 19
22 3.4 Database Design 6 days Thu 5/31/18 Thu 6/7/18
23 3.4.1 Selection of Attributes and Entities 2 days Thu 5/31/18 Fri 6/1/18 20
24 3.4.2 Schema Diagram Creation 2 days Mon 6/4/18 Tue 6/5/18 23
25 3.4.3 Generate Entity Relationship Diagram or ERD 1 day Wed 6/6/18 Wed 6/6/18 24
26 3.4.4 Database Normalizaion 1 day Thu 6/7/18 Thu 6/7/18 25
27 3.5 Webiste Design 6 days Fri 6/8/18 Fri 6/15/18
28 3.5.1 User Interaction Designing 2 days Fri 6/8/18 Mon 6/11/18 26
29 3.5.2 User Interface Designing 2 days Tue 6/12/18 Wed 6/13/18 28
30 3.5.3 Functionality Confirmation 2 days Thu 6/14/18 Fri 6/15/18 29
31 3.6 Network Diagram Designing 2 days Mon 6/18/18 Tue 6/19/18 30
32 3.7 Network Design 2 days Wed 6/20/18 Thu 6/21/18 31
33 3.8 Completion of Designing Phase 0 days Thu 6/21/18 Thu 6/21/18 32
34 4 Development 25 days Fri 6/22/18 Thu 7/26/18
35 4.1 Implement Webiste 6 days Fri 6/22/18 Fri 6/29/18 33
36 4.2 Implement Unit Application 12 days Mon 7/2/18 Tue 7/17/18 35
37 4.3 Implement Database 3 days Wed 7/18/18 Fri 7/20/18 36
38 4.4 Implement Network 4 days Mon 7/23/18 Thu 7/26/18 37
39 4.5 Complete of Development 0 days Thu 7/26/18 Thu 7/26/18 38
40 5 Deployment 70 days Sun 4/22/18 Fri 7/27/18
41 5.1 Go Live 1 day Fri 7/27/18 Fri 7/27/18 39
42 5.2 Deployment Completion 0 days Sun 4/22/18 Sun 4/22/18
Project Manager
Project Manager
Project Manager
Analyst,Project Manager
Project Manager
Project Manager
Project Manager
5/8
Analyst
Analyst
Analyst
Analyst,Project Manager
Analyst
Analyst
5/24
Designer
Designer
Database Developer,Designer
Designer
Designer
Database Developer,Designer
Web Designer
Web Designer
Web Developer
Designer
Designer
6/21
Web Developer
Coder
Database Developer
Web Developer
7/26
Analyst,Project Manager
4/22
Apr May Jun Jul Aug
Qtr 2, 2018 Qtr 3, 2018
Figure 1: Gantt Chart of UK Library System Development
(Source: Created by Author)
Document Page
15QUALITY SYSTEMS IN IT
CPM:
Most project management programming projects will compute a critical path for you.
This might be important if your project is perplexing. Nonetheless, you can regularly decide the
critical path yourself in straightforward cases. Begin with the most punctual errand, at that point
figure out which undertakings can't begin until the point when that one is finished. The longest of
these undertakings is the following errand in the critical path. Next, make sense of what
undertakings rely upon finish of that second assignment and the longest errand among these turns
into the third step in the critical path. Proceed with this procedure until the point that you achieve
the finish of the project (Subiyakto et al. 2016). The CPM or critical path method is a well
ordered project management procedure for process arranging that characterizes critical and
noncritical undertakings with the objective of avoiding time period issues and process
bottlenecks. The CPM is in a perfect world suited to projects comprising of various exercises that
communicate in a perplexing way (Prater, Kirytopoulos and Ma 2017). In applying the CPM,
there are a few stages that can be outlined as takes after:
i. Define the required assignments and put them down in a requested (sequenced)
list.
ii. Create a flowchart or other outline demonstrating each errand in connection to the
others.
iii. Identify the critical and noncritical connections (paths) among errands.
iv. Determine the normal fruition or execution time for each errand (Singh and Lano
2014).
v. Locate or devise options (reinforcements) for the most critical paths.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
16QUALITY SYSTEMS IN IT
PERT:
Sprightly is a minor dissimilar from Critical Path Analysis that takes a somewhat more
suspicious perspective of time gauges made for each project arrange. To utilize it, evaluate the
briefest conceivable time every action will take, the in all likelihood timeframe, and the longest
time that may be taken if the movement takes longer than anticipated (Sutrisna and
Kumaraswamy 2015).
A PERT chart displays a genuine illustration of a project like a system graph including of
numbered hubs (either circles or rectangles) discourse to events, or revolving points in the
project associated by obvious vectors (directional lines) communicating to errands within the
project. The sequence of the bars on the lines validates the alliance of projects (Chauma 2017).
In the chart, as an example, the assignments among hubs 1, 2, 4, 8, and 10 have to be completed
in sequence. These are named indigent or sequential errands. The projects among hubs 1 and 2,
and hubs 1 and 3 are not theme to the contentment of one to commence the other as well as can
be comprised at the equivalent time. These errands are named simultaneous or parallel projects.
Errands that have to be completed in series yet that do not need resources or consummation
period are taken to be occasional dependence (Sutrisna and Kumaraswamy 2015). Numbers on
the contrary sides of the vectors demonstrate the time allocated for the errand.
Tool Selection:
The SDLC is the best option for the proposed project. Without a proper SDLC method,
the project can never be established. The project manager will guide the phases and
interconnected activities of the selected SDLC. The SDLC will allow the organization to
complete the project successfully.
Document Page
17QUALITY SYSTEMS IN IT
Document Page
18QUALITY SYSTEMS IN IT
References:
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer Science
Issues (IJCSI), 12(1), p.106.
Batuwangala, E., Ramasamy, S., Bogoda, L. and Sabatini, R., 2017. Safety and security
considerations in the certification of next generation avionics and air traffic management
systems. In 17th Australian International Aerospace Congress: AIAC 2017 (p. 440). Engineers
Australia, Royal Aeronautical Society.
Brogan, M. and Galata, A., 2015. The VERYSchool Project: Valuable EneRgY for a Smart
School-Intelligent ISO 50001 Energy Management Decision Making in School Buildings. In
AIAI Workshops (pp. 46-58).
Chauma, C.N., 2017. The application of project management tools and techniques in ICT SME
projects in Western Cape (Doctoral dissertation, Cape Peninsula University of Technology).
Dwivedi, Y.K., Wastell, D., Laumer, S., Henriksen, H.Z., Myers, M.D., Bunker, D., Elbanna, A.,
Ravishankar, M.N. and Srivastava, S.C., 2015. Research on information systems failures and
successes: Status update and future directions. Information Systems Frontiers, 17(1), pp.143-157.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Korenko, M., Bujna, M., Foldesiova, D., Dostal, P. and Kyselica, P., 2015. Risk analysis at work
in manufacturing organization. Acta Universitatis Agriculturae et Silviculturae Mendelianae
Brunensis, 63(5), pp.1493-1497.

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
19QUALITY SYSTEMS IN IT
Lock, D., 2017. The essentials of project management. Routledge.
Madgunda, S., Suman, U., Praneeth, G.S. and Kasera, R., 2015. Steps in Requirement Stage of
Waterfall Model. International journal of computer & mathematical sciences, pp.86-87.
Marcelino-Sadaba, S., Perez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project
risk management methodology for small firms. International journal of project management,
32(2), pp.327-340.
Montenegro, C.W. and Flores, D.A., 2015. An integrated model for ICT governance and
management applied to the council for evaluation, accreditation and quality assurance of higher
education institutions in Ecuador (CEAACES). In Computing, Communication and Security
(ICCCS), 2015 International Conference on (pp. 1-9). IEEE.
Odeck, J., Welde, M. and Volden, G.H., 2015. The Impact of External Quality Assurance of
Costs Estimates on Cost Overruns: Empirical Evidence from the Norwegian Road Sector.
European Journal of Transport & Infrastructure Research, 15(3).
Prater, J., Kirytopoulos, K. and Ma, T., 2017. Optimism bias within the project management
context: A systematic quantitative literature review. International Journal of Managing Projects
in Business, 10(2), pp.370-385.
Shaari, N., Abdullah, M.N., Asmoni, M., Lokman, M.A., Hamid, H.A. and Mohammed, A.H.,
2015. Practice for project quality management systems (PQMS) in construction project. Jurnal
Teknologi, 77, p.26.
Silvius, A.J. and Schipper, R.P., 2014. Sustainability in project management: A literature review
and impact analysis. Social Business, 4(1), pp.63-96.
Document Page
20QUALITY SYSTEMS IN IT
Singh, R. and Lano, K., 2014. Literature Survey of previous research work in Models and
Methodologies in Project Management. Editorial Preface, 5(9).
Sowunmi, O.Y., Misra, S., Fernandez-Sanz, L., Crawford, B. and Soto, R., 2016. An empirical
evaluation of software quality assurance practices and challenges in a developing country: a
comparison of Nigeria and Turkey. SpringerPlus, 5(1), p.1921.
Subiyakto, A.A., Ahlan, A.R., Kartiwi, M. and Putra, S.J., 2016. Measurement of the information
system project success of the higher education institutions in Indonesia: a pilot study.
International Journal of Business Information Systems, 23(2), pp.229-247.
Sutrisna, M. and Kumaraswamy, M.M., 2015. Advanced ICT and smart systems for innovative"
engineering, construction and architectural management". Engineering, Construction and
Architectural Management, 22(5).
Turner, R., 2016. Gower handbook of project management. Routledge.
Verzuh, E., 2015. The fast forward MBA in project management. John Wiley & Sons.
1 out of 21
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]