Adaptation of the UML to Formalized Software Development Process Assessment and Modeling- Dedicated Metamodel and Case Study

2011 ◽  
pp. 95-112
Author(s):  
Stefan Dietze
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Process Modeling ◽  
Business Processes ◽  
Process Assessment ◽  
Development Processes ◽  
Definition Of ◽  
Process Elements ◽  
Uml Metamodel

This chapter introduces a conceptual metamodel which enables the assessment and semi-formal modeling of business processes in the domain of software engineering based on the UML metamodel. In addition to the definition of an appropriate process modeling method, a basis for performing empirical case stud-ies and structured process assessments is provided by defining and structuring the relevant process entities (artifacts, roles, tools), and process elements and their in-terdependencies on the metamodel level. Above all, some example models are presented which were developed by applying the introduced metamodel during an initial case study. The described metamodel allows the opportunity to create de-tailed organizational UML-based models which describe the relevant roles, work-flows, artifacts as well as the used tools and their interdependencies. Thus, it can facilitate a founded assessment, evaluation and re-engineering of organizational software development processes.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

A Method for Eliciting Goals for Business Process Models based on Non-Functional Requirements Catalogues

2013 ◽  
pp. 226-244 ◽  
Author(s):  
Evellin Cardoso ◽  
João Paulo A. Almeida ◽  
Renata S. S. Guizzardi ◽  
Giancarlo Guizzardi
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Process Modeling ◽  
Process Models ◽  
Functional Requirements ◽  
Business Process Models ◽  
Traditional Approaches ◽  
Goal Models

While traditional approaches in business process modeling tend to focus on “how” the business processes are performed (adopting a behavioral description in which business processes are described in terms of procedural aspects), in goal-oriented business process modeling, the proposals strive to extend traditional business process methodologies by providing a dimension of intentionality to business processes. One of the key difficulties in enabling one to model goal-oriented processes concerns the identification or elicitation of goals. This paper reports on a case study conducted in a Brazilian hospital, which obtained several goal models represented in i*/Tropos, each of which correspond to a business process also modeled in the scope of the study. NFR catalogues were helpful in goal elicitation, uncovering goals that did not come up during previous interviews prior to these catalogues’ use.

Developing and Maintaining Knowledge Management Systems for Dynamic, Complex Domains

2011 ◽  
pp. 203-229 ◽  
Author(s):  
Lisa J. Burnell ◽  
John W. Priest ◽  
John R. Durrett
Keyword(s):  
Knowledge Management ◽  
Business Processes ◽  
Systems Development ◽  
Management Systems ◽  
Knowledge Management Systems ◽  
Agent Architectures ◽  
Knowledge Resources ◽  
Knowledge Based ◽  
Development Processes

An effective knowledge-based organization is one that correctly captures, shares, applies and maintains its knowledge resources to achieve its goals. Knowledge Management Systems (KMS) enable such resources and business processes to be automated and are especially important for environments with dynamic and complex domains. This chapter discusses the appropriate tools, methods, architectural issues and development processes for KMS, including the application of Organizational Theory, knowledge-representation methods and agent architectures. Details for systems development of KMS are provided and illustrated with a case study from the domain of university advising.

Developing and Maintaining Knowledge Management Systems for Dynamic, Complex Domains

2011 ◽  
pp. 571-592
Author(s):  
Lisa J. Burnell ◽  
John W. Priest ◽  
John R. Durrett
Keyword(s):  
Knowledge Management ◽  
Business Processes ◽  
Systems Development ◽  
Management Systems ◽  
Knowledge Management Systems ◽  
Agent Architectures ◽  
Knowledge Resources ◽  
Knowledge Based ◽  
Development Processes

An effective knowledge-based organization is one that correctly captures, shares, applies and maintains its knowledge resources to achieve its goals. Knowledge Management Systems (KMS) enable such resources and business processes to be automated and are especially important for environments with dynamic and complex domains. This chapter discusses the appropriate tools, methods, architectural issues and development processes for KMS, including the application of Organizational Theory, knowledge-representation methods and agent architectures. Details for systems development of KMS are provided and illustrated with a case study from the domain of university advising.

A Tagging Approach to Extract Security Requirements in Non-Traditional Software Development Processes

2014 ◽  
Vol 5 (4) ◽  
pp. 31-47 ◽  
Author(s):  
Annette Tetmeyer ◽  
Daniel Hein ◽  
Hossein Saiedian
Keyword(s):  
Software Development ◽  
Software Security ◽  
Security Requirements ◽  
Software Systems ◽  
Small Organizations ◽  
Pos Tagging ◽  
Part Of Speech ◽  
Security Requirements Engineering ◽  
Development Processes

While software security has become an expectation, stakeholders often have difficulty expressing such expectations. Elaborate (and expensive) frameworks to identify, analyze, validate and incorporate security requirements for large software systems (and organizations) have been proposed, however, small organizations working within short development lifecycles and minimal resources cannot justify such frameworks and often need a light and practical approach to security requirements engineering that can be easily integrated into their existing development processes. This work presents an approach for eliciting, analyzing, prioritizing and developing security requirements which can be integrated into existing software development lifecycles for small organizations. The approach is based on identifying candidate security goals using part of speech (POS) tagging, categorizing security goals based on canonical security definitions, and understanding the stakeholder goals to develop preliminary security requirements and to prioritize them. It uses a case study to validate the feasibility and effectiveness of the proposed approach.

Lean, Light, Adaptive, Agile and Appropriate Software Development

2003 ◽  
pp. 42-52
Author(s):  
John Mendonca ◽  
Jeff Brewer
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Failure Rate ◽  
Environmental Context ◽  
High Failure Rate ◽  
Adaptive Approach ◽  
Definition Of ◽  
Oriented Approach

Historically, the approach to software engineering has been based on a search for an optimal (ideal) methodology — that is, the identification and application of a set of processes, methods and tools that can consistently and predictably lead to software development success. This chapter presents the basis for pursuing a more flexible and adaptive approach to methodology. Less methodical methodologies, under a variety of names, take a contingency-oriented approach. Because of the limitations in the nature of methodology, the high failure rate in software development, the need to develop methodology within an environmental context and the pressures of fast-paced “e-development,” the authors argue that further exploration and definition of an adaptive, contingency-based approach to methodology is justified.

scholarly journals The quest for organizational flexibility

2016 ◽  
Vol 22 (4) ◽  
pp. 763-790 ◽  
Author(s):  
Monica Anastassiu ◽  
Flavia Maria Santoro ◽  
Jan Recker ◽  
Michael Rosemann
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Design Methodology ◽  
Business Processes ◽  
Contextual Information ◽  
Decision Makers ◽  
Informational Support ◽  
Content Type ◽  
The Social

Purpose – The purpose of this paper is to propose a method for identifying business process-relevant contextual information that is likely to impact on the process goal. The ORGANON method describes a semi-structured procedural guide alongside with a set of criteria and a matrix for analyzing ontological transactions, which can be used to identify which context information can be considered relevant to a business process. Design/methodology/approach – The authors report on an evaluation of the ORGANON method through a case study conducted in an organization that works in the social security domain. Findings – The results provide evidences of the feasibility of the method application in this scenario. Originality/value – Our research contributes to the literature on business processes flexibility, specifically through a proposal for context identification that can be extended to current techniques for business process modeling and in turn forms the basis for existing approaches for making business processes more flexible. The work has implications for the strategic management of organizations, by suggesting a method that provides informational support to decision makers about when, where and why business processes need to be adapted.

A business process modeling‐based approach to investigate complex processes

2012 ◽  
Vol 18 (1) ◽  
pp. 122-137 ◽  
Author(s):  
Faisal A. Abu Rub ◽  
Ayman A. Issa
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Process Modeling ◽  
New Techniques ◽  
New Approach ◽  
Content Type ◽  
Complex Processes ◽  
Model Complex

PurposeThe purpose of this paper is to develop a new approach to investigate complex processes, such as software development processes, using business process modeling.Design/methodology/approachThe paper presents an investigation into the use of role activity diagramming (RAD) to model complex processes in the software industry sector, with reference to the process of TestWarehouse as a case study.FindingsSystematic extension and quantitative analysis to RAD models led to the discovery of process bottlenecks, identification of cross functional boundary problems, and focused discussion about automation of processes.Research limitations/implicationsFurther work is required to validate and evaluate the proposed approach using several cases with different application domains and thus generalize the adopted approach.Practical implicationsA new approach has been used successfully to understand and analyze business processes. The tools and techniques that are used to perform the approach are not complicated and do not need much specialist expertise, so the approach is not only oriented toward specialists but also toward organizations' managers and staff.Originality/valueNew techniques have been developed by using process modelling to deepen the understanding and analyzing of complex organizational processes. This research implements a practical investigation which uses a case study to validate the new techniques.

Sign in / Sign up

Export Citation Format

Share Document