HLA Java Release procedures

0) Before you release software, make sure you have a Test Plan and have followed this development cycleFor brand new designs/applications, ensure the following software development cycle is followed:

• • Gather Requirements
  • Requirements Document
  • Review Reqs w HLA
  • from users / colleagues
  • Write Reqs Document (Insert links to Reqs template)
  • Perform Reqs Review w colleagues / users
  • If GUI is required:
    • Perform GUI Mockup Design
    • Preform GUI Review w
    HLA
  • GUI Review w Users
  • Review Reqs w Users
  • SW Conceptual Design
  • Review Design w HLA Team
  • Write GUI
  • Write Controller
  • • engineers / users
  • Write SW Conceptual / Detailed Design (insert links to Design template)
    • Ensure all significant functions have an API
    • If GUI, ensure Model/View/Controller design Pattern
  • Perform Design Review w colleagues
  • Write Systems Integration Reqs, such as host systems and network considerations, database support, matlab PVs, etc,
  • Implement/Code (Insert link to Coding Standards)
    • Follow relevant Design Patterns where applicable
  • Unit Test (test in development)
  • Conduct Code Reviews / demo on development
  • Write Help / User Manual / Developer's GuideWrite Model
  • Write Test PlanUnit Test
  • Commission
  • Commissioning
  • Perform Training and Help
  • Code ReviewAll

Software Release Procedures

...

ln -s release/tagName <Module Name>

example:

[]$ ln -s release/score-R0-2-30 score

cd to <Module Name> and run the tester launch script.

[]$ cd score-R0-2-30

$ ./score.bash

...