Guidelines Graduation Project-All
Guidelines Graduation Project-All
&
Maritime Transport
Overview
All engineering students must participate in a graduation project as part of the graduation
requirements. The graduation project is an opportunity for students to work as a team to
solve a practical engineering design problem using the engineering skills and knowledge
gained over the past four years. Students must also organize time and tasks in order to
have enough time to complete the project. The project begins in the 9th term (Project I)
and is completed in the 10th term (Project II), as well as facing several challenges, which
indicates that the project objectives have been achieved, including:
- Defining the problem.
- Develop a number of candidate designs.
- Choose the optimal design from among them.
- Manufacture and test specific design.
- Review the chosen design.
- Submit the prototype/proof of concept at the end.
Students document the design process through a report that is reviewed and updated
throughout the academic year. The work will also be regularly presented to a panel of
internal and external examiners from faculty members, corresponding universities and
industry in order to check your progress and offer additional guidance along the way. The
students with their supervisor should also set a timetable for all activities (the initial
design - design stages - typing the project ... etc.). This timetable represents the maximum
time allotted to the project and you may progress more quickly, but it should at least meet
this chart.
2
Project Administration
At the beginning, the topics of the projects are presented and the students are divided into
teams according to the type of the project, with a supervisor on the project from the faculty
members who is responsible for evaluating you during the term with the internal and
external examiner of the project. The hours allocated to the project over the two semesters
are 9 hours (3 hours for the project in the first semester through Project I and 6 hours for
the project in the second semester through Project II).
Each team creates an information storage (google drive) that is a common place and
primary repository for all information associated with this project. Storage can be
accessed from anywhere. All files associated with the project are kept in this storage
location so that all team members, including the team admin, can access them. Also, it
allows you to collaboratively use this shared space on documents without having to email
them back and forth between group members as you review them, also reducing confusion
about the most recent version.
In the Design Team Google drive you’ll find the following subfolders:
1- Reports and Presentations. In this folder, keep the final version of all reports and
presentations.
2- Purchase Orders and Budget. In this folder, keep all purchase order paperwork
with files named so as to be able to discern their contents without having to open
them. Also, save an up-to-date copy of your team’s budget.
3- Work Orders and Shop Hour Tracker. In this folder, keep all work orders
including the associated part files, assembly files, and drawing files.
4- Weekly Meeting Minutes. One member of the team will be charged with keeping
a summary of the minutes for each weekly meeting.
5- Communications and Correspondence. Following each conversation with
supervisor or technical advisor … etc., type a brief summary of the
communication and save it in this folder for future reference.
3
6- Images and Video. It is easier than ever to capture the design process with images
and video, both of which will add to the effectiveness of your reports and
presentations.
7- Student Folder. Make a copy for each member of the team and rename it with
each student’s last name. You’ll use this folder to submit your weekly
assignments and store your personal materials.
Team Roles
Each team will identify someone in their group to assume the following roles:
Leader – tasked with organizing the efforts of the group and managing the project
schedule.
Design Communication Editor – tasked with reviewing reports and presentations
for consistency, ensuring all items included in the rubric are included in the
presentation or report, and proof-reading for spelling mistakes, grammar, etc.
Purchaser – tasked with obtaining purchase information and submitting purchase
orders in accordance with instructions included below.
Technical Support Detachment - tasked with reviewing shop work requests for
completeness, reviewing them with the supervisor.
The supervisor may assign additional roles as necessary.
Project Management.
The project will be implemented through 6 steps, two of which will be implemented and evaluated
during the first semester (project I) and four will be implemented and evaluated during the second
semester (project II), as follows:
4
Project I
Project Proposal (Project I 9th week evaluation)
The Project Proposal is the initial design communication. The client initiates the design process
by soliciting design teams to submit proposals for future work, called a bid. The client then
decides which bid it likes best and hires the design team to provide a design solution. The purpose
of the Project Proposal is to define as specifically as possible the problem and what will be
undertaken over the course of the project to solve it. It should communicate to the reader that a
specific need exists, provide background and context on the problem, present the problem
statement, outline specific design requirements, and convince him or her that a solution can be
achieved in a timely and cost effective manner.
Title Page: The title page shall include project short title, the name of report (in this case the
Project Proposal), the name of the course (Project I or II), the date submitted, the names of each
team member, and the names of the team supervisor.
Executive Summary: The executive summary is a brief summary of the contents of the report. At
its longest, when submitted affixed to your final report, it will be no longer than a page. It is used
to help the reader decide if the report as a whole contains information that is of interest. The
executive summary for the Project Proposal should contain a statement of the problem and a
summary of the work.
Table of Contents/List of Figures/List of Tables: Each report shall include a Table of
Contents followed by a List of Figures and a List of Tables. These come after the
executive summary.
Problem Definition: This section should begin with the problem statement – the one you
were provided at the start of the project. Next, it should include a discussion of the
essential questions and answers derived from preliminary research. These include but are
not limited to:
1. What is the problem? Why is the current situation unsatisfactory?
2. Who is having this problem? Who are the would-be customers for a solution?
3. What basic functions must the design perform?
4. How will the design be used by the customer(s)? Under what circumstances and
in what environment? Don’t limit your considerations only to those of the end
user!
5
5. What additional attributes does the customer want, need, and/or expect from the
design? These might be different from the basic function.
6. What products, currently available, perform a similar function?
7. What products, currently available, were not designed or intended for this
particular application but could be used to perform a similar function?
This section should include all relevant material collected by the team, including figures
and tables, edited and organized so as to provide the unfamiliar reader with all the
information he or she needs to appreciate the work included thereafter. Provide ample
evidence that you have used all sources of information mentioned in the text that are
applicable to your project.
There will likely be some engineering modeling/calculation required to answer some of
these questions, even at this early stage. Also, regardless of the design, there are most
likely associated codes and standards that may place particular constraints on the design
Need Identification: In this section you will define the goals toward which the entire rest of
your project will be focused.
First, include a table of your customer requirements (CRs), listed in order from most important to
least important. Be sure to explain any customer requirements that require it. Accompany the
table with a brief summary – how you developed them, with whom you spoke to confirm them,
and which are most important. Please include images wherever useful in communicating the
necessary details.
Next, include a table of your engineering characteristics (ECs) - listed from most to least
important - including units, and direction of improvement, as appropriate. Specify which of these
design parameters are design variables (a parameter over which the team has a choice) and which
are design constraints (a parameter whose value has been fixed). Discuss the top five ECs and
describe how they relate to your customer requirements.
Finally, include a table of Target Values. For design variables, include a range. For design
constraints, include the constraint limit itself.
Note: Every figure and table must be discussed. Tell the reader explicitly what the figure or table
tells you.
6
Deliverables: Talk to your customer(s). Together, develop a list of what you will provide
them at the conclusion of the project. Think of it in terms of answering the question,
“What are we going to give the customer in exchange for their patronage” be it their time,
material support, or financial support.
Project timeline: Understanding many of the specifics will not have been determined yet,
this section should provide us a proposed timeline by which progress can be tracked and
judged as well as a general schedule as to when they can expect your project deliverables.
Budget: This section should include an accounting of the anticipated expenditures for the
project, provided in table format. For reasons mentioned above, teams shall include a
discussion of which costs are estimated and which are well-defined. For example, because
you have not yet selected a design, you do not know what parts you’ll need to purchase,
let alone how much they cost. In this case, your accounting would be estimated and
perhaps be apportioned according to the stage in the design process (e.g. 200 LE for
testing, fabrication, and redesign), and/or design subsystems (e.g. 100 LE for structures,
100 LE for control, 500 LE for power, etc.). On the other hand, if you are traveling to a
design competition with well-documented travel and entry fees, these expenditures
should be considered well-defined. This budget will be used to request project funds.
For reference, a typical project budget is approximately 10000 LE.
References: Technical documentation should always be written such that without direct
contact with any of the group members someone could follow the design process and
continue or revise the design without reconstructing the project themselves.
Appendices: Appendices should be lettered A – Z and appear in the order they are referenced in
the text. Appendices are composed of any information that does not complement the narrative
flow of the in-text discussion, but must be included for the sake of completeness.
the Preliminary Design Report (PDR) is introduced to document the process of design evaluation
and selection. In it, all design concepts are included. In order to select a single design from these
alternatives they must be compared on an impartial basis, based on each concept’s predicted
performance with regards to the engineering characteristics developed in the Project Proposal. In
7
other words, the selected design which is predicted by modelling and experimentation to do the
best job of meeting the engineering characteristics.
In addition to those sections included in the Project Proposal, the PDR shall include sections
describing the Design Concepts and Concept Evaluation and Selection.
Executive Summary: In addition to what was included in the Project Proposal, include a
brief summary of the design concepts proposed. State which of the concepts was
ultimately selected by the team for detail design and why.
Design Concepts: Included after the Need Identification section, the purpose of this
section is to describe each of your design concepts and demonstrate, using research,
analysis, modeling, and/or experimentation, how each design concept will perform with
regard to each of the top ECs stated in your Project Proposal. Following a brief
introduction – including a description of all proposed design concepts – briefly
summarize which concept generation methods were used by the team and why they were
selected. Each student will develop a unique design concept. For each design concept,
you must have a separate, independent subsection that provides a complete description of
a proposed solution to the problem. It should be able to stand alone without reference to
the other concept subsections. It should describe a specific configuration for the design,
including specification of the major components and/or subsystems. The description of
each design concept should refer to solid models and/or drawings (notice the word
sketches was not used) in order to communicate the design concept. Three-dimensional
models such as foam-board or poster-board mock-ups can be extremely helpful, however,
in most cases computer rendering or professional quality drawings are also required.
Concept Evaluation and Selection: Once you have an objective view of how each of
your candidate designs is expected to perform with respect to each of your top ECs, you
can use this information to make an informed evaluation and select from among your
design concepts. Keep in mind that if there is little variation between the design concepts
with regard to your ECs, you may have to expand your consideration. This section
follows the Design Concepts section.
Summarize the predicted performance of each of your design concepts by creating a table
with the design concepts in the rows and the ECs in the columns. Include the predicted
8
performance parameters for each. Include the weighted-decision matrix and state
explicitly, referencing the matrix, which design was selected and why.
Budget: The budget for the project should be clearer now than it was in the previous
stage, so crude estimates should be revised in favor or more accurate estimates
Assessment Details and Rubric of the Project I (Proposal and Preliminary Design)
The project I is evaluated during the 9th semester as stated in Appendix (A) and according
to the following:
- Initial assessment by an internal examiner during the 9th week (20%).
- Final evaluation at the end of the semester by the project supervisor (40%).
- Final assessment at the end of the academic semester through two examiners, at
least one of whom is external examiner (from the corresponding universities or
from industrialists) (40%).
Assessment criteria are as follows;
A grade
The proposed project has excellent viability, in all relevant areas, including technical
and academic content.
An excellent case for the project is made.
Excellent structure to the presentation, arguments clear and presented in a reasonably
logical order, very good visual aids, very good summarization of project.
An excellent literature review that conforms to all academic requirements is included.
B grade
The proposed project has good viability, in all areas including technical and academic
content.
A very good case for the project is made.
A good structure to presentation, arguments clear, good visual aids, good
summarization of project.
A very good literature review that conforms to nearly all academic requirements is
included.
C grade
9
The proposed project is viable. It has areas including sufficient technical and
academic content.
A good case for the project is made.
Sound structure to presentation, arguments generally clear, reasonable visual aids,
reasonable summarization of project.
A good literature review that conforms to most academic requirements is included.
D grade
The proposed project is viable. It has some areas that include sufficient technical and
academic content. A case for the project is made.
Structure of presentation reasonable, not all arguments clear, some areas superficial,
adequate visual aids, work not well summarized.
A literature review that conforms to some academic requirements is included.
F grades
The proposed project is not viable
Structure of presentation confused, arguments unclear, work is largely superficial,
visual aids poor, work not well summarized.
No literature review or very poor conformity to academic requirements.
10
Project II
Detail Design Report (Project II 9th week evaluation)
Detail Design is a process which involves making decisions at successively finer levels of detail;
from enumerating functions, to identifying systems and subsystems to carry out those functions,
to designing and selecting specific components, to manufacturing and assembling those
components. The purpose of the Detail Design is to capture these choices in a process that will
ultimately result in the first generation prototype, ready for testing and evaluation.
Embodiment Design: Begin by providing a short overview of the prototype (not the
process of creating it), including an image of the envisioned completed system. The
purpose of this is to help the reader or members of the audience better understand your
detailed explanation to follow.
Next, discuss system or product architecture. Start with your decomposition as
appropriate. Identify the necessary components and summarize the key energy, mass,
and information flows. Review your different designs with regard to product architecture,
discuss how you arrived at the final layout, and what factors influenced your decision.
Be sure to include visual aids – simple block diagrams or flow charts are fine – and
identify the interactions between the modules (important because this is the most likely
point of failure).
Then, discuss configuration design. This section should include a drawing of the entire
assembly, preferably expanded to show detail. For each standard part (i.e. any part that
can be purchased and won’t need to be manufactured), provide justification in terms of
calculations and analysis as to why that particular part was selected.
Prototype Test Plan: At this point in your academic career, you’ve completed many lab
experiments and written many lab reports. Now it’s your turn to design the experiment.
You’ll need to test each of your top five ECs (and perhaps more) to determine whether or
not you’ve satisfied your customer(s) and met his/her/their constraints. You’ll also
compare the performance of your design to your targets to determine where to apply your
additional time and resources in order to best satisfy your customer(s).
As such, create one or more test plans for evaluating each of your top ECs. Keep in mind,
one experiment may provide measurement/observation for more than one EC. For this
11
report, you will write the Objectives, Background (as necessary), and Procedures sections
for each experiment. Unlike the Procedures section in a typical lab report which are
outlined in a handout provided by your instructor, you’ll have to provide the level of detail
that would otherwise be given in the handout. Be sure to include what parameters will
be fixed (some of which might need to be measured such as ambient temperature or
pressure), which will be varied and how, which will be measured, where the test will take
place, who will conduct the test, what equipment is needed, and what safety measures are
required. Include a safety plan in accordance with the division safety instruction as
necessary. Next semester you’ll write the Results, Analysis, and Discussion sections after
you’ve done the experiments.
For each test, create a test plan matrix and include them in an appendix.
Project Timeline: For the report, include a summary table as before including major,
project-specific tasks, the dates they are to be completed, and the personnel to which they
are assigned. Include your Gantt chart in calendar output format, as an appendix.
Budget: With detail design complete, the budget should be a translation of the purchase
orders you are ready to submit. There should be little uncertainty in your accounting.
Appendix – Engineering Drawings: as described above.
Appendix – Prototype Test Plan test matrices: as described above.
Appendix – Project Gantt Chart: as described above.
12
Prototype Demonstration (Project II 9th week evaluation)
The purpose of this assignment is to provide faculty and staff an opportunity to evaluate your
progress toward project completion by demonstrating your design prototype. 15 minutes’
presentation has to be introduced to discuss your prototype. You can demonstrate your prototype
anywhere in the complex so long as you arrange it with your project supervisor in advance.
Practice your presentation just as you would any other presentation. Ensure all group members
give a portion of the presentation. Be sure to discuss the following at a minimum:
Team and project introduction
Problem statement
General description of prototype
Description of subsystems
Description and demonstration of operation
Fabrication/manufacturing
Summary of prototype test plan
Summary of next steps
As you enter the first phase of testing and evaluation, you’ll find that the design process may
become much more recursive: design, build, test, break, repeat. There may not be a clear
delineation between versions 1 and 2. Thus, the purpose of the Progress Update Report (PUR) is
to provide a formal opportunity for reflection and to capture what you’ve done, summarize what
you plan to do with what time you have left, and plan out how you’re going to do it.
General Guidance:
All projects fall somewhere on a broad spectrum of scope and complexity. Some projects
are small in scope with designs that take little time to fabricate and test. Teams with these
sorts of projects may get the opportunity to go through several iterations - cycles of
design, build, test. With regard to the PUR, these teams should present the results,
analysis, and discussion – including how the design has or will change as a result of
fabrication and testing – for each of the experiments conducted in accordance with their
prototype test plan.
13
Other projects are of such scope and complexity that teams may only get one or two
opportunities to test their design. If your team’s project lies on this end of the spectrum,
you may still be working toward executing your prototype test plan. In this case, the
focus is twofold: 1) capture your design decision-making process, and 2) communicate
your progress with regard to the established project management plan.
In capturing your decision-making process, the intent here is not to digress into a day-to-
day design journal, but to summarize the group’s thought process: what design decisions
did you face? What were the considerations surrounding each design decision? What
did the team choose to do and why? For example, one year a team was tasked with
building a hydrofoil – essentially an underwater airplane. They had ordered aluminum
extrusions in the shape of an airfoil that they were going to use for wings. However, there
was a significant delay in the purchasing process and the students had to explore other
options. Why record this information you may ask? This project was sponsored by
Boeing. Several years down the road, if Boeing engineers want to build upon the efforts
of this student team, knowing what decisions were made and why is likely to save the
Boeing engineers a great deal of time and effort in not repeating what was already done.
Tracking and communicating your progress with regard to the project management plan
is especially critical for team whose projects have a significant scope and/or are fairly
complex. This is because you may only have time enough time to get one or two tests in
before Capstone Day. It is equally critical that you establish a well-considered project
management plan and prove to yourselves, your team leadership, and the review board,
that you are aware of your current progress with respect to the timeline and have a detailed
plan of execution. This discussion should be included in the Project Management section.
Regardless of where you fall on the spectrum of scope and complexity, the overall intent
is communicating your progress and to assure the board that you will finish what you set
out to achieve by the end of the semester. Exactly what content is required to
communicate this should come from a discussion with your team mentor and technical
expert.
Project Timeline: See guidance in preceding section.
14
Appendix – Engineering Drawings: Include all updated engineering drawings, paired
with the original versions (i.e. keep drawing revisions together in this appendix so the
reader can see how the design progressed).
The purpose of the final design report is to capture the details of your entire design process.
Specific additions since the Progress Update Report should include the results, analysis, and
discussion from your prototype test plan, competition results from applicable projects, and what
is your conclusion and future work.
Executive Summary: include a brief summary of your testing, evaluation, and redesign
process. Also include a brief summary of final evaluation results, including competition
results for applicable projects.
Prototype Test Plan: if your team had the opportunity to do one test or a dozen, please ensure all
testing and evaluation details are captured here. Ensure the discussion is held together with a
strong, logical narrative, but the specific formatting of this final version is up to you and your
team supervisor.
For a given EC you may have multiple modifications/redesigns and multiple associated
tests. Please try and capture, to the best of your ability, what changes were made to the
design and how those changes affected the performance of the design. Make sure to
compare initial and subsequent design performance and comment as to whether or not the
design changes made resulted in better performance and thus increased customer
satisfaction.
Future Work: In this section, the idea is to try and capture your customers’ level of
satisfaction with your design. Detail specific opportunities for future work and
improvement. Please limit your comments to technical evaluations.
Appendix - Closeout Memo: each member of the team will write a memo, addressed to
his or her project mentor, no more than two pages in length addressing the following
questions in order:
1. What did you do, specifically? What were your roles in the team – official and un-
official.
2. What did you learn about engineering, project management, team dynamics, etc.?
How does this compare to your original personal statement in the team charter?
15
3. What would you do differently, given the opportunity? (from a personal as opposed
to a technical standpoint)
4. What advice would you give to the next class?
5. What resources (people, books, programs, etc.) were most useful to you and how?
6. What grade to you think you’ve earned and why?
Include the closeout memos in alphabetical order by last name.
The project II is evaluated during the 10th semester as stated in Appendix (A) and according to
the following:
16
B grade
The researched information has been obtained from a wide range of relevant sources.
The work demonstrates a good understanding of the problem,
- technical issues understood but some limitations
- good analysis of data
- originality
The recommendations relate to the analysis and are reasonably realistic.
The limitations of the recommendations are recognized.
Further work is clearly identified.
The written report is of a professional nature, researched work is well integrated,
body of report is well structured, and arguments are well presented.
The Management Report is sound, well structured; arguments are well presented and
always clearly justified.
The ethical issues associated with the project have been addressed.
C grade
The researched information has been obtained from a range of relevant sources.
The work demonstrates a sound understanding of the problem,
- technical issues understood to a satisfactory level
- limited analysis, too much description
- limited recommendations which may not be realistic
Further work not identified.
The written report is sound, researched work is reasonably well integrated, body of
report is reasonably well structured, and arguments are reasonably well presented but
not always clearly justified.
The Management Report is sound, reasonably well structured; arguments are
reasonably well presented but not always justified.
The majority of ethical issues associated with the project have been addressed
17
D grade
The researched information is limited
The work demonstrates some understanding of the problem
- technical issues understood superficially
- limited description
- analysis is present but limited
the work contains minor inaccuracies
No real recommendations
Further work identified but not logical.
The written report is not well structured but some attempt has been made to argue a
case.
The Management Report is not very well structured; arguments are presented but not
clearly justified.
The ethical issues associated with the project have not been addressed well
F grades
The researched information is limited
The work demonstrates little understanding of the problem
- technical issues not understood
- limited description
- no analysis
the work contains many inaccuracies
No real recommendations
Further work not identified
The written report is not well structured.
The Management Report demonstrates poor understanding of the subject as listed on
the agreed checklist, and it is not introduced.
The ethical issues associated with the project have not been addressed.
18
Guidelines for Presenting Written Work
The project is written and presented at the end of the semester according to the guidelines stated
by templet in Appendix (B).
Project Poster
The purpose of the poster is to present a summary of each team’s capstone design project
to fellow students, faculty, staff, and visitors in a professional, eye-catching visual format.
Teams should emphasize visual/graphical versus textual explanations to the maximum
extent appropriate. The textual portions of the poster should be written with the non-
technical reader in mind. Specifically, the poster should have the following:
1. Project title, department name, course number, group member names, and project
supervisor’s name
2. Concise problem statement
3. Brief explanation of the project background
4. List of customer requirements
5. Figures of design concepts
6. Figure of selected design
7. Brief explanation of testing and evaluation (including images!)
8. Brief summary of the project outcome
9. Group picture with caption including group member names
Items 3-5, may be truncated or omitted as necessary to preserve presentation clarity.
Creative formatting, layout, and style are highly encouraged so long as they do not detract
from the purpose of the poster. Additional pictures showing design efforts, fabrication,
installation, testing, and design use are also highly encouraged.
Formatting:
1. Create all posters in PowerPoint (2010 version is preferred).
2. Size poster
a. Click on the “design” tab, and select “Page setup”
b. Select Landscape orientation
c. Make width 40” and height 30”
3. Insert text
a. As a general rule:
i. Title: 100 point font
ii. Body: 40 point font
4. Insert pictures
a. Use .jpg format
b. Use image files larger than 80k
c. Check images at 100% size to ensure images are not overly pixilated
i. Click on “View”, then “Zoom” and select the “100%” radio
button
Submission: once you and your team supervisor have agreed on the final poster design,
print a copy on an 8.5” x 11” sheet of paper.
19
Project Allocation
Proposal Details.
Project title: Give the title of your project.
Project team
1-
2-
3-
4-
Supervisors:
1-
2-
Objectives
Describes the project’s goal
III- Publication:
20
Detailed Plan on Project Activates (Gantt Chart):
Signatures
21
ARAB ACADEMY FOR SCIENCE, TECHNOLOGY AND MARITIME TRANSPORT
COLLEGE OF ENGINEERING AND TECHNOLOGY
Smart Village
Available Attained
Grading Criteria or Requirement
Mark Mark
Front Matter & Problem Definition
- Title Page: team member’s names, project title.
- Engineering modeling/calculation. 5
- Applicable codes and standards.
- Revised problem statement-include discussion of design concepts and design selection
Need Identification
- Table of CRs, in order of importance, discussion.
- Table of ECs including units and direction of improvement; identification of which are variables
5
and which are constraints, discussion.
- Technical Assessment tables; benchmark specs and images included discussion of agreement.
- Table of targets; description of how targets defined
Project Timeline
- Table of project-specific milestones. 5
- Specific members tasked as appropriate.
Budget: Discussion of anticipated costs and Table of expenditures; appropriate level of detail 5
Total 20
Internal Examiner:
Signature: ( )
Scoring
5.0 rating – All criteria are outstandingly present 3.0 rating – Some deficiency in criteria present
4.0 rating – All criteria sufficiently present 2.0 rating – Moderate deficiencies in criteria present
1.0 rating – A number of deficiencies to the extent where the
criteria is unacceptable
ARAB ACADEMY FOR SCIENCE, TECHNOLOGY AND MARITIME TRANSPORT
COLLEGE OF ENGINEERING AND TECHNOLOGY
Smart Village
# Available Attained
Evaluation Criteria for Ethical Reasoning (a part of OUTCOME 4A)
Mark Mark
Ethical Self-Awareness
1 Student discusses in detail/analyzes both core beliefs and the origins of the core beliefs and 5
discussion has greater depth and clarity
Understanding Different Ethical Perspectives/Concepts
2 Student names the theory or theories, can present the gist of said theory or theories, and 5
accurately explains the details of the theory or theories used
Ethical Issue Recognition
3 Student can recognize ethical issues when presented in a complex, multilayered (gray) 5
context and can recognize cross-relationships among the issues
Application of Ethical Perspectives/Concepts
4 Student can independently apply ethical perspectives/concepts to an ethical question, 5
accurately, and is able to consider full implications of the application
Evaluation of Different Ethical Perspectives/Concepts
Student states a position and can state the objections to, assumptions and implications of
5 5
and can reasonably defend against the objections to, assumptions and implications of
different ethical perspectives/concepts, and the student's defense is adequate and effective
Total 25
# Available Attained
Evaluation Criteria for Leadership and Teamwork (OUTCOME 5)
Mark Mark
Contributes to Team Meetings (5A)
1 Helps the team move forward by articulating the merits of alternative ideas or proposals. 5
Facilitates the Contributions of Team Members (5B)
2 Engages team members in ways that facilitate their contributions to meetings by both 5
constructively building upon and synthesizing the contributions of others as well as
noticing.Contributions
Individual When someone is not participating
Outside and inviting
of Team Meetings (5A) them to engage.
3 5
Completes all assigned tasks by deadline; work accomplished is thorough,
comprehensive,
Fosters Constructive andTeam
advances the project.
Climate (5B) Proactively helps other team members
complete atheir
Supports assigned team
constructive tasks climate
to a similar level all
by doing of excellence.
of the following:
4 1. Treats team members respectfully by being polite and constructive in communication. 5
2. Uses positive vocal or written tone, facial expressions, and/or body language to convey a
positive attitude about the team and its work.
3. Motivates
Responds teammates
to Conflict by expressing confidence about the importance of the task and the
(5A)
5 team's ability to accomplish it.directly and constructively, helping to manage/resolve it 5
Addresses destructive conflict
4. Provides
Totalinmark assistance
a way that and/oroverall
strengthens encouragement to team members.
team cohesiveness and future effectiveness 25
# Available Attained
Evaluation Criteria - Term Work
Mark Mark
Literature survey and research work: (OUTCOME 7)
1. Clear and complete background analysis of the problem is provided. (7A) 5
2. Is able to understand, interpret, and apply learned materials and concepts through
3 5
course of study (7A).
3. Is good in self-learning new topics (7A). 5
4. Is able to search for problems solutions without guidance (7B). 5
Total 20
Available Attained
Mark Mark
Total Evaluation 70
Average 40
Supervisor:
Signature: ( )
Scoring
5.0 rating – All criteria are outstandingly present 3.0 rating – Some deficiency in criteria present
4.0 rating – All criteria sufficiently present 2.0 rating – Moderate deficiencies in criteria present
1.0 rating – A number of deficiencies to the extent where the
criteria is unacceptable
ARAB ACADEMY FOR SCIENCE, TECHNOLOGY AND MARITIME TRANSPORT
COLLEGE OF ENGINEERING AND TECHNOLOGY
Smart Village
Examiner 1: Examiner 2:
Signature: ( ) Signature: ( )
Scoring
5.0 rating – All criteria are outstandingly present 3.0 rating – Some deficiency in criteria present
4.0 rating – All criteria sufficiently present 2.0 rating – Moderate deficiencies in criteria present
1.0 rating – A number of deficiencies to the extent where the
criteria is unacceptable
ARAB ACADEMY FOR SCIENCE, TECHNOLOGY AND MARITIME TRANSPORT
COLLEGE OF ENGINEERING AND TECHNOLOGY
Smart Village
Total Score
Examiner 1: Signature:( )
Examiner 2: Signature:( )
Supervisor: Signature:( )
Scoring
5.0 rating – All criteria are outstandingly present 3.0 rating – Some deficiency in criteria present
4.0 rating – All criteria sufficiently present 2.0 rating – Moderate deficiencies in criteria present
1.0 rating – A number of deficiencies to the extent where the
criteria is unacceptable
Graduation Project Guidelines
The graduation project should adhere the following organization and format.
Organization
Title Page
Declaration
Abstract
Dedication (optional)
Acknowledgments
Table of Contents
List of Tables
List of Figures
List of Acronyms/Abbreviations
List of Utilized Standards
List of Realistic Constraints
Main Body
References
Appendices (as needed)
The main body of the thesis or project report should be organized according to the
following general outline :
o Cost
o Environmental impact
M O N T H – Y E A R
o Manufacturability
o Ethics
o Social and Political Impact (if any)
o Health and Safety
o Sustainability
Format
The following is the format to use for the project documentation (see next page).
Arab Academy for Science, Technology and Maritime
Transport
Department Name
PROJECT TITLE
Project Subtitle
Presented By:
Student Name
Supervised By:
Supervisor(s)
DECLARATION
I hereby certify that this material, which I now submit for assessment on the programme
of study leading to the award of Bachelor of Science in (insert title of degree for which
registered) is entirely my own work, that I have exercised reasonable care to ensure that
the work is original, and does not to the best of my knowledge breach any law of
copyright, and has not been taken from the work of others save and to the extent that
such work has been cited and acknowledged within the text of my work.
Signed: _____________________________
Use this section to acknowledge the contribution of different people to your work; these
may include your supervisor(s), industry partners, sponsors, financial support, specific
faculty members in your department, and even your family.
ABSTRACT
The report must begin with a one- to two-paragraph abstract (max 350 words) that
orients the reader as to the contents as well as to the major sections of the report. The
abstract, by itself, must provide enough information about the project so that the reader
can judge simply by reading this portion if he or she wants to read further.
For example, as an abstract for this document, this document has been prepared by the
College of Engineering and Technology to help Undergraduate students in preparing
their final year project report. The document presents a general outline for these
documents as well as the formatting that students must abide to. Also, the exact method
for citation and referring to literature related to your work is detailed.
TABLE OF CONTENTS
1 INTRODUCTION .................................................................................................................................. 1
i
LIST OF FIGURES
ii
LIST OF TABLES
iii
LIST OF ACRONYMS/ABBREVIATIONS
iv
v
LIST OF UTILIZED STANDARDS
vi
vii
LIST OF REALISTIC CONSTAINTS
viii
Chapter One
1 INTRODUCTION
Presented By:-
1- Student name
2- Student name
This document was developed in order to standardize the method of writing final year
projects and to fulfill the requirements for the accreditation by the British Institute and
the basic criteria required for the preparation of the projects are as listed below:
1. The projects should not be dependent on internet information.
2. Images/figures … etc. should be referenced.
3. The experimentation, if any, should be subject to review of the work done, results
obtained, implications, conclusions, reflections … etc.
4. The text format should be consistent between chapters and the standard of English
used in the text should not be varied.
5. The project should contain strong elements of Design and Analysis activity,
experimental work where appropriate, manufacturing elements as appropriate and
include some business decisions such costing … etc.
6. The literature review should not be more than an account of the work undertaken by
students.
7. The conclusions should not be very short.
The details of how to format your document correctly and how to include your citations
and references are given in the following chapters of this document.
1
Chapter Two
2 FORMATTING DESCRIPTION
Presented By:-
1- Student name
2- Student name
The physical layout and formatting of your final year project report is highly important,
yet is very often neglected. A tidy, well laid-out and consistently formatted document
makes for easier reading and is suggestive of a careful and professional attitude towards
its preparation.
In effect, this document has been developed to give you the guidelines for preparing
reports for your final year project. Use this document as a template if you are using
Microsoft Word 6.0 or later. Otherwise, use this document as an instruction set.
Please set up your cover page so that the information listed below is visible through the
window of the front cover page of your project and in the correct format. The title page
should contain the following:
The Arab Academy for Science and Technology and Maritime Transport
(AASTMT) logo: a black and white logo should be centred and on top of the page
with a size of 3.25 cm x 3.25 cm.
The AASTMT title: this should be in Times New Roman, bold, 18 pt., title case,
centred, single line spacing, with 18 pt. spacing before and 72 pt. spacing after.
College title: this should be in Times New Roman, bold, 16 pt., title case, centred,
single line spacing, with 0 pt. spacing before and 0 pt. spacing after.
Your department title: this should be in Times New Roman, bold, 16 pt., title case,
centred, single line spacing, with 18 pt. spacing before and 48 pt. spacing after.
2
Project degree: this should be in Times New Roman, regular, 14 pt., title case,
centred, single line spacing, and no paragraph spacing.
Project title: this should be in Times New Roman, bold, 16 pt., all caps, centred,
single line spacing, with 72 pt. spacing before and 18 pt. spacing after.
Project subtitle: this should be in Times New Roman, bold, 16 pt., title case,
centred, single line spacing, and 48 pt. spacing after.
Presented by, student name, supervised by, and supervisor(s) name: this should
be in Times New Roman, regular (names in italic), 14 pt., title case, centred, single
line spacing, and 24 pt. spacing after.
Month – Year: this should be in Times New Roman, regular, 10 pt., Title case,
centered, footer text with no spacing before or after.
It should be noted that setting the line spacing and the spacing between different
paragraphs is accessed from the format menu, in MS Word, by selecting “Paragraph…”.
Deceleration.
Dedication (optional).
Acknowledgements.
Chapters
Chapter 1, which would be an introduction to the work. A 'Funnel' approach
which begins broadly within the topic and concludes the chapter with; focus on
what this thesis delivers, and where to find it in the other Chapters.
Chapter 2 is information gathering or literature review.
Chapter 3, 4 and 5 (and more if needed) would be specific work carried out and
appropriately collated to read well.
Chapter 6 would be overall Discussion and review/reflection on achievements.
3
Chapter 7 would be Conclusions.
Chapter 8 a small Chapter of Future Work, indicating a jumping off point for the
next investigator.
References.
Appendices (optional).
Your project report should be printed (single sided) on good quality A4 paper. Project
reports should be thermal-bound. Page should be set-up as shown in Figure 2-1. The
minimum number of pages for final year project reports is 50 pages (main report
chapters only). Remember that quantity does not automatically guarantee quality; a 150
page report is not twice as good as a 75-page one.
4
Figure 2-2: Paragraph settings.
The body text of the whole document should be in 12 pt Times New Roman font,
justified alignment, no indentation for first line in paragraphs, spacing before
paragraphs 12 pt, and line spacing set at 1.5 lines; as shown in Figure 2-2.
There are different headings and sub-headings that you may find useful in organizing
your report; these are summarised in Table 2-1.
Style Name in
Template Used for Format
Chapter Label Chapters labelling Times New Roman, Italic, 14 pt., expanded by
3.5, centred, space after: 24 pt., and page break
before.
Heading 1 Chapter title Times New Roman, bold, 16 pt., all caps,
centred, space before: 12 pt., space after: 36
pt., and outline numbered at level 1.
Heading 2 Main headings Times New Roman, bold, 14 pt., all caps,
aligned to the left, space before: 18 pt., space
after: 12 pt., and outline numbered at level 2.
Heading 3 Sub-headings level 1 Times New Roman, bold, 14 pt., title case,
5
aligned to the left, space before: 12 pt., space
after: 12 pt., and outline numbered at level 3.
Heading 4 Sub-headings level 2 Times New Roman, bold, 13 pt., title case,
aligned to the left, space before: 12 pt. and
space after: 12 pt.
Use the word “Figure” (“Table”) even at the middle of a sentence when referring to a
figure (Table) in text and make sure that all figures and tables are referred to. If your
figure has two parts, include the labels “(a)” and “(b)” as part of the figure itself (do not
use two different captions for each figure). Please verify that the figures and tables you
mention in the text actually exist.
Do not put borders around the outside of your figures. Do not use color unless it is
necessary for the proper interpretation of your figures. When re-sizing your figures,
make sure that you use the same percentage for your figures height and width.
Use Times New Roman, 12 pt., aligned to the left, single line spacing and with space
before: 6 pt. and space after: 6 pt. The style defined in this template for the text used in
tables is “Body Text (Tables)”.
Place figure captions below the figures; place table titles above the tables. Figure labels
should be in Times New Roman, bold, 10 pt., and centered with 6 pt. spacing before and
24 pt. spacing after. Table titles should be in Times New Roman, bold, 12 pt., and left
aligned with 12 pt. spacing before and 12 pt. spacing after.
The style defined for figure captions in the template is “Caption” and for table titles is
“Table Caption”.
6
2.4.2 Numbering of Figures and Tables
All figures and tables must be numbered in their order of appearance in text. Also, the
chapter number must be included in the numbering with a hyphen separating the chapter
number and the figure/table number in that chapter. This is set through the caption
dialogue box in MS Word as shown in Figure 2-3.
When referring to figures and tables in your text you can use “Figure 1-1 shows…”, “as
shown in Figure 1-1”, “(Figure 1-1)”, or “Table 1-1”.
7
Figure 2-4: Using Cross-reference.
2.5.1 Units
Using SI units as primary units are strongly encouraged. English units may be used as
secondary units (in parentheses). An exception is when English units are used as
identifiers in trade, such as “3½ in disk drive.” Avoid combining SI and English units,
as this often leads to confusion because equations do not balance dimensionally. If you
must use mixed units, clearly state the units for each quantity in an equation.
Define abbreviations and acronyms the first time they are used in the text, even after
they have already been defined in the abstract. Abbreviations such as SI, ac, and dc do
not have to be defined. Abbreviations that incorporate periods should not have spaces:
write “C.N.R.S.,” not “C. N. R. S.” Do not use abbreviations in the title unless they are
unavoidable.
2.5.3 Equations
Number equations consecutively with equation numbers in parentheses flush with the
right margin, as in (1). First use the equation editor to create the equation. Then select
the “Equation” mark-up style. Press the tab key and write the equation number in
parentheses. Use parentheses to avoid ambiguities in denominators. Punctuate equations
when they are part of a sentence, as in
r2
0
F ( r, ) dr d [ r2 / (2 0 )]
exp( | z j zi | ) 1 J 1 ( r2 ) J 0 ( ri ) d .
0
(1)
Be sure that the symbols in your equation have been defined before the equation appears
or immediately following. Refer to equations as “Equation (1) is…”; even if it is in the
middle of a sentence.
8
2.5.4 Other Recommendations
Use one space after periods and colons. Hyphenate complex modifiers: “zero-field-
cooled magnetization.” Avoid dangling participles, such as, “Using (1), the potential
was calculated.” [It is not clear who or what used (1).] Write instead, “The potential was
calculated by using (1),”
Use a zero before decimal points: “0.25,” not “.25.” Use “cm3,” not “cc.” Indicate
sample dimensions as “0.1 cm 0.2 cm,” not “0.1 0.2 cm2.”
Do not mix complete spellings and abbreviations of units: use “Wb/m2” or “webers per
square meter,” not “webers/m2.”
The serial comma is preferred: “A, B, and C” instead of “A, B and C.”
If you wish, you may write in the first person singular or plural and use the active voice
(“I observed that ...” or “We observed that ...” instead of “It was observed that ...”).
However, passive voice is preferred.
9
Chapter Three
Presented By:-
1- Student name
2- Student name
The report should be based on the student’s own work and in case of using any parts or
copying any figures or diagrams from previous work this should be properly referenced
according to the format explained below.
A numbered list of references must be provided at the end of the paper. The list should
be arranged in the order of citation in text, not in alphabetical order. List only one
reference per reference number.
Footnotes or other words and phrases that are not part of the reference format do not
belong on the reference list. Phrases such as “For example,” should not introduce
references in the list, but should instead be given in parentheses in text, followed by the
reference number, i.e., “For example, see [5].”
Books:
[1] G. O. Young, “Synthetic structure of industrial plastics,” in Plastics, 2nd ed., vol.
3, J. Peters, Ed. New York: McGraw-Hill, 1964, pp. 15–64.
10
[2] W.-K. Chen, Linear Networks and Systems. Belmont, CA: Wadsworth, 1993, pp.
123–135.
Periodicals:
[4] E. P. Wigner, “Theory of travelling-wave optical laser,” Phys. Rev., vol. 134, pp.
A635–A646, Dec. 1965.
[5] E. H. Miller, “A note on reflector arrays,” IEEE Trans. Antennas Propagat., tobe
published.
[7] D. Ebehard and E. Voges, “Digital single sideband detection for interferometric
sensors,” presented at the 2nd Int. Conf. Optical Fibre Sensors, Stuttgart,
Germany, 1984.
Standards/Patents:
[8] G. Brandli and M. Dick, “Alternating current fed power supply,” U.S. Patent 4
084 217, Nov. 4, 1978.
Technical Reports:
11
3.2 REFERENCES TO ELECTRONIC SOURCES
The guidelines for citing electronic information as offered below are a modified
illustration of the adaptation by the International Standards Organization (ISO)
documentation system and the American Psychological Association (APA) style. Three
pieces of information are required to complete each reference: 1) protocol or service; 2)
location where the item is to be found; and 3) item to be retrieved. It is not necessary to
repeat the protocol (i.e., http) in Web addresses after “Available” since that is stated in
the URL.
Books:
[10] J. Jones. (1991, May 10). Networks. (2nd ed.) [Online]. Available:
http://www.atm.com
Journals:
[12] PROCESS Corp., MA. Intranets: Internet technologies deployed behind the
firewall for corporate productivity. Presented at INET96 Annu. Meeting. [Online].
Available: http://home.process.com/Intranets/wp2.htp
12