Professional Documents
Culture Documents
For Ace Cardiopathy Solutions 1.0: Software Requirement Specifications
For Ace Cardiopathy Solutions 1.0: Software Requirement Specifications
For Ace Cardiopathy Solutions 1.0: Software Requirement Specifications
Purpose 3
Current State of the Business 3
Future State of Business 3
Tools and Technology 4
Definitions Acronyms and Abbreviations 4
Functional Requirement 4
Out of scope 4
System Use Case 3
User and Role Setup 5
Hospital Management 6
Doctor Management 7
Opportunity Management 7
Quote Management 9
Product and Pricebook Management 10
Asset Management 11
Target Management 12
Visit Management 12
Reports & Dashboard 12
Purpose
The Software Requirement Solution (SRS) focuses on the Business Perspective as it
contains details of the Business Solution for the Project. It captures functional Requirement
for
● Salesforce Implementation, CRM and Digital Platform for Customer, Sales Team,
Procurement Team, Management Team.
● Integrating core systems and other third-party systems to facilitate customer journey.
Challenges:
● No common place to see the daily activities of Users and next steps related to
customers.
● Unable to track Consignment, because of this they are not able to find out expired
products.
Focus On:
● Want to move beyond excel sheets to track Consignment and Purchase Order.
● 360 view of the customer and related information on a single platform to maintain a
single version of truth.
Functional Requirement
The functional requirement captured into the use cases listed in this document.
Out of scope
● Any point which is not part of this SRS & signed SOW is out of scope.
Normal Flow User will click on the setup and then in the quick find box he will
search for “Users”. He needs to click new user and the from will
appear where user need to fill following information:
First Name*
Middle Name
Last Name*
Suffix
Alias
Email*
Mobile
Username*
Nickname
Role
User License
Profile*
Active
Validations N/A
Alternate Flow If a user leaves the organisation the new user will take over his
role, for this admin will create a new user and assign the same
role and profile.
References N/A
Description The use case contains details about the Hospital Management
Assumption System already has the list of converted Hospitals into the CRM.
Pre-Condition CRM User log into the CRM application and has the option to
create, view and edit Hospital information.
Post-Condition The detailed information of the Hospital will be created and saved
into the CRM.
Normal Flow It will have the following Information as mentioned below:
● Hospital Record Type
o Government Hospital
o Private Hospital
● Hospital Name*
● Parent Account
● Email Id
● Website
● Phone
● Industry
● Description
● Billing Street
● Billing City
● Billing State Province
● Billing Zip/Postal Code
● Billing Country
● Shipping Street
● Shipping City
● Shipping State Province
● Shipping Zip/Postal Code
● Shipping Country
Notifications N/A
Validations De- Duplication of Account Based on
● Hospital Name
● Opportunity Name
● Opportunity Owner
● Hospital Name
● Close Date
● Created By (Read Only)
● Amount
● Next Step
● Probability (%)
● Type -
o Existing Customer Upgrade
o Existing Customer Replacement
● Synced Quote
● Stage -
o Qualification
o Negotiation/Review
o Closed Won
o Closed Lost
● Description
Information that will be captured on the Opportunity Line Item
● Product
● Size
● Quantity
● Discount
● Date
● List Price
● Sales Price
● Subtotal
● Total Price
● Line Description
Notifications N/A
● Quote Name
● Opportunity Name
● Account Name
● GST
● Email
● Quotation Number (It will be unique in the system)
● Date
● Status
o Draft
o Needs Review
o In Review
o Approved
o Rejected
● Description
● Contact Name
● Phone
● Email
● Fax
● Bill to Name
● Billing Street
● Billing City
● Billing State Province
● Billing Zip/Postal Code
● Billing Country
Notifications N/A
Validations N/A
Alternate Flow N/A
References N/A
Notifications N/A
Validations N/A
Alternate Flow N/A
References N/A
Notifications System will send a Notification to Sales person once the record is
created
Validations N/A
Alternate Flow N/A
References N/A