MILTON MARGAI TECHNICAL UNIVERSITY

CONGO CROSS CAMPAU

FACULTY OF ENGINEERING

FIRST SEMESTER CONTINUOUS ASSESSMENT

SUBJECT: ENGINEERING PROFSSIONAL ETHICS

NAME: PETER GBOKODAY KOROMA

ID NO: 19350

SUBMITED TO Ing. Umar M Lahai

ELECTRICAL AND ELECTRONIC ENGINEERING

QUESTION-1

A dissertation is a detailed and structured academic document that presents the research
conducted by a student as part of their higher education degree. The framework generally
includes the following sections:
1. Title Page: Includes the title of the dissertation, the student's name, the institution, the
department, the degree program, and the date of submission.
2. Abstract: A summary of the research, including the research question, methods, results,
and conclusions.
3. Acknowledgements: A section to thank those who helped and supported the research.
4. Table of Contents: Lists all the sections and sub-sections with page numbers.
5. Introduction: Introduces the research topic, provides background information, states the
research problem, objectives, and significance of the study.
6. Literature Review: A comprehensive review of existing literature related to the research
topic.
7. Methodology: Describes the research design, data collection methods, and data analysis
procedures.
8. Results: Presents the findings of the research, often including tables, graphs, and charts.
9. Discussion: Interprets the results, discusses their implications, and relates them to the
existing literature.
10. Conclusion: Summarizes the research, its findings, and suggests future research
directions.
11. References: Lists all the sources cited in the dissertation.
12. Appendices: Includes additional material such as raw data, questionnaires, or detailed
calculations.

Here are examples of how to cite different sources using the IEEE style:
a. Books:
The IEEE style for citing books includes the author's name, publication year, book title, and
publisher. For example:
[1] Peter Bokoday Koroma, "Digital Signal Processing: Principles, Algorithms, and
Applications," Wiley, 2011.
b. Book chapter:
To cite a chapter in an edited book, include the author's name, publication year, chapter title,
book title, editor's name, and page numbers. For example:
[1] J. Doe, "Neural Networks for Image Recognition," in "Artificial Intelligence: Methods
and Applications," Peter Bokoday Koroma and Ing. Umar M Lahai, Eds., Wiley, 2015, pp.
123-156.
c. Journal article:
To cite a journal article, include the author's name, publication year, article title, journal title,
volume number, issue number, and page numbers. For example:
[1] Peter Bokoday Koroma and M. Johnson, "A Survey of Deep Learning Techniques for
Image Recognition," IEEE Transactions on Neural Networks and Learning Systems, vol. 26,
no. 1, pp. 1-15, 2015.
d. Information from website:
To cite information from a website, include the author's name (if available), publication year
(if available), title of the webpage, the URL, and the date accessed. For example:
[1] "Deep Learning: A Brief Overview," IEEE Spectrum, [online], available:
https://spectrum.ieee.org/computing/software/deep-learning-a-brief-overview, accessed 10
Jan. 2023.

QUESTION -2

Variables and Formulas

Communication: The process of exchanging information, ideas, and emotions through
speech, signals, writing, or behaviour.
Preferred firm: A company that aligns with one's values, goals, and work style.
Concepts
Effective communication: The ability to convey information clearly, concisely, and
persuasively, ensuring mutual understanding and engagement.
Preferred firm culture: A work environment that fosters collaboration, innovation, and
growth, valuing open and honest communication.
Main Body
Step 1: Importance of Communication
Effective communication is crucial in any engineering field, as it enables the sharing of ideas,
facilitates collaboration, and fosters a positive work environment. Good communication skills
help engineers convey complex concepts to diverse audiences, ensuring that everyone
understands the information and can contribute to problem-solving efforts.
Step 2: Preferred Firm Culture
A preferred firm is one that aligns with an individual's values, goals, and work style. In such
a firm, communication is open, honest, and respectful, fostering a culture of collaboration and
innovation.
Step 3: Types of Communication Tolerated in a Preferred Firm
In a preferred firm, the following types of communication are tolerated and encouraged:
Active Listening: Engaging in conversations with an open mind, asking clarifying questions,
and demonstrating empathy.
Clear and Concise Messaging: Conveying information in a straightforward and concise
manner, avoiding jargon and unnecessary complexity.
Constructive Feedback: Providing feedback that is specific, actionable, and focused on
improvement, rather than criticism.
Collaborative Problem-Solving: Encouraging team members to share ideas, brainstorm
solutions, and work together to address challenges.
Transparency and Honesty: Being open and honest about project status, challenges, and
successes, fostering trust and credibility.
Step 4: Benefits of Effective Communication in a Preferred Firm
Effective communication in a preferred firm leads to several benefits, including:
Improved Collaboration: Team members can work together more effectively, leveraging
diverse perspectives and expertise.
Increased Innovation: Open communication encourages the sharing of ideas, leading to
creative solutions and continuous improvement.
Enhanced Trust and Credibility: Transparent and honest communication fosters trust and
credibility among team members and stakeholders.
Greater Employee Engagement: Clear and concise messaging helps employees understand
their roles, responsibilities, and contributions, increasing engagement and motivation.
Final Answer
In a preferred firm, effective communication is tolerated and encouraged, fostering a culture
of collaboration, innovation, and growth. Active listening, clear and concise messaging,
constructive feedback, collaborative problem-solving, and transparency and honesty are
essential components of communication in such a firm. By promoting open and honest
communication, a preferred firm can reap the benefits of improved collaboration, increased
innovation, enhanced trust and credibility, and greater employee engagement.

QUESTION -3

Concepts
Early Estimate: A preliminary cost estimate of a project, usually created during the planning
phase.
Final Actual Cost: The actual cost of a project, calculated after its completion.
Owner: The person or entity responsible for funding and managing the project.
Designer: The person or entity responsible for designing and overseeing the project's
implementation.
Main Body
Step 1: Financial Consequences
Insufficient Funding: If the early estimate is significantly lower than the final actual cost, the
owner may not allocate enough funds for the project, leading to financial strain and potential
delays.
Overbudgeting: The designer may need to request additional funds from the owner, causing
delays and negatively impacting the project's reputation.
Step 2: Schedule Consequences
Delayed Completion: Insufficient funds may lead to delays in the project's completion,
causing frustration for the owner and potential financial penalties for the designer.
Rushed Work: To compensate for the delays, the designer may need to rush the project,
leading to compromised quality and potential safety issues.
Step 3: Reputation Consequences
Loss of Trust: The owner may lose trust in the designer's ability to accurately estimate project
costs, leading to strained relationships and potential future disputes.
Negative Publicity: If the project's cost overruns become public, both the owner and designer
may face negative publicity, damaging their reputations.
Step 4: Legal Consequences
Breach of Contract: If the early estimate is significantly lower than the final actual cost, the
designer may be in breach of contract, leading to legal action and potential financial
penalties.
Contract Termination: The owner may terminate the contract, leading to financial losses for
the designer and potential legal disputes.

QUESTION -4

1. Technology
Challenges:
Infrastructure Deficiencies: Many regions in Africa suffer from inadequate technological
infrastructure. Engineers often have to work with outdated or insufficient tools and
equipment, which can hinder their productivity and the quality of their work.
Access to Latest Technology: There is limited access to the latest technological
advancements and innovations. This gap can make it difficult for engineers to stay up-to-date
with global engineering practices.
Internet Connectivity: Reliable internet access is not universally available, which can restrict
access to information, resources, and remote collaboration opportunities.
Impact:
These technological constraints can limit the efficiency and effectiveness of engineering
projects.
Engineers may face difficulties in implementing cutting-edge solutions and may have to rely
on less efficient methods.
The lack of technological resources can also affect professional development and continuous
learning.
2. Geopolitical
Challenges:
Political Instability: Many African countries experience varying degrees of political
instability, which can disrupt engineering projects and create unsafe working conditions.
Conflict Zones: Engineers working in or near conflict zones face significant risks, including
threats to their personal safety and challenges in maintaining project continuity.
Corruption: Corruption can be a major issue, impacting project funding, resource allocation,
and regulatory compliance.
Impact:
Political and security challenges can lead to project delays, increased costs, and in some
cases, the complete abandonment of projects.
Engineers may be forced to navigate complex political landscapes, which can divert attention
from their technical responsibilities.
3. Standards
Challenges:
Inconsistent Standards: There is often a lack of consistent engineering standards across the
continent. Different countries may have varying regulations and standards, which can
complicate cross-border projects.
Quality Control: Ensuring quality and safety standards can be challenging, particularly in
regions where regulatory bodies are weak or underfunded.
International Compatibility: African engineers may face difficulties in aligning local
standards with international benchmarks, affecting the global competitiveness of their work.
Impact:
Variations in standards can lead to inconsistencies in project outcomes and affect the overall
quality and safety of engineering works.
Engineers might spend additional time and resources to meet diverse regulatory requirements.
The lack of standardized practices can hinder collaboration with international partners and
limit access to global markets.
4. Engineering Professionals Practice Act
Challenges:
Regulatory Framework: The presence and effectiveness of Engineering Professionals Practice
Acts (EPPAs) vary across African countries. Some nations have robust regulatory
frameworks, while others lack comprehensive legislation.
Licensing and Certification: Obtaining and maintaining professional licensure can be
cumbersome, particularly in countries with less developed regulatory bodies.
Enforcement: Enforcement of these acts can be inconsistent, and in some cases, non-existent,
reducing their efficacy in maintaining professional standards.
Impact:
Well-implemented EPPAs can enhance the professional standing and accountability of
engineers, ensuring adherence to ethical and technical standards.
In regions with weak enforcement, engineers may face challenges in maintaining professional
integrity and standards.
The disparity in regulatory practices can create an uneven playing field, with some engineers
facing more rigorous requirements than others.
Conclusion
Engineers in Africa navigate a complex landscape shaped by technological constraints,
geopolitical challenges, varying standards, and regulatory frameworks. Addressing these
issues requires a concerted effort from governments, industry stakeholders, and the
international community to improve infrastructure, enhance political stability, standardize
practices, and strengthen regulatory bodies. By tackling these challenges, the working
conditions for engineers can be significantly improved, enabling them to contribute more
effectively to the continent's development.

QUESTION -5

Differences between project objectives and project scope definition.

Scope: The totality of outputs, outcomes and advantages and also the work needed to provide
them.
Objectives: Planned results towards that effort is directed. Objectives could also be outlined
in terms of outputs, outcomes and/or advantages.
General
Scope includes the totality of the outputs, outcomes and advantages and also the work needed
to provide them. It's the scope of labour that's the deciding issue on whether it'll be managed
as a project, program or portfolio.
The means within which scope is managed depends upon 2 things; the character of the
objectives (outputs, advantages or strategic) and also the definability of the objectives.
The scope of a project can generally embrace outputs, however could also be extended to
hide advantages.
Objectives could also be expressed in terms of outputs (such as a brand-new headquarters
building), outcomes (such as employees being settled from multiple locations to the new
HQ), advantages (such as reduced travel and facilities management costs) or strategic
objectives (such as doubling the organization’s share worth in 3 years).
Where the target is well understood and contains a tangible output (e.g. in construction and
engineering) it's usual to outline the scope as accurately as attainable at the start of the life
cycle.
Where the target is a smaller amount tangible, or subject to vital modification e.g. business
modification or some IT systems, a lot of versatile approach to scope is required. This needs a
careful approach to avoid escalating prices.
Interactive role of the owner and designer in this process to ensure a well-defined
understanding between the two parties.
A project owner’s role is a smaller amount active than the project manager’s role, however
there’s still lots to stay them busy.
Because the project’s Champion In Chief™, they give the impression of being for
opportunities to spice up the project’s profile each day: talking with stakeholders concerning
however this project contributes to their goals, obtaining feedback from the project’s target
customers, and congratulating the project team for milestones met in company- or
department-wide forums.
They’re conjointly answerable for creating high-level choices, whether it’s sinking a dispute
concerning the approach or prioritizing “must-haves” vs. “nice to haves”. For instance, if the
project falls behind, the project owner is that the one that decides whether to cut back the
project’s scope, extend its timeline, or fortify the team. In contrast, implementation choices –
say, whether a campaign desires a landing page or a journal post – ought to be left to the topic
matter specialists on the project team.
Last, as a part of making certain alignment up and down the org, a project owner advocates
for resources. If the project team desires the assistance of an internet developer for per week,
the project owner can work with whoever manages the net developers to know what their
team’s high priorities square measure and discern the way to secure per week of someone’s
time. Similarly, if the project manager desires facilitate release dependencies or unclogging a
bottleneck, they will intensify that to the project owner (who, in turn, could eventually get to
intensify it to the project sponsor, though this sometimes isn’t necessary).

QUESTION-6

Variables and Formulas

Owner: The person or entity responsible for the project.
Project: A set of interrelated tasks to achieve a specific goal.
Requirements: The necessary features, functions, and constraints of a project.
Expertise: Knowledge and skills in a specific area.
Concepts
Assisting the Owner
Project Requirements: The necessary features, functions, and constraints of a project.
Owner Expertise: The owner's knowledge and skills in their area of business.
Main Body
Let's explore the methods that can be used to assist an owner with defining project
requirements when they lack the necessary expertise.
Step 1: Hiring a Consultant
A consultant is a professional with expertise in a specific area who can provide guidance and
support to the owner. Consultants can help the owner define project requirements by:
Conducting a feasibility study to assess the project's viability.
Identifying the necessary resources, such as personnel, equipment, and materials.
Establishing project goals and objectives.
Defining project scope, timelines, and budgets.
Identifying potential risks and developing mitigation strategies.
Step 2: Engaging a Project Management Firm
A project management firm specializes in managing projects from conception to completion.
They can assist the owner by:
Providing project management expertise and resources.
Developing a project plan and schedule.
Managing project risks and issues.
Coordinating project activities and stakeholders.
Monitoring project progress and performance.
Step 3: Collaborating with Industry Experts
Industry experts are professionals with specialized knowledge and experience in a particular
field. They can provide valuable insights and guidance to the owner by:
Sharing best practices and lessons learned.
Providing technical expertise and advice.
Recommending appropriate technologies and solutions.
Identifying potential challenges and opportunities.
Step 4: Conducting a Workshop
A workshop is a facilitated meeting where stakeholders collaborate to define project
requirements. A workshop can be conducted by a consultant or project management firm and
can include:
Identifying project goals and objectives.
Defining project scope and constraints.
Brainstorming ideas and solutions.
Prioritizing requirements.
Developing a project plan and schedule.
Step 5: Using a Requirements Management Tool
A requirements management tool is software that helps manage project requirements. It can
assist the owner by:
Capturing and organizing project requirements.
Tracking changes and updates.
Facilitating communication and collaboration among stakeholders.
Ensuring requirements are complete, consistent, and traceable.
Generating reports and documentation.