...
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 to integration with existing development resources using API.
2. Project Goal
Sunset 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)
...
Sl No# | Task | Task Description | Estimated Effort(Hours) | ||||
|---|---|---|---|---|---|---|---|
1Attachment | In-Transit UtilityCITI Integration |
|
| ||||
1.1 | Business logic Logic to to Save the attachment rename the files/images | 32 | |||||
1.2 | Develop API for CITI app to push the attachment |
| 24 | ||||
1.3 | Screen design to view the attachment |
| 16 | ||||
2 | CITI 2 | Net X Integration |
|
| |||
2.1 | Development of Screen for CITI Net X App Integration | Connection Settings to Store CITI NetX credentials, | 32 16 | ||||
2.2 | Development of Business logic for JSD integration | Saving data to JSD and pushing data to CITI app | 32 | ||||
2.3 | Develop API for CITI app to push the data to JSD | REST API | 24 | ||||
3 | Nextx Integration |
|
| ||||
3.1 | Development of Screen for Net X App Integration | Connection Settings to Store NetX credentials, | 32 | ||||
3.2 | business to save data to JSD |
| 16 | ||||
2.4 | Development of Business Logic to push data from JSD to Net X |
| 32 24 | ||||
3.3 | Development of Business Logic logic to push save the data from JSD to CITI App |
| 24 | 3.4 | Development of business to save data to JSDin JSD based upon the workflow | 80 | |
4 | Implementation of Logger |
| 24 | ||||
45 | Integration Testing |
| 32 | ||||
6 | |||||||
5 | Implementation of Logger |
| 24 | ||||
6UAT | 40 | ||||||
7 | Hyber-Care Post-Golive | 40 | |||||
8 | Documentation |
| 16 | ||||
280 |
7. Dependency
Sl No | Items | Phase | 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 integration6 | Access of Server to deploy the attachment service.7to the client’s JSD server to test the integration(No required for development) | |
6 | Availability of Artic team for any queries | Requirement Gathering/Development/Integration Testing | 8Availability of business users |
7 | Availability of Artic team for testing | UATAvailability 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. |