Implementation of a New IT System - Desklib

This document discusses the implementation of a new IT system for ASDA Stores Ltd. It covers the concepts of software engineering, software development lifecycle, software implementation and management, and the impact of Waterfall and Agile methodologies. It also includes UML diagrams and programming constructs and ways of implementation by C language.

Running head: IMPLEMENTATION OF A NEW IT SYSTEM
Implementation of a New IT System
Name of the Student
Name of the University
Author’s note

1IMPLEMENTATION OF A NEW IT SYSTEM
Table of Contents
Question 1........................................................................................................................................2
1. Concept of Software Engineering and their difference from programming............................2
2. Concept of Software Development Lifecycle (SDLC) and stages..........................................2
3. Software Implementation and Management............................................................................3
Question 2........................................................................................................................................3
Question 3........................................................................................................................................8
Question 4......................................................................................................................................13
References......................................................................................................................................17

2IMPLEMENTATION OF A NEW IT SYSTEM
Question 1
1. Concept of Software Engineering and their difference from programming
The software engineering concept in relation to the case study based on ASDA Stores.
There is a need for the development of a new kind of IT systems that would be able to support
the various functionalities of operations and data (Fitzgerald and Stol 2017, pp. 176-189). The
act of programming would be based on providing the instructions to computer for doing
something with some form of input based on producing some kind of output.
On the other hand as stated by Mall (2018), it can be described that the concept of
software engineering defines the ways of providing solution to a problem based on solving,
providing solutions, providing limitations to solutions, think about the implications of privacy
and implications of security. Software engineering focuses on the concepts of bringing efficiency
within the code quality, perform solutions within a certain environment, test for solutions, save
costs incurred and thus focus on the efficiency of the programs.
2. Concept of Software Development Lifecycle (SDLC) and stages
The Software Development Lifecycle (SDLC) could be defined as a process within the
software industry that would be needed for the design, development and testing of high-quality
softwares (ELZAMLY and HUSSIN 2014, p.2). The primary aim of SDLC is based on
producing efficient software, which would meet with the needs and expectation of customer.
The different stages of SDLC are:
1. Planning – This stage defines the requirement and is considered as the fundamental
stage within the SDLC. The information gathered is based on planning and conducting product
feasibility study.

3IMPLEMENTATION OF A NEW IT SYSTEM
2. Defining – This stage defines the documentation of product requirements and getting
them approved from customer. This would be done with a Software Requirement Specification
(SRS) document.
3. Designing – The design of product architecture would be proposed and documented as
per the specifications of the SRS document. The Design Document Specification (DDS) would
document the design of the architecture.
4. Building – This stage defines the design of the software or product as per the DDS.
The programming language would be chosen as per the requirements of the software.
5. Testing – This stage is regarded as a subset of the entire stages within the SDLC
models (Cois, Yankel and Connell 2014, pp. 1-7). The detected defects would be reported,
developed again and retested until a proper solution would be reached.
6. Deployment – After a proper testing has been made ready, the product or software
would be deployed. After the release of the product, there would be a continuous need for
maintenance.
3. Software Implementation and Management
In this study, the software that would be developed for ASDA Stores Ltd. would be
implemented based on proper kind of metrics. The software that would be developed would
include four kind of functions. These include – Planning, Organization of requirements, Control
and Improve the functionalities.
Question 2
The impact of Waterfall and Agile methodologies in relation to the case study based on
the implementation of the IT system within ASDA Stores Ltd could be described as:

4IMPLEMENTATION OF A NEW IT SYSTEM
The Waterfall SDLC Methodologies:
(Fig 1: Waterfall SDLC Methodology for Development of IT systems for ASDA Stores)
(Source: Created by author)
The different stages within the development of IT systems for ASDA Stores Ltd.
according to the Waterfall Model are described in the above diagram. The evaluation of each of
the stages are:
 Analysis of Requirement – Primarily, the requirements for the development of the IT
system should be properly accessed by the development team.
 Designing of IT System – In this stage, the plan for the design of the IT system would
be described by the project lead in order to fulfil the requirements.

5IMPLEMENTATION OF A NEW IT SYSTEM
 Implementation of the System – The pre-defined requirements would be followed by
the developers and thus they would develop the system.
 Testing – During this phase, the developed system would be tested by highly qualified
testing team who would have a check over the system.
 Deployment of the System – After the system has been developed and tested properly,
the system would be deployed by the project team for the users.
 Maintenance – After the system is deployed in the market, there would be a regular
need of maintenance of the system (Saltz 2015, pp. 2066-2071). This would be
performed by the development team.
Based on the understanding of the Waterfall model for the use within the development of
the IT system, the features supported by the system could be described as:
 The estimation of budget and time would be much reliable.
 The processes of development would be considered as more secure.
The strengths of the system supported by Waterfall model are:
 Documentation the entire design process.
 Easy creation of budget for the entire project.
The weakness of the system supported by Waterfall model are:
 There is a constant need for the testing of design stages.
 This model is not user-centred and inflexible.

6IMPLEMENTATION OF A NEW IT SYSTEM
The Agile SDLC Methodologies:
(Fig 1: Agile SDLC Methodology for Development of IT systems for ASDA Stores)
(Source: Created by author)
The different stages within the agile methodology based on the development of IT
systems for ASDA Stores Ltd. is described as:
 Evaluation of current organisational structure – During this phase of the IT system,
the different processes would be mapped. This would determine the ‘Actual State’ of the
project.
 Suggestions for continuous improvement – Based on evaluation of processes, there
would be a need for optimizing the process based on the right use of technologies.
 Application design – During this stage, the developers would choose the appropriate
technology and thus review the options with the client.
Evaluation of
current
structure of the
organisation
Suggestions
based on
improvement
and
optimization
of processes
Design of
application
based on
discussion
with client
Construction of
application and
Implementation
Continuous
evaluation and
monitoring

7IMPLEMENTATION OF A NEW IT SYSTEM
 Construction of application – There would be a weekly form of delivery of reports
based on the development process of the IT system (Kassab 2014, pp. 254-261). The
developments would be viewed by the end user.
 Evaluation and monitoring – After the development of IT system for ASDA systems,
there would be a continuous evaluation of the ongoing systems.
The features supported by the agile system are:
 Testing phase is integrated within the entire lifecycle process. This enhances the quality
of the system due to regular form of testing.
 They help in active involvement of the user throughout the entire process of software
development of the organisation.
 This methodology helps in early identification of issues due to continuous evaluation due
to which the faults are detected prior to delivery of exact solution. This helps in proper
project delivery.
The strengths of the system supported by agile model are:
 The Agile methodology helps in the promotion of the experimental design of the
software.
 They have a flexible model for the design of IT system software.
 They facilitate efficient communication and interaction between the development team
and client.
The weakness of the system supported by agile model are:
 The turnover of the team could be a major risk for the processes.
 There is a lack of proper structure for software development.

8IMPLEMENTATION OF A NEW IT SYSTEM
The Waterfall model could be applied for those projects that would be static in nature and
where there would not many changes within the development process. On the other hand, the
agile methodology could be applied to such projects in which the requirements would change on
a rapid basis.
Based on the discussion, the recommendation to ASDA Stores is that they should follow
the agile method for the development of the project. This kind of approach would help the
organisation to provide a transparency to the client based on involvement throughout the project
(Huckabee 2015, p. 4). The IT system should focus on the quality control and conduction of
audit based on the business.
Question 3
(Fig 1: Class Diagram of the entire system)
(Source: Created by author)

9IMPLEMENTATION OF A NEW IT SYSTEM
(Fig 2: Activity Diagram of the built of the IT based system)
(Source: Created by author)

10IMPLEMENTATION OF A NEW IT SYSTEM
(Fig 3: Sequence Diagram of the built of the IT based system)
(Source: Created by author)

11IMPLEMENTATION OF A NEW IT SYSTEM
(Fig 4: Use Case Diagram of the built of the IT based system)
(Source: Created by author)
Comparison of two different UML Modelling Tools employed for the design of the system
Comparison of Microsoft Visio and Lucidchart
Ease of Usage – There is a common form of complaint against Lucidchart is that the
web-based software is a bit tough for usage. There should be complete kind of training and
spending of hours to understand the concept of drawing a certain diagram. On the other hand, the
Microsoft Visio is a licensed software of Microsoft Visio that is very easy for new users to draw

12IMPLEMENTATION OF A NEW IT SYSTEM
different kinds of diagrams (Vician and Pierce 2018, pp. 62-85). The user would find the
different shapes from the list placed at the left side. They can simply drag and drop the different
shapes onto the white canvas. The powerful functionality of drag and drop would help the user to
drag a line from a particular shape and thus connect them to another shape. Microsoft Visio also
offers a wide range of templates from which users can select the same and thus use them as per
their needs.
Work from anywhere – In this case, it has been seen that Visio is just limited to
Windows. However, Lucidchart is compatible with any kind of platform such as Microsoft
Windows, iOS and various Android based applications (Neges, Wolf and Abramovici 2017, pp.
33-42). The software application helps the users to open workflow in their respective field. They
can also leave their personal feedback within the diagrams after they have designed them as per
their needs.
Barriers for Collaboration – Each of the details supported on the platform for Visio are
updated as per the needs of the user. The different kind of changes that would be made to the
diagrams. Visio stores their files with the extension of (.vsdx). This file can be further
reproduced in order to make any kind of changes (Claghorn 2015, pp. 739-753). The file can also
be converted into different other formats such as jpeg, png and many others for the comfort and
suitability factor of the users. These files are exported while saving of the file and thus can be
used in different purposes.
On the other hand, Lucidchart allows different people to edit and make their comments
on the produced documents in a real-time scenario. Each of the documents can be synced
automatically and thus they are also saved on an automatic basis (Papademetriou and Karras

13IMPLEMENTATION OF A NEW IT SYSTEM
2016, pp. 161-182). After the documents are made, the link can be shared with other concerned
users and they can also view the saved documents without possessing a Lucidchart account.
Regular Updates and Compatibility – Lucidchart supports multiple updates that are
defined within their system. As Lucidchart is a web and cloud based software platform, there are
constant form of updates that are made within the system. The users would not have to wait for
the downloading the updates and installing them. They are automatically downloaded and are
updated and synced while using.
On the other hand, Lucidchart also integrates different forms of versions. The users can
also import their Visio files on the Lucidchart platform and thus continue with their diagrams
(Bradford et al. 2015, pp. 169-188). This reduces the wasting of time for drawing and recreating
the previous work. These works could further be downloaded in different file formats based on
the benefits and suitability factor of the users.
Web Link for Lucidchart –
https://www.lucidchart.com/documents#docs?folder_id=home&browser=icon&sort=saved-desc
Question 4
The two kind of implementation languages that would mainly be used for the planning of
the implementation of IT system are –
The Procedural language that could be used is C and the object-oriented language is Java.
Brief Overview of Programming Constructs and ways of Implementation by C
language:

14IMPLEMENTATION OF A NEW IT SYSTEM
 Sequence, Selection and Iteration – Sequence would define the different sequences of
actions that a certain program would carry out in a sequenced manner. The process of
selection could be defined as a programming construct that would allow a program to
make a choice between two different kinds of actions. This kind of construct would
permit for alternative paths that would be taken within a program (Falkenthal et al. 2014,
pp. 12-21). The selection based constructs that are used within the C language are: if,
nested if, if else and switch. The iteration can be defined as a loop, which would be
defined as a small form of program, which could be executed in several forms within the
main program.
 Programming Interfaces and Parameter Passing – Whenever a function would get
executed within a program, the control of execution would be transferred from the calling
function and thus executes the definition of the function. In C language, there are two
ways of passing of parameters (Armbrust et al. 2015, pp. 1383-1394). These are – actual
parameters and formal parameters. The actual parameters are those kind of parameters
that would be specified during the calling function.
 Modularity and Programming Units – The modular programming within C could be
defined as the certain process of subdividing the computer program into different separate
sub-programs. The larger form of C programs would be difficult to understand and thus
impossible for maintaining the entire code structure (Pinho and de Carvalho Junior 2014,
pp. 65-90). The form of modular programming can be considered as the primary manner
of management of complexity. The C language does not support the concept of
modularity. Some of the features of C such as pre-processor and language could be opted
for providing the capabilities of modular programming.

15IMPLEMENTATION OF A NEW IT SYSTEM
Brief Overview of Programming Constructs and ways of Implementation by Java
language:
 Sequence, Selection and Iteration – In Java, the selection statement would allow the
user to allow the flow of control over the program execution. This would be based on the
outcome of some kind of expression or some state of a particular variable during the
runtime of the program (Ivanović, Budimac and Paunić 2015, p. 310010). The repetition
of the same fragment of code that would run several times within a certain program is
known as iteration. The iteration statements in Java would be able to execute the same
kind of instructions until the condition of termination would be met.
 Programming Interfaces and Parameter Passing – An interface is similar to the Java
class. It has only some form of abstract method and static constraints. The Java
programming language makes use of interfaced to implement the functionality of
multiple inheritance. A Java class could also be able to implement the multiple form of
Java interfaces (Vega-Gisbert, Roman and Squyres 2016, pp. 1-20). Each of the methods
within the interface would be implicitly be defined as abstract and public. The passing of
parameters would be performed in the case of a method. The Java language passes
parameters by value. In pass-by-value technique, the actual kind of parameters within the
method calling would be copied based on dummy parameters provided within the method
definition. The performed changes within the dummy parameters would not be reflected
based on the actual parameters. These would be displayed based on the changes to the
originals and the copies. In the pass-by-reference technique, the address (or reference)
based on the actual parameters would be passed to the dummy parameters provided
within the definition of the method (Nobakht and de Boer 2014, pp. 37-53). The different

16IMPLEMENTATION OF A NEW IT SYSTEM
kind of changes that would be performed on the dummy parameters would mainly be
reflected on the actual parameters. This would happen as both the references would be
pointing to the same kind of memory location that would contain the original values.
 Modularity and Programming Units – The modularity could be defined as a general
concept that would be applied to the development of software in a certain fashion. This
would help the individual modules to be developed in a perfect manner. The method of
modularity would be a standardised interface, which would allow each of the modules to
communicate with each other (Park et al. 2015, pp. 745-757). The process of modularity
could be defined as a general kind of concept based on breaking down of an application
into several parts. The concept of modularity can be considered as modules based on the
production of libraries that would be easy to get consumed. Another aspect for the
benefits of modularisation could be defined as testing. A small kind of module could be
typically tested than a monolithic application. This kind of concept would be true in the
case of GUI applications in which the GUI itself would not be easily testable but the
calling code would be easily testable. Another aspect of modularity could be defined as
evolution. As the entire system would have an entire version number, there would be a
product of multiple versions and modules. The process of project management would
also be benefited with the help of modularisation. The process of modularising of an
application would help in concretely identifying of the different versions of dependent
libraries (Porter 2014, pp. 29-34). This would be based in the order of harmonising of the
dependencies of the library across a certain large project.

17IMPLEMENTATION OF A NEW IT SYSTEM
References
Armbrust, M., Xin, R.S., Lian, C., Huai, Y., Liu, D., Bradley, J.K., Meng, X., Kaftan, T.,
Franklin, M.J., Ghodsi, A. and Zaharia, M., 2015, May. Spark sql: Relational data processing in
spark. In Proceedings of the 2015 ACM SIGMOD International Conference on Management of
Data (pp. 1383-1394). ACM.
Bradford, M., Gerard, G.J., Abubakker, H., Adesola, S., Baines, T., Andrews, C., Bradford, M.,
Carpenter, T.D., Damelio, R., Dennis, A. and Carte, T., 2015. Business Process Reengineering
and Improvement. Journal of Emerging Technologies in Accounting, 12(1), pp.169-188.
Claghorn, R., 2015, October. The Virtual Instrumentation Diagram. In INCOSE International
Symposium (Vol. 25, No. 1, pp. 739-753).
Cois, C.A., Yankel, J. and Connell, A., 2014, October. Modern DevOps: Optimizing software
development through effective system interactions. In Professional Communication Conference
(IPCC), 2014 IEEE International (pp. 1-7). IEEE.
ELZAMLY, A. and HUSSIN, B., 2014. AN ENHANCEMENT OF FRAMEWORK
SOFTWARE RISK MANAGEMENT METHODOLOGY FOR SUCCESSFUL SOFTWARE
DEVELOPMENT. Journal of Theoretical & Applied Information Technology, 62(2).
Falkenthal, M., Barzen, J., Breitenbücher, U., Fehling, C. and Leymann, F., 2014, May. From
pattern languages to solution implementations. In Proceedings of the Sixth International
Conferences on Pervasive Patterns and Applications (PATTERNS 2014) (pp. 12-21).
Fitzgerald, B. and Stol, K.J., 2017. Continuous software engineering: A roadmap and
agenda. Journal of Systems and Software, 123, pp.176-189.

18IMPLEMENTATION OF A NEW IT SYSTEM
Huckabee, W.A., 2015. REQUIREMENTS Engineering in an AGILE Software Development
ENVIRONMENT. Defense Acquisition Research Journal: A Publication of the Defense
Acquisition University, 22(4).
Ivanović, M., Budimac, Z. and Paunić, Đ., 2015, March. Educational influences of choice of first
programming language. In AIP Conference Proceedings (Vol. 1648, No. 1, p. 310010). AIP
Publishing.
Kassab, M., 2014, August. An empirical study on the requirements engineering practices for
agile software development. In 2014 40th EUROMICRO Conference on Software Engineering
and Advanced Applications (SEAA) (pp. 254-261). IEEE.
Mall, R., 2018. Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Neges, M., Wolf, M. and Abramovici, M., 2017, September. Enabling Round-Trip Engineering
Between P&I Diagrams and Augmented Reality Work Instructions in Maintenance Processes
Utilizing Graph-Based Modelling. In International Conference on Intelligent Systems in
Production Engineering and Maintenance (pp. 33-42). Springer, Cham.
Nobakht, B. and de Boer, F.S., 2014, October. Programming with actors in Java 8.
In International Symposium On Leveraging Applications of Formal Methods, Verification and
Validation (pp. 37-53). Springer, Berlin, Heidelberg.
Papademetriou, R.C. and Karras, D.A., 2016, June. Towards a thorough evaluation framework of
Software Tools Suitable for Small and Medium size Enterprises focusing on Modelling and
Simulating Business Processes. In International Symposium on Business Modeling and Software
Design (pp. 161-182). Springer, Cham.

19IMPLEMENTATION OF A NEW IT SYSTEM
Park, J., Esmaeilzadeh, H., Zhang, X., Naik, M. and Harris, W., 2015, August. Flexjava:
Language support for safe and modular approximate programming. In Proceedings of the 2015
10th Joint Meeting on Foundations of Software Engineering (pp. 745-757). ACM.
Pinho, E.G. and de Carvalho Junior, F.H., 2014. An object-oriented parallel programming
language for distributed-memory parallel computing platforms. Science of Computer
Programming, 80, pp.65-90.
Porter, B., 2014, June. Runtime modularity in complex structures: A component model for fine
grained runtime adaptation. In Proceedings of the 17th international ACM Sigsoft symposium on
Component-based software engineering (pp. 29-34). ACM.
Saltz, J.S., 2015, October. The need for new processes, methodologies and tools to support big
data teams and improve big data project effectiveness. In Big Data (Big Data), 2015 IEEE
International Conference on (pp. 2066-2071). IEEE.
Vega-Gisbert, O., Roman, J.E. and Squyres, J.M., 2016. Design and implementation of Java
bindings in Open MPI. Parallel Computing, 59, pp.1-20.
Vician, C.M. and Pierce, E.M., 2018. Accounting Documentation Software: An Overview of
Options and Results from a Lucidchart Software Evaluation. AIS Educator Journal, 13(1), pp.62-
85.