Scribd
Upload
27 views

Capstone 1 Report Checklist

The document outlines the requirements for a Capstone 1 report, including sections on introduction, use case, requirements, design, schedule, and budget. It provides detailed instructions for each section, specifying required subsections, content, and formatting. Key aspects that must be included are problem statement, stakeholder interests, ethics, figures, use case description, requirements table, architectural decisions, prototypes, work breakdown structure, schedule charts, and budget.

Uploaded by

ali basit
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
27 views

Capstone 1 Report Checklist

The document outlines the requirements for a Capstone 1 report, including sections on introduction, use case, requirements, design, schedule, and budget. It provides detailed instructions for each section, specifying required subsections, content, and formatting. Key aspects that must be included are problem statement, stakeholder interests, ethics, figures, use case description, requirements table, architectural decisions, prototypes, work breakdown structure, schedule charts, and budget.

Uploaded by

ali basit
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Capstone 1 Report Checklist

1. Introduction
a. Outline, background, and overall objective of the project. If the project involves solving a
problem then outline the specific problem.
b. Outline the major and relevant interest of each member of the team.
c. Discuss an economic, environmental, or social impact that your project could have and why this
project is worth performing.
d. Discuss at least one topic involving ethics. This will be a brief scenario, such as that associated
with cyber security, the law, or safety.
e. Include at least one non-technical figure or image that makes your plan more accessible to the
general reader in a way that is easy to understand. Detailed technical drawings are not
appropriate for this section. Be sure to always introduce and discuss your figures.

2. Detailed Use Case


a. conceptual block diagram that outlines your use case.
b. Outline an actual scenario in which you foresee your project being used by your customer.
i. Clearly describe who the user/customer is
ii. what the project role is or how it will be used
iii. where and when the project will be used
iv. why or for what purpose.

3. Requirements
a. In a table organize the requirements and constraints into groups relevant for your project
i. In a subsection for each of these groups provide an outline elaborating each
requirement or constraint in detail
1. Indicate where it came from
2. Account for the value you have chosen
3. In this section use a number in square brackets for each reference.

4. The Design
a. 4.1 Architectural decisions
i. Architectural decisions: Describe at least one architectural decision for each member of
the team. Elaborate each in a brief paragraph.

b. 4.2 Key Principles and Risk Assessment


i. Be sure to revise the Key Principles writing assignment.
1. Outline each principle from that writing assignment.
2. For each key principle you provided at least two relevant sources.
3. Include references to the sources in the References section. In this section use a
number in square brackets for each reference.
ii. For your risk assessment you will need more key principles than those you listed in your
Key Principles writing assignment.
1. Follow the example in the Considering Risk notes and assignment. To enhance
the probability of success it is important to assess the associated risk of the key
principles in terms of your knowledge and experience.
iii. Assess the Key Principles. Use the assessment data from before your investigation.
Present the risk mapping of all the key principles. In areas of ‘expertise’ the map should
indicate the initials of the members that bring this expertise.
1. In your assessment table use light colors such as red, yellow, and green to
indicate severity. Red indicates high risk, yellow indicates moderate risk, and
green indicates low risk.
2. Create a summary risk map

c. 4.3 How Your Project Evolved


i. have a brief introduction.
ii. list important feedback items your team received.
1. The minimum number of significant feedback items for your report is the number
of members in your team.
2. For each feedback item describe how the feedback was used to improve your
project.

d. 4.4 Your Investigation Prototype and Mock-Up


i. Introduce this section with at least one paragraph.
ii. In several paragraphs, as well as diagrams, photos, and figures, clearly outline the
following:
1. The purpose of your investigation, that is, “why” the investigation is important.
2. Establish what was to be approximated, learned, or verify, that is, “what”
3. Determine the form of the prototype, that is “how”
4. Describe the nature of the tests and data that was gathered, that is, the “output”
iii. Present what came of your investigation. You are expected to use a combination of text,
diagrams, photos, figures, graphs, tables, and bullets.
1. If your goal was to collect data, then present the data collected in a way that is
clearly understood, along with your conclusions.
2. If your goal was to learn new concepts, then present an example that clearly
demonstrates your mastery of the concepts.
3. If your goal was to learn a skill, then present evidence that you learned the skills.
iv. The closing paragraph will tie up all the points and conclusions that you made. Did your
investigation strengthen your strategy? If there were any necessary changes to your
project strategy, describe them
e. 4.5 Overall Design: this section will divide your project into work content areas by team member
i. Brief introductory paragraph
ii. Present a “Work Area Block Diagram”:

1. is not a schematic, but a connection of “boxes” that each show a work content
area
2. architectural decisions will be evident and identifiable in the diagram.
3. key principles should be identifiable in the diagram.
4. The work content areas should be highlighted to indicate attribution as to who’s
most responsible. Consider colors, various shapes, or something else.
iii. Describe each work content area in a brief paragraph
iv. Component Selection
1. Describe at least one significant component your team will select
2. Describe at least two requirements for that component
5. Projected Schedule
a. Short introduction
b. Numbered list of tasks required to complete your project
i. At least one sentence to describe each task
c. Introduce and present PERT chart
d. Introduce and present GANTT chart
i. Have supplemental notes that support the Gantt chart
ii. Indicate who is primarily responsible for each task

6. Budget
a. Produce a summary estimate of the most expensive parts of your project
b. Also, list significant purchases and expenditures to date.

7. References, Formatting, etc.


a. This section will be organized into subsections, one for each of the corresponding sections that
makes use of a reference.
b. Please refer to all the sections following this one for proper formatting. Etc.

You might also like