Class Activity Requirement Elicitation
Simple Music Portal
Task:
1. Identify which of the above-mentioned requirements/descriptions
are functional and which are non-functional requirements.
2. Develop Use Case Diagram identifying important actors, use cases,
and system boundaries.
3. Generate system requirements by expanding any 3 functional
requirements mentioned above using Use Case Descriptions that
are detailed enough to be easily implemented.
Solution:
1. Functional And Non-Functional Requirements:
Functional Requirements:
• To log in by username and password.
• Searching by name of the album • A list of matches of the album is shown.
• Album details.
• Buy and then download option available/shown.
• Payment through credit card.
• Profile/account of the user is maintained.
• History of previously bought albums. Non-Functional Requirements:
• Links for login or logout should be shown/available.
• Links for registration should be shown.
• Link for the user account that is logged in should be shown.
• A search box should be displayed on each page.
• Each album should only have one artist name to avoid complexity
• The data of the credit card recharge should be available.
