LECTURE # 4

REQUIREMENT ENGINEERING
 Requirement Engineering
 Types of Requirements
 Functional requirements
 Non-functional requirements
 Domain requirements
 Inverse Requirements
 System Requirements
 User requirements
 Business Requirements
 Design and implementation constraints
Your organization received a task for the development of an
interactive application to attract artists and regular people
and encourage them to build a virtual wall. The “Wall
painting app” should be a place where people can show their
paintings, share their emotions or just tell something to each
other by drawing.
Another important feature of the application is to give
capabilities to publish commercial advertisement along with
user’s painting. The application should be integrated with a
payment system, should have pricing plans and user friendly
UI. Also an admin panel is required for convenient
application maintenance. Since the major audience is people
who enjoy drawing, the design should be attractive and
related to the urban culture.
 CUOnline System
Distance learning pioneer Stafford Global knew that attracting potential
students online was crucial to its continued growth. Stafford then heard
about HubSpot and thought it was better suited to help Stafford Global
pursue a more joined-up inbound strategy. It was incredibly easy to use, and
it would allow to truly personalize the visitor’s journey. As well as that, its
built-in analytics would give organization the ability to make smarter, data-
driven decisions. HubSpot’s “always-on” support was also a big draw for
Stafford.
Stafford Global transferred its website to the HubSpot CMS and imported
their contacts and began generating reports. It also set up
detailed Workflows. Moreover, they have an instant access to information
on every lead. It has become a real timesaver for them. There’s total
transparency. Since partnering with HubSpot, Stafford Global has boosted
its organic web traffic by 11%. It’s helping them to attract and convert
students in a cost-effective way.
 According to the customer’s requirements, your organization
is to come up with a solution aimed at facilitating the process
of room decoration and to develop a proper mobile
application for android operating system. The organization is
issued a challenge to design 4,000 Furniture items with
Multilanguage records, perfect from performance point of
view. Graph views will be updated in real time reflecting
customer history of items chosen.

 The challenge is to have optimized work with Database of

furniture items which has over 4,000 different items and to
produce effective graphs with real time parameters. The
team has to develop an algorithm as well for realistic
rendering of furniture, also taking into account performance
 Supplementary Information to project
 Additional functionality added to a project for
enhancing Quality
 e.g.; Usability, Performance, Reliability
Tasks and techniques that lead to requirements
understanding.
 Inception
 Problem understanding
 People who want solution
 Nature of desired solution
 Effectiveness of communication and collaboration
between customer and developer
 Elicitation
elicit requirements from all stakeholders
 Elaboration
 Refine information collected earlier.
 Create an analysis model that identifies data,
function and behavior
 Negotiation
Agree on a realistic deliverable.
 Specification
Can be any one (or more) of the following:
 A written document
 A set of models
 A formal mathematical model or usecases
 Validation- Technical Review in which review
team looks for
 Errors in content or interpretation
 Areas where clarification may be required
 Missing information
 Inconsistencies (a major problem when large
products or systems are engineered)
 Conflicting or unrealistic (unachievable)
requirements.
 Requirements management
 Maximizing Customer Satisfaction.
 Results of Questionnaires, Interview and raw
data are translated to Customer Voice Table.
 Normal requirements.
Requested types of graphical display, defined
levels of performance.
 Expected requirements.
Ease of human/machine interaction, Ease of
software installation.
 Exciting requirements.
Set of unexpected capabilities e.g., multitouch
screen, visual voice mail.
 Statement of need and feasibility.
 Statement of scope for the system
 A list of customers, users, and other stakeholders
who participated in requirements elicitation
 a list of requirements and domain constraints
 A set of usage scenarios that provide insight into
the use of the system
 Prototypes
 Identify the key stakeholders
 Determine each of the stakeholders “win
conditions”
 Negotiate
 Work towards “win-win”