Design Phase (The Business Leader's Playbook of Software Development, #3) (eBook, ePUB)
PAYBACK Punkte
0 °P sammeln!
Business leaders and managers are expected to not only understand the goals of their organizations but also effectively collaborate with technical teams throughout the Software Development Life Cycle (SDLC). Design Phase - Business Architecture and System Architecture is an essential resource designed to help leaders actively engage with consultants and technical staff during this pivotal stage.The book explains the use of enterprise and business architecture frameworks, such as the Zachman Framework, to provide clarity on how different components of a business-data, function, people, network,...
Business leaders and managers are expected to not only understand the goals of their organizations but also effectively collaborate with technical teams throughout the Software Development Life Cycle (SDLC). Design Phase - Business Architecture and System Architecture is an essential resource designed to help leaders actively engage with consultants and technical staff during this pivotal stage.
The book explains the use of enterprise and business architecture frameworks, such as the Zachman Framework, to provide clarity on how different components of a business-data, function, people, network, and motivation-are represented and modeled in system design. The book emphasizes the role of business leaders in system architecture and details how their involvement can impact system design from defining business requirements to participating in governance and decision-making.
The Table of Contents of the book comprises:
I. Glossary
II. Introduction
About this Publication
III. Information Technology Project Phases
IV. Impact of AI on SDLC
1. System Development Phases
2. Design Phase
A. Overview of the Design Phase
B. About Use Cases
2.1. Enterprise Architecture
2.2. Business Architecture
2.2.1. Row 1 - Contextual (Planner's View)
2.2.1.1. Row 1 - Column 1 - Data
2.2.1.2. Row 1 - Column 2 - Function
2.2.1.3. Row 1 - Column 3 - Network
2.2.1.4. Row 1 - Column 4 - People
2.2.1.5. Row 1 - Column 5 - Time
2.2.1.6. Row 1 - Column 6 - Motivation (Why)
2.2.2. Row 2 - Conceptual (Owner's View)
2.2.2.1. Row 2 - Column 1 - Data
2.2.2.2. Row 2 - Column 2 - Function
2.2.2.3. Row 2 - Column 3 - Network
2.2.2.4. Row 2 - Column 4 - People
2.2.2.5. Row 2 - Column 5 - Time
2.2.2.6. Row 2 - Column 6 - Motivation (Why)
2.3. System Architecture
2.3.1. Aspects of Business Involvement in System Architecture
1. Defining Business Requirements
2. Setting Strategic Objectives
3. Participation in Design and Planning
4. Governance and Decision-Making
5. Change Management and User Adoption
6. Continuous Improvement and Feedback
2.3.2. Zachman Framework Business Involvement in System Architecture
1. Data Architecture (Column 1 - What)
2. Application Architecture (Column 2 - How)
3. Network Architecture (Column 3 - Where)
4. User Architecture (Column 4 - Who)
5. Process Architecture (Column 5 - When)
6. Motivation Architecture (Column 6 - Why)
2.3.3. Business Leaders Must Get Involved in System Architecture
Appendix A - Use Cases
The book explains the use of enterprise and business architecture frameworks, such as the Zachman Framework, to provide clarity on how different components of a business-data, function, people, network, and motivation-are represented and modeled in system design. The book emphasizes the role of business leaders in system architecture and details how their involvement can impact system design from defining business requirements to participating in governance and decision-making.
The Table of Contents of the book comprises:
I. Glossary
II. Introduction
About this Publication
III. Information Technology Project Phases
IV. Impact of AI on SDLC
1. System Development Phases
2. Design Phase
A. Overview of the Design Phase
B. About Use Cases
2.1. Enterprise Architecture
2.2. Business Architecture
2.2.1. Row 1 - Contextual (Planner's View)
2.2.1.1. Row 1 - Column 1 - Data
2.2.1.2. Row 1 - Column 2 - Function
2.2.1.3. Row 1 - Column 3 - Network
2.2.1.4. Row 1 - Column 4 - People
2.2.1.5. Row 1 - Column 5 - Time
2.2.1.6. Row 1 - Column 6 - Motivation (Why)
2.2.2. Row 2 - Conceptual (Owner's View)
2.2.2.1. Row 2 - Column 1 - Data
2.2.2.2. Row 2 - Column 2 - Function
2.2.2.3. Row 2 - Column 3 - Network
2.2.2.4. Row 2 - Column 4 - People
2.2.2.5. Row 2 - Column 5 - Time
2.2.2.6. Row 2 - Column 6 - Motivation (Why)
2.3. System Architecture
2.3.1. Aspects of Business Involvement in System Architecture
1. Defining Business Requirements
2. Setting Strategic Objectives
3. Participation in Design and Planning
4. Governance and Decision-Making
5. Change Management and User Adoption
6. Continuous Improvement and Feedback
2.3.2. Zachman Framework Business Involvement in System Architecture
1. Data Architecture (Column 1 - What)
2. Application Architecture (Column 2 - How)
3. Network Architecture (Column 3 - Where)
4. User Architecture (Column 4 - Who)
5. Process Architecture (Column 5 - When)
6. Motivation Architecture (Column 6 - Why)
2.3.3. Business Leaders Must Get Involved in System Architecture
Appendix A - Use Cases
Dieser Download kann aus rechtlichen Gründen nur mit Rechnungsadresse in A, B, CY, CZ, D, DK, EW, E, FIN, F, GR, H, IRL, I, LT, L, LR, M, NL, PL, P, R, S, SLO, SK ausgeliefert werden.
Andere Kunden interessierten sich für
