Workflow Analysis and Management Report - Business Processes Analysis

This report delves into the critical aspects of workflow analysis and management, focusing on Joint Application Development (JAD), Joint Requirements Planning (JRP), and Rapid Application Development (RAD). It explores how JAD facilitates system design through interaction between designers and users, emphasizing structured workshops for requirement gathering. The report also examines Joint Requirements Planning (JRP) as a structured group meeting technique for defining requirements, problem analysis, and promoting project ownership. Furthermore, it discusses Joint Application Requirements (JAR) and Rapid Application Development (RAD) as methodologies. RAD, in particular, is highlighted for its user-centric approach, time-boxed developments, and iterative nature, which makes it suitable for quickly developing software driven by user interface requirements. The report includes an overview of the phases of RAD such as business modeling, data modeling, process modeling, application generation, turnover, and testing. Finally, the report cites relevant academic references to support its analysis.

Workflow Analysis and
Management
Student’s Name:
Student’s ID:
Subject:

1
Table of Contents
Joint Application Development.......................................................................................................2
Joint Requirements Planning...........................................................................................................2
Joint Application Requirements......................................................................................................2
Rapid Application Development.....................................................................................................3
References........................................................................................................................................4

2
Joint Application Development
A development approach system that can be used to design a system based on computer and is
useful to any process of development is referred to as Joint Application Development (JAD).
JAD involves constant interaction with various designers and users of the development system.
The main emphasis of JAD is to bring the business community and IT together in a setting of
structured workshops for extracting requirements on the consensus-based system.
The topic Process Discovery is a set of techniques which automatically or manually constructs a
representation of current business procedures of an organization and its key variations (De
Smedt, De Weerdt and Vanthienen, 2015). JAD is relevant to the topic since it is an important
aspect of iterative development and is used as a technique to develop requirements for the
business processes.
Joint Requirements Planning
A process where highly structured group meetings are conducted to define requirements and
analyze problems is known as Joint Requirements Planning (JRP). It is a subset of a complete
JAD technique which encompasses the whole system’s development process. JRP has the
advantage to save time as they involve bringing system builders, designers, users, analysts, and
owners together for analyzing, defining and identifying problems within a framework of JAD
(Junus and Andula, 2018).
JRP is relevant to the topic of process discovery as it includes administration and users in the
development project and inspires them to take the project's ownership. Moreover, the time
necessary for developing systems is reduced by JRP and the benefits of prototyping are
recognized, as prototyping is incorporated by JRP to confirm requirements and obtain design
approvals.
Joint Application Requirements
The technique used by practitioners to develop requirements of the business system is known as
Joint Application Requirements (JAR). It comprises of workshops that are designed for getting
users and system developers regarding different views and upbringing them all together in an
innovative and productive environment. The process of JAR results in designing set and
application requirements that encompasses the process, technical and business needs of the client

3
(Hyseni and Dika, 2016). From the JAR sessions, the clients will be benefitted as stronger
commitment, acceptance and ownership to the new systems will be developed.
JAR is relevant to the topic as it is a useful technique to build commitment of user to the success
of application systems by their active participation in analyzing the specification and
requirements of the system design.
Rapid Application Development
A type of methodology of agile software development which focuses on user feedback and
working software over requirements, recording and strict planning is known as Rapid
Application Development (RAD). It is suited for developing software which is driven by
requirements of user interface ((Vijayasarathy and Butler, 2016). The developments are time-
boxed, distributed and accumulated into a working protocol. Five phases of RAD are modeling
of business, modeling of data, modeling of the process, generation of application, turnover, and
testing.
This item is chosen as it proved to work much better than other methodologies and it develops a
big project into smaller parts which can help in the formation of specialized teams. Creation of
small wins can create motivation among the team while achieving tough goals.

4
References
De Smedt, J., De Weerdt, J. and Vanthienen, J., 2015. Fusion miner: Process discovery for
mixed-paradigm models. Decision Support Systems, 77, pp.123-136.
Hyseni, L.N., and Dika, Z., 2016. Integrated Approach to Conceptual Modeling. International
Journal of Advanced Computer Science and Applications, 7(12), pp.213-219.
Junus, F.B. and Andula, N., 2018. A Preliminary Study Strategy on Development of
Personalized Education Tool Using Joint Requirement Planning Technique. Journal of
Educational Science and Technology (EST), 1(1), pp.209-218.
Vijayasarathy, L.R. and Butler, C.W., 2016. Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE Software, 33(5), pp.86-94.