Content tagged with: modeling
Techne is an abstract requirements modeling language that lays formal foundations for new modeling languages applicable during early phases of the requirements engineering process. During these phases, the requirements problem for the system-to-be is being structured, its candidate solutions described and compared in terms of how desirable they are to stakeholders.
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
The power of a service-oriented architecture (SOA) is in its ability to enable business agility through business process integration and reuse. SoaML (Service-Oriented Architecture Modeling Language) is an Object Management Group (OMG) standard that is intended to help realize the potential of SOA.
The Unified Modeling Language (UML) is a modeling language standardized by the Object Management Group (OMG) used to manage requirements in software development projects. IDEF, the acronym for Integration DEFinition, refers to a family of modeling languages in the field of systems and software engineering.
Aspect-orientation provides a new way of modularization by clearly separating crosscutting concerns from non-crosscutting ones. While aspect-orientation originally has emerged at the programming level, it has now stretched also to the modeling activity.
Cassandra stores data fundamentally differently than traditional RDBMS. These differences allow for vast improvements in performance, availability and scalability, but in order to achieve the gains one must understand the differences. This talk covers a Cassandra solution to a problem often believed to only be solvable in a strictly ACID compliant system. The focus of the solution is on the data model and the interactions with it to achieve scalability, availability and performance at scale.
The video lecture discusses the concepts associated with the Requirements Stage in the process of developing a database system. Specifically with the creation of the ERD or Entity Relationship Diagram based on a business case study.
Software requirements are often thought to be textual material that can take the form of free “system shall…” statements, user stories, or “give when then” of behavior driven development. This blog post explore the usage of visual models to capture software requirements. It explains that models are not requirements, but they help us find and understand requirements.
This article provides a methodological approach that focuses on requirements engineering within the Model-Driven Development (MDD) context. Our approach is an OpenUP extension in which the requirements discipline is placed in the model-driven context. We believe that the integration of requirements engineering and MDD into one consistent process will provide practitioners with the benefits of both. This paper presents the definition of the proposed process, OpenUP/MDRE, including its activities, roles, and work products. We also provide an example of its use in a SOA-based software development project. The use of …