Software Engineering: Development Methods, Quality, Diagrams, and Lucid Chart

SOFTWARE ENGINEERING
Anglia Ruskin University
BSc Computing (Information Systems)
Software Engineering
Software Engineering
STU50613
John Piperias
2460
0

SOFTWARE ENGINEERING
Table of Contents
Question 1: Software Development Methods............................................................................2
RAD model specifics:.............................................................................................................3
Question 2: Software Quality.....................................................................................................4
3: Diagrams................................................................................................................................7
Question 4: Lucid Chart...........................................................................................................10
Usages...................................................................................................................................11
Bibliography:............................................................................................................................12
1

SOFTWARE ENGINEERING
Question 1: Software Development Methods
RAD is an abbreviation of Rapid Action Development. This software development model
makes use of minimum planning (Sarker et al. 2015). Prototypes are created in this model
from a very early stage. The prototypes or functional models are produced simultaneously in
this model so that the development process can track bugs faster.
RAD or Rapid Application Development RAD can be considered as an incremental
programming development activity highlights a short SDLC and empowers steady criticism
from clients all through the product development life-cycle (Arora and Arora 2016). The
principal target of Rapid Application Development is to keep away from broad pre-arranging,
for the most part enabling programming to be composed significantly quicker and rolling out
it less demanding to improvement requirements.
Waterfall Model is the conventional predictive approach based SDLC model. The waterfall
model is consisting of five stages that are executed sequentially. The waterfall model is best
suited for short and simple projects. The biggest drawback of the SDLC model that no
additional requirement can be adjusted into the project system scope after the project
requirement gathering phase is complete.
Various adaptive SDLC methodologies use the iterative approach for making the project
processes more dynamic. The iterative models entails that various phases can be executed
simultaneously. Thus, making the project team more efficient. For applying the approach, the
system is divided into various units that are completed separately.
Choice of the appropriate development model for using within the business is fundamental
regarding conventional accomplishment of the activity (Kumar 2018). A Project Manager
may employ the associated benchmarks for selecting a rational model to develop another
project as per the requirements. The selection of a model over other models is powered by
Requirement analysis, Project measure, Team estimate, Budget, criticality of the activity and
a ton of different components (Dora and Dubey 2015). The diverse perspectives which should
be remembered while choosing a reasonable procedure model can be chosen based on the
following benefits:
1. Part-Based methodology might be perfect if the reuse of existing components is
needed.
2. A Spiral SDLC could be used to achieve a very substantial activity with high
risks or mind-boggling expense of failure.
3. Although an organisation’s client has categorised business aims yet the
requirement is not set yet Agile (light Weight) SDLC will have the favourable as
it is adaptable to changes.
4. If there are small teams and time is essential, an Agile methodology may be the
best option for fast, informal interactions and collaboration between the teams
(Sobri et al. 2016).
5. An Incremental procedure Model will provide a better quality assurance as it
validates the code immediately after it is written.
6. If a system component needed to be programmed for an immediate need you
could the use the Prototyping model, in this model feedbacks will be delivered
2

SOFTWARE ENGINEERING
quickly as well while allowing the component to perfectly fit into a fully
operational system easily.
7. A Waterfall or Spiral process Model will help inexperienced developers to be on
track and be aware of the project milestones.
RAD model specifics:
i. Less time is in hand to deliver a project.
ii. The cost saving is an important part of the project. The model does that by
developing quick prototypes.
iii. The model requires very few members to complete a project.
iv. Measuring the project progress is a part if deliverable.
v. If all the requirements are clear then RAD model is a very effective
methodology.
vi. Users are considered as a significant part of the project.
Challenges:
i. RAD model often misses many points as there is no specific software
requirement collection method which creates comprise that project staff has to
adapt for quicker software development (Alshamrani and Bahattab 2015).
ii. The team performs based on the response speed of the user feedback. If the
user gets confused, then the whole project will get paused.
As per the current growth in the industry and the exhaustive competition for getting better
hold in the market, the organizations do not get a lot of time to implement something every
time they want to change organization structure. The organization may want to implement a
subsystem in any of the department or an application for short time purpose. For these kind of
implementation minimum time of provided to the development team. The RAD or rapid
action development approach becomes the most suitable solution. The RAD model is best
suited for the development where end users are known and can be asked to participate in the
development project. Taken as an example, the staff of a particular department can take part
in the project by sharing the review against the developed prototypes. The waterfall model
can be thought of an alternative to RAD model but die to short time allocated to the project
the project team does not get enough time to gather and verify requirements. That is why the
dynamic projects are completed using the RAD models. Organizations often use the LEAN
development approach as an alternative of RAD. The reason is that LEAN is less costly.
However, the quality of the project gets lower due to utilization of the LEAN model.
Different projects are based on different situation, requirements and business needs.
Table 1: A Comparison of SDLC models
Characteristics RAD Spiral Incremental Waterfall
Requirement Time boxed
release
Beginning Beginning Beginning
Planning Not require Yes Yes Yes
Documentation Not necessary Yes Yes Yes
Handle large
project
Not necessary Yes Not necessary Not necessary
User
involvement
At beginning
only
High Intermediate At beginning
only
Returning to
early phase
Yes Yes Yes No
3