Meeting Scheduler RE Process: RAD Role Actor Diagram

1
Meeting Scheduler RE ProcessRAD (Role Actor
Diagram)

• An RE Process is dominated by human, social and
  organizational factors

ACTIONS
Process Specification
Modeling Requirements
Describe Issues
Improved Understanding
Select and Develop Prototype
Evaluate Prototype
Req. Engineer Project Manager
Req. Engineer Domain Expert End User
Req. Engineer Domain Expert End User
Req. Engineer Domain Expert End User
Req. Engineer SW Engineer
Req. Engineer
ROLES
Stakeholders/ Actors/ Agents
2
Process Specification UML Activity Diagram
Define, Model Process
Identify StkHlds/ sources/ roles
FORK
Model Functional Requirements
Model Non-Functional Requirements

• Different Tools for each Phase such as Use Case,
  Sequence, Class, Activity Diagrams, SIG, SADT Etc.

Specify Constraints
Specify Constraints
JOIN
Propose Clarifications
Finalize Models/ Specs
Prototype Brainstorming
Define Issues

• Obtain Agreement
• Set deadlines

FORK

• Prototype should be functional, 80/20 rule,
  demonstrate requirements

Document Reqs Models
Document Process
Further Develop Prototype
Document Issues
Compare Demo function v. Reqs.
needs improvement
meets requirements
JOIN

• Post files on 3 separate URLS, one per team member

Compile Team Parts
Turn in Hard Copy
Control
3
Controls influence execution, not consumed
Informal requirements definition
User Input
Domain Knowledge
Class Notes (FR, NFR, etc)
Outputs produced by activity
Inputs consumed by activity
Process Specification
Complete Phase 1
Initial Dependency Graphs
Requirements document template
Improved Dependency Graphs
Web-based Prototype
Issues
A0
1
Mechanisms makes activity happen
Project Manager
Requirements Engineer
Developer
SADT ACTI-GRAM
4
Controls influence execution, not consumed
Complete Phase 1
Domain Knowledge
User Input
Class Notes (FR, NFR, etc)
Informal requirements definition
Outputs produced by activity
Inputs consumed by activity
Process Specification
Requirements document template
Complete Process Specification
Initial Dependency Graphs
1
Complete Initial Dependency Graphs
2
Define Issues
Issues
3
Improved Dependency Graphs
Improve Dependency Graphs
4
Web-based Prototype
Begin Prototype
A0
1
5
Mechanisms makes activity happen
Project Manager
Requirements Engineer
Developer
SADT ACTI-GRAM
5
Controls influence execution, not consumed
Current Scheduling System Examples
User Input
Domain Knowledge
Class Notes (SADT, UML, etc)
Outputs produced by activity
Identified Stakeholders, Requirement Sources
Inputs consumed by activity
Refined Process Specification
Complete Phase 2
Process Specification
Improved NFR Dependency Graph
Improved Dependency Graphs
FR UML Diagrams
Web-based Prototype
Improved Web-based Prototype
Issues
Refined Issues
A0
2
Mechanisms makes activity happen
Project Manager
Requirements Engineer
Developer
SADT ACTI-GRAM
6
Complete Phase 2
Controls influence execution, not consumed
Domain Knowledge
User Input
Class Notes (SADT, UML, etc)
Current Scheduling System Examples
Outputs produced by activity
Inputs consumed by activity
Identified Stakeholders, Requirement Sources
Improve Process Specification
Refined Process Specification
Process Specification
1
Improved Dependency Graphs
FR UML Diagrams
Refine Functional Reqs
Improved Web-based Prototype
Web-based Prototype
Improve Prototype
2
5
Improved NFR Dependency Graph
Refine NFR
3
Refined Issues
Issues
Expand Issues
A0
4
2
Requirements Engineer
Project Manager
Mechanisms makes activity happen
Developer
SADT ACTI-GRAM
7
Controls influence execution, not consumed
User Input
Domain Knowledge
Class Notes (SIG, etc)
Inputs consumed by activity
Identified Stakeholders, Requirement Sources
Outputs produced by activity
Refined Process Specification
Complete Phase 3
Process Specification
Improved NFR Dependency Graph
Data Model
FR UML Diagrams
Improved UML FR Diagrams
Improved Web-based Prototype
SIG for NFR
Refined Issues
Functional, Enhanced Quality Prototype
A0
3
Mechanisms makes activity happen
Project Manager
Requirements Engineer
Developer
SADT ACTI-GRAM
8
Controls influence execution, not consumed
Complete Phase 3
User Input
Class Notes (SIG, etc)
Domain Knowledge
Inputs consumed by activity
Outputs produced by activity
Identified Stakeholders, Requirement Sources
Process Specification
Refined Process Specification
Refine Process Specification
Data Model
1
Improved UML FR Diagrams
Improved NFR Dependency Graph
Model Requirements
SIG for NFR
FR UML Diagrams
2
Improved Web-based Prototype
Functional, Enhanced Quality Prototype
Refine Process Specification
Refined Issues
3
A0
3
Requirements Engineer
Developer
Mechanisms makes activity happen
Project Manager
SADT ACTI-GRAM
9
Security
Meeting Scheduler System Development
Process Data Preservation
Protection from Competition
Documentation Access Authentication
Documentation Archives
Data Backups
File Encryption
Finger Print Identification
Password Identification
Monthly Backups
Daily Backups
SIG (Softgoal Interdependency Graph)
10
Meeting Scheduler System Development
Adaptability
Ability to be Tailored Easily
Ability to Change Quickly
Ability to Scope Appropriately
Ability to Prioritize Tasks
Periodic Brainstorming
Periodic Evaluations
Process Activity Attributes
Activity Resource Requirements
Activity Duration
SIG (Softgoal Interdependency Graph)
11
Meeting Scheduler System Development
Clarity
Understandability
Completeness
Defined
Communicated
Process Meetings
Approvals by Management
Visible Reminders
Training
Checklists
Brainstorming
May conflict with security
SIG (Softgoal Interdependency Graph)
12
Meeting Scheduler System Development
Evolvability
Controlled
Improvability
Measured
Managed
Iterative Definition
Implement Lessons Learned
Baselines and Benchmarks
Brainstorming
SIG (Softgoal Interdependency Graph)
13
Data Hierarchical Diagram
Specification
Product Specification
Process Specification
Enterprise Requirement Specification
Nonfunctional Process Specification
Functional Process Specification
System Requirement Specification
Enterprise Functional Part
Enterprise Non-Functi onalPart
Enterprise Functional Part
Enterprise Non-Functi onalPart
Textual Description
UML Diagram
Dependency Graph
SADT Diagram
SIG Diagram
DataHierarc hyDiagram
Textual Description
Prototype
14
Controls influence internal state of the data
Class Notes (SIG, UML, etc)
Inputs activities that create the data
Outputs activities that consume the data
Process Specification
Process Brainstorming
Requirements Definition Process
Process Modeling
D0
0
Mechanisms Device for storage, representation,
etc.
Share Drive
SADT DATA-GRAM