Changes between Version 2 and Version 3 of Test

Timestamp:

11/28/12 15:36:33 (13 years ago)

Author:

13242

Comment:

--

Test

@@ +1 @@
+Biographies for people who have team work and want
+                       to publish their common work
+                                                Vision
+
+                                        Version <1.0>
+              ReVision document History
+      Date    Version               Description        Author
+
+<dd/mmm/yy>   <x.x>     <details>                 <name>
+                                  Table of Contents
+
+                                              Vision
+           1. Introduction
+Software (web site) for research group of people data base
+
+
+The user first will enter a site that will have text box, which from the text box will check
+(according key words, date and place) if there is already some portfolio, group, biography, event
+or etc. Nonregistered users have access to the site but not and to the files and the important
+information. The system is consisted of: admin, registered user and nonregistered user. Everyone
+for themselves enter the needed information. Every user can approve if the file will be public or
+not. Every user will need to be able to rang their own portfolio and every other activity. The first
+group of users will be the informatics. The admin will define the structure of the site, to choose
+which modules will exist, to configure the system, to define the basic parameters (important: the
+admin will not enter the information about the people). The entering of the information and
+activities needs to be acceptable for every group of users, simpler and more practical.
+
+                   1. Purpose
+The goal of this document is to have the biographies on one place for certain group of people.
+With arrangement of the web site where the biographies will be arranged, the companies and the
+other people will be able to see on one place the biographies, in which files one person was
+included and many other convenient.
+
+                   2. Scope
+The software is connected with certain group of people that have their own biographies
+
+                  3. Definitions, Acronyms and Abbreviations
+Shortcut (bio=biography)
+
+                   4. References
+Beside this document we have other documents for example: weekly reports, interview,
+presentations and etc.
+
+                  5. Overview
+This document represents the vision of the software, review and access to the software.
+              2. Positioning
+                      1. Business Opportunity
+  The software will be used for reading, searching and discovering certain information, files etc,
+  for a certain person.
+
+                       2. Problem Statement
+                          The problem of         Overlap of the files (one person wrote with one
+                                                 name on one file, and the other one that associated
+                                                 in that file wrote it under other name. With this will
+                                                 be achieved more duplicates and etc.)
+
+                          Affects                Musicians, informatics, poets…
+
+                          the impact of which    Searching of one person whose files have wrote and
+                          is                     what worked.
+
+                          a successful           Here the files are connected with that person and he
+                          solution would be      can add and summarize.
+
+                       3. Product Position Statement
+
+
+                 For                  Musicians, informatics, poets..
+
+                 Who                  [statement of the need or opportunity]
+
+                 The (product         Web software for biography
+                 name)
+
+                 That                 Simpler way of having more biographies on one
+                                      place
+
+                 Unlike               [primary competitive alternative]
+
+                 Our product          [statement of primary differentiation]
+
+
+3. Stakeholder and User Descriptions
+
+  For this project we ask many people from different areas and we will put the best and most liked
+  features from asked people. Also for this project we ask the people which will read the
+  biographies and we make survey which features are most interested for them and how they want
+  to classify the information for the people and which features they want to see on different place
+  in the biographies.
+Market Demographics
+
+
+Our small team work on this project and we want to grow up our respect between the IT
+companies. We make discount on our prices because we want to be competitive with other
+companies who work on this type of software.
+
+Stakeholder Summary
+
+      Name                     Represents                   Role
+
+      Person who write his     Often users                  They will write information
+      biography                                             about their work
+
+      Biography reader         People who will read the     People who will see the work
+                               biographies                  on the people their shared
+                                                            work, people who are
+                                                            interested about some
+                                                            projects, events etc.
+User Summary
+
+      Name                       Description                    Stakeholder
+
+      Name the user type         [Briefly describe what      [List how the user is
+                                 they represent with respect represented by the
+                                 to the system.]             stakeholders.
+                                                             For example, Represented by
+                                                             Stakeholder 1.1
+
+
+
+User Environment
+
+
+For completion of this project there is a team from 5 professional programmers who will work 5
+months in this company. First they will make some prototype and after that they will upgrade the
+application and will make the final version.
+
+Stakeholder Profiles
+
+<Stakeholder Name>
+
+      Representative       [Who is the stakeholder representative to the project? (optional if
+                           documented elsewhere.) What we want here is names.]
+
+      Description          [Brief description of the stakeholder type.]
+
+      Type                 [Qualify the stakeholder’s expertise, technical background, and
+                           degree of sophistication—that is, guru, business, expert, casual user,
+                           etc.]
+
+      Responsibilities     [List the stakeholder’s key responsibilities with regards to the system
+                           being developed—that is, their interest as a stakeholder.]
+
+      Success Criteria [How does the stakeholder define success?
+                       How is the stakeholder rewarded?]
+
+      Involvement          [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.]
+
+      Comments /           [Problems that interfere with success and any other relevant
+      Issues               information go here.]
+User Profiles
+
+<User Name>
+
+        Representative     [Who is the user representative to the project? (optional if
+                           documented elsewhere.) This often refers to the Stakeholder that
+                           represents the set of users, for example, Stakeholder: Stakeholder1.]
+
+        Description        [A brief description of the user type.]
+
+        Type               [Qualify the user’s expertise, technical background, and degree of
+                           sophistication—that is, guru, casual user, etc.]
+
+        Responsibilities   [List the user’s key responsibilities with regards to the system being
+                           developed— that is, captures details, produces reports, coordinates
+                           work, etc.]
+
+        Success Criteria [How does the user define success?
+                         How is the user rewarded?]
+
+        Involvement        [How the user is involved in the project? Relate where possible to
+                           RUP workers—that is, Requirements Reviewer, etc.]
+
+        Deliverables       [Are there any deliverables the user produces and, if so, for whom?]
+
+        Comments /         [Problems that interfere with success and any other relevant
+        Issues             information go here.
+                           These would include trends that make the user’s job easier or harder.]
+
+
+
+Key Stakeholder / User Needs
+
+
+            • Little information about group work on some team
+                   • This problem is solved with this application because all group works will
+                       be networked between the people.
+
+ Need                          Priority Concerns        Current             Proposed Solutions
+                                                        Solution
+   Broadcast messages
+
+
+
+  Alternatives and Competition
+
+  Our purpose is to tell to the IT world that we can be quality and competitive on the market.
+
+
+4. Product Overview
+
+  Product Perspective
+
+
+  There are a lot of similar sites where there are parts for biography but they are not connected
+  which one in which file, activity and etc worked, so there wouldn’t be overlap of the files and
+  etc.
+  Summary of Capabilities
+                                        Customer Support System
+                        Customer Benefit                Supporting Features
+
+               Less spent time for the admin     Only with few clicks you’ll get the
+                                                 needed information for a certain type
+                                                 of a person.
+
+               Easier way for reviewing of
+               the biographies
+
+  Assumptions and Dependencies
+
+
+  The web site can be accessible through mobile and PC.
+  Cost and Pricing
+
+  We’ll need a certain server where will be our web site which will have certain configuration
+  (more users more memory ex. 500 users, 1GB ram).
+
+  Licensing and Installation
+
+
+  The application will be able to be used by everyone, but the registered users will have more
+  possibilities and more functions.
+5. Product Features
+  The user can list all the projects that he entered or participated in. He will be also able to search
+         thought the projects using the keywords.
+
+  If a project is rewritten the user should be able to add only the year to the existing data for the
+           project.
+
+  When a user applies for a new job/project the system should select only the projects that are
+        necessary for the new job/project so that the employer can see the experience on the user.
+
+  Avoidance from additional costs.
+
+
+
+6. Constraints
+            • Users can limit which data will be visible for others.
+            • Users will have access only if they are connected on the internet.
+              • The user interface design must be simpler so that it could be handled by
+                people with lack of computer experience.
+
+
+7. Quality Ranges
+   7.1. Usability
+  7.1.1. The software must be easy to learn and operate with.
+  7.2. Performance
+  7.2.1. The system must return results in no more than 3 seconds.
+  7.3. Robustness
+  7.3.1.
+  7.4. Fault tolerance
+  7.4.1.
+8. Precedence and Priority
+9. Other Product Requirements
+  Applicable Standards
+
+  System Requirements
+
+  Performance Requirements
+
+  Environmental Requirements
+    10.Documentation Requirements
+User Manual
+
+         The user manual will help the users of the software to understand better its functionality
+         and have a full benefit from it. The manual will be detailed with all the things that the users
+         need to know, such as what to do with the login page, what to do with the groups,
+         assignments, user’s CV-s, events etc. According to the number of groups of users, the
+         manual will be separated into as many parts as groups. Also there will be information
+         about what the user has to do in an error event or some wrong input/display. All of the
+         above will be explained graphically.
+On-line Help
+         If needed, an online instruction/help will be provided, along the user manual. The online
+         help will be used in case of a system error or wrong input/function so that the user can
+         apply the solution fast and successful. The online help will contain information about some
+         unpredicted action that the users may conduct and solutions.
+
+Installation Guides, Configuration, Read Me File
+
+         The software does not require installation, configuration or Read Me File. The
+         configuration, i.e. the login actions will be provided in the user manual.
+         .
+
+Labeling and Packaging
+
+         The CD cases (with the user manual and access to the software ) will be printed in black
+         color and some simple logo.
+
+
+    11.Appendix 1 - Feature Attributes
+Status
+
+
+                                   Prop                  • Adding new users
+                                   osed
+                                                         • Inserting new CV-s
+                                                         • Inserting new assignments and
+                                                           events
+                                                         • Inserting new companies
+                                                           • Editing/Inserting Assignment’s details
+                                                           • Inserting/Editing User’s details
+                                                           • Inserting data has to be
+                                                             Simultaneously with all user’s groups
+
+                                    Appr                    /
+                                    oved
+
+                                    Incor           /
+                                    porat
+                                    ed
+
+Benefit
+
+          The benefit from this project is to have all the CV-s at one place of a group of people with
+          certain qualifications, their assignments and events they participated in. That way, all of
+          the essential information can be found on one place, so that users could search for
+          specific assignment/events.
+
+
+
+                                    C                   • Adding new users
+                                    rit
+                                                        • Adding new group of users
+                                    ic
+                                    al                  • Adding new projects
+                                                        • Administrator’s approval
+
+                                    I                   • Assigning users to projects/events
+                                    m
+                                                        • Inserting/Editing user’s information
+                                    p
+                                    or
+                                    ta
+                                    nt
+
+                                    U                   • User manual
+                                    s
+                                    ef
+                                    ul
+
+
+Effort
+
+
+          The implementation of this project will be conducted in the time period of 18-24
+          months. User’s training will be conducted in the time period of 1-7 days. The full
+          amount of time to implement this software in the society is 24-30 months.
+Risk
+
+
+        The risk of the development/implementation of this software is the consistency of
+        the data different users has access to, therefore misleading users that use the
+        software.
+
+Stability
+
+Target Release
+
+Assigned To
+
+Reason