Digital Computing System IT and Computer Software Development Group

---

Programming and IT Services

• Business Continuity Program – Remote critical data backup. Emergency procedure, and Catastrophe recovery plan. Use ASP, Java, JSP, ADO, CDO and other script languages to deploy thin-client based recovery applications. Allows HTTP, TCP/IP over T1/DSL/Dial/WAP/GPSR/3G/Satellite, and other wireless networks. Generalized BCP proposal
• Offsite Storage – Remote critical data backup in our e-vaults. Use 2-tier backup plans. Generalized proposal
• Database and Visual C++ for Windows
  Client List and Product Deployment
• HTML, ASP, Java, Flash for e-commerce
  Computer Doc
• C and Assembly for embedded systems
• Applications based on Palm OS and Cellular OS

Software Products

• C248 Area Code Change Program - Scan computer files for 810 area codes, and change them to the new code 248. Windows 3.1, 95, NT compatible. ($69) Download
• CA66 Image Database - Stores customer data and images, Caller-ID interface, print mailing labels, track product sales, print invoice, shipper. -- for medium size company or sales people. ($199)
• CA96 Mortgage/Lease Program - For mortgage companies, loan companies, banks, and equipment leasing companies.($199)

Digital Computing System Software Quality Assurance Plan:

• We propose a two teams validation and verification (V&V) approach for large project. One team is made up of senior software engineers and non-technical users from in-house and client. The other team is from an independent contractor, which have no financial or contractual link to the project.
• Document the original design specifications, updates, and history of changes including hardware and network requirements, operating environment, and conditions. V&V team member would not allow modifying the code under any condition.
• Conduct failure mode and effects analysis (FMEA)
• Develop a test plan based on specs and FMEA
• Developer to schedule and host at least one design review
• Technical checkers (must be a experienced programmer or engineer) to validate design specs and software functions
• Non-technical checkers (at least 2) to stress test every data input field, document the outcome of every input, activate every available functions on the screens, and document the result (monkey test).
• Technical checkers to read source code in its entirety. Check for memory space, I/O address and allocation errors, branch control errors, computation errors, loop control errors, timing errors, floating point and fix point data precision, overflow, and underflow conditions, interrupt strategy and task scheduling issues. Most frequent errors for thin-client apps are data type, field length, data source, and multi-session problems. Most frequent problems for embedded apps are timing, memory and I/O usage, and computational.
• Technical checkers test every algorithm with typical and extreme values from the specs. Most common problems are typos, computing, and program flow issues.
• Develop a simulation program to feed input and compare outputs, where possible.
• Must rerun a partial monkey test every time there is a small modification. Rerun the entire monkey test if change is substantial. Generate report for every test. This test is required to run at least twice on every different system prior to release.
• Independent team test and certify the program.