Requirements Analysis
- •
def
- •
the process of evaluating, clarifying, and structuring all collected requirements to produce a clear, precise understanding of what the client wants the software to do
- •
performed after Requirements Elicitation to identify inconsistencies, gaps, overlapping needs, and dependencies
- •
- •
- •
- •
output
- •
an analysis model that gives both developer and customer a means to assess software quality once built
- •
feeds into Requirements Specification
- •
- •
conflict in requirements
- •
def — a situation where two or more stakeholders have requirements that cannot be fulfilled simultaneously
- •
- •
categories
- •
conflict of interest — stakeholders have different goals (e.g., students want 24-hour chat access with lecturers; lecturers want limited service hours)
- •
conflict of priority — all stakeholders want their needs prioritized first (e.g., admin wants financial reports first; management wants attendance reports first)
- •
technical conflict — proposed technical solution conflicts with business expectations (e.g., real-time sync is desired but the infrastructure doesn't support it)
- •
- •
- •
negotiation techniques
- •
MoSCoW Prioritization
- •
Must Have — features that must exist for the system to function (e.g., the attendance system must record student attendance)
- •
Should Have — important but non-critical features; can be delayed without breaking the system (e.g., export attendance data to Excel)
- •
Could Have — optional additional features if time and resources allow (e.g., graphical attendance statistics dashboard)
- •
Won't Have — explicitly excluded from the current version (e.g., biometric integration; planned for a future phase)
- •
- •
Trade-off Analysis
- •
comparing two or more conflicting options by weighing cost, time, quality, and risk
- •
e.g., if a lecturer wants facial recognition attendance (high cost, long development time) while admin wants manual attendance (cheap, fast), a trade-off could suggest a photo ID-based method as a moderate alternative
- •
- •
Win-Win Negotiation (Boehm)
- •
collaborative approach where all stakeholders seek a common ground without feeling disadvantaged
- •
steps — all parties state their ideal needs → discuss limitations and concerns of each party → design a solution that meets the core elements of all parties
- •
e.g., lecturers want all thesis submissions as print; academic admin wants everything digital → win-win: final document stored digitally, but a printed recap is produced weekly
- •
- •
- •
- •