636-530-7776
Legend: RUP Notation
Workflow > Detail > Role

Role: Requirements Analyst

Discovering and communicating the software needs, desires, and ideas of your end-users and other stakeholders is the primary role of the Requirements Analyst.

More detail: Description - Staffing

Click the icons for definition

Business Strategist
Software Architect
Information Architect
Subject Matter Expert
Project Manager
Requirements Analyst
Stakeholder
Business Concept (from Business Strategy)Business Use Case Model (from Business Strategy)User Research ReportBusiness Operations Plan (from Business Strategy)
Find Actors and Use Cases
Manage Dependencies		 Glossary (from Environment)
Use Case Modeling Guidelines
Supplementary SpecificationUse Case (sketch)Requirements AttributesUse Case ModelActor Catalog
Software ArchitectPrioritize Use CasesSoftware Architecture Document (updated)
Requirements Analyst Define System Wide Attributes

Description

The Requirements Analyst captures the requirements in use case models, use cases, and supplementary specifications. Facilitating the definition of the scope and details of the requirements, how the requirements relate to and depend on each other, and promoting a common vocabulary, are this role's most important activities.

This role also ensures that the stakeholders agree to the written requirements. By working with Information Architects and other roles, the Requirements Analyst assures that the requirements and user interface are kept in sync. The Requirements Analyst must also help Information Architects, Graphic Designers, Software Designers, Implementers, Testers, Course Developers, and others involved in the project understand the requirements.