SpringCM Implementations - Analysis and User Stories

This report analyzes SpringCM Implementations, focusing on user stories and their corresponding acceptance criteria. It outlines a series of user stories, including requests for Non-Disclosure Agreements (NDAs), and details the expected functionality and validation processes. The report covers various user roles, such as customers, managers, and legal personnel, and describes their interactions with the system. The report provides insights into how the system should handle customer registration, data storage, email notifications, and document revisions. It also considers the access rights of different roles within the system, ensuring data security and efficient workflow. Furthermore, the report highlights the importance of maintaining records and providing clear communication throughout the process.

SPRINGCM IMPLEMENTATIONS
STUDENT
05 OCTOBER, 2016

1 | P a g e
Contents
FLOWCHART..........................................................................................................................................2
USER STORIES AND ACCEPTANCE..........................................................................................................3
1 | P a g e

2 | P a g e
FLOWCHART
2 | P a g e

3 | P a g e
USER STORIES AND ACCEPTANCE
USER STORY 1: As a customer I should be able to request for NDA.
ACCEPTANCE:
1. The customer should register first
2. The customer should provide complete information in the form before submitting it.
3. The information must be correct and validated by company as well.
4. Registration mail must be sent back to customer.
USER STORY 2: As a manager I should be able to view all the past and new requests and their status.
ACCEPTANCE:
1. All the request info must be stored in the database.
2. All the info must be accessible to the manager.
3. The status must be updated regularly.
USER STORY 3: As a customer I should get acknowledgement mails about my request.
ACCEPTANCE:
1. Customer must provide valid email ID.
2. Regular mails must be followed up with each status update.
USER STORY 4: as a customer, I should get proper reasons for redlines in the document.
ACCEPTANCE:
1. The legal department during review, should add reasons or details for every change in the
document before sending it back to customer.
2. All the details must be stored in the database to keep records.
USER STORY 5: As a legal person, I should have access to all the data related to the NDA process
before review it.
ACCEPTANCE:
1. Legal department should be provided with the access to see the data in request tables so
that it can be thoroughly reviewed before it is approved or rejected.
2. Legal department should update status after review process.
USER STORY 6: as a contract admin I should have access to all the request data so that I can look for
flexibility and rerouting or cancellations.
3 | P a g e

4 | P a g e
ACCEPTANCE:
1. The admin should have access to all the data related to the request sent by the legal
department.
2. If the request is rerouted or cancelled by admin, he or she should be able to update the
status.
4 | P a g e