Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 9: Application Architecture

Software Architecture vs Application Architecture:

While both terms are related to designing software systems, "software architecture" refers to the high-level design of an entire system, encompassing its components, interactions, and overall structure, while "application architecture" focuses specifically on the structure and design of a single application within that system, defining how its various components interact to achieve desired functionality; essentially, application architecture is a subset of software architecture concerned with the details of a particular application.

Example:

Enterprise architecture example:

Enterprise architecture create overall architecture of a e-commence platform which includes Hardware, RDBS, Cloud, Networking etc. 

Software architecture example:

Choosing a microservices architecture for an entire e-commerce platform, where different services (user management, product catalog, payment processing) are loosely coupled and can be independently developed and scaled. 

Application architecture example:

Designing the user interface, backend logic, and database interactions for the "cart" feature within that e-commerce platform.

Application architecture involves:

  • Allows agility, reliability, and scalability
  • It ensures an organisation can implement change effectively and swiftly.
  • Simplify complicated applications by decomposing them into two or more applications.
  • Identify logical applications and the most appropriate physical applications.
  • Develop matrices across the architecture by relating applications to business service, business function, data, process, etc.
  • Elaborate a set of Application Architecture views by examining how the application will function, capturing integration, migration, development, and operational concern
Application portfolio management:
An organisation and processes designed to catalogue, describe, and value the applications
of an enterprise, with a view to rationalisation or optimisation of those applications.

Applications Architecture Structural Model
  1. A diagram that displays applications and the data flows that pass between them
  2. Typically drawn using some kind of Data Flow Diagram
  3. Where there are too many data flows, they may be abstracted into dependencies in some kind of dependency diagram

Applications Architecture Behavioural Model
  1. A diagram that shows how a process works by illustrating the interaction of users and applications
  2. Often drawn using some kind of interaction diagram
  3. Frequently used to inspect where time is lost in or between application processing stages

Labels:

Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more