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

Stakeholders/ Actors/ Agents
2
Meeting Scheduler RE ProcessRAD (Role Actor
Diagram)

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

ACTIONS
Process Specification
Semi-formal Requirements Definition
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
3
Meeting Scheduler RE Process

• The RE Process for the project will be as
  described below.
• The Process Specification will be completed
  first.
• This task will require a meeting for team
  brainstorming followed by a rough draft of the
  Process Specification.
• Once the rough draft is completed, the team shall
  meet to discuss any needed changes.
• The final document can then be completed. This
  needs to be done by September 13th.
• The Semi-formal Requirements Description will be
  completed second.
• Three dependency diagrams shall be completed. One
  for the Enterprise requirements, and one each for
  the Functional and Non-Functional requirements.
• The team shall get together to discuss drafts of
  these 3 times. The dependency diagrams will be
  rotated between the three team members each time.
• The dependency diagrams need to be complete by
  September 15th
• Issues with the Semi-formal Requirements should
  be identified next.
• The team will meet to discuss the final
  dependency diagrams. Issues will then we
  discussed.
• Formal write up of the issues will be handled
  between two team members.
• Requirements based on an improved understanding
  should be completed fourth.
• The final requirements will be then be redone to
  show an improved understanding over the previous
  dependency diagrams.
• The fifth step shall be to select and develop a
  prototype based on the improved requirements
  understanding.
• The third team member will start the mock up of a
  prototype system based on the system
  requirements.
• The team will meet to discuss the proposed
  solution and necessary changes.
• The last step shall be to test and evaluate the
  prototype with all team members. Iterations of
  steps 5 and 6 may be necessary to meet and verify
  all requirements.