📜 ⬆️ ⬇️

Cycle of articles on web service design


We, Denis Beskov ( beskov ) and Ilya Polyak ( ilyap1 ) are starting to publish a series of articles on the process of designing web services. The cycle is built around a 3-level process in which the levels of analysis and design are explicitly highlighted:
  1. Of business
  2. Product
  3. Technology
Here, on Habré, the theme of designing at the level of technologies is well covered. We want to show the relationship of this level, types of work and design decisions with higher levels on the example of a through demo case - designing a web service for booking movie tickets, which was developed a couple of years ago by one of the authors.

The series of articles is built around redundant project documentation (requirements), which is developed by internal company employees, contains a brief description of theoretical aspects and helps answer the following questions that you may have in your work:
  1. What are some ways to describe software requirements?
  2. Which of the system requirements must be included in the TZ, and which ones can be dispensed with?
  3. What could be the options when choosing formats for describing requirements?
  4. How does the choice of the type of description of requirements depend on the parameters (duration, risks, etc.) of the project?
  5. What kind of decisions help make the appropriate types of requirements?
The cycle does not address aspects of custom software development. The article is intended for users who work in a non-sports environment, i.e. not bound to any regulations.

Using the example of designing a new service for an entertainment and information portal, we will tell and show:
  1. What decisions need to be made on the 3 phases of analysis and design: “business”, “product” and “technology”;
  2. The classical approach to the analysis and design of the product;
  3. Different formats for presenting requirements (process models, glossary, use cases, etc.);
  4. What format of presentation of requirements is most appropriate in each situation;
The cycle is designed for project managers, novice systems analysts, designers, interface designers, marketers and developers who want to learn how to design web services not on the knee, but based on industry best practices from the software development industry.
The process of making design decisions at several levels of development of requirements for a software product (business analysis and design, product analysis and design, technical analysis and design) is shown on the example of a ticket booking service on the website afisha.ru.

We will publish one article per week. Please ask questions, we will be happy to answer them.

Table of contents
Business analysis. Context and stakeholder profiles
Business analysis. Description of existing business processes (AS-IS)
Business analysis. Domain Description
Business analysis. Business Problem Analysis

Source: https://habr.com/ru/post/107487/

All Articles