Codespring took responsibility for full life cycle software development of our customer’s flagship product, no matter what stage we entered the project. We have completed full life cycle software testing on implemented new functionalities, provided support and elaborated documentation of application errors occurred during functional enhancements.
Actions we took to address these challenges were:
1. FULL LIFE CYCLE SOFTWARE DEVELOPMENT
- Implemented a CAMT XML message import and integrated this into the existing product with support of the old MT 94x messages;
- Adapted validation rules and processed phases for different CAMT import formats;
- Adapted CAMT messages to support easy extensibility;
- Provided an alternative login solution in case of USB smartcard reader failure.
Oracle Database, XML SAX, Spring, JMS, WebSphere MQ, Struts, WebService, JSF.
Used Development Tools:
Maven, Sonar, Hudson, JIRA, Jboss4, WebSphere 6.1.
Our actions resulted in:
- The existing product of the client complies with ISO 20022 CAMT XML message standard that replaces the old MT 94x messages;
- CAMT import implementation satisfies the requirements of configurability, extendibility and high performance.
- “Zero footprint” solution to access the banking application: it enables authentication and signature by using the same combination of reader and smartcard. No need to physically connect the reader to the PC and to install software.
2. FULL LIFE CYCLE SOFTWARE TESTING
Elaborated high level documentation.
- Test plan: verified and ensured design specifications & requirements.
- Test design: created specific test cases to ensure QA coverage for all customer specific implementations.
- Test specification (frontend): performed high level quality assurance based on the Functional Design and Use Cases.
Test development: elaborated test procedures, test scenarios, test cases, test datasets, test scripts to use in testing software.
Test execution (performed functional and non-functional testing):
- System Tests –executed full test of a specific functionality.
- Connectivity Tests – validated frontend and backend communication.
- Migration Tests –ensured seamless database SQL scripts meet customer requirements.
- Regression Tests –ensured existing functionality is still working as expected.
- Jira Retests –retested bug fixes from development.
- Acceptance Tests – determined that requirements specifications are met.
- Usability Test – checked that user interface is easy to use and understand.
Gap analysis – identified that base lined requirements defined by the business analyst are covered in the design.
Used Testing Tools:
Jira, Confluence, internal quality assurance software, SQL tools (SQuirreL, Navicat)
SFTP, SCP, FTPS, FTP clients (WinSCP)
Our actions resulted in:
- Less than 5% test case reopens after final review;
- Improved quality thorough a QA process and wider coverage of testing areas;