CAP314: Unit 2

To outline the software architecture and design.

To provide a detailed project timeline and budget.

To list all programming languages used in the project.

To ensure a common understanding of software requirements among stakeholders.

Focus Groups

Brainstorming Sessions

Interviews, Surveys

Document Analysis

The system shall automatically generate reports every hour.

The system shall allow users to change their profile picture.

The system shall provide a dark mode for users.

An example of a functional requirement is: 'The system shall allow users to log in using their email and password.'

The system shall have a user-friendly interface.

The system shall be deployed on a cloud platform.

The system shall be developed using Java.

An example of a non-functional requirement is 'The system shall be able to handle 1000 concurrent users without performance degradation.'

Ambiguous terminology.

Clarity and simplicity in language.

Lengthy and detailed descriptions.

Complex technical jargon.

Stakeholder analysis

System architecture

Functional requirements, non-functional requirements, use cases

Project timeline

To organize and present project specifications clearly.

To list team members and their roles.

To define the project timeline.

To create a budget for the project.

Problem analysis is only necessary for technical teams.

Problem analysis ensures accurate identification of needs, prioritization of requirements, and alignment with business goals.

It focuses solely on budget constraints.

Problem analysis is irrelevant to project success.

System requirement

Non-functional requirement

Functional requirement

User requirement

Subjective and opinion-based

Vague and confusing

Overly complex

Clear and unambiguous