Issues and Challenges of

Requirements Modeling in
SAAS

Presented by: Muhammad Azeem

Paper 1:Global Requirements Engineering on
the Cloud
Problems
Lack of documentation caused ambiguities. Due to
the time zone issue, things took time before get
corrected by the onsite team, software development
was delayed as a result.
In addition to the time zones, there was other
communication overhead as well. As the
communication between the client and the
practitioners (offsite) was going on through us
Solutions
Do proper documentation and analysis and
determine what needs to be developed.
Requirements related artifacts should be
developed upfront.
We would want requirements to be well thought out,
easy to understand, so that with a quick handover,
you would be good to go. Requirements in a
structured format would have saved the time.
Requirements document should depict the technical
details as well, like how a specific requirement could
be implemented.
Initially, developers had problems understanding our
documents because those outlined in a high level.
You have to make sure that your requirements
documents contain sufficient level of details.
Paper 2: Requirements Engineering Process for
Software-as-a-Service (SaaS) Cloud Environment
Problems
The biggest challenge in Cloud Computing is the lack
of a standard that has been designed specifically for
SaaS. For any organization transforming from a
standalone business style into a collaborative
business trend by reusing and sharing processes and
services with the help of cloud, it is very difficult to
understand the clear requirements and the
relationship between those requirements [21].
Solutions
Requirements engineering until now involved end
users, and software engineers. But for SaaS it has to
involve cloud service providers as well, as they will be
providing the computing infrastructure, software
development, management, maintenance platforms,
etc.
As the cloud providers are only conversant with the
infrastructure utilization details, their experts can do
the capacity planning, risk management,
configuration management, quality assurance, etc., as
well. Similarly, Requirements management activities
should also include Cloud Service Providers, who can
chip in with some decision-enabling details such as
software-development cost, schedule, resource, and
time .
Paper 3: Requirements Engineering for SaaS
Application Security in Cloud Using SQUARE
Methodology

Problems
SaaS are becoming the gatekeeper for sensitive
information, whether it is in the form of personal data
or corporate data. Security breaches can therefore be
potentially devastating for both users and SaaS
providers. A SaaS provider will need to check if the
development team has implemented secure
engineering practices in the design and code to make
sure the SaaS application is secure.
Solutions
The Secure Quality Requirements Engineering
(SQUARE) methodology defines a process for a
software development team to effectively elicit
security requirements from different stakeholders and
prioritize security requirements based on the security
goals of the system.
 CATEGORIZATION
Categorization of Problems
1. Documentation related issues
2. Time zone issues in distributed development
teams.
Communication Problems
3. Process standardization issues.
4. Security related requirements.
Categorization of Solutions
1. Try to document requirements in a structured way.
2. Requirements document should contain sufficient
level of information.
3. Include cloud related SMEs and stakeholders in RE
process.
4. SQUARE model