How to become the perfect Web and Information Architect

本课程旨在支持信息和解决方案架构师提高他们在网站、Web 应用程序和移动应用程序的设计和开发方面的技能。

这是一门过于全面的课程，涵盖了信息和/或解决方案架构师应该参与的软件开发过程的所有方面。

本课程涵盖的主要主题是

什么是解决方案和信息架构：真正的解决方案和信息架构是什么。如何建立心态以了解您的客户以及设计和开发团队并解决冲突和误解。

设计过程中的不同角色：了解网络产品设计和开发阶段涉及的主要角色，例如用户体验设计师、用户界面设计师、产品设计师等。

需求收集：如何收集和定义客户想要和理解的需求。

产品概念：如何进行高级和低级设计，设计流程工作流，定义业务逻辑和算法以实现功能，定义用例，为前端部分/页面准备线框、原型、草图和模型最终的网络解决方案。

数据库架构：指定数据库表，定义主键和外键，链接/引用表，指定用户权限。

技术需求：如何将业务需求转化为详细的技术需求，如何指定布局和功能需求；以用户故事的形式编写技术要求（遵循敏捷方法，例如 SCRUM）；以“完成的定义”的形式规定技术规范的验收标准。

项目管理：解决方案架构师在项目管理方面需要了解的内容；如何制定项目计划；如何基于 sprint 定义发布计划（遵循敏捷方法，例如 SCRUM）；如何评估每个设计和开发任务所需的时间和精力。尽管信息架构师在很多情况下最终都不是项目经理，但通常要求架构师还负责项目管理活动（至少作为项目或项目群中的技术项目经理）管理机构）。

质量保证：对于过去的项目管理，信息架构师可能会参与每个技术规范的验收标准的定义。在本节中，学生将学习如何定义测试场景、测试用例和测试程序（最终将由其他团队执行）。我的意思是学生将学习如何指定测试技术规范的方法以及验收程序应参考的标准。

文档管理：信息架构师在定义阶段交付大量文档，并且还需要在需要审查时对其进行更新（例如，在项目执行阶段或当客户决定提出新更改时或当开发人员通知需要更正时）。在本课程中，学生将学习如何管理他们的文档以及如何处理文档包、实施修订过程并指定文档数据结构（包括历史和文档包版本的管理）。

代码和组件模块化：软件架构成功的关键是单个模块和模板的规范，以用作前端解决方案的一部分，并作为软件代码片段在需要时重用，并减少冗余、开发周期时间和维护问题、努力和时间。在本课程中，学生将学习如何作为开发人员进行模块化 Web 设计和模块化 Web 应用程序。

前端设计：这是架构师定义网站或 Web 应用程序的布局、字体、颜色、用户界面和交互的地方。

响应式网页设计：这并不意味着设计和开发响应式网站或 Web 应用程序，而是如何指定必须响应的网站或 Web 应用程序，即必须在所有设备（台式电脑、桌子、智能手机、 ETC。）。这是上一个会话（前端设计）的扩展，但专注于使一切在浏览器/设备的所有可能组合上都能正常工作。

后端设计：后端和管理面板之间以及后端编程和后端管理之间有什么区别。学生在这里学习如何为内容管理系统指定管理面板和后端管理员的架构。

最后，我提供了一些特别的奖励，其中包括一些案例研究以及对最新网页设计的一些趋势和技术的概述。

所有主题均得到 3 个案例研究的澄清支持

B2B 产品管理应用程序
抽奖活动网站
电子学习网络平台
学生学习如何使用 Microsoft PowerPoint 和 LucidChart 创建他们的工作流程、流程、线框和数据库架构，并将了解最流行的网络架构师创建原型和样机。他们还学习如何使用 Microsoft Word 编写技术简报和 Microsoft Excel 列出技术规范、生成测试用例和测试场景、指定项目和发布计划以及跟踪文档版本。

本课程适用于谁

谁想要与网页设计和开发建立业务
想要/需要成为软件架构师的
软件开发人员想要/需要提高他们在软件架构方面的知识的软件开发
人员需要生成线框、模型、原型的 UI 和 UX 设计师
软件项目经理
解决方案架构师
信息架构师

In this course the students will learn Web Information and Solution Architecture and define software requirements

Last Updated 06/2018
MP4 | Video: h264, 1280×720 | Audio: AAC, 44.1 KHz, 2 Ch
Genre: eLearning | Language: English + srt | Duration: 265 lectures (22h 33m) | Size: 4.54 GB

What you’ll learn

• define the architecture of websites, web applications and mobile apps
• create wireframes, prototypes, sketcjes and mokups as concepts of new websites and apps
• define business requirements and turn them into technical specifications
• define test scenarios and test cases for the acceptance of the implementation of requirements for a website or app
• define the release plan and do project management for the design and development of a website and/or app
• specify process workflows and business logic of functionalities and back end of a website or app
• describe the architecture of a database

Requirements

• Basic knowledge of Windows or OSX for MAC
• Basic knowledge of Microsoft Office tools, e.g. Word, Excel, PowerPoint
• (nice to have) Basic knowledge of software development

Description

This course has been created to support information and solution architects to improve their skills for the design and development of website, web applications and mobile apps.

It is an over-comprehensive course with the scope of covering all the aspects of the software development process where an information and/or solution architect should be involved to.

The main topics covered in this course are

What is solution and information architecture: what really solution and information architecture is. How to setup your mindset to understand your customers and the design and development teams and solve conflicts and misunderstandings.

Different roles in the design process: get to know the main roles involved in the design and development phases of a web product, e.g. User Experience designers, User Interface designers, Product designers, etc.

Requirement Gathering: how to collect and define the requirement as your customer wants and understands.

Product Conception: how to do high and low level design, design the process workflows, define the business logic and algorithm to implement the functionalities, define the use cases, prepare wireframes, prototypes, sketches and mokups for the front end parts/pages of the final web solutions.

Database Architecture: specify database tables, define primary and foreign keys, link/reference tables, specify the user privileges.

Technical Requirements: how to translate business requirements into detailed technical requirements, how to specify layout and functionality requirements; write the technical requirements in form of user stories (following AGILE methodologies e.g. SCRUM); specify the acceptance criteria of the technical specifications in form of “definition of done”.

Project Management: what a solution architect needs to know with regards to project management; how to layout a project plan; how to define a release plan based on sprints (following AGILE methodologies e.g. SCRUM); how to evaluation the time and effort needed for each design and development task. Although an information architect is not a project manager at the end in many cases in the real life of a business it is quite often required that an architect also take care of project management activities (at least as a technical project manager within a project or program management organization).

Quality Assurance: as for the project management past, an information architect may be likely involved in the definition of the acceptance criteria of each technical specifications. In this section students learn how to define test scenarios, test cases and test procedures (which at the end will be executed by other teams). With that I mean that the students will learn how to specify the way to test the technical specifications and to which criteria the acceptance procedures should refer to.

Documentation management: an information architect delivers a lot of documentation in the definition phase and needs also to update it when reviews are needed (e.g. during the project execution phase or when the customers decides to proposed new changes or when the developers inform that corrections are needed). In this session the students learn how to manage their documentation and how to deal with documentation packages, implement the revision process and specify the documentation data structure (including the management of the history and of the documentation package versions).

Code and component modularity: the critical key to success in software architecture is the specifications of single modules and templates to use as parts of the front end solutions and as pieces of software code to be reused at need and reduce redundancy, development cycle times and maintenance issues, efforts and times. In this session the students learn how to do modular web design and modular web applications as developers.

Front End Design: this is where an architect define the layout, the fonts, colors, user interfaces and interactions of a website or web application.

Responsive Web Design: this does not mean design and develop a responsive website or web application but how to specify a website or web application that must be responsive, i.e. must have the best look & feel on all devices (desktop computers, tables, smartphones, etc.). This is an extension of the previous session (Front End Design) but focused on making everything work on all the possible combinations of browsers/devices.

Back End Design: what is the difference between back end and admin panel and between back end programming and back end administration. Students learn here how to specify the architecture of an admin panel and back end admin for content management systems.

At the end I have included some special bonuses which include some case studies and an overview of some of the trends and technologies in web design up to date.

All the topics are supported by clarifications from 3 case studies

a B2B product management application
a raffle campaign website
an eLearning web platform
The students learn how to use Microsoft PowerPoint and LucidChart to create their workflows, processes, wireframes and database architectures and will get to know the most popular tools for web architect to create prototypes and mokups. They also learn how to use Microsoft word to compile technical briefing and Microsoft Excel to list the technical specifications, generate the test cases and test scenarios, specify the project and release plans and track the documentation versions.

Who this course is for

Whoever wants to build a business with web design and development
Software developers who want/need to become software architects
Software developers who want/need to improve their knowledge in software architecture
UI and UX designers who need to generate wireframes, mokups, prototypes
Software project managers
Solution architects
Information architects