- Final proposal document due by Wednesday
- Quick demo in class, next week (hopefully, next Monday)
- Projects grading - how well proposed specifications of the project were implemented
- "Extreme programming" rarely used in practice
- "Waterfall" process is widely used and widely adapted at the SW project planning. It is also a luxury to have it in some cases.
- All testers are not alike; testing time is expensive.
- "Recapture" (training set for system learning)
System requirements document:
- High level goal (tree structure) - while most of implementations done in bottom-up approach
- (A) Functional requirements
- Performance, timing
- Concurrency
- HW requirements, platforms requirements
- (B) Non-functional
- Documentation
- Trademark, legal
- Aesthetics (look & feel)
- Coding Standards
- (C) Testing
- (D) Security (not sure where it fits, it is overlapping possibly more than one particular requirement, so placed in its own category for now)
No comments:
Post a Comment