Capstone Project

CH3 and CH4

JOVITO P. BOLACOY, JR.
Chapter 3: Results and Discussion
A. System Analysis - System Requirements

System requirements is a statement that identifies the

functionality that is needed by a system in order to satisfy the
customer's requirements.
Separate it by Functional and Non-Functional Requirements.
Read this link for more information and examples:
https://qracorp.com/functional-vs-non-functional-requirements/
Functional and Nonfunctional Requirements
A. System Analysis - Process Model: Use Case Diagram
and Description
A use case
diagram is a
graphical
depiction of a
user's possible
interactions with
a system.
Use Case Diagram
Example
Use Case Description:
 A. System
Analysis -
Process
Model: Use
Case Diagram
and
Description

Links:
https://www.visual-paradigm.co
m/guide/uml-unified-modeling-la
nguage/what-is-use-case-diagra
m/
A. System Analysis - Process Model: Activity Diagram

An activity diagram is a behavioral diagram i.e. it depicts the

behavior of a system. An activity diagram portrays the control
flow from a start point to a finish point showing the various
decision paths that exist while the activity is being executed.
Create an activity diagram for each user.
Must have discussion every diagram.
Link: https://www.lucidchart.com/pages/uml-activity-diagram
A. System
Analysis -
Process Model:
Activity Diagram
A. System
Analysis -
Process Model:
Activity
Diagram
A. System Analysis -Data Model: Context Data Flow
Diagram

Data flow diagrams are used to graphically represent the flow of

data in a business information system. DFD describes the
processes that are involved in a system to transfer data from the
input to the file storage and reports generation.
Must have discussion every diagram.
Link:
https://www.visual-paradigm.com/guide/data-flow-diagram/what-is-
data-flow-diagram/
A. System Analysis - Data Model: Context Data Flow
Diagram
A. System Analysis - Data Model: Context Data Flow
Diagram
A. System
Analysis - Data
Model: Level 1
Data Flow
Diagram
B. System Design - Object Model: Entity-Relationship
Diagram
An entity relationship diagram (ERD), also known as an entity relationship
model, is a graphical representation that depicts relationships among people,
objects, places, concepts or events within an information technology (IT)
system.
Must have discussion every diagram.
Links:
https://www.visual-paradigm.com/guide/data-modeling/what-is-entity-relations
hip-diagram/
https://searchdatamanagement.techtarget.com/definition/entity-relationship-di
agram-ERD
B. System Design - Object Model: Entity-Relationship
Diagram
B. System Design - Data Dictionary

A data dictionary is used to catalog and communicate the structure

and content of data, and provides meaningful descriptions for
individually named data objects.
It must be aligned with the ERD.
Link:
https://www.techopedia.com/definition/27752/data-dictionary
https://www.usgs.gov/products/data-and-tools/data-management/data-
dictionaries
B. System Design - Data Dictionary
B. System Design - System Architecture

System Architecture is abstract,

conceptualization-oriented, global, and focused to
achieve the mission and life cycle concepts of the
system.
Must have a comprehensive discussion.
B. System Design - System Architecture

Mobile Phone Application of Agricultural Resources and Environment Information Based

on Agricultural Short Message Service Content (Hu et al, 2019)
B. System
Design -
System
Architecture

https://www.upc.edu/learn-sql/en/system-architecture
B. System Design - System Architecture

Development of Employee Attendance and Payroll System using Fingerprint Biometrics (Indico, 2016)
B. System Design - Screenshots of the System UI

This section shows the input and output forms based on

the prototype you will develop. Make sure to put captions
and short discussion per figure.
C. System Testing Plan - Software Testing Tools and
Methods
● Describe the Software Testing tools and methods to be
conducted upon completion of the software project.
● Provide a comprehensive discussion of how to conduct
the software testing using the tools/methods described.
● Provide possible implications of the Software Testing
results.
● Include blackbox testing.
Blackbox Testing
C. System Testing Plan - Usability Testing Tools and
Methods
● Describe the User Testing tools and methods to be
conducted upon completion of the software project.
● Provide the questionnaire or checklist.
● Provide a comprehensive discussion of how to
conduct the usability testing using the tools/methods
described.
● Provide possible implications of the Usability Testing
results.
C. System Testing Plan - Review and Audit Plan

● Provide the audit process and program

● Specify the schedule, resources, and processes, and
procedures to be used in conducting project reviews and
audits.
● Specify the plans for joint customer-project reviews,
management
● progress reviews, developer peer reviews, quality
assurance audits, and customer-conducted reviews and
audits.
● List the external agencies that approve or regulate any
project deliverable.
See example.
E. Discussion

● Discuss in great detail the discussion of the

achievement of the objectives and what was the
methods to achieve this.
● Discuss the results based on the achievement of the
objectives.
Chapter IV. Conclusion and Recommendation

The conclusion is intended to help the reader understand why

your research should matter to them after they have finished
reading the paper. A conclusion is not merely a summary of your
points or a re-statement of your research problem but a
synthesis of key points.
This must be a summary of the discussion section in Chapter 3.
Make sure that the achievement of the objectives will be
highlighted.
Source: Teixeira, L., Xambre, A. R., Figueiredo, J., & Alvelos, H. (2016). Analysis and Design of a Project Management
Information System: Practical Case in a Consulting Company. Procedia Computer Science, 100, 171–178.
doi:10.1016/j.procs.2016.09.137
Chapter IV. Conclusion and Recommendation

Recommendations are used to call for action or solutions to the

problems you have investigated in your research paper. Your
recommendations highlight specific solutions and measures to
be implemented based on the findings of your research.
Future improvements of the design and proposed
recommendations by the users not included in the paper can be
included as well.
PREFINAL DEFENSE REQUIREMENT

1. Chapter 1, 2, 3, 4
2. Prototype Development (no functionality but must be
with working links)
3. Adviser recommendation
Note: Those who have not yet submitted their Outline
Defense minutes and approval, must submit before
Midterm Exam.
FINAL DEFENSE REQUIREMENT

1. Abstract
2. Chapter 1, 2, 3, 4
3. Appendices
4. Prototype Development (no functionality but must be with
working links)
5. Presentation to the project sponsor with certificates and
evidence
6. Adviser recommendation