Software Requirements and Specifications

Running head: SOFTWARE REQUIREMENTS AND SPECIFICATIONS
SOFTWARE REQUIREMENTS AND SPECIFICATIONS
Name of the student:
Name of the University:
Author Note:

1SOFTWARE REQUIREMENTS AND SPECIFICATIONS
Assignment 1
In relevance to a software project, elaborate the 3 requirement levels in
terms of:
A. User level
The user level for the concerned case study of Open Bravo for implementing the innovative e-
commerce based operations includes 3 contrasting portions:
 Requirements for the users.
 Rules associated with the business.
 Quality attributes.
From the perspective point of view of the users, the requirements of the users is directly
proportional to the functionality of the software item. The user based requirements elaborates the
functions needed to be executed by the software for the accomplishment of the desired objectives.
Even for the purpose of achievement of the desired business requirements, multilevel user
requirements may be needed to be addressed1.
The particular citation in this regard that deserves mention is the business requirement that
empowers the customers with the potentials that eventually facilitates them to withdraw liquid cash
from the ATM. For the successful execution of this entire procedure they are required to perform the
certain functions in the proper chronological order2.
The rules in the event of a business like Open Bravo are the specified business standards, relevant
protocols, guidelines and the relevant practices that have attained success in defining the procedures
of the execution of the business by the users. These protocols must be abided by the software product
to perform accordingly in an appropriate manner in regards to the domain of the concerned
application.
The quality attributes of the user level are efficient in defining the quality of the software product
of the Open Bravo owing to the non-functional characters that are embedded within its infrastructure.
The attributes of the software quality incorporates the characteristics like the availability, reliability,
safety and the security.
B. Business level
1 Alnæs, Martin, Jan Blechta, Johan Hake, August Johansson, Benjamin Kehlet, Anders Logg, Chris
Richardson, Johannes Ring, Marie E. Rognes, and Garth N. Wells. "The FEniCS project version 1.5." Archive
of Numerical Software 3, no. 100 (2015).
2 Muller, Ralf. Project governance. Routledge, 2017.

2SOFTWARE REQUIREMENTS AND SPECIFICATIONS
Within the territorial limits of the business, in our particular case the Open Bravo, the business
requirements are the parameters to define the problems and issues that have crept into the business
scenario and needs to be mitigated 3. The business requirements also address the business
opportunities for the software product. Business requirements clearly illustrates the purpose of
developing the software products to meet the business targets of the Open Bravo. The requirements of
the business are postulated as the customer oriented objectives or in more generalised terms the
request generated by the organization for the software development4.
The particular citation in this regard is the permit granted to the customers for availing the
benefits of cash withdrawal from the ATM. This also enables the customers to undergo transactions at
the petrol pump for availing the benefits of the petrol.
C. Product level
The product level is characterized by the diversified categories of requirements among which the
requirements in terms of functionality, the non-functional requirements, requirements of the external
interfaces and finally the requirements of the data. The functional requirements are the services
rendered by the system5. Non-functional requirements refer to the parameters that impose potential
threats and hindrances in the way of procurement. The requirements in regards to the data refer to the
specified array of the data that are required to be embedded in the software to meet the business
specifications of the Open Bravo.
Illustrate the 3 below mentioned approaches to resolve the volatility issues
of the software requirement:
Involvement of the business side in the project
Alterations in the customer organization
Software projects encounter numerous alterations in their lifecycle. In case of Open Bravo
also, software alterations will affect the customers. The customers of the organization will have to
adapt to the software changes. The customers need to get acquainted to the new updates of the
software and the management is responsible to check that their customers are able to make use of the
updates done without their help. According to the article, understanding requirement volatility is vital
and important. The example of the survey given in the article shows that only 50% of the respondents
had the understanding of requirement volatility.
3 Uhl, Axel, and Lars Alexander Gollenia, eds. A handbook of business transformation management
methodology. Routledge, 2016.
4 Rosemann, Michael, and Jan vom Brocke. "The six core elements of business process management." In
Handbook on business process management 1, pp. 105-122. Springer, Berlin, Heidelberg, 2015.
5 Muller, Ralf. Project governance. Routledge, 2017.

3SOFTWARE REQUIREMENTS AND SPECIFICATIONS
Alterations in the scale
To bring about software alterations Open Bravo needs to face changes in the scale as well.
Changes in the scale include the structural changes that have to be done as per the software
requirement. As per the article the changes in scale include appointing change control boards,
software developers, personnel managing the configuration, contextual management staffs. The
change control boards will be responsible for aligning the staffs towards the software alteration being
initiated6. The software developer will look into the new alterations being made to the software. The
contextual management staff will look after the context being altered and the new context being
implemented. The configuration at present and the required configuration will be checked by the
personnel handling the configuration management department.
External alterations
External changes in a business organization like the Open Bravo refer to the external
parameters or the factors that directly affects the operational procurement of the business. External
factors relate to the ongoing software alterations in the competitive market. The volatility requirement
can be analysed by the same type of software alterations been done to competitor web sites.
New ideas are imbibed within the customer owing to their increasing awareness in
terms of system capabilities
The zeal and the potential that has been encountered within the customers of Open Bravo have
influenced the business performance of the organization that in turn has boosted the involvement of
the business in the concerned project. As per the article the business users should know about the size
of the final value to be delivered in situations where constant change is required as in case of Open
Bravo
Negotiation of the scope of the project
Alterations in the customer organization
Changes in the customer organization influence the negotiation of the project scope by
affecting the discussion with the business users about the potential and the strength of the ultimate
outcome in the event of the constant alterations witnessed in the requirements. As per the article the
volatile requirements of software update projects needs the involvement of the business users thus
Open Bravo should discuss the project details with the stakeholders.
Alterations in the scale
The scaling factor contributes to the operational management by controlling the work-flow.
Hence, the alterations in the scaling factor have greatly influenced the participation of the business in
the concerned project. As per the article, Open Bravo should focus on making decisions relating to
6 Laplante, Phillip A. Requirements engineering for software and systems. Auerbach
Publications, 2017