- New assignment posted
- Make refined version available
- List of requirements for system(functional, non-functional)
- Requirements is the hardest problem to nail down for SW Engineers
- Prepare short oral presentation (1-2 minutes) - Monday and Wednesday classes
- Link by the end of the day
- Last time, requirements were covered in detail
- Function of every system is different
- Non-functions requirements: Usability, maintainability, ecstatics, marketing, all process aspects of developing SW(testing planning, code standards), security and privacy
- Unix password system(hashing) - inversion is really difficult
- Saving time for possible adaptation of existing standards (why is that the correct way to go)
- Consideration of the end user, as well as possible other types of users (see Example below)
- Testability - some way of verifying that the requirement was met
- Traceability (SVN, logs, team queues, requirement traceability as they change and increase)
- Requirement MUST be unambiguous
- Completeness of requirements
- Is the requirement is realistic?
Vendor machine example (user types)
- purchasing user
- person that maintains vendor machine with the inventory
- hackers :)
No comments:
Post a Comment