Book Image

Rapid Application Development with OutSystems

By : Ricardo Pereira
Book Image

Rapid Application Development with OutSystems

By: Ricardo Pereira

Overview of this book

OutSystems is a software development platform that speeds up the build phase by abstracting code and making almost everything visual. This means replacing textual language with visual artifacts that avoid lexical errors and speed up code composition using accelerators and predefined templates. The book begins by walking you through the fundamentals of the technology, along with a general overview of end-to-end web and mobile software development. You'll learn how to configure your personal area in the cloud and use the OutSystems IDE to connect with it. The book then shows you how to build a web application based on the best architectural and developmental practices in the market, and takes the same approach for the mobile paradigm. As you advance, you'll find out how to develop the same application, and the great potential of reusing code from one paradigm in another and the symbiosis between them is showcased.The only application that'll differ from the application in the exercise is the one used in business process technology (BPT), with a focus on a common market use case. By the end of this OutSystems book, you'll be able to develop enterprise-level applications on the web and mobile, integrating them with third parties and other systems on the market. You'll also understand the concepts of performance, security, and software construction and be able to apply them effectively.
Table of Contents (21 chapters)
1
Section 1: OutSystems 101
5
Section 2: The Magical Path of the Backend
10
Section 3: Create Value and Innovate with the Frontend
16
Section 4: Extensibility and Complexity of the OutSystems Platform

The architecture design process

Designing an architecture is a process that must include the following three important steps:

  1. Disclose: Find out the business concepts of the project and what kind of integrations they need. We must consider the functional and non-functional requirements of the business concepts.
  2. Organize: Organize and distribute the concepts across the Architecture Canvas layers.
  3. Assemble: Organize and match these concepts with recommended patterns. We must bear in mind that we must join concepts if they are conceptually related and we must separate them if they have different life cycles and/or are too complex.

At the end of these three steps comes one of the most important phases: iteration. We must iterate this cycle of steps as many times as necessary until we have a solid, understandable, and scalable architecture. Furthermore, we must bear in mind that an architecture is not immutable and we may have to repeat this process even during other...