Filter by products, topics, and types of content

(98 Products)

(181 Topics)

(10 Industries)

(8 Types)

1 - 6 of 6 results
Show Summaries | Hide Summaries
View Results
Title none Type none Date none
The operational context diagram
For many years, application architects and analysts have used the system context diagram (SCD) as a powerful tool to share the high-level view of a system. The SCD provides only a functional view of the system, a view that later leads to the use case model. To completely specify the system under development, non-functional requirements must be taken into account. NFRs create another view of the system context: the operational context diagram, which then segues to the operational model. In this article, learn about a technique to complement the SCD with a non-functional oriented operational context diagram.
Articles 17 Feb 2009
Representing nonfunctional aspects using TOGAF ArchiMate
The Open Group Architecture Framework (TOGAF) and its modeling language, ArchiMate, are increasingly popular techniques for documenting and evolving the architecture of an enterprise. Several tools, including Rational System Architect support them. However, ArchiMate lacks the elements needed to describe the nonfunctional aspects of the enterprise, thereby limiting the usefulness of the resulting enterprise architecture in environments, such as cloud, where service levels are primary business requirements. This article shows how to extend the ArchiMate metamodel to build a nonfunctional model extension that goes from business to technical architecture. A simple customization is also provided to download, so that you can use the new metamodel extension in Rational System Architect.
Also available in: Chinese  
Articles 24 Apr 2012
Manage operational requirements for production: Part 1. Four steps to ensure that dev and ops teams agree on nonfunctional requirements
Software requirements are too often automatically identified with user requirements, such as functions related to use cases or performance levels. However, there are other requirements that are often sources of serious problems for production systems, such as number of connections to the database, memory allocation, or coexistence with other, even unrelated, systems. In this two-part article, we show how IBM Rational Requirements Composer enables the collaboration between the Development and the Operation departments to model and track requirements related to the runtime execution of the application and how IBM Rational Quality Manager can be added later to prepare and track the preproduction tests.
Also available in: Chinese   Russian  
Articles 01 Mar 2011
Enterprise architecture in the age of cloud services
This article shows how to use an enterprise architecture to specify requirements for public cloud service, using a hybrid software as a service (SaaS) example. Enterprise architecture (EA) is a key tool to help cloud customers understand how to take advantage of the new business model that is enabled by the technology and how to fit external services into their current applications and technical environments. In reading this article, an IT architect will learn how to use EA notations and IBM Rational System Architect to communicate effectively with business users and other stakeholders, including the service provider.
Also available in: Chinese   Japanese   Portuguese  
Articles 25 Sep 2012
Manage operational requirements for production: Part 2. Build test cases for pre-production testing
In this second article of our series, we examine the effects of non-functional requirements that occur simultaneously to identify the stress cases for a system. Further, we show how Rational Quality Manager can greatly improve this process by establishing and tracking relationships among requirements, test environments, and test cases.
Also available in: Russian  
Articles 20 Sep 2011
Analyze requirements for complex software systems in a new, holistic way
This article describes a method for systematically analyzing requirements of an IT system so you can create a component model that addresses the requirements in a holistic way. Explore sample requirements with uses cases and "stress cases" to identify potential conflicts between functional and non-functional requirements. Stress cases must be addressed by defining an optimum solution that resolves the conflict. Learn how functional and non-functional requirements are opposing forces that are handled similarly to forces in civil engineering structures.
Articles 17 Feb 2009
1 - 6 of 6 results
Show Summaries | Hide Summaries