Complete Software Documentation Package

Answer the following questions about a team project that was delivered in multiple stages. You’ll need additional information, which I’ll provide, to complete these questions for the final project report.

Final Deliverable: Complete Software
Documentation Package
Dear Students,
As we approach the culmination of our course, we are thrilled to introduce the Final
Deliverable – a comprehensive Software Documentation Package, due on July 19, 2024.
Final Deliverable Details: Complete Software Documentation Package
Submission Deadline: July 19, 2024
Included Components:
1. Software Requirements Document (SRD):
o
A thorough documentation of the software’s requirements, providing the
foundation for the subsequent development phases.
2. Design Document (DD):
o
Detailed documentation outlining the design aspects, including high-level
architecture, detailed system design, data structures, algorithms, interface
design, and security considerations.
3. Implementation (Coding):
o
Submission of the actual code implementing the design. Your coded
solution should align with the specifications outlined in the SRD and DD.
4. Test Cases:
o
Comprehensive test cases that validate the functionality, performance, and
security aspects of your software. Include both positive and negative
scenarios to ensure a robust system.
5. User’s Guide:
o
A user-friendly guide providing instructions on how to install, use, and
troubleshoot the software. This guide is crucial for end-users to effectively
interact with the developed system.
Submission Instructions:
•
•
•
Combine all components into a well-organized and cohesive documentation package.
Ensure each section is clearly labeled and follows the prescribed format.
Submit the complete package through the Canvas by the specified deadline.
This final deliverable marks the culmination of your hard work throughout the course. It
reflects not only your technical proficiency but also your ability to translate concepts into
a tangible, functional software solution. Your dedication to this project is commendable,
and we look forward to witnessing the fruition of your efforts.
Feel free to reach out if you have any questions or require guidance during this final
phase.
Best regards,
Abdul
Rubric
Final Deliverable
Final Deliverable
Criteria
This criterion is linked to
a Learning
OutcomeImplementation
(Coding)
Ratings
20 pts
15 pts
10 pts
5 pts
0 pt
Excellent
Good
Satisfactory
Weak
Poo
The code is wellstructured, follows
best practices, and
aligns closely with
the design
specifications. It is
thoroughly
documented and
demonstrates a
high level of
proficiency.
The code is wellstructured and
mostly follows best
practices but may
have some minor
issues or
inconsistencies.
Documentation is
adequate but could
be more
comprehensive.
The code is
functional but may
lack some
organization or
adherence to best
practices.
Documentation is
lacking or unclear.
The code is
incomplete, poorly
structured, or does
not align with the
design
specifications.
Documentation is
missing or severely
inadequate.
The
miss
non
func
Final Deliverable
Criteria
This criterion is linked to
a Learning
OutcomeFunctional
Requirements
This criterion is linked to
a Learning OutcomeNonfunctional Requirements
Ratings
15 pts
11.25 pts
7.5 pts
3.75 pts
0 pts
Excellent
Good
Satisfactory
Weak
Poor
The code effectively
implements all
functional
requirements
specified in the SRD
and DD, providing
the expected
functionality and
behavior.
The code mostly
implements
functional
requirements but
may have some
minor deviations
or omissions.
The code partially
implements
functional
requirements,
with noticeable
deviations or
omissions.
The code poorly
implements
functional
requirements,
with significant
deviations or
omissions.
The code
not imple
functiona
requirem
20 pts
15 pts
10 pts
5 pts
0 pts
Excellent
Good
Satisfactory
Weak
Poor
The code
effectively meets
all non-functional
requirements
specified in the
SRD and DD, such
as performance,
security, and
reliability.
The code mostly
meets nonfunctional
requirements but
may have some
minor issues in
performance,
security, or
reliability.
The code partially
meets nonfunctional
requirements,
with noticeable
issues in
performance,
security, or
reliability.
The code poorly
meets nonfunctional
requirements,
with significant
issues in
performance,
security, or
reliability.
The code
not mee
function
requirem
Final Deliverable
Criteria
This criterion is linked to
a Learning OutcomeTest
Cases
This criterion is linked to
a Learning
OutcomeUser’s Guide
Ratings
15 pts
11.25 pts
7.5 pts
3.75 pts
0 pts
Excellent
Good
Satisfactory
Weak
Poor
The test cases are
comprehensive, covering
a wide range of scenarios
and effectively validating
the software’s
functionality,
performance, and
security aspects. They
include both positive and
negative scenarios.
The test cases
are thorough
but may lack
some coverage
or depth in
certain
scenarios. They
effectively
validate most
aspects of the
software.
The test cases are
adequate but may
lack thoroughness
or coverage in
certain scenarios.
They validate some
aspects of the
software.
The test cases
are incomplete
or lack coverage
in critical
scenarios. They
do not
effectively
validate the
software.
The te
are mi
signific
inadeq
15 pts
11.25 pts
7.5 pts
3.75 pts
0 pts
Excellent
Good
Average
Weak
Poor
The user’s guide is clear,
well-organized, and
provides comprehensive
instructions for
installation, usage, and
troubleshooting. It
effectively assists users
in interacting with the
software.
The user’s guide
is clear and
mostly wellorganized but
may lack some
detail or clarity
in certain
sections. It
provides
adequate
assistance to
users.
The user’s guide is
adequate but lacks
thoroughness or
clarity in certain
sections. It
provides some
assistance to
users.
The user’s guide
is incomplete or
lacks detail,
making it
difficult for users
to understand
and interact
with the
software.
The us
guide i
missin
signific
inadeq
Final Deliverable
Criteria
This criterion is linked to
a Learning
OutcomeDocumentation
Quality and Clarity
Ratings
15 pts
11.25 pts
7.5 pts
3.75 pts
0 pts
Excellent
Good
Average
Weak
Poor
All documentation
components (SRD,
DD, code
comments, test
case descriptions,
user’s guide) are
clear, concise, and
effectively
communicate their
respective
purposes.
Language and
terminology are
appropriate for the
intended audience.
Most
documentation
components are
clear and concise
but may lack
some clarity or
consistency in
language and
terminology.
Documentation
components are
generally clear
but may lack
consistency or
have some
instances of
unclear language
or terminology.
Documentation
components lack
clarity or
conciseness in
several areas,
making it difficult
to understand
their content.
Language or
terminology is
often
inappropriate or
unclear.
Documenta
componen
missing or
significantl
clarity and
concisenes
throughou
Language a
terminolog
consistentl
inappropri
unclear.
Final Deliverable
Criteria
This criterion is linked to
a Learning
OutcomeSemester
Project
Students will apply both
computer science theory
and software
development
fundamentals in the
development of the final
deliverable.
Ratings
2 pts
1 pts
0 pts
Full Marks: Adeptly applies both
computer science theory and
software development
fundamentals in the development
of the final deliverable,
demonstrating a seamless
integration of knowledge and
producing an outstanding result.
Partial Marks: Partially applies
computer science theory and
software development
fundamentals, with some gaps or
inconsistencies in the integration,
resulting in a satisfactory but not
exceptional final deliverable.
No Marks: Submits
final deliverable, la
the application of
computer science t
and software
development
fundamentals.
2 pts
1 pts
0 pts
Full Marks: Creates comprehensive
documentation for a medium-sized
software project, covering all
necessary aspects and providing
clear and detailed information for
understanding and future
development.
Partial Marks: Creates
satisfactory documentation for a
medium-sized software project,
but some aspects may lack
completeness or clarity,
impacting understanding and
future development.
No Marks: Submits p
documentation miss
parts or insufficient
documentation lacki
details for a medium
software project.
threshold: 1.0 pts
This criterion is linked to
a Learning
OutcomeWritten
Communication
Students will create
documentation for a
medium-sized software
project.
threshold: 1.0 pts
Final Deliverable
Criteria
This criterion is linked to
a Learning
OutcomeSoftware
Development
Students will design,
implement, and evaluate
a medium-sized software
system.
threshold: 1.0 pts
Total Points: 100
Ratings
2 pts
1 pts
0 pts
Full Marks: Successfully designs,
implements, and evaluates a
medium-sized software system.,
demonstrating a thorough
understanding of best practices
and producing a high-quality final
product.
Partial Marks: Partially succeeds in
designing, implementing, and
evaluating a medium-sized
software system, with some
aspects falling short of best
practices or resulting in a less-thanoptimal final product.
No Marks: Delivers
design, implementa
and evaluation of a
medium-sized softw
system.
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Design
Requirements
Document
Deliverable 2.0
July 5, 2024
Creators:
Jasmine Aiken
Mohammad Baig
Alejandro Folgueira
Berto Lorenzo
Jesus Mota
Page | 1
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Table of Contents
Section 1.
Introduction ……………………………………………………………………… Pg. 3
Section 2.
High Level Architecture………………………………………………………… Pg.3
Section 3.
Detailed System Design ……………………………………………………… Pgs.4-6
Section 4.
Algorithms ………………………………………………………………………. Pgs.7-8
Section 5.
Interface Design ………………………………………………………………… Pgs.9-11
Section 6.
Security Considerations ……………………………………………………. Pg.12
Page | 2
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Section 1
Introduction
Sepulchrosoft is a software program catered towards updating the process of plot reservation and
maintenance for patrons and cemetery administrators. The coding languages involved in the
creation of this application are HTML, JavaScript, and Python. The primary goal of this product is to
provide security of personal data with encryption technology while supplying users with a simple
interface to choose their desired funeral arrangements.
Section 2
High Level Architecture
Sepulchrosoft will operate using Client Server Architecture. The client side will be responsible for
showing the interface and handling any interactions such as the login process for both patrons and
the cemetery administrators. The interface will be constructed by a mix of HTML,CSS, and
JavaScript. On the Admin side it will display a dashboard with the maintenance schedule and plots
available for reservation. It will allow for customization of options relating to the plot size and
location specific to the layout of the administrator’s cemetery. It will send out alerts when the plot
needs upkeep. The server side oversees request handling, selecting API endpoints to access
specific resources, and manages the algorithms that will exchange information between the
database and user interface. The database will handle the storing of user data( saving their
preferred plot sections, custom requests, and feedback), plot records, and any additional data or
edits made by the administrator.
Page | 3
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Section 3
Detailed System Design
Class Diagram
Page | 4
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Use Case Diagram
Page | 5
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Sequence Diagram
Page | 6
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Section 4
Algorithms
The features pertinent to the successful running of Sepulchrosoft would be those that support data
encryption, user interactions, plot reservations, and maintenance scheduling. To securely handle
user login and registration Sepulchrosoft must employ several algorithms.
o
The User Authentication Algorithm – will validate the data entered into its system i.e. the
user’s username, email address, and password. It will use Python to hash the password
using the bcrypt, then store the hashed password in the database. When the
patron/administrator attempts to login Sepulchrosoft will retrieve the stored password for
the given username. It will compare the password inputted against the stored hashed
password. If the password does not match the program will deny the user access to
proceed further. Once the password matches the system will launch a session token that
grants the user access.
o
The Plot Reservation Algorithm – will moderate the selection, reservation, and release of
available plots. Once implemented the algorithm queries the database for unreserved plots
based on the filters that the user selects(price, location, or size). It will then display the
results on the interface for the user to choose from. For the task of reserving plots the
system will cross check the database to see if the plot is free. If so, it will mark the plot as
reserved and record the user’s details and reservation timestamp.
o
The Modify/ Add Burial Records Algorithm – will retrieve burial results associated with the
specified plot ID and will add a new record or update an existing one based on the
administrator’s needs.
o
The Reservation Confirmation Algorithm – will access the database and send a
confirmation email to the user information on record.
o
The Maintenance Scheduling Algorithm – will use predefined rules set by the
administrator to plan the frequency that plots must be serviced. It will generate alerts
based on the schedule which will inform the administrators and groundskeepers when
upkeep is necessary. The schedule can be revised if need be.
o
The Data Encryption Algorithm – will use a symmetric cipher system imported from the
Python AES library to encode the data before storing it. The algorithm will retrieve and
decrypt the data for use in the application.
o
The Data Backup Algorithm – will periodically backup data to prevent loss. The
administrator can schedule the times in which the system is backed up. The system will
Page | 7
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
export the current database state then store the data securely. The algorithm allows for the
restoration of old data.
o
The Customer Feedback Algorithm – will collect feedback from users whether that be a
rating, comment, or suggestions. It will be checked by the feedback fields to ensure there is
no prohibited content or spam. The feedback will be stored to the database for
administrators to view.
Page | 8
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Section 5
Interface Design
Page | 9
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Page | 10
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Interaction Flow
o
o
o
o
o
User Login: The user navigates to the login page, enters credentials, and logs in.
Dashboard Navigation: The admin lands on the dashboard and can navigate to different
sections by selecting an option.
Plot Reservation: The user selects the ‘Reserve Plot’ option, browses available plots, and
reserves a desired plot.
Leave Feedback: The user submits feedback via the ‘Leave Feedback’ box.
Administrator Functions: The administrator accesses the admin dashboard, manages
plots, updates burial records, and views maintenance schedule/customer feedback.
Page | 11
CEN 4010 – Group 3
Sepulchrosoft Software System
Design Requirement Document Deliverable 2.0 July 6, 2024
Section 6
Security Considerations
Sepulchrosoft employs multiple security measures to protect user data and ensure system
integrity. For authentication and authorization, it uses `bcrypt` to hash passwords, making them
unreadable if accessed. JWTs are used to manage user sessions checking to make sure that only
authorized users remain logged in. Sepulchrosoft uses role-based access control to differentiate
between regular users and administrators, assigning appropriate permissions to each. For data
encryption, AES is used to encrypt sensitive information stored in the database. For input
validation and sanitization, user inputs are checked on the client side with HTML5 and JavaScript to
ensure they are accurate.
Page | 12
CEN 4010
May 17, 2024
Group 3 Proposal
Chosen Outdated Software:
Cemetery Software- automated system used by cemetery administrators to manage burial records,
plot reservations, and maintenance schedules.
Pending Title: Sepulchrosoft
Limitations: Most cemetery systems have poor interfaces and outdated navigation systems that don’t
coincide with current technological advancements. It lacks customization options and is a nonevolving
software. Data security and privacy features are also faulty leading to leakage of personal data such as:
financial records and personal information of the deceased and their family members.
Solution: Create a simple cloud-based software system with a feedback mechanism that updates
cemetery administrators and family members about changes to the plot. Include encryption/verification
software to protect private information. It will have customization options and a help guide to ensure
new users understand how to operate the application. It will be integrated with mapping tools, CRM
systems, and a basic accounting program. We will do research to make sure that the software complies
with local regulations. Existing burial records will be transferred to this new application and can be
edited. New burial records can be added and stored in the cloud. This way the information is constantly
backed up. The maintenance schedule will be shown on the home page and will send an alert to the
groundkeepers when a plot is due for maintenance. There will be a section where patrons can reserve
plots by size.
SEPULCHROSOFT
RESTING
REVOLUTIONIZED
Presented By:
Jasmine Aiken
Mohammad Baig
Alejandro Folgieura
Berto Lorenzo
Jesus Mota
TABLE OF
CONTENTS
1 Cover Page
10 Hardware + Software Requirements
2 Contents
11 – 12 Use Case 1 + Alternative Flow
3 Introduction
13 – 14 Use Case 2 + Alternative Flow
4 Purpose
5 – 6 Scope
7 – 8 Functional Requirements
9 Non-Functional Requirements
19
15
Use Case Diagram
16
Task Distribution
17
Gantt Chart
18
References
Thank you + Q & A 🙂
INTRODUCTION
As the management of cemeteries becomes increasingly complex, the need
for modern and efficient software solutions is more critical than ever. Current
cemetery management systems are often plagued by outdated interfaces,
limited functionality, and significant security vulnerabilities. These
shortcomings hinder administrators from effectively managing burial records,
plot reservations, and maintenance schedules, while also exposing sensitive
personal data to potential breaches. To address these issues, we present
Sepulchrosoft, an innovative, cloud-based software solution designed to
revolutionize cemetery operations.
PURPOSE
The purpose of Sepulchrosoft is to provide cemetery administrators with a
comprehensive, user-friendly tool that streamlines the management of burial
records, plot reservations, and maintenance schedules. This software aims to
replace outdated systems with a modern, secure, and highly customizable
platform that aligns with contemporary technological standards. By
integrating advanced features such as real-time updates, encryption for data
security, and compatibility with other essential tools, Sepulchrosoft seeks to
enhance operational efficiency, improve user experience, and ensure the
privacy of personal information.
User-Friendly Interface
An intuitive interface that simplifies navigation and enhances
usability for administrators and family members alike.
Cloud Based System
Ensuring data is constantly backed up and accessible from
anywhere, facilitating seamless management and reducing the
risk of data loss.
Customization Options
Allowing administrators to tailor the system to their specific
needs, including customizable templates and settings.
SCOPE
Limitations
Customization Limitations: Sepulchrosoft may not
offer enough flexibility for customization to meet
the specific needs of every cemetery, leading to
potential gaps in functionality or workflow
inefficiencies.
Data Migration and Management
Aiding in the transfer of existing burial records to the new
system, with options for editing and adding new records to
ensure comprehensive data management.
Data Security and Privacy
Implementing robust encryption and verification mechanisms to
protect sensitive data, ensuring compliance with privacy
regulations, and preventing unauthorized access.
Integration Capabilities
Seamlessly integrating with mapping tools, CRM systems, and
basic accounting programs to provide a unified solution for all
cemetery management needs.
Real Time Feedback
SCOPE
Limitations
Internet Dependency: As a cloud-based solution,
Sepulchrosoft relies heavily on internet
connectivity. Any disruptions in internet service
could hinder access to critical data and
functionality.
Enabling real-time notifications and updates to administrators
and family members regarding plot changes and maintenance
schedules.
Maintenance Scheduling/ Plot
Reservation
Displaying maintenance schedules prominently on the home
page and sending alerts to groundskeepers for timely upkeep of
plots. Allows patrons to reserve plots based on size and other
preferences, with an easy-to-use reservation interface.
FUNCTIONAL
REQUIREMENTS
User Friendly Interface
Customization
The software must contain a welldesigned graphical user interface with
straightforward navigation as the
frequent users of the software include
administrators and the families eligible
for its services.
Users are able to create their own profile
and save browsed plot options.
Cloud Based System
Data Security
Sepulchrosoft will be cloud based to
ensure a copy of the data is stored and
able to be retrieved in case of data loss.
It will include remote access that only
allows the general public to see the main
homepage. Administrators have full
control of the system.
It will include encryption schemes to
manage sensitive data. Sepulchrosoft
will adhere to the existing laws
governing the privacy of data like the
General Data Protection Regulation
(GDPR) and the Health Insurance
Portability and Accountability Act
(HIPAA)
FUNCTIONAL
REQUIREMENTS
Integration Capabilities
Real Time Updates
It will be able to link with mapping
software to enable the planning of the
cemetery. An accounting/payment
process program is necessary to
integrate budget packages and for
financial management.
Sepulchrosoft sends notifications to
family members to update them about
the availability of plots. Users can give
feedback and report any problems
encountered.
Maintenance Scheduling
Data Migration
Alerts will be sent out periodically to
alert the groundskeepers when it is time
to upkeep the plots. The maintenance
schedule will be placed on the homepage
as well.
Data from the previous software can be
imported into Sepulchrosoft. This
maintains the integrity of old burial
records. The data can be edited in case of
errors. New records are added once the
plot is in use to avoid confusion.
NON – FUNCTIONAL
REQUIREMENTS
Performance & Reliability
Security & Legal Compliance
Compatibility & Maintainability
• Response Time: within 5 seconds
• Throughput: up to 1000 concurrent users
• Scalability: High
• Uptime: 99%
• Backup and Recovery: daily backups with a 30
min restore time.
• Authentication: secure log in methods
• Data Encryption: standard inscription
• Access Control: role-based control
• Audit Trials: maintain detailed log of user
activity to ensure accountability.
• Browser Compatibility: works with
major browsers such as Google
Chrome, Microsoft Edge, Safari, and
Firefox
• Operating Systems: Windows and
MacOS.
• Code Quality: follows good coding
procedure and documentation
• Monitoring: implement tools to track
performance and update issues.
HARDWARE & SOFTWARE
REQUIREMENTS
Servers:
• Cloud Servers: AWS, Google Cloud,
Microsoft Azure
• Local Servers: Enterprise-grade servers from
Dell, HP, IBM
End-User Devices:
• Desktops/Laptops: Intel i5/i7 or AMD Ryzen
5/7, 8GB+ RAM, SSD storage
• Tablets/Smartphones: Modern iOS and
Android devices
Networking Equipment:
• Routers and Switches: Enterprise-grade from
Cisco, Netgear, Ubiquiti
• Firewalls: Fortinet, Palo Alto Networks, Cisco
Frontend:
Frameworks: React.js, Angular, Vue.js
Languages: HTML5, CSS3, JavaScript
Backend:
Frameworks: Node.js (Express), Django, Ruby on Rails, Spring Boot
Languages: JavaScript, Python, Ruby, Java
Database:
Relational: MySQL, PostgreSQL
NoSQL: MongoDB
Cloud Services:
Providers: AWS, Google Cloud, Azure
Security:
Encryption: TLS/SSL, AES
Auth: OAuth 2.0, JWT
APIs:
Google Maps API, Salesforce, QuickBooks
Real-Time:
Websockets: Socket.io
Notifications: FCM, APNS
Data Migration:
Tools: Apache Nifi, Talend
Testing/Deployment:
CI/CD: Jenkins, GitLab CI/CD, GitHub Actions
Testing: Jest, Selenium, Cypress
Project Management:
Tools: JIRA, Trello, Slack
USE CASE 1: PLOT RESERVATION BY FAMILY
MEMBER
PRECONDITIONS
• The family member has access to the
cemetery’s website or mobile app.
• Available plots and their details are up to date
in the system.
POST CONDITIONS
• The plot reservation is recorded in the
system, and the plot status is updated.
• The family member receives a confirmation
email with the reservation details.
• The administrator is notified of the new
reservation for review and approval.
MAIN FLOW
1. The family member accesses the “Plot Reservation” section of
the website or app.
2. They browse through the available plots, using filters like
location, size, and pricing.
3. The system displays a map or list view of plots matching the
filters.
4. The family member selects a desired plot and clicks “Reserve.”
5. The system prompts the user to enter relevant information,
such as name, contact details, and any special requests.
6. The family member reviews the details and confirms the
reservation.
7. The system processes the reservation, updates the plot status,
and generates a unique reservation number.
8. The system sends a confirmation email to the family member
with the reservation details and any further instructions.
9. The system notifies the administrator about the new
reservation.
USE CASE 1: ALTERNATIVE FLOWS
1A. NO AVAILABLE PLOTS MATCH FILTERS
1. The system displays a
message informing the user
that no plots are available
based on the selected
filters.
2.The user can modify the
filters or contact the
administrator for
assistance.
1B. PLOT ALREADY RESERVED
1. If the user tries to reserve
a plot that is already
reserved or occupied, the
system displays an error
message.
2. The user must select a
different available plot.
USE CASE 2: BURIAL RECORD MANAGEMENT BY
ADMINISTRATOR
PRECONDITIONS
• The administrator has a valid account and is
logged into the Sepulchrosoft system.
• Existing burial records are stored in the
system.
POST CONDITIONS
• New burial records are added to the system
with accurate information.
• Existing records are updated or deleted as
needed, maintaining data integrity.
• Relevant files and documents are associated
with burial records for future reference.
MAIN FLOW
1. The administrator navigates to the “Burial Records” section of
the system.
2. The system displays a list or search interface for existing burial
records.
3. To view a record, the administrator selects or searches for the
desired record.
4. The system displays the burial record details, including the
deceased’s information, plot location, and any attached files or
documents.
5. To add a new record, the administrator clicks “New Record”
and fills out a form with the necessary details, such as name, date
of burial, plot location, and any additional notes.
6. The administrator can attach relevant files or documents to the
record, such as death certificates or obituaries.
7. The administrator reviews the information and saves the new
record.
8. The system assigns a unique identifier to the new record and
updates the database.
USE CASE 2: ALTERNATIVE FLOWS
3A. EDIT AN EXISTING RECORD
1. The administrator selects an
existing burial record from the list or
search results.
2. The system displays the recorded
details in an editable form.
3. The administrator makes the
necessary changes and saves the
updates.
4. The system updates the record in
the database with the new
information.
3B. DELETE A RECORD
1. The administrator selects an
existing burial record from the
list or search results.
2. The system prompts the
administrator to confirm the
deletion.
3. If confirmed, the system
removes the record from the
database and updates the plot
status accordingly.
USE CASE DIAGRAM
SEPULCHROSOFT
Administrator
View Existing
Burial Records
Add New Burial
Records
User
Create an
Account
Reserve a Plot
TASK
DISTRIBUTION
Team Member
Role
Jasmine Aiken
Formatting SRD + PPT
(Intro, Scope, Purpose)
Mohammad Baig
Use Cases
Alejandro Folguiera
Functional Requirements
Berto Lorenzo
Non – Functional Requirements
Jesus Mota
Hardware & Software/Edits
GANTT CHART
REFERENCES
Baashar, Y., Alhussian, H., Patel, A., Alkawsi, G., Alzahrani, A. I.,
Alfarraj, O., & Hayder, G. (2020). Customer relationship
management systems (CRMS) in the healthcare environment:
A systematic literature review. Computer Standards &
Interfaces, 71, 103442. Geurtsen, M., Didden, J. B., Adan, J.,
Atan, Z., & Adan, I. J. B. F. (2023). Production, maintenance and
resource scheduling: A review. European Journal of
Operational Research, 305(2), 501-529.
THANK YOU
IT’S Q & A TIME 🙂