MODELLING SYSTEM REQUIREMENTS

Table of Contents
Introduction................................................................................................................................3

Methodologies............................................................................................................................3

Evaluation..................................................................................................................................4

Requirement Gathering..............................................................................................................5

Requirements..............................................................................................................................6

Requirement Modelling.............................................................................................................7

Conclusion..................................................................................................................................7

References..................................................................................................................................9
Introduction

Big mart is a growing business in the sector of retail and has planned to develop and expand
its operation in the online and digital market, and attract more customers. The business has
aimed in developing warehouses at various countries that would ease the activity of
production and the deliver time required is less than expected and could provide efficient
services to the customers. They also maintained a good and efficient transportation system for
the quick and rapid service (Adenuga, et al. 2019). This will create advantages to both the
sellers and the consumers as the consumers will get fresh items at a minimum cost just sitting
at their home and the sellers will benefit as their business is expanding and more revenue will
be generated. The online services that is being introduced by the business is an very
important aspects of the business, as it consists many benefits like attracting more customers
from beyond the country in which the business is being operated . Making the operations of
the business world wide and globally famous and create a stand in the place of competitors.

Methodologies

“The System development Life Cycle (SDLC)” should be effective and should be designed in
such a way that it develops a high system which meets the expectations of the customer,
completion of the task within the cost and the time evaluations, which efficiently and
effectively works within the planned and the current infrastructure of information technology
(Chen, et al. 2018). It is conceptual model which consists of the procedures and the policies
for the development or alteration of systems that is required through the planning of life
cycles. As being the analysts of the company it is the role to develop a good system for
information. “System development Life Cycle “is an organised and systematized way of
breaking the work into segments that is required to perform the work either through modified
or new information system, which reduces the work load and has made the completion of an
ease. The activities which constitute the “System development Life Cycle” are as follows:

 Maintenance
 Requirements
 Implementation
 Deployment
  Design
 Testing
 Operations

“The adaptive and predictive approaches to System development Life Cycle” has an
important aspect in the introduction of new technology in the business. The life cycles of
adaptive like kanban or SCRUM which are designed in order to recapitulate on the projects
which are of more experimental in nature and certainty is low (Faldik et al. 2017). They
mainly depend upon the contribution of the stakeholder who acts quickly in the changes of
the scope of the project and the requirements of the system. This is often known as the design
of freeform software, offered an incredible design model which is flexible, aims in promoting
evolutionary and adaptive approach of planning development when the goal is not concrete
and not decided. On the other hand the predictive development also known as incremental
development is a way or a method of developing software where the system designed, tested,
and implemented incrementally till the time the product is being finished or when the
requirements are being satisfied. The model is a combination of all the elements of the model
that is related to water fall model with the philosophy related to waterfall model. In this type
of model, the model passes along the design, implementation, requirements, and the phases of
testing. This model consists of the system of delivering component, when they are completed,
the partial utilization which means completion of features that can be useful before the whole
project can be completed, which also avoids the huge time for the development (Feng et al.
2016). This model helps in the ease of the effect of traumatic side effects of the introduction a
system that is completely new to the market and in the introduction of new technology.

Evaluation

With the introduction of online marketing, Big mart is planning to adopt the model of
predictive development. The model is a set of combination of all the elements of the model
and the factors that is related to water fall model with the philosophy related to waterfall
model. In this type of model, the model passes along the design, implementation,
requirements, and the phases of testing. This model consists of the system of delivering
component, when they are completed, the partial utilization which means completion of
features that can be useful before the whole project can be completed, which also avoids the
huge time for the development (Mancarella et al. 2016). The associated predictive
development has pros and cons associated with it:

Pros

 The model of predictive produces a software that make the product development
quicker as compared to the model of adaptive
 It is very easy to debug and test at the time of iterations of small parts than as
compared to the full development of product.
 This model helps the business to develop more flexibility, and it changes the
requirements and the scope that many help the business to increase their sales and
increase their revenue.
 This model helps in the management of risk as the obstacles are greatly handled and
identified at the time of the iterations. These helps in the identification of the potential
risks.

Cons

 Additional efforts is put and is required for the integration of all and each components
of the informational system, which put delays in the work and extra efforts are put
rather than the original effort
 A complete and clear definition of the system is necessary to break down the system
and to build incrementally (Maylawati et al.2018). A full knowledge of the system is
required so this causes a lot of trouble for the business.
 In this model it is necessary to develop a good design and planning, if the tasks are
not perform properly in every phases, it can impact the entire project.

Requirement Gathering

The two techniques for gathering of information that are very useful and are used to gather
specific requirements have been discussed and been critically analysed. The techniques have
explained as follows:

1. “Interview”- the stakeholder’s interview and the interview of users are critical in the
creation of the software, with the expectations and the goals of the stakeholders and
the users and having improper knowledge about them will result in the dissatisfaction
 of fulfilling the needs and the desires of the customers (Meyer, and Riechert, 2019).
The perspective of the interviewee has also been taken into consideration as to
analyse the address and weigh the inputs. By developing the skill of listening will
help in creating and gathering of information for the analysts and make their work
easier.
2. “Prototyping”- it is a modern method for the collection of requirements. In this
method, the preliminary requirements are being collected so as to build a beginning
version of the solved problems i.e. a prototype. This is now showed to the client to in
turn advise and desired for the changes that is being made and recorder by them.
Again this prototype is developed by considering all the points of the client again and
this process is being performed continuously until the critical needs of the business
are satisfied.

Requirements

As discussed in the case study, Big Mart is an on growing business of retail sector which is
planning to spread its business in the online websites as well. The activities that can be seen
in the areas of functional and non-functional have been discussed in this area. The area of
function considers building of warehouses so to speed up the delivery time and also reduces
cost. They try to create a wide range of products with high discounts so to attract many
consumers and they have a score in the market by creating great offerings in the market. They
had also make the payment scheme very convenient to the users as they can make online
payments by just sitting at their home and many more amenities like tracking or orders, easy
to exchange if a user is not satisfied with the services or the product. The system that has
developed should have the capability of handling all the shipping of delivered and ordered
items and also keeps a track of items and stock at the store or warehouse and also generate
reports which is required to the management. There needs to be a restricted access to the
confidential information regarding the activities of the business.
Requirement Modelling

Conclusion

As with the development of the online business, the tends of the market and the revenue
being generated for the business seems to be increasing but with the system of the
advancement being developed there always come with some associated problems with it and
this report has been undertaken and has analysed various issues faced with the upcoming
expansion. It passes along the design, implementation, requirements, and the phases of
testing. As being the analysts of the company it is the role to develop a good system for
information. “System development Life Cycle “is an organised and systematized way of
breaking the work into segments that is required to perform the work either through modified
or new information system. Developing the skill of listening will help in creating and
gathering of information for the analysts and make their work easier. A full knowledge of the
system is required so this causes a lot of trouble for the business.
References

Journals

Adenuga, O.T., Mpofu, K. and Boitumelo, R.I., 2019. Energy efficiency analysis modelling
system for manufacturing in the context of industry 4.0. Procedia CIRP, 80, pp.735-740.

Chen, K., Xu, G., Xue, F., Zhong, R.Y., Liu, D. and Lu, W., 2018. A physical internet-
enabled building information modelling system for prefabricated construction. International
Journal of Computer Integrated Manufacturing, 31(4-5), pp.349-361.

Faldik, O., Payne, R., Fitzgerald, J. and Buhnova, B., 2017. Modelling system of systems
interface contract behaviour. arXiv preprint arXiv:1703.07037.

Feng, S., Lauvaux, T., Newman, S., Rao, P., Ahmadov, R., Deng, A., Díaz-Isaac, L.I., Duren,
R.M., Fischer, M.L., Gerbig, C. and Gurney, K.R., 2016. Los Angeles megacity: a high-
resolution land–atmosphere modelling system for urban CO2 emissions. Atmospheric
Chemistry and Physics (Online), 16(14).

Mancarella, P., Andersson, G., Peças-Lopes, J.A. and Bell, K.R., 2016, June. Modelling of
integrated multi-energy systems: Drivers, requirements, and opportunities. In 2016 Power
Systems Computation Conference (PSCC) (pp. 1-22). IEEE.

Maylawati, D.S., Darmalaksana, W. and Ramdhani, M.A., 2018. Systematic design of expert
system using unified modelling language. In IOP Conf. Ser. Mater. Sci. Eng (Vol. 288, No. 1,
p. 012047).

Meyer, D. and Riechert, M., 2019. Open source QGIS toolkit for the Advanced Research
WRF modelling system. Environmental Modelling & Software, 112, pp.166-178.

Mouratidis, H., Shei, S. and Delaney, A., 2020. A security requirements modelling language
for cloud computing environments. Software and Systems Modeling, 19(2), pp.271-295.

O’Driscoll, K., 2016. The agile data modelling & design thinking approach to information
system requirements analysis. Journal of Decision systems, 25(sup1), pp.632-638.