Changes between Version 8 and Version 9 of VirtualLibrary/Vision

Timestamp:

05/10/19 23:34:26 (6 years ago)

Author:

Bojan Popov

Comment:

—

VirtualLibrary/Vision

@@ -64 +64 @@
 **3.5 Профили на засегнати странки**
 
+3.5.1 <Stakeholder Name>
+|| Претставник || <Име и презиме> ||
+|| Опис || <Brief description of the stakeholder type> ||
+|| Тип || <Qualify the stakeholder’s expertise, technical background, and degree of sophistication—that is, guru, business, expert, casual user, etc> ||
+|| Обврски || <List the stakeholder’s key responsibilities with regards to the system being developed—that is, their interest as a stakeholder> ||
+|| Критериум за успешност || <How does the stakeholder define success? How is the stakeholder rewarded?> ||
+|| Вклученост || <How the stakeholder is involved in the project? Relate where possible to RUP workers—that is, Requirements Reviewer etc> ||
+|| Deliverables || <Are there any additional deliverables required by the stakeholder?  These could be project deliverables or outputs from the system under development> ||
+|| Коментари || <Problems that interfere with success and any other relevant information go here> ||
+
 
 **3.6 Кориснички профили**
 
+3.6.1 <Stakeholder Name>
+|| Претставник || <Име и презиме> ||
+|| Опис || <Brief description of the stakeholder type> ||
+|| Тип || <Qualify the stakeholder’s expertise, technical background, and degree of sophistication—that is, guru, business, expert, casual user, etc> ||
+|| Обврски || <List the stakeholder’s key responsibilities with regards to the system being developed—that is, their interest as a stakeholder> ||
+|| Критериум за успешност || <How does the stakeholder define success? How is the stakeholder rewarded?> ||
+|| Вклученост || <How the stakeholder is involved in the project? Relate where possible to RUP workers—that is, Requirements Reviewer etc> ||
+|| Deliverables || <Are there any additional deliverables required by the stakeholder?  These could be project deliverables or outputs from the system under development> ||
+|| Коментари || <Problems that interfere with success and any other relevant information go here> ||
 
 **3.7 Клучни засегнати странки / Кориснички побарувања**
 
 
+
 **3.8 Алтернативи и конкуренција**
+
+
+
+**4 Product overview**
+
+
+
+**4.1 Product Perspective**
+
+
+
+**4.2 Summary of Capabilities**
+
+|| Customer Benefit || Supporting Features ||
+|| New support staff can quickly get up to speed || Knowledge base assists support personnel in quickly identifying known fixes and workarounds ||
+|| Knowledge base assists support personnel in quickly identifying known fixes and workarounds
+ || Problems are uniquely itemized, classified and tracked throughout the resolution process. Automatic notification occurs for any aging issues ||
+|| Management can identify problem areas and gauge staff workload || Trend and distribution reports allow high level review of problem status ||
+|| Distributed support teams can work together to solve problems || Replication server allows current database information to be shared across the enterprise ||
+|| Customers can help themselves, lowering support costs and improving response time || Knowledge base can be made available over the Internet. Includes hypertext search capabilities and graphical query engine ||
+
+**4.3 Assumptions and Dependencies**
+
+
+
+**4.4 Cost and Pricing**
+
+
+
+**4.5 Licensing and Installation**
+
+
+
+**5 Product Features**