Академический Документы
Профессиональный Документы
Культура Документы
Requirements Engineer:
Roles, Responsibilities
Elicitation
Analysis
Specification
Clarify
Validation
Re-Write
Requirements Issues
Customer
Engineer
Question
Should stakeholders learn how to write
good requirements so they can
communicate with BIM Engineers?
Should BIM Engineers learn about
business processes and needs so they can
come up with better requirements?
Business Needs
Stakeholders Needs
Business Requirements
Do we have a Business Case ???
Senior Management
Project Management
Business
Requirements
User Requirements
Requirement Engineer
Architect
System Requirements
BIM Requirements
Relationships of Requirements
Requirements
Business
Requirements
Document
Users view
(The Problem Space)
Use-case
System
Requirements
BIM
Requirements
Hardware
Requirements
Developers view
The solution Space
BIM Requirements
Specification
RED SUN Inc.
10
11
12
Business Flow
Business
Drivers
Product
Scope
Product Creating
Business
Needs
Business
Events
Use Cases
Product Constraint
Business Boundary
Implementing
Requirements
Specification
Functional
Non-Functional
Constraints
13
Process Flow
1
Identify
Purposes & Goals
And Stakeholders
Business
Needs
Business
Drivers
Product
Scope
2
Set Boundary
Business
Events
Use Cases
3
Determine
Constraint
4
Collect Facts &
Assumptions
5
Establish use
cases
Functional
Requirements
Specification
Non-Functional
Constraints
14
Requirements Development
Customers Needs
Senior Manager
Project Manager
Requirements
Engineer
Architect
Requirements
Developers
Testers
15
Senior Manager
Allocates resources (people, materials,
budget).
Ensures project goals and objectives align
with business goals.
Defines and approves overall vision &
scope.
Makes decisions about scope of project &
schedules.
Resolves conflicts in requirement priorities.
RED SUN Inc.
16
Project Manager
Coordinates users involvement.
Acts as a liaison between project team and
business management.
Ensures that requirements engineers and
architects have the resources, tools, training and
knowledge to work on requirements activities.
Defines business requirements and product vision.
Oversees requirements prioritization.
Monitors progress of requirements development.
Reviews requirements documents to ensure that
they adequately and completely represent users
needs.
17
Requirements Engineer
Selects elicitation techniques and
coordinates requirements activities.
Collaborates with stakeholders to develop
requirements.
Defines user requirements, creates models
and documents requirements.
Verifies that requirements are correct,
complete and consistent.
Transforms user requirements to BIM
requirements specification.
RED SUN Inc.
18
Architect
Provides details about user needs, business rules
and data.
Represents the needs of users who may not be
able to participate.
Identifies integration issues between hardware,
BIM,
and systems.
Ensures requirements align with product vision.
Consults with other experts who have relevant
requirements knowledge.
Reviews requirements document to ensure that it
adequately and completely represents users
needs.
RED SUN Inc.
19
20
Requirement Development
Define Business
Requirements
Develop User
Requirements
Specify BIM
Requirements
Senior Manager
Owner
Reviewer
Approver
Approver
Project Manager
Producer
Reviewer
Reviewer
Reviewer
Requirements
Engineer
Reviewer
Producer
Producer
Architect
Reviewer
Approver
Owner
Owner
Developers
Reviewer
Reviewer
Reviewer
Reviewer
Reviewer
Reviewer
Reviewer
Reviewer
Producer
NG ITR C TI P LM
Testers
NG IKI M TRA
21
22
23
24
Project Scope
The project scope defines the concept and range
of the proposed solution. The scope also limits
certain capabilities that the product will not
include.
Having the project scope defined early, will help
to establish realistic stakeholder expectations. It
avoids features that are too expensive or lie
outside the intended project scope.
Out-of-scope requirements must be rejected
unless they are so valuable that the scope must
be enlarged to accommodate them, with
additional budget, schedule and resources.
RED SUN Inc.
25
Operating Environment
BIM Engineers must describe the
environment in which the system will be
used and define the vital quality attributes
such as availability, reliability,
performance and integrity requirements.
This information will influence the system
architecture as a key important factor of
the system design.
26
27
Project Priorities
There are five key factors that every project must
operate: Scope (Feature), Quality, Schedule, Cost
and Resources (Staff).
Constraint: A limiting factor within which the
project manager must operate.
Driver: A significant success objective with
limited flexibility for adjustment.
Degree of Freedom: A factor that the project
manager has some latitude to adjust and balance
the other factors.
Project managers goal is to adjust those factors
within degrees of freedom to achieve the projects
success drivers in the limits imposed by the
constraints.
RED SUN Inc.
28
Balancing Act
Due to certain constraints such as time,
cost and features, Project Managers may:
Have multiple product releases.
Defer certain requirements to later release.
Shorten the system testing.
Incur overtime for project team.
Hire more staff to do work.
Reduce features
29
Acceptable risks
Acceptable costs
Others
Needs
30
Best Practices
Develop a clear vision for the product.
Establish a shared understanding of the
project s cope.
Involve stakeholders throughout the
requirements process.
Solicit requirements using multiple
techniques.
Document the requireme nts clearly,
accurately, consistently.
Continue to validate that requirements are
the correct ones to implement.
31
Best Practices
Verify the quality of requirements early
and frequently.
Prioritize the requirements and remove
unnecessary ones.
Establish a baseline for requirements that
will serve as a basis for further
development.
Trace the requirements to original form
and how they link to other requirement s or
components.
Anticipate and manage all requirements
changes.
RED SUN Inc.
32
Summary
Analyze business needs and requirements:
How many requirements are being
addressed?
What percentage of stakeholders
problems are being solved?
How much will it cost, approximately
(Time & resources)?
How much risk is being undertaken to
satisfy these requirements?
How much revenue will be achieved or
how much savings will occur as a
result?
RED SUN Inc.
33
34