Business System Analysis
System analysis is such a broad term, that if you ask five systems analysts to define the term, you end up with 20 different definitions. So, we shall take the Peter Drucker approach and simply focus on two items:
This page focuses on these two questions and provides links to best business practices, current events, or other tools that enable us to understand our business and how to improve them. A good starting point is a System Definition , or in author David Ruble's term, a context diagram.
SMARTDRAW Academic License (click here) The SmartDraw Suite Edition helps you draw professional flowcharts, DFD, ERD, org charts, Gantt charts, mechanical, floor plans, calendars—any kind of business drawing, chart, or diagram.
Development Methodologies - Waterfall (SDLC), RAD, Agile/Xtremme Programming, BPR
STRATEGIC PLANNING: Benchmarking Balanced Scorecarding Boston Matrix Cliff Bowan's
ASCII = American National Standard Code for Information Interchange EBCDIC = Extended Binary Coded Decimal Interchange Code
Architecture description languages (ADLs), seek to increase the understandability and reusability of architectural designs, and enable greater degrees of analysis.
Module Interconnection Languages (MILS), only describe the structure of an implemented system.
ADLs also typically address:
•Component behavioral specification - component functionality, support for specifying both functional and non-functional (safety, security, reliability, and performance). Depending on the ADL, timing constraints, properties of component inputs and outputs, and data accuracy may all be specified.
•Component protocol specification. Some- ADLs, such as Wright and Rapide support the specification of relatively complex component communication protocols. Other ADLs, such as UniCon, allow the type of a component to be specified (e.g., filter, process, etc.) which in turn restricts the type of connector that can be used with it.
Connector specification. ADLs contain structures for specifying properties of connectors, where connectors are used to define interactions between components. In Rapide, connector specifications take the form of partially-ordered event sequences, while in Wright, connector specifications are expressed using Hoare's Communicating Sequential Processes (CSP) language
•Aesop - supports the specification and analysis of architectural styles (formal characterizations of common architectures such as pipe and filters, and client-server)
•Rapide - uses event posets to specify component interfaces and component interaction [
•Wright - supports the specification and analysis of communication protocols
•MetaH – support real-time avionics domain
•LILEAnna - for use with Ada and generalizes Ada's notion of generics
UniCon - addresses packaging and functional issues associated with components
•Garlan, David & Shaw, Mary. "An Introduction to Software Architecture," 1-39. Advances in Software Engineering and Knowledge Engineering Volume 2. New York, NY: World Scientific Press, 1993.
•Garlan, D.; Allen, R.; & Ockerbloom, J. "Exploiting Style in Architectural Design Environments." SIGSOFT Software Engineering Notes 19, 5 (December 1994): 175-188.
•Hoare, C.A.R. Communicating Sequential Processes. Englewood Cliffs, NJ: Prentice Hall International, 1985.
•Luckham, David C., et al. "Specification and Analysis of System Architecture Using Rapide." IEEE Transactions on Software Engineering 21, 6 (April 1995): 336-355
•Shaw, Mary, et al. "Abstractions for Software Architecture and Tools to Support Them." IEEE Transactions on Software Engineering 21, 6 (April 1995): 314-335
•Software Architecture Technology Guide [online]. Available WWW <URL:
•Tracz, W. "LILEANNA: a Parameterized Programming Language," 66-78. Proceedings of the Second International Workshop on Software Reuse. Lucca, Italy, March 24-26, 1993. Los Alamitos, CA: IEEE Computer Society Press, 1993.