Home » Archives

Content tagged with: modeling

[21 Feb 2014 | Comments Off on Techne: New Requirements Modeling Languages | ]

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.

[7 Jan 2014 | Comments Off on Understanding System Analysis Models | ]

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.

[11 Dec 2013 | Comments Off on Find Missing Requirements | ]

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

[6 Jun 2013 | Comments Off on Modeling with SoaML: Service identification | ]

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.

[15 May 2013 | Comments Off on Using UML or IDEF for Business Modeling | ]

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.

[27 Sep 2012 | Comments Off on Data Modeling in Cassandra | ]

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.

[14 Mar 2012 | Comments Off on Entity Relationship Modeling | ]

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.

[12 Mar 2012 | Comments Off on Visual Models for Software Requirements | ]

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.

[30 Jan 2012 | Comments Off on An Agile Method for Model-Driven Requirements Engineering | ]

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 …

[9 Jan 2012 | Comments Off on Database Modeling and Use Cases | ]

This discussion on the topic of Database Modeling with Dr. Michael Blaha try to answer the question “How good are UML use cases for Database Design“? His opinion is that use cases are rote work. The developer listens to business experts and slavishly write what they hear with little interpretation and no abstraction. There is little reconciliation of conflicting use cases. In a database project, the conceptual data model is a much more important software engineering contribution than UML use cases.