Laserfiche WebLink
NORTHISTAR" <br />a Additional integration updates <br />o Modifications to leak adjustments on Account gateway <br />o Usability enhancements <br />o Service Bench integration <br />o Bill print enhancements <br />• Northstar Bi <br />o Updates <br />o Usability enhancements <br />o Template development <br />o ETL development <br />• NorthStar mCare v6 <br />o Map enhancements <br />a Meter location screen modifications <br />o Usability enhancements <br />• NorthStar CustomerConnect v6 <br />o Enhancements to; <br />■ Register, view and pay bills <br />■ Meter reads, PAP, service orders <br />■ Interval usage, notifications, SSO, CSRJump, NetMetering <br />o Usability enhancements <br />o Usage stats logging <br />How are new features identified and placed into releases? <br />Through a combination of feedback from our clients and testing and reorganization through the R & D <br />team. <br />What are your quality control processes prior to issuing updates or enhancements? <br />What does a typical development environment look like? <br />Describe your company process for software development including standards, policies, controls, testing <br />and acceptance. <br />We believe the following answer cover all three of the above questions. <br />New software features and change requests are broken down into user stories with detailed <br />acceptance criteria which must be fulfilled before the feature or change request can be considered <br />resolved. QA bases its testing on those user stories. Testers draft detailed test plans based on each <br />user story's acceptance criteria. The test plans consist of individual "success" and "fail" cases for each <br />story, with each case having clearly defined input, pre -conditions and expected results. "Success <br />cases" are designed to validate that the feature or change request meets the business and design <br />requirements and functions as expected. "Fail cases" are designed to prove that built-in error trapping <br />operates as expected and protects the system from input errors. Test scripts are drafted from criteria <br />in the test cases. Manual testers follow the script to validate system behavior and automation <br />engineers use the scripts as a framework for coding automated test scripts used for regression <br />testing. If the feature in development deviates from the script at any point during manual or <br />automated testing it is returned to Development for investigation, resolution and retesting. <br />Do you offer a separate mobile application? Please describe. <br />NorthStar Proposal Response — South Bend Indiana <br />