Software System Architecture Essay

Software System Architecture Essay

03/04/2008

      Once a business need is established, software system architecture is formulated to meet this business need.   To properly formulate the software system architecture we must employ proven strategies, such as diagrams that illustrate the parts of the system and how they work together.   These subsystems collaborate intelligently to support the functionality of the whole system.   Project managers must be aware of the system architecture involved and how to manage the parts that make up the entire system.   A good analogy for visualizing the software systems as subsystems is the manufacture of a successful bicycle line.   This particular bicycle consists of many subsystems, such as the frame assembly, wheel assembly, sprocket drive assembly, steering assembly, and the braking subsystem.   The subsystems work cohesively to form a main system of functionality as required by stakeholder specifications.   The concept of a modular design is very important in a complex system; it enables the designer to modify the system easily by adding or changing existing system components.   In addition, all subsystem specifications must be taken into account before any change can be introduced into the system.   A software system, when programmed modularly and designed to work in concert to compliment the design, is a proven system that works well.   One example of this design is protocol event handlers that stream data across networks.   In order to express this modular concept effectively to the stakeholders, a diagramming system is employed called the Unified Modeling Language (UML).   The UML is a modern standard convention that enables software designers to achieve a common, consistent view of the system.   The UML is a standard maintained by the Object Management Group (OMG).   The OMG was founded by eleven high-tech companies which endeavor to revise and enhance the standard.   “OMG’s modeling standards, including the Unified Modeling...