Large systems architecture was developed as a way to handle systems too large for one person to conceive of, let alone design. Ensuring that all architectural products and products with architectural input are maintained in the most current state and never allowed to seriously lag or become obsolete.Generating products such as sketches, models, an early user guide, and prototypes to keep the users and the engineers constantly up to date and in agreement on the system to be provided as it is evolving.Generating a set of acceptance test requirements, together with the designers, test engineers, and the users, which determine that all of the high-level requirements have been met, especially for the computer-human-interface.Ensuring that a maximally robust and extensible design is developed.Interfacing with the design and implementation engineers and architects, so that any problems arising during design or implementation can be resolved in accordance with the fundamental design concepts, and users' needs and constraints.Partitioning large systems into (successive layers of) subsystems and components each of which can be handled by a single engineer or team of engineers or subordinate architect.Developing partitioning algorithms (and other processes) to allocate all present and foreseeable requirements into discrete partitions such that a minimum of communications is needed among partitions, and between the users and the system.Performing cost–benefit analyses to determine whether requirements are best met by manual, software, or hardware functions making maximum use of commercial off-the-shelf or already developed components.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |