Architectural Artifact - Explore the Science & Experts | ideXlab

Scan Science and Technology

Contact Leading Edge Experts & Companies

Architectural Artifact

The Experts below are selected from a list of 87 Experts worldwide ranked by ideXlab platform

Ricardo J. Machado – One of the best experts on this subject based on the ideXlab platform.

  • AMPLA: An Agile Process for Modeling Logical Architectures
    Advances in Systems Analysis Software Engineering and High Performance Computing, 2020
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred to as “agile architecting,” promotes the emerging and incremental design of the Architectural Artifact in a sense of avoiding “big design upfront” (BDUF). This chapter presents the Agile Modeling Process for Logical Architectures (AMPLA) method, an approach for supporting the emergence of a candidate (logical) architecture, rather than BDUF, the architecture in an early phase. The architecture then emerges throughout agile iterations, where AMPLA plays a key contribution for providing traceability between models, from the business need to service specifications, ranging from design stages to deployment, hence covering a software development life cycle (SDLC).

  • SIGSAND/PLAIS – Towards Agile Architecting: Proposing an Architectural Pathway Within an Industry 4.0 Project
    Information Systems: Research Development Applications Education, 2019
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred as “agile architecting”, promotes the emerging and incremental design of the Architectural Artifact, in a sense of avoiding “big design upfront” (BDUF). Performing “agile architecting” is not always straightforward, mainly because the architecture has a required life-cycle and each stage responds to different needs. There is a lack of a pathway that guides agile architecting in an end-to-end approach (from business requirements to deployment). This paper proposes a pathway that includes architecture design from software development life-cycle (SDLC) stages of software development that use ASD approaches, where two main Artifacts are considered: a candidate logical architecture and a refined logical architecture. These Artifacts are included in a pathway where they receive input from business processes perspective and guide software development during ASD iterations (Sprints).

  • Towards Agile Architecting: Proposing an Architectural Pathway Within an Industry 4.0 Project
    Information Systems: Research Development Applications Education, 2019
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred as “agile architecting”, promotes the emerging and incremental design of the Architectural Artifact, in a sense of avoiding “big design upfront” (BDUF). Performing “agile architecting” is not always straightforward, mainly because the architecture has a required life-cycle and each stage responds to different needs. There is a lack of a pathway that guides agile architecting in an end-to-end approach (from business requirements to deployment). This paper proposes a pathway that includes architecture design from software development life-cycle (SDLC) stages of software development that use ASD approaches, where two main Artifacts are considered: a candidate logical architecture and a refined logical architecture. These Artifacts are included in a pathway where they receive input from business processes perspective and guide software development during ASD iterations (Sprints).

Simon P. Frechette – One of the best experts on this subject based on the ideXlab platform.

  • Development Life Cycle for Semantically Coherent Data Exchange Specification
    Concurrent Engineering, 2008
    Co-Authors: Boonserm Kulvatunyou, Katherine C. Morris, Nenad Ivezic, Simon P. Frechette

    Abstract:

    In enterprise integration, a data-exchange specification is an Architectural Artifact that evolves along with the business. Maintaining a coherent, data-exchange, semantic model is an important, yet nontrivial task. A coherent, semantic model of data — exchange specifications supports reuse, promotes interoperability, and, consequently, reduces integration costs. Components of data-exchange specifications must be consistent and valid in terms of agreed upon standards and guidelines. In this article, we propose an activity model for the creation, test, and maintenance of a shared semantic model that is coherent and supports scalable standards-based enterprise integration. While it frames our research and the development of tools to support those activities for semantic models implemented using XML (Extensible Markup Language) Schema, the activity model presented in this article is independent of the data-exchange technology.

  • DEVELOPMENT LIFE CYCLE AND TOOLS FOR DATA EXCHANGE SPECIFICATION
    Volume 3: 28th Computers and Information in Engineering Conference Parts A and B, 2008
    Co-Authors: Katherine C. Morris, Puja Goyal, Simon P. Frechette

    Abstract:

    In enterprise integration, a data exchange specification is an Architectural Artifact that evolves along with the business. Developing and maintaining a coherent semantic model for data exchange is an important, yet non-trivial, task. A coherent semantic model of data exchange specifications supports reuse, promotes interoperability, and, consequently, reduces integration costs. Components of data exchange specifications must be consistent and valid in terms of agreed upon standards and guidelines. In this paper, we describe an activity model and NIST developed tools for the creation, test, and maintenance of a shared semantic model that is coherent and supports scalable, standards-based enterprise integration. The activity model frames our research and helps define tools to support the development of data exchange specification implemented using XML (Extensible Markup Language) Schema.

Nuno Santos – One of the best experts on this subject based on the ideXlab platform.

  • AMPLA: An Agile Process for Modeling Logical Architectures
    Advances in Systems Analysis Software Engineering and High Performance Computing, 2020
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred to as “agile architecting,” promotes the emerging and incremental design of the Architectural Artifact in a sense of avoiding “big design upfront” (BDUF). This chapter presents the Agile Modeling Process for Logical Architectures (AMPLA) method, an approach for supporting the emergence of a candidate (logical) architecture, rather than BDUF, the architecture in an early phase. The architecture then emerges throughout agile iterations, where AMPLA plays a key contribution for providing traceability between models, from the business need to service specifications, ranging from design stages to deployment, hence covering a software development life cycle (SDLC).

  • SIGSAND/PLAIS – Towards Agile Architecting: Proposing an Architectural Pathway Within an Industry 4.0 Project
    Information Systems: Research Development Applications Education, 2019
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred as “agile architecting”, promotes the emerging and incremental design of the Architectural Artifact, in a sense of avoiding “big design upfront” (BDUF). Performing “agile architecting” is not always straightforward, mainly because the architecture has a required life-cycle and each stage responds to different needs. There is a lack of a pathway that guides agile architecting in an end-to-end approach (from business requirements to deployment). This paper proposes a pathway that includes architecture design from software development life-cycle (SDLC) stages of software development that use ASD approaches, where two main Artifacts are considered: a candidate logical architecture and a refined logical architecture. These Artifacts are included in a pathway where they receive input from business processes perspective and guide software development during ASD iterations (Sprints).

  • Towards Agile Architecting: Proposing an Architectural Pathway Within an Industry 4.0 Project
    Information Systems: Research Development Applications Education, 2019
    Co-Authors: Nuno Santos, Nuno Ferreira, Ricardo J. Machado

    Abstract:

    Software architecture design, when performed in context of agile software development (ASD), sometimes referred as “agile architecting”, promotes the emerging and incremental design of the Architectural Artifact, in a sense of avoiding “big design upfront” (BDUF). Performing “agile architecting” is not always straightforward, mainly because the architecture has a required life-cycle and each stage responds to different needs. There is a lack of a pathway that guides agile architecting in an end-to-end approach (from business requirements to deployment). This paper proposes a pathway that includes architecture design from software development life-cycle (SDLC) stages of software development that use ASD approaches, where two main Artifacts are considered: a candidate logical architecture and a refined logical architecture. These Artifacts are included in a pathway where they receive input from business processes perspective and guide software development during ASD iterations (Sprints).