1 / 23

Ritesh Jain M. Tech. Information Architecture Software Engineering 1st Sem,

Information Architecture. Information Architecture is art of expressing a model or concept of information used in activities that required details of complex system. Information architecture has somewhat different meanings in all these different branches of information technology. Most definitions h

heman
Download Presentation

Ritesh Jain M. Tech. Information Architecture Software Engineering 1st Sem,

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    2. Information Architecture

    5. Phase C Information System Architectures

    8. Parts of Information System Architectures Data Architectures Definition Inputs Steps Outputs Application Architectures Definition Inputs Steps Outputs

    10. understandable by stakeholders and system developers must be complete and consistent with respect to business or proposed system. relevant with the Business process. Data Architectures

    11. data is not located where it is needed data not available when needed the needed data is not available data not created data not consumed

    13. Application Architectures application system necessary to process the data applications are not described as computer systems, but as logical groups of capabilities that manage the data objects in the data architecture applications support the business functions and their capabilities

    14. Application Architectures here applications are defined without reference to technologies applications are stable and relatively unchanging over time, whereas the technology used to implement them will change over time,

    16. Inputs (for Data and Application) Business Principles (if existing) Request for Architecture Work Business Vision (from Architecture vision) Relevant technical requirements Gap analysis (from Business Architecture)

    17. Inputs (for Data and Application) Target Business Architecture (from Business Architecture) Re-usable building blocks (from previous organizational System) (if available) definitions and description of current data and process

    18. Steps (for Data and Application) Data/Application Baseline Description. Principles, Reference Models, Viewpoints and Tools Architecture Models. Select Data architecture building blocks (e.g., metamodels) Identify candidate application systems.

    19. Steps (for Data and Application) Conduct a formal checkpoint review of the architecture model and building blocks with stakeholders. Review the qualitative criteria (e.g., security, availability, accuracy, performance, costs, volumes), providing as Complete the Data and Application architecture. Gap analysis

    20. Outputs (for Data and Application) Statement of Architecture Work (updated if necessary) Data / Applications Baseline Description Validated Applications Principles, or new Applications Principles Target Data Architecture (Models like Conceptual data model, Logical data model, Data Process models, Data entity / business function matrix) Target Applications Architecture (Models like Process, Place, Time, People)

    21. Outputs (for Data and Application) Applications interoperability requirements Viewpoints addressing key stakeholder concerns. Views corresponding to the selected viewpoints; Gap analysis results Data and Applications Architecture Report, summarizing what was done and the key findings of this phase Impact Analysis

    23. Thank You !

More Related