Documenting an architecture one is building from scratch is one thing, documenting one that already exists quite another. As a software architect, one will quickly learn that designing and documenting a system from the ground up is much easier than documenting one that's already been built. Unfortunately, one will just as quickly learn that both scenarios fit under the job description. In fact, software architects are commonly called in for the worst-case scenario: the long overdue documentation of a large architecture consisting of dozens (or hundreds) of interdependent systems. A company faced with documenting such a sprawl will typically have no idea where to begin, which is, of course, where one comes in.
Related white papers
On Guard: Producing Run-Time Checks From Integrity Constraints
Software applications are inevitably concerned with data integrity, whether the data is stored in a database, files, or program memory. An integrity guard is code executed before a data update...
WebEx Builds Interactive Media Platform Using Forte Developer 6
WebEx is the leader in real-time communications infrastructure for Web meetings. WebEx built a service that could handle massive concurrent connections while maintaining exceptional response times to support live video,...
3-D Look at the IBM Software Development Platform for Linux
This webcast explains how the IBM Software Development Platform supports development teams in a Linux environment. This event covers the 3-D aspect of the IBM SDP for Linux: Discovery, Development...
An Assessment Process for Software Reuse
Each organization is unique in that they have different cultures and maturity with software processes and thus each organization should have a reuse plan specifically designed for their purposes. Therefore...
Object-Oriented Project Management
Object-orientation is a way of looking at the world as "classes" of "objects" in order to model the real world more effectively than traditional structured software engineering or other methods...
Process Reengineering and the Data Flow Diagram
In a structured design environment, DFD use proceeds in the following sequence (Yourdon, 1988): (1) hierarchical chart of system processes, (2) physical DFDs of the current system (both the Whats...
A Grounded Theory Study of Successful Organizational Integrated CASE Technology Implementation
This paper describes a research project that endeavors to answer the question are there certain characteristics of an organization that will predict whether ICASE will be successful in that organization?...


