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
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.
Comments (Undergoing maintenance)
Back to top
Trademarks | My developerWorks terms and conditions
Help: Update or add to My dW interests
What's this?
This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.
And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.
View your My developerWorks profile
Return from help
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=
