What do you think?
Rate this book
아키텍트 이야기
Architect Story
In the era of 35 years of developers retirement age, architects are more desperate.
Who is an Architect and what does it do?
Architect refers to a system that looks at the system from a technical standpoint and is responsible for the entire design and implementation, leading the development team. The basic policy for development is to define the architecture, and to design and implement the framework based on it. It can also be said that a complex set of project stakeholders - users, clients and developers - balances their needs from a technical point of view in terms of cost, development scope, quality and schedule. The book introduces a virtual architect and makes it easy to see how an architect plays a part in a projects workflow. This solves the question of how architects solve problems in system development projects and contribute to project success. This book will be an introduction to the architect who knows what architects are doing and explains easily and realistically to people who are not clearly understood.
This book points to the nature of the developer who is pleased to create something, It suggests that there is a different path from the reality that the manager or the sales front line is deployed when the career is completed. It is really about letting developers think again about what they want. And that the hope is never far from reality.
In the era of 35 years of developers retirement age, architects are more desperate.
Who is an Architect and what does it do?
Architect refers to a system that looks at the system from a technical standpoint and is responsible for the entire design and implementation, leading the development team. The basic policy for development is to define the architecture, and to design and implement the framework based on it. It can also be said that a complex set of project stakeholders - users, clients and developers - balances their needs from a technical point of view in terms of cost, development scope, quality and schedule. The book introduces a virtual architect and makes it easy to see how an architect plays a part in a projects workflow. This solves the question of how architects solve problems in system development projects and contribute to project success. This book will be an introduction to the architect who knows what architects are doing and explains easily and realistically to people who are not clearly understood.
This book points to the nature of the developer who is pleased to create something, It suggests that there is a different path from the reality that the manager or the sales front line is deployed when the career is completed. It is really about letting developers think again about what they want. And that the hope is never far from reality.
228 pages, Paperback
Published April 14, 2007
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
No one has reviewed this book yet.