Scribd
Upload
47 views10 pages

Week 1 - Assignment 1 INF

Uploaded by

Jacob the undertaker 1888
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
47 views10 pages

Week 1 - Assignment 1 INF

Uploaded by

Jacob the undertaker 1888
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Title: Proposal for Employee Expenditure Tracking System

Course: INF340: Business Systems Analysis


Instructor: Mark Fairbanks
Date Submitted: 10/21/24
Student Name: Jacob Ortega
● Business Need:
Frequent employee travel requires an efficient
system to track expenses such as travel, lodging,
and meals.
● Current Challenges:

Business
Manual expense tracking leads to errors, delays,
and inefficient reporting.
● Existing Solutions:

Overview and
Systems like SAP Concur and Expensify automate
expense submission and approval workflows,
improving efficiency.

Background Technology Platform:

● Cloud-based, mobile apps, and web-based


systems.
● Integration with accounting platforms.
Off-the-Shelf Solutions and Technology
Platforms
● SAP Concur:
Widely used for large organizations. Supports real-time tracking, reporting, and policy compliance.
Cost: Typically per-user, requires a significant budget.
● Expensify:
Popular for small businesses, easy to use, supports mobile submissions.
Cost: More flexible pricing, but fewer advanced features.

Technology Platform:

● Both solutions offer cloud-based infrastructure, mobile capabilities, and require employee training for smooth adoption.
Cost Considerations and Technology
Feasibility

Cost Comparison: Technology: Cloud-based, scalable, supports


mobile use.
● SAP Concur: High initial cost, per-user
pricing. Training: Minimal employee training required for
● Expensify: Lower upfront costs, scalable both systems
for smaller organizations
Functional Requirements:

● Expense submission.
● Approval workflow.

Business
● Reporting and analytics.
● Integration with accounting software.

Non-Functional Requirements:

Requirements ●
●
Security (Data encryption, access control).
Usability (Mobile and web accessibility).
● Reliability (99% uptime guarantee).
Methods:

Eliciting ●

●
Stakeholder Interviews: Understand needs from
finance teams, managers, and employees.
Surveys: Collect input on current pain points in

Requirements ●
expense management.
Observation: Review the current manual process
and identify inefficiencies.

from Key Stakeholders:

Stakeholders
● Finance team, employees, managers, IT
department.
Alternative Development Methodologies

● SDLC:
○ Sequential, structured process. Best for well-defined requirements.
● Agile:
○ Iterative development, flexible to changes. Best for dynamic environments.
● RAD (Rapid Application Development):
○ Focuses on quick iterations and prototypes.

Best Approach: Hybrid Agile-SDLC method.


Why This Proposal Should Be Funded

Business Alignment:

● Reduces manual errors.


● Increases efficiency and saves time.
● Improves data accuracy for financial reporting.

Strategic Value:

● Aligns with organizational goals of improving operational efficiency.


● Enables better decision-making through accurate data.
Additional Benefits and Impact

Employee Satisfaction: Simplifies the expense submission process.

Managerial Control: Provides visibility into spending and enforces policy compliance.

Finance Team Efficiency: Reduces workload, increases accuracy in financial reporting.


References

Smith, J. (2021). Business Information Systems and Management. XYZ Publishing.

Johnson, A., & Lee, B. (2019). System Development Methodologies. IT Management Journal, 34(2), 12-23.

SAP Concur. (2020). Expense Management Solutions.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy