4.1 out of 5
4.1
23 reviews on Udemy

How to become the perfect Web and Information Architect

In this course the students will learn Web Information and Solution Architecture and define software requirements
Instructor:
Daniele Protti
261 students enrolled
English [Auto-generated]
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

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.

What is solution and information architecture

1
Introduction
2
Information Architecture
3
The scenario in a software project
4
Roles & Responsibilities
5
The problem: understand the customer requirement
6
Web/Information architect: the solution architect
7
Presentation of 3 case studies

Different roles in the design process

1
Different roles in the design process - Introduction
2
Different roles in the design process - UX Designer
3
Different roles in the design process - UI Designer
4
Different roles in the design process - Visual/Graphic Designer
5
Different roles in the design process - Interaction Designer
6
Different roles in the design process - UX Researcher
7
Different roles in the design process - Front end developer
8
Different roles in the design process - Product designer
9
How to choose a designer

Requirement Gathering

1
What is requirement gathering?
2
Example #1 - The product catalog app - customer requirement
3
Example #2 - A website campaign - customer requirement
4
Example #3 - An eLearning membership website - customer requirement (Part I)
5
Example #3 - An eLearning membership website - customer requirement (Part II)
6
Example #3 - An eLearning membership website - customer requirement (Part III)
7
Example #3 - An eLearning membership website - customer requirement (Part IV)
8
Example #3 - An eLearning membership website - customer requirement (Part V)
9
Example #3 - An eLearning membership website - customer requirement (Part VI)
10
Identify the solution
11
Identification of the skills and technologies
12
Work organization

Product Conception

1
High level design
2
Example #1 - The product catalog app - high level design
3
Example #2 - A website campaign - high level design
4
Example #3 - An eLearning membership website - high level design
5
Low level design - use cases (Part I)
6
Low level design - use cases (Part II)
7
Example #1 - The product catalog app - use cases
8
Example #2 - A website campaign - use cases
9
Example #3 - An eLearning membership website - use cases
10
Low level design - detailed process descriptions
11
Example #1 - The product catalog app - detailed process descriptions (Part I)
12
Example #1 - The product catalog app - detailed process descriptions (Part II)
13
Example #2 - A website campaign - detailed process descriptions (part I)
14
Example #2 - A website campaign - detailed process descriptions (part II)
15
Example #2 - A website campaign - detailed process descriptions (part III)
16
Example #2 - A website campaign - detailed process descriptions (part IV)
17
Example #3 - An eLearning membership website - detailed process description (I)
18
Example #3 - An eLearning membership website - detailed process description (II)
19
Example #3 - An eLearning membership website -detailed process description (III)
20
Example #3 - An eLearning membership website - detailed process description (IV)
21
UX Design
22
UI Design
23
UX vs UI Design
24
Wireframes and fast prototyping
25
What Is The Difference Between Wireframe, Mockup and Prototype?
26
Wireframes (Part I)
27
Wireframes (Part II)
28
Prototypes
29
Mokups
30
What deliverable to choose (Part I)
31
What deliverable to choose (Part II)
32
Tools for sketches
33
Tools for wireframes
34
Tools for mockups
35
Tools for prototypes
36
Example #1 - The product catalog app - Wireframes, mokups and prototypes (1)
37
Example #1 - The product catalog app - Wireframes, mokups and prototypes (2)
38
Example #1 - The product catalog app - Wireframes, mokups and prototypes (3)
39
Example #1 - The product catalog app - Wireframes, mokups and prototypes (4)
40
Example #2 - A website campaign - Wireframes (Part I)
41
Example #2 - A website campaign - Wireframes (Part II)
42
Example #2 - A website campaign - Wireframes (Part III)
43
Example #3 - An eLearning membership website - Wireframes (I)
44
Example #3 - An eLearning membership website - Wireframes (II)
45
Example #3 - An eLearning membership website - Wireframes (III)
46
Example #3 - An eLearning membership website - Wireframes (IV)
47
Example #3 - An eLearning membership website - Wireframes (V)

Database Architecture

1
What is a database
2
Relational database
3
Define a database
4
Ho to specify primary keys
5
How to specify foreign keys
6
Specify database roles and privileges
7
Example #1 - Database structure (I)
8
Example #1 - Database structure (II)
9
Example #1 - Database structure (III)
10
Example #1 - Database structure (IV)
11
Example #1 - Database structure (V)
12
Example #1 - Database structure (VI)
13
Example #1 - Database structure (VII)
14
Example #1 - Database structure (VIII)
15
Example #2 - Database structure
16
Example #3 - Database structure (I)
17
Example #3 - Database structure (II)
18
Example #3 - Database structure (III)
19
Example #3 - Database structure (IV)
20
Example #3 - Database structure (V)
You can view and review the lecture materials indefinitely, like an on-demand channel.
Definitely! If you have an internet connection, courses on Udemy are available on any device at any time. If you don't have an internet connection, some instructors also let their students download course lectures. That's up to the instructor though, so make sure you get on their good side!
4.1
4.1 out of 5
23 Ratings

Detailed Rating

Stars 5
8
Stars 4
8
Stars 3
3
Stars 2
2
Stars 1
2
af42d1ecfa79d22b7eae5608cc023968
30-Day Money-Back Guarantee

Includes

23 hours on-demand video
Full lifetime access
Access on mobile and TV
Certificate of Completion