capstone projects se 490
TRANSCRIPT
Capstone Projects
SE 490
Dr. Simon Fan
Professor of Computer Science and Software Engineering
California State University ● San Marcos
Report Writing
Time Table
You have a lot to do within 2 weeks:
1. Collect and document 2-3 user functional
requirements
2. Collect and document critical user non-
functional requirements
3. Refine user requirements into system
requirements
4. Work on use cases, diagrams, and other
artifacts
5. Write project report
6. Set up development environment
(complete in the week of 10/18)
Report Version 1.0
CapStone→Resource→Project Requirements→Report Structure
Remove hints in brackets: [hint]
At least 1.5 pages
200-300 words
Writing Report Abstract
Using 200-300 words to summarize the whole project is not easy.
It should cover
1) The driving needs of developing the system (or drawbacks of existing solutions)
2) The main features to be or have considered/designed/implemented in the system
3) The potential benefits/impacts of the system in a broader sense
To the business/users
Broader impacts on individuals, organizations, and society.
Erie Insurance employs hundreds of Property Claims Adjustors (adjustors) to file reports on insurance claims.
Each adjustor currently uses a digital camera to take photos, which must be loaded onto a computer first,
tagged with information of the claim, and then uploaded into Erie Insurance's content database. This
process has proven to be tedious and time consuming, hampering the data quality due to mislabeling or
non-labeling. Erie Insurance has proposed a project, demanding a Mobile Photo Upload Application which
may enable claim adjustors to take, organize, label, and upload photos of claim damages to a database
from a mobile device. This application will help Erie Insurance streamline the business process of collecting
and organizing photo documentation of damages associated with hundreds of claims every day. In this
report, we document the output of our requirements engineering process, giving all the user requirements,
system requirements engineered from the user requirements, as well as UML artifacts that capture the main
features of the system to be developed.
Requirements (how many in sprint 0)
Engineers get used to “cook” user
requirements automatically
Refined “testable” requirements
should be treated as system
requirements
Functional Non-functional
User 2-3 Critical
System Fully engineered Fully engineered
• More user functional requirements will
be added and engineered in later
sprints
• Remove a subsection on non-functional
requirements if that category does not
apply to your project
Report Version 1.0
Appendix U
Appendix R
• Do not put tables/figures generated
from CapStone into report body.
• In report body, use text to briefly
describe each table and refer the
reader to the appendix for the table
Report Version 1.0
• Each subsection describe a list of
non-functional requirements
• Remove a subsection if that category
does not apply to your project
Appendix R
Report Version 1.0
• Data input
• Data output
• Legacy data
• Data representation format
(e.g. database, file)
• Each subsection describe a list of non-
functional requirements
Appendix R
Appendix R
Report Version 1.0
Appendix R
Example work
Example mapping
Report Version 1.0
5.1: Describe possible development framework options that can be used as supporting platform
• Not software development approaches (such as Agile) or commonly used
management tools (such as Git)
• If there are similar systems or products, what are the frameworks, or technology stacks, upon which these systems are built?
• For example, NativeScript and React Native, as well as Xamarin, are alternatives for
building cross-platform mobile apps.
• If there exist several alternatives, conduct a comparison research: research on their
pros/cons, capability & applicability
5.2: Describe possible solution techniques, such as
• 3rd-party open-source packages/libraries that may be reused as part of your product.• For example, integrate RESTful web services such as Google Map service, IBM’s
Watson service, etc.
• Domain-specific algorithms/techniques that need to be implemented into the system
under development
• For example, specific Machine Learning approaches required by clients
• If multiple options available, research on pros/cons, capability & applicability
You may have many citations for this section
Report Version 1.0
Report Grading Rubric
CapStone→Student→Feedbacks→Project Technical Reports
More to check the Rubric page
Report evaluation rubric
Report evaluation rubric
Report evaluation rubric
Report writing
CapStone→Resource→Project Requirements→Report Instructions
CapStone→Resource→Project Requirements→Report Writing Skills