Notes for 1/06/09
- Where is the risk management
- Add progress reports to website on it’s own page
- Subversion needs to be set up
- Not on Virtual Machine but on Linus
- Requirement gathering misunderstanding.
- Schema, Antler, Xml?
- Haven’t made a final decision
- Project Plan
- Clear up what each release should have as a result
- Project Lifecycle section
- Export product deliverable
- Export as a save “view”
- Export to support systems format
- Mapping to spreadsheet, spokes, sql format
- Go into the tool and say export to SQL
- Product info is mapped to this field, etc
- Overview
- Sounds a bit odd. Has to be reworked. Lots of detail upfront, kind of tampers off.
- Roles Responsibilities
- Make a note that Rob might not be note taker in all situations
- Identify a backup
- Resource and allocation section
- Time is resource do we want to mention development time?
- Yes as well as time per week
- Department Computes
- Only use project @ campus
- Tracking Control
- Differences between estimates…
- Reword. We plan on reworking our schedule to make it more accurate
- Environment
- Plugins, GWT,
- Everything we need to know
- Methods tools techniques
- not needed for actual build
- Redefine as build and runtime environment?
- Add what we are using for prototyping
- Metrics
- What do we plan on capturing?
- Mention Time Spreadsheets
- Mention required to have Three.
- Function Point analysis
- Has a different connotation
- Rename use cases satisfied
- See if there is a type of method for definition
- Think about factors such as size of use case, etc
- Goal of these metrics
- Each Metric has a goal and a question that says is it satisfied
- Write down why we choose these metrics
- Project Artifacts
- Easier to read if in Chronological order
- Risk Management Document
- Keep in mind some risks are unavoidable
- System Architecture and design document
- Design layout of system
- Architecture is how modules interact where things go.
- Split them out
- Too much detail and massive document
- Test Plan and Test Results
- Roll that into one big document
- Overall test plan and phase one
- Separate Release Notes
- Requirement Revisions
- How are we going to do it
- Risk forgetting to add stuff
- Risk mitigation strategies
- Schedule
- Yes. It needs work.
- Change BRS and SRS estimations
- Initial draft by this time next week / end of this week
- What are requirements for talking about requirements to stakeholders?
- For upfront stuff we need to do interviews and elicit from them
- They need to know subject so they can get right resources.
- Get Business requirements and use cases soon
- Research existing definitions
- Some predecessors may not be defined.
- Try to add details to reflect the current project more
- Looking into notes for adding rationale
- Architecture and Design Document is not accurate
- Estimation might have to change. Take a closer look and re estimate.
- Add detailed subtasks for each release for implementation
- Spell out RIT deliverables
- Break out Week 10/20 deliverables into detail
- Working in Parallel on Requirements may be a bad idea: be skeptical
- May have to stop and reallocate rescources
- Add it will be web based is assumptions and constraints
- Add more Specific Requirements (Break it down)
- Regroup about Test Plan and procedures
- Clarification: do we meet with people, or do we create a draft before meeting?
- Add Y or N to completion of Time Sheets
- Is there a Template for BRS
- Action Items (w/ person responsible and dues dates)
- Add progress reports to website
- Set Up Blueprint on Virtual Machine
- Get done a new schedule
- Get BRs by Thursday evening High level
- Match up schedules and relay the info to Erika and Neil
- Meet at paetec two weeks from today 20th