What This Document Is
This is a User Manual created by Team 01 for CSCI 577 Software Engineering at the University of Southern California. Specifically, it details the functionality and usage of a cloud-based Customer Relationship Management (CRM) system developed as part of a course project. The manual focuses on guiding users through understanding and interacting with the system, intended to improve operations related to client/donor/partner management and project tracking. It appears to be version 1.0, indicating an initial release for review and implementation.
Why This Document Matters
This manual is essential for anyone involved in utilizing the newly developed CRM system. This includes end-users who will be directly inputting and accessing data, as well as administrators responsible for system oversight. It’s particularly valuable during the initial rollout and adoption phase, providing a reference point for understanding the system’s capabilities and intended workflow. Students involved in the software engineering project will also find it crucial for understanding the practical application of their work and gathering feedback for future iterations.
Common Limitations or Challenges
This manual provides a high-level overview of the system and its intended operation. It does *not* include detailed code documentation or the underlying technical architecture. It also doesn’t cover specific customization procedures beyond initial setup. While it addresses common questions, it may not resolve every unique issue encountered during real-world usage. Furthermore, the manual references external resources (like Salesforce success pages) for additional support, meaning users may need to consult those separately.
What This Document Provides
* A comprehensive overview of the CRM system’s purpose and core functionalities.
* Details regarding system requirements – both hardware and software – for accessibility.
* An outline of operational procedures, differentiating between general user and administrator perspectives.
* A section dedicated to troubleshooting, including a compilation of frequently asked questions.
* Information regarding team roles and responsibilities involved in the project.
* A structured table of contents for easy navigation.
