HLA Software Development Cycle
...
1. Gather Requirements and Use Cases
Include interviews with physicists, operators, engineers, project leads, and any other stakeholders for use cases
...
2. Write Requirements document.
Requirements Template: https://slacspace.slac.stanford.edu/sites/LCLS%20Document%20Storage/01%20-%20LCLS%20Systems/electronbeamsys/controls/Shared%20Documents/Applications/Requirements%20Specification%20Template.doc
...
3. Review Requirements with users
- email Email requirements doc to distribution prior to review meeting
- prepare Prepare power point for review meeting
- take Take minutes and notes during review and publish
- update Update requirements doc with comments and republish
...
after review, republish and distributet
4. Gui Mockup Review with HLA developers
include Include Mike, the GUI consistency guy
- For Java apps, use our standard GUI framework unless you get authority to do otherwise
...
5. Gui Mockup Review with users
Note: c,e 3 and 5 can be the same review
...
6. Prototype the code (usually no longer than 2-4 weeks)
...
7. Write Software Conceptual Design
Conceptual and Design Template: https://slacspace.slac.stanford.edu/sites/LCLS%20Document%20Storage/01%20-%20LCLS%20Systems/electronbeamsys/controls/Shared%20Documents/Applications/SoftwareCandDDesignTemplate.doc
...
8. Review Design with developers
...
9. Write Software
...
10. Code Review
...
11. Write Test Plan
...
12.
...
Write Help
Plan is to place html on operations wiki
...
13. Write Test and Release
...
Plan
Release procedures: ? /usr/local/lcls/physics/README
Notes:
Documentation
Post all documents on Sharepoint under Controls | Applications folder
Confluence wiki home for Accelerator Software - Meeting minutes and more interactive documentation:
http://confluence.slac.stanford.edu/display/ACCSOFT/Home