System Development Methodologies: STRADIS, DSDM, and Selection

This report provides a comprehensive analysis of two system development methodologies: STRADIS and DSDM, within the context of a small manufacturing company aiming to reengineer its e-business system. The report begins with an introduction to system development methodologies, emphasizing their importance in structured planning and control. It then delves into a detailed examination of the STRADIS methodology, including its background, chronological tasks, and application in a case study. The report further explores the DSDM methodology, although the provided text does not include details on DSDM. A comparative analysis is conducted to justify the final selection of an appropriate methodology for the company's needs. Finally, the report includes individual and group reflective reports, offering insights into the project's process and outcomes. The report covers essential aspects such as feasibility studies, requirement specifications, and logical system design, providing a structured approach to understanding and implementing system development methodologies.

REPORT PROJECT 2

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
MAIN BODY..................................................................................................................................1
Section 1: STRADIS....................................................................................................................1
Section 2: DSDM.........................................................................................................................9
Section 3: Final selection-.........................................................................................................15
Section 4: Group Reflective report............................................................................................16
Section 5: Individual Reflective report......................................................................................17
CONCLUSION..............................................................................................................................17
REREFENCES..............................................................................................................................19

INTRODUCTION
System development is based on the process by using framework which is used for
structured planning and controlling of process development of an information system. There are
various kinds of difficulties that are encountered by developers whenever they are developing or
building an information system. It is extremely important for the developers to adopt a system
development methodology so that development of information system can be done in an easy
and effective manner (Smidstrup and et. al., 2019). Adaptation of an effective methodology also
led towards innovative methods in order to bring improvement within information system.
Adaptation of an effective methodological approach helps in completing development of a
system against all kinds of physical and human time constraints including time and cost
constraints.
System development methodologies can also be defined as a step by step process which
is majorly used to form, control, plan development process of information system as it is quite
impossible to drive the project forwards without prior completed work. There are various kinds
of system development methodologies that can be used for development of system development
methodologies. Some of the most commonly used system development methodologies used
within organizations are: STRADIS, SSADM, JSD, SSM, DSDM and many more (Viljoen,
2016). Each of these methodologies has its own processes, advantages and disadvantages and are
used as per the needs and requirements of the project. This report will focus upon a case study of
a small manufacturing company and the company wants to retain the business process
knowledge embedded in its applications in the same time they are embedding those systems with
the new applications (Fahmideh, Sharifi and Haghighi, 2020). For this they want to follow re-
engineering approach to develop the new e-business system. This report will also focus upon
STARDIS methodology, DSDM methodology, final selection of appropriate methodology and
reason because of which a particular methodology is being chosen, as well as individual and
group reflective report.
MAIN BODY
Section 1: STRADIS
Background of the methodology
STRADIS methodology is also known as Structured Analysis, Design and
Implementation of Information Systems methodology. This methodology was originally
1

developed in 1979 by Trish Sarson and Chris Gane (Macheque, 2019). This methodology is
being mostly used by developers as it has already been convinced that this methodology can be
used, is suitable and applicable to development of all kinds of information systems. This
methodology is completely based upon structured- process modelling in which all kinds of
complex problems ae divided into formal and detailed manner. It is a kind of step by step
methodology which is based upon structured approach on data or information because of this,
this methodology works in a much better manner in a context where there is an evident need and
requirement of prioritization, defined project size, restricted deadline and many more.
This methodology is mostly used in which projects in which least part of information
system is automated. But there is one restriction i.e. this system development methodology is
majorly used within system development process in which emphasis is more on the data. This
methodology was developed in an era in which major focus was laid upon development of
computer- based applications by planning whole process in a step by step process. Similar is the
case with this methodology (Steinke, Al-Deen and LaBrie, 2018). Each and every- thing is done
in a sequential manner or process. This methodology is based upon functional decomposition in
which all kinds of problems are broken down into small manageable units in a disciplined
manner. This methodology also focused upon inter- association and selection of interfaces and
components that can be deciphered within a specific problem (Fahmideh, Sharifi and Haghighi,
2020). But there are requirements of this methodology such as: objective of the project must be
clear and concise and all the needs should be defined since the beginning of the project. The
project must be data oriented as this methodology is largely oriented towards problem solving.
This methodology is based upon top down approach and uses data flow diagram in many
cases. This whole methodology consists of four major steps, that are: initial study, detailed study,
defining and designing of alternative solutions and physical design. Initial study stage focuses
upon ensuring that the system chosen which is required to be developed is developed in a
competing environment (Steinke, Al-Deen and LaBrie, 2018). Monitory benefits and cost of
each proposal are argued in a clear and concise manner. At detailed study stage work initial
study is taken further by examining details of existing system. This is majorly done by using
interview process in which interview of users is done and on the basis of it DFD is made. At
defining and designing of alternative solutions stage alternative solution to the problem is
defined on the basis of existing system and then it is designed (Fahmideh, Sharifi and Haghighi,
2

2020). Lastly, at physical design stage three parallel activities are involved, in which production
of detailed DFD is done, designing of database is done in a logical manner. With the help of all
the four processes problems of system development can be resolved easily and appropriate
solution for it can be identified (Kashevnik and et. al., 2017). With the help of top down
approach whole system is divided into sub system and is graphically represented using some
diagrams especially data flow diagram. These diagrams and graphical representation help in
providing an overview and outline of the system which is required to be developed or is going to
be developed. While using this methodology it is extremely important to carefully document
whole problem analysis so that existing solutions and possibilities can be analysed in a proper
and effective manner and project can be completed within defined timeline and constraints.
Chronological sequence the tasks/processes that are likely to occur in each phase of the
methodology
In above analysis, it has been discussed about STRADIS methodology is also known as
Structured Analysis, Design and Implementation of Information Systems methodology. Based on
the given case study, it has concerned about the new system design or development. The
organization has been able to meet up its current goal and objective. Initially, it always faced
challenging issue due to rapid market growth. It became difficult to find itself in critical situation
due to competitors (Steinke, Al-Deen and LaBrie, 2018). Therefore, organization has been
decided to develop new system through STRADIS methodology that meet enterprises
requirement. Also, it can be identified the various stages such as feasibility study, requirement
specification, functional model design, build iteration and implementation. There are various
activities that should be conducted in order to get out the better result or outcome.
Feasibility study
It is initial step when proposed the methodology that contain a feasibility which
providing the valuable opportunity to identify whether proposed project should be acceptable by
company. In this phase, it is mainly include two areas to be identified, which are enterprise and
technical perspectives that investigate the solution potential time frame, price or cost (Steinke,
Al-Deen and LaBrie, 2018). At this phase, feasibility is an essential require before preparing the
project. It can be defined the project problem by highlighting the consumer’s requirements.
Through feasibility study, it can be find out the problem and issues. Afterwards, it is collecting
the important information that should prepare a final feasibility.
3

In additional, it should prepare various documentation such as ERD, data flow diagram,
context diagram and other requirement of catalog. Also, it provides the technique of project
management by using Gantt charts, network activities. in order to pass the phase of feasibility,
system development should be produced when it contain the operational feasibility, economic
and technical feasibility. For Example- As estimate the overall cost, price of new system which
includes the location of system developer where user can access time for acquisition. In context
of technical feasibility, it is simplest way to concern about the solution that can be identified by
using methodology (Steinke, Al-Deen and LaBrie, 2018). In the organization, project manager
detailed review of technical feasibility and investigate about the functionality. As a result, it can
easily calculate the solution after installation. The organization is collecting or gathering
important information related new system design and development.
Requirement analysis
It is another phase for identifying the requirements of new system development. It
consists of two stages that have different activities. Initially, it is analysing the essential need
which can be done through investigating the current environment or culture. The primary aim is
to improve the efficiency of new system to increase productivity and profitability of organization
in global marketplace (Steinke, Al-Deen and LaBrie, 2018). The analyst provide the wide range
of options that meet the define need and requirement by users. It may select one of best option on
the basis of request. It will be able to understand the requested system and provide the solution.
In this phase, it is analysing the features of system requirement that should be identified
and examined the current business environment. Sometimes, it will be modified in term of data
structure which carried out process. After producing the system logical model, DFD, LDS that
can be achieved during task management. As per case study, organization should be created the
catalogs that simply achieve different activities. In another way, it include all functional as well
as non-functional requirements.
The stage is further processed that should get the business system option which mainly
described the system based on different factors such as functionality (Fahmideh, Sharifi and
Haghighi, 2020). In order to suggest the boundaries such as input, output data and processes.
Main aim of phase is allow the team member to choose an appropriate requirements.
4

Requirement specification
In this phase, it should contain only one stage which can be defined the requirements. It is
an essential step is to enhance the work carried out during initial phase (Fahmideh, Sharifi and
Haghighi, 2020). It contains the clear identification of detailed non-functional as well as
functional. It is basically used to identify the required processing as well as data structure. For
LDS, it has been implemented to new system design or development. Also, organization should
identify the new system operation and link between the users and desired functions. Moreover,
developers, designer focus on the conceptual process, behaviour model. By doing better way that
will be able to have idea on impact on proposed system. In order to specify the design
requirement within new system development.
Logical system specification
It is another step of propose methodology that consists of two stages, which are basically
technical system as well as logical design. Project manager is responsible for identifying the
system environment such as specifying and selecting the environment development, software
configuration and implementation (Fahmideh, Sharifi and Haghighi, 2020). For logical design, it
carried out the various area during system development such as inquiry, update, processing and
proposed the system dialogues. Moreover, it also specified the primary logic of database that
automatically update detailed in the system related particular events. For instance, once existing
client record is created and all attribute is going to be empty at initial step. It might be processed
and attribute’s state will be changed. Therefore, organization will able to highlight the overall
system process implementation.
Functional model iteration
It is an important stage where project manager is responsible for building prototype of
new system, which is considered as one of iterative phases. It always assists by analyst to
identify the user’s requirement and hence calculate desirable outcome (Fahmideh, Sharifi and
Haghighi, 2020). On the basis of phase, prototype always helps in improving the quality of
system since it is based on the user’s feedback. Furthermore, developer mainly follows the main
processes which are investigate, consolidate and refines. In additional, life cycle is generally
repeated one or more times until they can achieve the functional model agreed by authority. The
final new system is generally contain functional model that consists of software components. In
order to analyse the model.
5

Design and build iteration
In this phase, it is mainly focused on the prototypes that meet users satisfactory and also
designed the best model for fulfilling the requirements of organization (Fahmideh, Sharifi and
Haghighi, 2020). Therefore, aim of this phase is to ensure that final system satisfied with quality
which is based on the functional modelling. Afterwards, it can be refined until gaining the better
satisfactory standards and parameters.
Implementation
It is the last phase which mainly considered the development life cycle. It has been
proposed the solution which placed into target operational environment where end user trained
on how new system can be used. In additional, there are various cased that can be identified
certain outcome for this stage. For instance, each and every requirements are delivered on the
basis of user’s demand whether there no further development requirement. In another way, it
may discover the new functionality that always support for business to increase demand in global
marketplace (Hidalgo, Guaiña and Gutiérrez, 2020). It can be possible when current design
model satisfied the user’s requirements. Sometimes, there are essential parts missing due to time
constraint, which mainly referred back to functional model. As per case study, organization will
able to manage the overall new system development project effectively and efficiently.
Afterwards, it can easily control the implementation phase in proper manner.
Advantages and disadvantages of the methodology
Advantage of STRADIS methodology is basically used three technique to identify the
information system. In order to utilise the logical data modelling and establish the relationship
between different entities within system. Data flow modelling determines the way in which data
changes from one place to another (Hidalgo, Guaiña and Gutiérrez, 2020). Afterwards, it will be
holding the entities that send information or data into new system. Sometimes, it also following
the route through which data flows in proper manner. Moreover, entity event modelling
document should be contained how event within enterprise affect the new system.
STRADIS methodology is considered the most efficient method for proposed an
appropriate solution which has extremely controlled the functionality of new project. it has a
standard methodology for all parts of creation process (Fahmideh, Sharifi and Haghighi, 2020). It
can be performed the different procedure for making information system work in same time.
6

STEADIS is followed the process but sometimes, it may occurs errors, bugs in execution so that
this methodology control the activities.
Another advantage is that when STRADIS consider as structured method of creating
information system. It also exercised control over every aspects of process creation. It is the
reason to STRADIS methodology for new system design or development (Hidalgo, Guaiña and
Gutiérrez, 2020). This method has become standards and easily control the errors during task
execution. However, it can be improved the difficulties while fulfilling the requirement or need
to system functionality. STRADIS has already analysis which undertaken place, recommended
by data may be generated in appropriate manner (Fahmideh, Sharifi and Haghighi, 2020). On the
other hand, STRADIS methodology compiles with large amount of data or information that is
deeply analysed. It will be performed the long process that leads to improve comprehension of
how system will come to be and also reduce the chances in data interpretation. Especially when
it perform three different process of project development. Since, STRADIS has proposed the
standard solution which easily save both money and time.
Furthermore, this methodology is mainly focused on the testing and this focus is so strong
that it is expected that there should be at least one tester within all the teams of the project and at
every iteration, test of the project is done and conducted. Design of whole project is grounded up
by staff members (Hidalgo, Guaiña and Gutiérrez, 2020). Therefore, value of the enterprise is
determined in an appropriate manner. This methodology is not only identified business value is
expected to be one of the main and highest priority which is required to be delivered. This
methodology has implemented an efficient approach with the help of which significance of each
requirements. At every stage, it consists of iteration that will be determined in a proper and
appropriate manner. As per case study, according to the identified importance of requirements
they can be fulfilled.
The biggest disadvantage/ drawback of STRADIS methodology is that when it takes
more time and possibly expensive. Sometimes, it is great deals of time when business take so
much time required to analyse the new system design project. Sometimes, it is very difficult to
create information system through desirable data. It is largely delay between inception of project
and delivery of system (Hidalgo, Guaiña and Gutiérrez, 2020). If staff members within
organization that are not well-trained in STRADIS technique. Therefore, organization will need
7

to spend more time and money on providing better training but it not easy to handle. In this way,
it consider as disadvantage of STRADIS methodology.
Assumption on the basis of case study
Based on the e-business case study, there are different areas that can be assumed which
are likely in following manner.
 The organization will not able to manage the system development project on specific
time intervals.
 It will not monitor the development in proper manner. There is no specific version to
control especially when it has occurred complex project.
 It will not provide the better understanding and get user’s requirement in clearly since, it
is lack of user involvement.
Section 2: DSDM
Background of the methodology
DSDM stands for dynamic system development method. DSDM was invented in 1994,
when project managers using another agile framework which determined new iterative approach
to software development. In 1990, the rapid application development approach was becoming the
increasing the popularity which directly enabled the developer to show their customers, users
possible solution quickly (Hidalgo, Guaiña and Gutiérrez, 2020). It became easier to build the
prototypes. However, Approach was often unstructured with no such process occurs between
team members. It led to each department building their framework and splitting standards which
making it difficult to experience.
To resolve the issue or problem so that apply DSDM technique which developing and
promoting an independent framework. DSDM has proven the framework for agile project
management and delivery which always helping to deliver the better outcome quickly manner. It
is concentrated on the strategic goals and incremental delivery of real enterprise advantage,
benefits while keeping control of cost, risk, quality and time. The agile method is enabled with
by using self-direction which establish the collaboration between team members during project
execution.
Since, 1994 DSDM has effectively applied to wide range of project from new system design
or development (Mach-Król, 2020). It is an essential thing to understand the different phases of
DSDM project which become different to analysis, design step in new system development. This
8

methodology is carried out the various activities for understanding the current situation of project
but deliberately avoid going into details.
Dynamic system development methodology is based on the methodological analysis which
mainly used through information system professionals. They are mainly focused on develop
software project which is originated from rapid application development. DSDM is mainly
described the project management, estimating, prototyping, configuration management,
prototyping time, quality testing (Kaushik and Datta, 2020). This methodology is based on the
principles that consider as one of agile project management techniques which mainly deliver the
software on time and within specific budget. As per case study, It can be applied the
methodology to improve the customer system which mainly covered the customer details. In
currently, organization will be performed the operation the basis of computerised and remaining
is still done by paper work. Afterwards, it has been proposed the system that must be
implemented with centralised database over LAN (Fahmideh, Sharifi and Haghighi, 2020). There
are different stakeholder involves project manager, facilitators, programmers and system analyst.
They were performed the various operation to achieve the business tasks by using DSDM
technique within case study.
Chronological sequence the tasks/processes that are likely to occur in each phase of the
methodology
There are different phases of DSDM methodology that mainly discussed, within each phase
DSDM lies on the multiple activities and technique based on the principles. DSMS method is
mainly consists of different phases which performed the significant role in the project
development. It involves Feasibility study, functional model iteration, business study and so on.
Feasibility study
it is all about whether proposed the method that can be applied or not. As per case study,
it is an important stage where before developing new system which require to check the
feasibility. Therefore, it help for identifying the existing problem or issue (Fahmideh, Sharifi and
Haghighi, 2020). Feasibility study has been carried out the e-business with provided which
shows. There is no software which is integrated together and produced the system that is efficient
to use.
9

Business study
It is another step where acquiring the clear understanding towards the flow of business and
how processes are related to each other. It involved for identifying the stakeholders who are
involved in the new system project. This type of stage involved in different ways.
Arranging JAD workshop: in this process, it involved the meeting with multiple stakeholder
by arranging for location as well as time. The activities including the workshop and discussing
on the requirements with managing sales manager, directors and warehouse manager of e-
business firm (Wang, Zhang and Xu, 2020). Now move to next level, when involved the activity
to analyse current need where system boundaries, sub system can easily identified by
identification to produce final result or outcome. As per give case study, the organization can be
divided into three different sub-systems. They are buying, importing stock and delivery,
marketing and selling the products in marketplace. The final activity is to produce the final
project by using suitable resources, time frame.
Produce business report: in this stage, it will be performed the activity to identify the
enterprise process and to produce DFD which mainly involved context diagram, physical as well
as logical diagram. In final, it may produce the ER model which always support for
implementing the logical design through database (Paucar-Caceres and Jerardino-Wiesenborn,
2020). Next activity is that when define the development of target platform. It consists of major
components and give more prioritise as per requirement of new system. Furthermore, the final
activity is related to the business study and outline the overall prototyping plan of new system
development.
Functional model iteration
In this phase, it is mainly works on refining high level enterprise which identified the
requirement and function of new system at the time of business study by using DSDM
methodology. There are various risk increase during system development that will be identified
and recognise through an effective plan (Iyoho and et.al., 2020). Therefore, it can easily deal
with risk for future growth and development. Functional model iteration is based on the standard
analysis for improving overall functionality of new system within organization.
Rectify enterprise aspects: in this process, it mainly involved the activities related to high
level functional and information that require to refine effectively.
10