Requirement management

Question 1

Requirement management process general

Answer 1

1. Happens in definition phase, only change requirements through change request in linear lifecycle. 2. Important to understand stakeholder requirement - facilitates development of agreed scope

Question 2

Requirements management process 4

Answer 2

1. Gather requirements (from key stakeholders, project context, technical, regulartory requirements), 2, Analysis (weigh up value (benefit)), look at addressing any conflicting requirements how can be achieved. 3.justify requirements (weigh them up, use MoSCoW. May need to compromise)prioritise requirements. Time (when need to be met), cost quality, priorifunction analysis ro cost function analysis 4. Baseline needs (freeze them so something to go against, avoid scope creep)

Question 3

Baseline needs

Answer 3

1. Determine deliverables and manage change and scope creep. 2. PM to identify specific terms and steps in PMP. 3. Baseline produced that encompasses all key docs in configuration library. 4. Any changes need to see their impact

Question 4

Functions analysis or function cost analysis

Answer 4

Evaluate requirements and their business drives. When benefits will be delivered, requirements and org strategy. Do benefits outweigh cost

Question 5

If no configuration management?

Answer 5

1. Individual products may not work together. 2. May have poor quality of deliverables bc cannot test against spec. 3. Can be a lot of re-work 4. Can be confusion - impacts staff morale. 5. Can mean unsafe products in operation

Question 6

Process of configuration management

Answer 6

1. Planning (Create a configuration management plan defining all roles and responsibilities pertaining to configuration activities And that there is a appropriate procedure in place, everyone aware of the implications of the system in operation). 2. Identification (break project into identifiable items and give each one a unique reference. 3. Control (during deployment, process of updating docs bc change control - check what else is impacted, records are up to date, notify people) 4. Status accounting (Recoding and reporting of all information. Each account for a configuration item would have identifier, owners date of last update, current status, latest version number) 5. Verification audit ( ensure item or deliverable conforms to requirements and configuration information. Throughout life cycle. Control: Ensures that any changes to items are controlled and dependencies between items are understood.
   Status accounting: Items are under full version control so there is an audit trail of all configurable items.
   Verification audit: Ensures that all items conform to requirements/that deliverables meet what has been documented.