Structure of Final Report of Capstone Project
Uploaded by
ScribdTranslationsStructure of Final Report of Capstone Project
Uploaded by
ScribdTranslationsFinal Report of Capstone Project
Project Name
Name1 Lastname1 Lastname5;[email protected]
Name2 Lastname2 Lastname6;[email protected]
Name3 LastName3 LastName7;[email protected]
Teacher: Name Surname;[email protected]
Computer Systems Engineering Program
Private University of the North
San Juan de Lurigancho Campus - Lima, Peru, 2020
SUMMARY
The final report of the Capstone Project must be a maximum of 10 pages and must
highlight that an engineering design, appropriate constraints and standards are used.
The summary should include the main points of the project (problem, method used)
and results obtained), which will provide a view of the complete work. It must have
a maximum length of 200 words. The inclusion of 5 keywords is suggested.
ABSTRACT
Same.
I. INTRODUCTION
Reality check: this section clearly identifies and describes without
ambiguities its final theme (or final thematic area) Include sufficient information
introductory and/or background for the reader to appreciate the statement
of the problem in the following section.
II. DESCRIPTION OF THE PROBLEM
Express the problem you will address in a simple sentence. You may find
difficulties in articulating the problem in a sentence. If so, the reason may be
that is thinking about more than one problem or that is overloading the statement
of the problem with too many details.
Examples of problem statements:
• The confidential information received from third parties is not adequately
protected in many universities.
• Forty percent of graduate students in the BIG program
DATA that complete their courses never finish a final project.
• The documentation requirements necessary to obtain approval for
selling a biological product in Peru. They have become too complex and
massive to manage them effectively in paper format.
II.1 Importance of the problem and potential benefits
Discuss / explain the problem. Here you can provide details and add
rating. In this section, do not include statements that refer to your
enthusiasm for the subject, past experiences, and their general desire to graduate.
Rather, use the following questions to guide your discussion: why do others
Would they be interested in your proposed work? If a solution or a solution
partial can be identified and studied and/or developed, what would be the
potential benefits? Reality check: Are they reasonable?
claims of benefits? Test your answers to these questions against
the (feared) challenge questions that potential committee members
Can they do: Who cares? or So what?
II.2 Project Objectives
The objectives are broad in nature. Often responding to the question:
What are the best possible results of this final project? It will identify the
goals. For a software development project, an example objective could be
Develop a system that has the necessary processing capability
to meet the expected transaction volumes of the organization
over the next 10 years. Alternatively, the statements of objectives
they can be seen as a summary of the motivations to study. For some
projects, a statement of purpose is sufficient. A high-level explanation
level can accompany the statement of objectives.
II.3 Specific objectives of the project
Objectives are activities that support the achievement of goals. For a project of
software development, an example objective could be: Develop a
prototype to explore alternative approaches to meet the requirements of
transaction processing performance.
III. THEORETICAL FRAMEWORK
This section, which is sometimes referred to as literature review,
presents a summary and a synthesis of the existing work that has already been reported.
related to the problem statement, the goals of the project and/or the
project objectives. The types and sources of previous work that will be presented here
they will depend on the nature of your proposed project. For example, suppose that
he is interested in the development of an application with augmented reality. This is
an emerging field that has already attracted academic researchers, as well as to the
open source community. For this example, the previous work section
It will include both references to published research and to open source software.
open available. A bibliographic search in research journals
it will identify the first ones, while a web search will locate the
Mondays.
On the contrary, if your project is based on an HTML5 application, then the
previous work section will likely include references to tutorials and
Information on standards, an assessment of the potential of HTML5, and reports of
applications located through a web search.
IV. SOLUTION APPROACH
IV.1 Plan
This section presents, in detail, your plan to complete the project. This is not
a timeline. It should specify what steps it will follow and describe and explain the
main activities at each step.
Reality check: have you fully specified your approach?
Will the reader come to the conclusion that they have carefully considered what
What needs to be achieved to complete the proposed final project?
IV.2 Challenges or barriers
Clearly indicate any technical, resource, or process challenges that
may affect your ability to carry out the plan specified in the section
4.1. How do you plan to overcome these challenges? Reality check: Are they
Are the proposed strategies reasonable for overcoming the challenges?
IV.3 Limitations
An important element when writing a proposal is to set boundaries on the
scope of the project. The known challenges / barriers often suggest
the need to reduce the scope. Indicate and justify the scope of your project
proposed.
Reality check: has it justified the limitations of the scope of
project with a solid reasoning?
IV.4 Deliverables
Indicate and describe accurately the results that you will deliver as a result of
follow the plan specified in section 4.1.
Reality check: Are your deliverables stated clearly?
unequivocal?
V. TECHNICAL DESCRIPTION
Analyze the software design and the proposed implementation approach with
sufficient detail for the reader to determine their readiness for
undertake the proposed project. Generally, it is helpful to improve the discussion about
the design with an appropriate modeling language and/or graphics.
VI. RESULTS
This section should contain the results obtained after the implementation.
or simulation. They must be discussed when compared to the standards
previously identified appropriate ones.
VII. CONCLUSIONS
This section should contain the conclusions of the objectives mentioned in the
introduction.
VIII. REFERENCES