What We Evaluate
Stands Above The Rest
Each project has characteristic unpredictability since it is intended to serve at least one client class, pertinent for at least one division (work units), and includes the innate multifaceted nature of the most recent innovations.
System / Logical Models
Models showing Logical Models of Applications, Data, Network, UI, Rule, etc. Also, how does Application related to Data, Data linked to Network, Application Models relationship to UI Models, etc
Strategy Models illustrating business initiatives that lead to company Goals and Objectives, Products and Services, and the Business Processes that enable them, etc.
Implementation Models showing brand names of tools, products, etc for Physical Application, Physical Network, Storage, Server components, Security, Physical Database Design, etc.,
Stakeholders and Key Expectation
How did the project address the worries and issues of business owners, project owners, users, technology teams, process owners, operation team? How does did it impact the priorities of the project?
It is important to use performance metrics, i.e. projects goals as a basis for evaluating architecture and rating project readiness.
Process Models showing Business Processes, the Process Operational Objectives, Business Processes vs the Applications that support them etc.,
A project operating model, digital representation of how did the company provides value to its customers, and how the organization handles the project. It will have information such as Operational Data, info update, process instances, actual locations with roles, performance metrics (weekly / monthly), etc.
Well defined Taxonomy
Well-defined taxonomy for business, technology, operations to ensure effective communication, information exchange, and related models. Evaluate classification and categories related to market classes, technical components focused on common characteristics.