10. Requirement Analysis
- Sharmendra Vishwakarma
- Gaurav (Unlicensed)
1. Business Requirement
The Art Institute of Chicago is looking to create a new image ordering request system with Jira Service Desk. The new system will replace an internally developed system (Phoenix) and interface with new digital asset management systems (Net X - currently in development) and collections management system (CITI) through the use of API services. Need integration with existing development resources using API.
2. Project Goal
decommission existing image ordering request system (Phoenix) and replace with Jira Service Desk
Integration of CITI ( Collections Management System) with Jira Service Desk
Integration of Jira Service Desk with Net X (Digital Asset Management System)
3. Scope
Sl No# | Items | Description |
|---|---|---|
1 | CITI App Integration | REST API is required to push the data |
2 | Net X API Integration | REST API is required to push the data |
3 | JSD ( Development of Integration Code) | Development of integration functionality in JSD |
4. Out of Scope
Sl No | Items | Description |
|---|---|---|
1 | Configuration of JSD for Go -live
|
|
2 | Advanced email integration : Transaction automated emails to create new acquisition orders (Parse email information into custom fields) |
|
3 | Configuration/Enhancement of CITI App and Net X. |
|
5. Architecture
5.1 Overall Architecture
6. Work Breakdown Structure (WBS)
Sl No# | Task | Task Description | Estimated Effort(Hours) |
|---|---|---|---|
1 | CITI Integration |
|
|
1.1 | Business Logic to rename the files/images |
| 32 |
2 | Net X Integration |
|
|
2.1 | Development of Screen for Net X App Integration | Connection Settings to Store NetX credentials, | 16 |
2.2 | Development of business to save data to JSD |
| 16 |
2.4 | Development of Business Logic to push data from JSD to Net X |
| 24 |
3 | Business logic to save the data in JSD based upon the workflow |
| 80 |
4 | Implementation of Logger |
| 24 |
5 | Integration Testing |
| 32 |
6 | UAT |
| 40 |
7 | Hyber-Care Post-Golive |
| 40 |
8 | Documentation |
| 16 |
|
|
| 280 |
7. Dependency
Sl No | Items | Remarks |
|---|---|---|
1 | Access of CITI application | We need this access to test the link |
2 | Access of Net X Application | We need this to validate the integration |
3 | Access of CITI Rest API to push the data | CITI app api details |
4 | Access of Net X REST API to push the data | NET X api details |
5 | Access of JSD to test the integration | Access to the client’s JSD server to test the integration(No required for development) |
6 | Availability of Artic team for any queries | Availability of business users |
7 | Availability of Artic team for testing | Availability of business users |
8. Deliverables
Codebase of integration
Technical documentation
9. Glossary
CITI : Collection Management Application
Net X : Digital Asset Management System
JSD : Jira ServiceDesk
Addendum
List of task leads to more efforts
Sl No# | Items | Description |
|---|---|---|
1 | Development of business logic to save into JSD | Initially, our understanding was CITI app user will initiate the request and lands on JSD Customer Portal ( If not logged in, user has to log in to the customer portal). Then, user will select the request types and enter the details to create the Jira issues. Due to this whole approach to save the data changes. We developed separate logic for 5 request types with almost 13 scenarios with custom URLs and for each scenarios we have developer logic to pull the CITI data and save the data in JSD. Major efforts are spent here to build the architecture to support the above requirement. |
2 | Folder Structure in NetX | As per our understanding we developed the logic to push the assets to single folder but later on based on the discussion with Artic team we have made folder selection is dynamically. |