Changes between Initial Version and Version 1 of Vision

Timestamp:

05/11/24 20:15:49 (8 months ago)

Author:

223078

Comment:

--

Vision

@@ +1 @@
+
+= Визија
+
+== 1. Вовед
+
+
+
+== 2. Позиционирање
+
+=== 2.1 Дефиниција на проблем
+
+||= Тема на проблем =|| [describe the problem] ||
+||= Кого засега =|| [the stakeholders affected by the problem] ||
+||= Со последици како =|| [what is the impact of the problem?] ||
+||= Успешно решение би било =|| [list some key benefits of a successful solution] ||
+
+=== 2.2 Позиција на пазарот
+
+||= За =|| [target customer] ||
+||= Кои =|| [statement of the need or opportunity] ||
+||= !FINKI Maps =|| is a [product category] ||
+||= Кој овозможува =|| [statement of key benefit; that is, the compelling reason to buy] ||
+||= За разлика од =|| [primary competitive alternative] ||
+||= Нашиот продукт =|| [statement of primary differentiation] ||
+
+== 3. Опис на засегнатите лица
+
+=== 3.1 Преглед
+
+||= Име =||= Опис =||= Одговорности =||
+|| [Name the stakeholder type.] || [Briefly describe the stakeholder.] || Summarize the stakeholder’s key responsibilities with regard to the system being developed; that is, their interest as a stakeholder. For example, this stakeholder:
+ensures that the system will be maintainable ensures that there will be a market demand for the product’s features monitors the project’s progress
+approves funding and so forth]||
+||  ||  ||  ||
+||  ||  ||  ||
+||  ||  ||  ||
+||  ||  ||  ||
+
+=== 3.2 Корисничка околина
+
+[Detail the working environment of the target user. Here are some suggestions:
+Number of people involved in completing the task? Is this changing?
+How long is a task cycle? Amount of time spent in each activity? Is this changing?
+Any unique environmental constraints: mobile, outdoors, in-flight, and so on?
+Which system platforms are in use today? Future platforms?
+What other applications are in use? Does your application need to integrate with them?
+This is where extracts from the Business Model could be included to outline the task and roles involved, and so on.]
+
+== 4. Преглед на производот
+
+=== 4.1 Барања
+
+Avoid design. Keep feature descriptions at a general level. Focus on capabilities needed and why (not how)       they should be implemented. Capture the stakeholder priority and planned release for each feature.]
+
+||= Потреба =||= Приоритет =||= Карактеристики =||
+|| Dummy text ||  ||  ||
+||  ||  ||  ||
+||  ||  ||  ||
+||  ||  ||  ||
+||  ||  ||  ||
+
+
+
+== 5. Други барања
+
+[At a high level, list applicable standards, hardware, or platform requirements; performance requirements; and environmental requirements.
+Define the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics that are not captured in the Feature Set.
+Note any design constraints, external constraints, assumptions or other dependencies that, if changed, will alter the Vision document. For example, an assumption may state that a specific operating system will be available for the hardware designated for the software product. If the operating system is not available, the Vision document will need to change.
+Define any specific documentation requirements, including user manuals, online help, installation, labeling, and packaging requirements.
+Define the priority of these other product requirements. Include, if useful, attributes such as stability, benefit, effort, and risk.]
+
+||= Барање =||= Приоритет=||
+|| Dummy text ||  ||
+||  ||  ||
+||  ||  ||
+||  ||  ||