| 1 | | Biographies for people who have team work and want to publish their common work |
| 2 | | Vision |
| 3 | | |
| 4 | | Version <1.0> |
| 5 | | |
| 6 | | |
| 7 | | ReVision document History |
| 8 | | Date Version Description Author |
| 9 | | <dd/mmm/yy> <x.x> <details> <name> |
| 10 | | |
| 11 | | |
| 12 | | |
| 13 | | |
| 14 | | |
| 15 | | Table of Contents |
| 16 | | 1. Introduction 3 |
| 17 | | 1.1 Purpose 3 |
| 18 | | 1.2 Scope 3 |
| 19 | | 1.3 Definitions, Acronyms and Abbreviations 3 |
| 20 | | 1.4 References 3 |
| 21 | | 1.5 Overview 3 |
| 22 | | 2. Positioning 3 |
| 23 | | 2.1 Business Opportunity 3 |
| 24 | | 2.2 Problem Statement 3 |
| 25 | | 2.3 Product Position Statement 3 |
| 26 | | 3. Stakeholder and User Descriptions 3 |
| 27 | | 3.1 Market Demographics 3 |
| 28 | | 3.2 Stakeholder Summary 3 |
| 29 | | 3.3 User Summary 3 |
| 30 | | 3.4 User environment 3 |
| 31 | | 3.5 Stakeholder Profiles 3 |
| 32 | | 3.5.1 <Stakeholder Name> 3 |
| 33 | | 3.6 User Profiles 3 |
| 34 | | 3.6.1 <User Name> 3 |
| 35 | | 3.7 Key Stakeholder / User Needs 3 |
| 36 | | 3.8 Alternatives and Competition 3 |
| 37 | | 3.8.1 <aCompetitor> Error! Bookmark not defined. |
| 38 | | 3.8.2 <anotherCompetitor> Error! Bookmark not defined. |
| 39 | | 4. Product Overview 3 |
| 40 | | 4.1 Product Perspective 3 |
| 41 | | 4.2 Summary of Capabilities 3 |
| 42 | | 4.3 Assumptions and Dependencies 3 |
| 43 | | 4.4 Cost and Pricing 3 |
| 44 | | 4.5 Licensing and Installation 3 |
| 45 | | 5. Product Features 3 |
| 46 | | 5.1 Error! Bookmark not defined. |
| 47 | | 5.2 Error! Bookmark not defined. |
| 48 | | 6. Constraints 3 |
| 49 | | 7. Quality Ranges 3 |
| 50 | | 8. Precedence and Priority 3 |
| 51 | | 9. Other Product Requirements 3 |
| 52 | | 9.1 Applicable Standards 3 |
| 53 | | 9.2 System Requirements 3 |
| 54 | | 9.3 Performance Requirements 3 |
| 55 | | 9.4 Environmental Requirements 3 |
| 56 | | 10. Documentation Requirements 3 |
| 57 | | 10.1 User Manual 3 |
| 58 | | 10.2 Online Help 3 |
| 59 | | 10.3 Installation Guides, Configuration, Read Me File 3 |
| 60 | | 10.4 Labeling and Packaging 3 |
| 61 | | 11. Appendix 1 - Feature Attributes 3 |
| 62 | | 11.1 Status 3 |
| 63 | | 11.2 Benefit 3 |
| 64 | | 11.3 Effort 3 |
| 65 | | 11.4 Risk 3 |
| 66 | | 11.5 Stability 3 |
| 67 | | 11.6 Target Release 3 |
| 68 | | 11.7 Assigned To 3 |
| 69 | | 11.8 Reason 3 |
| 70 | | |
| 71 | | Vision |
| 72 | | 1. Introduction |
| 73 | | Software (web site) for research group of people data base |
| 74 | | |
| 75 | | 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. |
| 76 | | 1.1 Purpose |
| 77 | | 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. |
| 78 | | 1.2 Scope |
| 79 | | The software is connected with certain group of people that have their own biographies |
| 80 | | 1.3 Definitions, Acronyms and Abbreviations |
| 81 | | Shortcut (bio=biography) |
| 82 | | 1.4 References |
| 83 | | Beside this document we have other documents for example: weekly reports, interview, presentations and etc. |
| 84 | | 1.5 Overview |
| 85 | | This document represents the vision of the software, review and access to the software. |
| 86 | | 2. Positioning |
| 87 | | 2.1 Business Opportunity |
| 88 | | The software will be used for reading, searching and discovering certain information, files etc, for a certain person. |
| 89 | | 2.2 Problem Statement |
| 90 | | 2.3 |
| 91 | | 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.) |
| 92 | | Affects Musicians, informatics, poets… |
| 93 | | the impact of which is Searching of one person whose files have wrote and what worked. |
| 94 | | a successful solution would be Here the files are connected with that person and he can add and summarize. |
| 95 | | 2.4 Product Position Statement |
| 96 | | |
| 97 | | For Musicians, informatics, poets.. |
| 98 | | Who [statement of the need or opportunity] |
| 99 | | The (product name) Web software for biography |
| 100 | | That Simpler way of having more biographies on one place |
| 101 | | Unlike [primary competitive alternative] |
| 102 | | Our product [statement of primary differentiation] |
| 103 | | |
| 104 | | 3. Stakeholder and User Descriptions |
| 105 | | |
| 106 | | 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. |
| 107 | | |
| 108 | | 3.1 Market Demographics |
| 109 | | |
| 110 | | 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. |
| 111 | | |
| 112 | | 3.2 Stakeholder Summary |
| 113 | | Name Represents Role |
| 114 | | Person who write his biography Often users They will write information about their work |
| 115 | | Biography reader People who will read the biographies People who will see the work on the people their shared work, people who are interested about some projects, events etc. |
| 116 | | |
| 117 | | |
| 118 | | 3.3 User Summary |
| 119 | | Name Description Stakeholder |
| 120 | | Name the user type [Briefly describe what they represent with respect to the system.] [List how the user is represented by the stakeholders. |
| 121 | | For example, Represented by Stakeholder 1.1 |
| 122 | | |
| 123 | | 3.4 User Environment |
| 124 | | |
| 125 | | 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. |
| 126 | | |
| 127 | | 3.5 Stakeholder Profiles |
| 128 | | 3.5.1 <Stakeholder Name> |
| 129 | | Representative [Who is the stakeholder representative to the project? (optional if documented elsewhere.) What we want here is names.] |
| 130 | | Description [Brief description of the stakeholder type.] |
| 131 | | Type [Qualify the stakeholder’s expertise, technical background, and degree of sophistication—that is, guru, business, expert, casual user, etc.] |
| 132 | | Responsibilities [List the stakeholder’s key responsibilities with regards to the system being developed—that is, their interest as a stakeholder.] |
| 133 | | Success Criteria [How does the stakeholder define success? |
| 134 | | How is the stakeholder rewarded?] |
| 135 | | Involvement [How the stakeholder is involved in the project? Relate where possible to RUP workers—that is, Requirements Reviewer etc.] |
| 136 | | Deliverables [Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.] |
| 137 | | Comments / Issues [Problems that interfere with success and any other relevant information go here.] |
| 138 | | |
| 139 | | 3.6 User Profiles |
| 140 | | 3.6.1 <User Name> |
| 141 | | 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.] |
| 142 | | Description [A brief description of the user type.] |
| 143 | | Type [Qualify the user’s expertise, technical background, and degree of sophistication—that is, guru, casual user, etc.] |
| 144 | | Responsibilities [List the user’s key responsibilities with regards to the system being developed— that is, captures details, produces reports, coordinates work, etc.] |
| 145 | | Success Criteria [How does the user define success? |
| 146 | | How is the user rewarded?] |
| 147 | | Involvement [How the user is involved in the project? Relate where possible to RUP workers—that is, Requirements Reviewer, etc.] |
| 148 | | Deliverables [Are there any deliverables the user produces and, if so, for whom?] |
| 149 | | Comments / Issues [Problems that interfere with success and any other relevant information go here. |
| 150 | | These would include trends that make the user’s job easier or harder.] |
| 151 | | |
| 152 | | 3.7 Key Stakeholder / User Needs |
| 153 | | |
| 154 | | • Little information about group work on some team |
| 155 | | o This problem is solved with this application because all group works will be networked between the people. |
| 156 | | |
| 157 | | Need Priority Concerns Current Solution Proposed Solutions |
| 158 | | Broadcast messages |
| 159 | | |
| 160 | | 3.8 Alternatives and Competition |
| 161 | | Our purpose is to tell to the IT world that we can be quality and competitive on the market. |
| 162 | | |
| 163 | | 4. Product Overview |
| 164 | | |
| 165 | | 4.1 Product Perspective |
| 166 | | |
| 167 | | 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. |
| 168 | | 4.2 Summary of Capabilities |
| 169 | | Customer Support System |
| 170 | | Customer Benefit Supporting Features |
| 171 | | Less spent time for the admin Only with few clicks you’ll get the needed information for a certain type of a person. |
| 172 | | Easier way for reviewing of the biographies |
| 173 | | 4.3 Assumptions and Dependencies |
| 174 | | |
| 175 | | The web site can be accessible through mobile and PC. |
| 176 | | 4.4 Cost and Pricing |
| 177 | | |
| 178 | | 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). |
| 179 | | |
| 180 | | 4.5 Licensing and Installation |
| 181 | | |
| 182 | | The application will be able to be used by everyone, but the registered users will have more possibilities and more functions. |
| 183 | | |
| 184 | | 5. Product Features |
| 185 | | 5.1 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. |
| 186 | | 5.2 If a project is rewritten the user should be able to add only the year to the existing data for the project. |
| 187 | | 5.3 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. |
| 188 | | 5.4 Avoidance from additional costs. |
| 189 | | |
| 190 | | 6. Constraints |
| 191 | | • Users can limit which data will be visible for others. |
| 192 | | • Users will have access only if they are connected on the internet. |
| 193 | | • The user interface design must be simpler so that it could be handled by people with lack of computer experience. |
| 194 | | |
| 195 | | 7. Quality Ranges |
| 196 | | 7.1. Usability |
| 197 | | 7.1.1. The software must be easy to learn and operate with. |
| 198 | | 7.2. Performance |
| 199 | | 7.2.1. The system must return results in no more than 3 seconds. |
| 200 | | 7.3. Robustness |
| 201 | | 7.3.1. |
| 202 | | 7.4. Fault tolerance |
| 203 | | 7.4.1. |
| 204 | | |
| 205 | | 8. Precedence and Priority |
| 206 | | 9. Other Product Requirements |
| 207 | | 9.1 Applicable Standards |
| 208 | | 9.2 System Requirements |
| 209 | | 9.3 Performance Requirements |
| 210 | | 9.4 Environmental Requirements |
| 211 | | |
| 212 | | |
| 213 | | 10. Documentation Requirements |
| 214 | | 10.1 User Manual |
| 215 | | |
| 216 | | 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. |
| 217 | | |
| 218 | | 10.2 On-line Help |
| 219 | | |
| 220 | | 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. |
| 221 | | |
| 222 | | 10.3 Installation Guides, Configuration, Read Me File |
| 223 | | |
| 224 | | 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. |
| 225 | | . |
| 226 | | 10.4 Labeling and Packaging |
| 227 | | |
| 228 | | The CD cases (with the user manual and access to the software ) will be printed in black color and some simple logo. |
| 229 | | |
| 230 | | 11. Appendix 1 - Feature Attributes |
| 231 | | 11.1 Status |
| 232 | | |
| 233 | | Proposed - Adding new users |
| 234 | | - Inserting new CV-s |
| 235 | | - Inserting new assignments and events |
| 236 | | - Inserting new companies |
| 237 | | - Editing/Inserting Assignment’s details |
| 238 | | - Inserting/Editing User’s details |
| 239 | | - Inserting data has to be Simultaneously with all user’s groups |
| 240 | | Approved / |
| 241 | | Incorporated / |
| 242 | | 11.2 Benefit |
| 243 | | |
| 244 | | 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. |
| 245 | | |
| 246 | | |
| 247 | | |
| 248 | | Critical - Adding new users |
| 249 | | - Adding new group of users |
| 250 | | - Adding new projects |
| 251 | | - Administrator’s approval |
| 252 | | Important - Assigning users to projects/events |
| 253 | | - Inserting/Editing user’s information |
| 254 | | Useful - User manual |
| 255 | | |
| 256 | | 11.3 Effort |
| 257 | | |
| 258 | | 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. |
| 259 | | |
| 260 | | |
| 261 | | 11.4 Risk |
| 262 | | |
| 263 | | 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. |
| 264 | | |
| 265 | | 11.5 Stability |
| 266 | | 11.6 Target Release |
| 267 | | 11.7 Assigned To |
| 268 | | 11.8 Reason |
