MILTON MARGAI TECHNICAL UNIVERSITY

CONGO CROSS CAMPAU

FACULTY OF ENGINEERING
FIRST SEMESTER CONTINUOUS ASSESSMENT
SUBJECT: ENGINEERING PROFSSIONAL ETHICS
NAME: CHRIS JACK-LAMIN
ID NO: 13760
LECTURER; ING. UMAR M LAHAI
BUILDING AND CIVIL ENG
QUESTION 1
The format of a dissertation typically follows a structured framework designed to
systematically present research findings and analysis. Here's a detailed breakdown of the
typical sections included in a dissertation:
1. Title Page:
- Includes the title of your dissertation, your name, institution, department, date of
submission, and sometimes your supervisor's name.
2Abstrac:
A concise summary of your dissertation, typically around 150-300 words, covering the
research problem, methodology, key findings, and conclusions. It's often the first substantive
description of your work read by others.
3. table of Contents:
Lists all major sections and subsections of your dissertation along with their page numbers
for easy navigation.
4. List of Figures and Tables:
If applicable, lists the figures and tables included in your dissertation along with their page
numbers.
5. List of Abbreviations (optional):
Includes definitions of abbreviations used throughout the dissertation, ensuring clarity for
readers.
6. Introduction:
Sets the stage for your research by providing background information, stating the research
problem or question, outlining the objectives or aims of your study, and explaining the
significance or relevance of the research.
7.Literature Review:
A critical examination and synthesis of the existing literature relevant to your research
topic. It demonstrates your understanding of the field, identifies gaps or controversies, and
justifies the need for your research.
8. Methodology:
Describes the methods and techniques used to conduct your research. This section should
include details on research design, data collection methods, instruments or tools used,
sampling strategy (if applicable), and data analysis procedures.
9. Results:
Presents the findings of your research in a clear and systematic manner. Depending on your
field, this may include textual descriptions, tables, figures, and statistical analyses. Ensure
that results are presented objectively without interpretation.
10. Discussion:
Interprets and analyses your results in relation to your research question(s) and objectives.
Discusses the implications of your findings, addresses limitations, compares with existing
literature, and suggests directions for future research.
11. Conclusion:
- Summarizes the key findings of your research, reiterates the significance of your study,
and discusses the broader implications of your findings. It should also reflect on the
limitations of your study and propose recommendations for further research or practical
applications.
12. References:
Lists all sources cited in your dissertation using a specific citation style (e.g., IEEE, APA,
MLA). Ensure consistency and accuracy in formatting.
13. Appendices (if applicable):
Includes additional material that supports your dissertation but is not essential to
understanding the main text. This may include raw data, questionnaires, detailed descriptions
of methodologies, or supplementary tables and figures.
Tips for Writing a Dissertation
Plan and Manage Time: Break down your work into manageable tasks and set deadlines for
each chapter or section.
Be Clear and Concise: Write clearly and logically, ensuring that each section contributes to
the overall coherence of your argument.
Seek Feedback: Share drafts with your supervisor or peers for constructive feedback and
suggestions for improvement.
In a dissertation, the IEEE referencing style is commonly used for citing sources.
For books, the format includes the author(s), title of the book, edition, place of publication,
publisher, year, and page numbers.
For example, in-text: [1], and in the reference list: [1] A.MM. Musu, Building and Civil Eng
structure’s, 4th ed. Freetown, Sierra Leone: JJ. Peter, 2021, 27. 38-30.
For a book chapter, the format includes the author(s), title of the chapter, Building
and Civil Eng, 5th, place Freetown, JJ. Peterborough, 2022, and 56.
For example, in-text: [2], and in the reference list: [2] A. Chris Jack-Lamin, "Title of
chapter," in Title of Book, the ed. Freetown, Sierra Leone: JJ. JOHN, 1997, 50. 78-100.
For a journal article, the format includes the author(s), title of the article, title of the journal,
volume, issue, page numbers, month, year.
For example, in-text: [3], and in the reference list: [3] A. Author, "Title of article," Abbrev.
Title of Journal, vol. x, no. x, pp. xxx-xxx, Month, year.
For information from a website, the format includes the author(s) (if available), title of the
webpage, name of the website, URL, and access date.
For example, in-text: [4], and in the reference list: [4] A. Author, "Title of Webpage," Name
of Website. [Online]. Available: URL. [Accessed: Month Day, year]
QUSTION 2
Communication in Engineering Firms
Effective communication is essential in engineering firms to facilitate collaboration, ensure
project success, and maintain client satisfaction. Engineers must convey technical
information accurately to both technical and non-technical stakeholders, including coworkers,
clients, and management. Here’s an in-depth discussion on the preferred communication
standards and practices within engineering firms:
Clarity and Precision: Communication in engineering firms should prioritize clarity and
precision. Technical jargon should be used appropriately and explained when necessary to
ensure understanding across different levels of expertise. Ambiguity in communication can
lead to misunderstandings, errors in project execution, and delays.
Structured Reporting: Engineers often need to prepare reports, proposals, and technical
documents. These documents should be well-structured, organized logically, and supported
by data and analysis. Clear headings, bullet points, and visual aids (such as charts and
diagrams) can enhance the readability and effectiveness of technical documents.
Effective Presentations: Engineers frequently need to present their findings, project updates,
and proposals to various audiences. Effective presentation skills involve not only delivering
information clearly but also engaging the audience and addressing questions and concerns
effectively. Visual aids should be used to support key points without overwhelming the
audience with excessive detail.
Collaborative Communication Tools: Engineering firms often utilize collaborative tools such
as project management software, communication platforms (like Slack or Microsoft Teams),
and document sharing platforms (such as Google Workspace or SharePoint). These tools
facilitate real-time communication, document version control, and seamless collaboration
among team members, regardless of their physical location.
Feedback and Iteration: A culture that encourages constructive feedback is crucial in
engineering firms. Engineers should be open to receiving feedback on their work and willing
to iterate based on suggestions and insights from peers, supervisors, and clients. This iterative
process helps improve the quality of deliverables and ensures alignment with project
requirements.
Client Communication: Engineers must effectively communicate with clients throughout the
project lifecycle. This includes understanding client expectations, providing regular updates
on project progress, discussing technical challenges and solutions, and managing client
feedback and expectations. Clear and transparent communication builds trust and strengthens
client relationships.
Training and Development: Engineering firms often provide training and development
opportunities focused on communication skills. This may include workshops on technical
writing, presentation skills, conflict resolution, and cross-cultural communication.
Continuous improvement in communication skills is valued for career advancement within
the firm.
QUESTION 3
From the perspective of both the owner and designer, significant discrepancies between early
estimates and final actual costs can lead to various critical issues. Here are some examples:
Owner's Perspective:
Budget Overrun: A significantly underestimated project cost can result in severe budget
overruns, leading to financial strain or the need to secure additional funding. This could
disrupt the owner's capital allocation strategy and potentially lead to liquidity crises.
Project Scope Creep: If early estimates are too low, the owner might be forced to scale back
the project's scope or compromise on quality, affecting the project's overall value and
functionality.
Stakeholder Discontent: Investors, stakeholders, and end-users may lose confidence in the
owner's project management capabilities, leading to reputational damage and potential
withdrawal of support.
Contractual and Legal Issues: Misalignment between estimated and actual costs can lead to
disputes and litigations with contractors and subcontractors, complicating contractual
obligations and potentially incurring legal costs.
Designer's Perspective:
Design Constraints: If the initial estimate is unrealistically low, the designer may face severe
constraints in material selection, design innovation, and overall project creativity, leading to a
compromised final product.
Professional Reputation: Frequent cost overruns can tarnish the designer’s reputation, leading
to a loss of credibility and future business opportunities.
Resource Allocation: An underestimated budget can cause improper resource allocation,
resulting in inefficiencies, rushed work, and higher chances of errors and rework during the
construction phase.
Client Relationship: Discrepancies between early estimates and final costs can strain the
relationship with the client, leading to potential disputes and dissatisfaction. This could
hinder collaborative efforts and future projects.
In summary, significant underestimation in early project costs can lead to budgetary,
contractual, and reputational risks for both owners and designers, emphasizing the critical
need for accurate and realistic early cost estimation.
QUESTION 4
Here's a breakdown of the dilemmas faced by engineers in Africa, categorized into the
specified areas:
Standard Dilemma: Engineers in Africa often struggle with adhering to international
standards versus local regulatory frameworks. The challenge lies in balancing global best
practices with region-specific requirements, which can affect project feasibility and
compliance.
Geopolitical Dilemma: The geopolitical landscape in Africa introduces complexities such as
regulatory instability, political interference in project execution, and varying levels of
infrastructure development across different countries. These factors impact project planning,
risk assessment, and resource allocation.
Technology Dilemma: Access to cutting-edge technology versus local technological
capabilities poses a dilemma for engineers. While advancements like AI, IoT, and renewable
energy solutions offer transformative potential, limited infrastructure and technological
adoption rates in some regions hinder widespread implementation.
Engineering Professional Practice Act Dilemma: Engineers in Africa encounter challenges
related to the enforcement and interpretation of professional practice acts. Issues such as
licensing procedures, ethical standards, and professional liability frameworks vary
significantly across countries, impacting project execution and industry credibility.
QUSTION 5
Differences Between Project Objectives and Project Scope Definitions
Project Objectives:
Project objectives refer to the specific, measurable outcomes that a project is intended to
achieve. They are the goals and targets that guide the project's execution and success criteria.
Objectives are typically defined in terms of quality, time, and cost constraints. For example,
an objective could be to increase sales by 20% within one year.
Project Scope Definitions:
Project scope defines the boundaries of the project—what is included and what is excluded. It
outlines the deliverables, features, functions, and tasks that need to be accomplished to
achieve the project objectives. Scope provides clarity on the work that needs to be done and
helps in managing expectations. It also includes constraints such as budget, resources, and
timeline.
Interactive Role of Owner and Designer:
In defining project objectives and scope, the owner and designer play crucial roles:
Owner's Role: The owner articulates the business needs and desired outcomes of the project.
They define the objectives in terms of business benefits and strategic goals. The owner
ensures that the project aligns with broader organizational objectives and provides the
necessary resources and support.
Designer's Role: The designer, often an architect or a project manager, translates the owner's
objectives into specific project requirements and scope definitions. They collaborate with the
owner to understand the functional requirements, technical considerations, and constraints.
The designer ensures that the scope is clearly documented and agreed upon by all
stakeholders.
Ensuring Understanding Between Parties:
To ensure a well-defined understanding between the owner and designer:
Clear Communication: Regular meetings and clear communication channels should be
established to discuss objectives, scope, and any changes.
Documentation: Detailed documentation of project objectives and scope helps in avoiding
misunderstandings and scope creep.
Agreement and Sign-Off: Both parties should review and agree on the defined objectives and
scope before proceeding further. Formal sign-off ensures mutual understanding and
commitment.
QUSTION 6
Methods to Assist an Owner in Defining Project Requirements
When an owner lacks expertise in defining project requirements, several methods can assist
in conducting this study:
Consulting with Subject Matter Experts (SMEs): Engaging with experts in relevant fields
such as architecture, engineering, or business analysis can provide valuable insights into
project requirements.
Conducting Workshops: Facilitated workshops involving stakeholders and key team
members can help in identifying and prioritizing requirements. Brainstorming sessions can
clarify needs and expectations.
Benchmarking and Best Practices: Researching similar projects or industry standards helps in
understanding common requirements and best practices.
Prototyping and Mock-ups: Creating prototypes or mock-ups of the project deliverables can
visualize requirements and validate functionality early in the process.
User Surveys and Interviews: Gathering feedback directly from end-users or stakeholders
through surveys and interviews provides insights into their needs and expectations.
Requirement Documentation Templates: Utilizing standardized templates for documenting
requirements ensures completeness and clarity in articulating project needs.
By leveraging these methods, an owner can systematically define project requirements, even
without prior expertise, ensuring that the project objectives are effectively translated into
actionable requirements.