Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Appendix A: Analysis Mechanisms

Peter Eeles, Senior IT Architect, IBM, Software Group
Author Photo

Peter Eeles has over 15 years experience developing software solutions, and has spent the majority of this time architecting and implementing large-scale distributed systems, culminating in the writing of his first book entitled Building Business Objects (John Wiley and Sons). Peter works as a Process Consultant for IBM Rational (UK), and is the Rational Architecture Practice representative for Northern Europe. In his spare time, Peter enjoys bike racing and playing jazz guitar, although not at the same time.

Summary:  from The Rational Edge: Appendix A for the article "Capturing Architectural Requirements," at http://www-128.ibm.com/developerworks/rational/library/4706.html

Date:  30 Apr 2004
Level:  Introductory

Activity:  10948 views
Comments:  

From "Capturing Architectural Requirements"

Consider the following analysis mechanisms when gathering architectural requirements.

Analysis Mechanism Description
Auditing Provides audit trails of system execution.
Communication Allows distributed processes to communicate.
Debugging Provides elements to support application debugging.
Error Management Allows errors to be detected, propagated, and reported.
Event Management Supports the use of asynchronous messages within a system.
File Management Provides services for accessing a file system.
Graphics Supports user interface services, such as 3D rendering.
Information Exchange Supports data format conversion.
Licensing Provides services for acquiring, installing, tracking, and monitoring license usage.
Localization Provides facilities for supporting multiple human languages.
Mail Services that allow applications to send and receive mail.
Mega-data Support for handling large amounts of data in a client-server environment.
Memory Management Services for abstracting how memory is allocated and freed.
Meta-data Supports the runtime introspection of components.
Online help Provides online help capability.
Persistence Services to manipulate persistent data.
Printing Provides facilities for printing.
Process Management Provides support for the management of processes and threads.
Reporting Provides reporting facilities.
Resource Management Provides support for the management of expensive resources, such as database connections. Provides support for the management of expensive resources, such as database connections.
Scheduling Provides scheduling capability.
Security Provides services to protect access to certain resources or information.
System Management Services that facilitate management of applications in a distributed environment.
Time Services to synchronize time on a network, and to translate times into different time zones.
Transaction Management A mechanism for handling ACID 1 transactions.
Workflow Support for the movement of documents and other items of work, typically through an organization.

1 The acronym ACID refers to four characteristics of a transaction: Atomic, Consistent, Isolated and Durable.


About the author

Author Photo

Peter Eeles has over 15 years experience developing software solutions, and has spent the majority of this time architecting and implementing large-scale distributed systems, culminating in the writing of his first book entitled Building Business Objects (John Wiley and Sons). Peter works as a Process Consultant for IBM Rational (UK), and is the Rational Architecture Practice representative for Northern Europe. In his spare time, Peter enjoys bike racing and playing jazz guitar, although not at the same time.

Report abuse help

Report abuse

Thank you. This entry has been flagged for moderator attention.


Report abuse help

Report abuse

Report abuse submission failed. Please try again later.


developerWorks: Sign in


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


Rate this article

Comments

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational
ArticleID=87671
ArticleTitle=Appendix A: Analysis Mechanisms
publish-date=04302004
author1-email=dwinfo@us.ibm.com
author1-email-cc=

Table of contents

IBM SmartCloud trial. No charge.

IBM PureSystems on a kaleideoscope background

Unleash the power of hybrid cloud computing today!


Special offers