Meeting with James 20th April - hamstar/Braincase GitHub Wiki
Agenda
Confirm created use case requirements are on track with James vision.
###Actions from previous meeting on 13th April.
- Confirm reading of requirements elicitation (RE) literature
- "Managing Software Requirements: A Unified Approach By Dean Leffingwell, Don Widrig"
- Confirm we made a decision on RE method
- Interviewing, Use Cases and Prototyping
- Show James the Issue that we made to decide the RE method
Minutes
- James found current usecase + requirements to be good (good level of abstraction)
- Need some further usescases;
- How frontend will work
- Core Wiki Pages
- Private and Public wiki page uses
- Once packages are chosen, reasons are justified
- Tests should be repeatable. Ie test environment, details
- Ensure Licence conditions are honoured
- List licences for each piece of software
- Show how the system respects the licence
- Need to look harder at how the backups are going to work
- In respect to the bandwidth used
- In respect to the storage systems used (delta-ing)
- How to backup only changes
- Maybe put warnings against methods that don't delta
- James agreed that prototype -> show client -> get more reqs would work
Requirements
- Backups should be every 24 hour instead of scheduled (but could be a NTH)
- Feature Suggestion: Verification of backups
- Notification of completed/errored backup over email
- Efficient use of storage (medium priority)
Non-functional requirements
Property of the software that doesn't relate to it when its running
- Convenient (turnkey system)
- Good code
- Guiding principles of UI design
##Issues
- Change Name of Project
- Decide on a way to manage requirements/usecases
- Decide on Linux environment product will primarily support.
Actions for this meeting
- Complete initial set of requirements
- Implement priority's given by Client
- Find a way to manage requirements
- Read the book to find out how acceptances tests are done
- Complete UseCases for interface