| 1 | | Biographies for people who have team work and want |
| 2 | | to publish their common work |
| 3 | | Vision |
| 4 | | |
| 5 | | Version <1.0> |
| 6 | | ReVision document History |
| 7 | | Date Version Description Author |
| 8 | | |
| 9 | | <dd/mmm/yy> <x.x> <details> <name> |
| 10 | | Table of Contents |
| 11 | | |
| 12 | | Vision |
| 13 | | 1. Introduction |
| 14 | | Software (web site) for research group of people data base |
| 15 | | |
| 16 | | |
| 17 | | The user first will enter a site that will have text box, which from the text box will check |
| 18 | | (according key words, date and place) if there is already some portfolio, group, biography, event |
| 19 | | or etc. Nonregistered users have access to the site but not and to the files and the important |
| 20 | | information. The system is consisted of: admin, registered user and nonregistered user. Everyone |
| 21 | | for themselves enter the needed information. Every user can approve if the file will be public or |
| 22 | | not. Every user will need to be able to rang their own portfolio and every other activity. The first |
| 23 | | group of users will be the informatics. The admin will define the structure of the site, to choose |
| 24 | | which modules will exist, to configure the system, to define the basic parameters (important: the |
| 25 | | admin will not enter the information about the people). The entering of the information and |
| 26 | | activities needs to be acceptable for every group of users, simpler and more practical. |
| 27 | | |
| 28 | | 1. Purpose |
| 29 | | The goal of this document is to have the biographies on one place for certain group of people. |
| 30 | | With arrangement of the web site where the biographies will be arranged, the companies and the |
| 31 | | other people will be able to see on one place the biographies, in which files one person was |
| 32 | | included and many other convenient. |
| 33 | | |
| 34 | | 2. Scope |
| 35 | | The software is connected with certain group of people that have their own biographies |
| 36 | | |
| 37 | | 3. Definitions, Acronyms and Abbreviations |
| 38 | | Shortcut (bio=biography) |
| 39 | | |
| 40 | | 4. References |
| 41 | | Beside this document we have other documents for example: weekly reports, interview, |
| 42 | | presentations and etc. |
| 43 | | |
| 44 | | 5. Overview |
| 45 | | This document represents the vision of the software, review and access to the software. |
| 46 | | 2. Positioning |
| 47 | | 1. Business Opportunity |
| 48 | | The software will be used for reading, searching and discovering certain information, files etc, |
| 49 | | for a certain person. |
| 50 | | |
| 51 | | 2. Problem Statement |
| 52 | | The problem of Overlap of the files (one person wrote with one |
| 53 | | name on one file, and the other one that associated |
| 54 | | in that file wrote it under other name. With this will |
| 55 | | be achieved more duplicates and etc.) |
| 56 | | |
| 57 | | Affects Musicians, informatics, poets… |
| 58 | | |
| 59 | | the impact of which Searching of one person whose files have wrote and |
| 60 | | is what worked. |
| 61 | | |
| 62 | | a successful Here the files are connected with that person and he |
| 63 | | solution would be can add and summarize. |
| 64 | | |
| 65 | | 3. Product Position Statement |
| 66 | | |
| 67 | | |
| 68 | | For Musicians, informatics, poets.. |
| 69 | | |
| 70 | | Who [statement of the need or opportunity] |
| 71 | | |
| 72 | | The (product Web software for biography |
| 73 | | name) |
| 74 | | |
| 75 | | That Simpler way of having more biographies on one |
| 76 | | place |
| 77 | | |
| 78 | | Unlike [primary competitive alternative] |
| 79 | | |
| 80 | | Our product [statement of primary differentiation] |
| 81 | | |
| 82 | | |
| 83 | | 3. Stakeholder and User Descriptions |
| 84 | | |
| 85 | | For this project we ask many people from different areas and we will put the best and most liked |
| 86 | | features from asked people. Also for this project we ask the people which will read the |
| 87 | | biographies and we make survey which features are most interested for them and how they want |
| 88 | | to classify the information for the people and which features they want to see on different place |
| 89 | | in the biographies. |
| 90 | | Market Demographics |
| 91 | | |
| 92 | | |
| 93 | | Our small team work on this project and we want to grow up our respect between the IT |
| 94 | | companies. We make discount on our prices because we want to be competitive with other |
| 95 | | companies who work on this type of software. |
| 96 | | |
| 97 | | Stakeholder Summary |
| 98 | | |
| 99 | | Name Represents Role |
| 100 | | |
| 101 | | Person who write his Often users They will write information |
| 102 | | biography about their work |
| 103 | | |
| 104 | | Biography reader People who will read the People who will see the work |
| 105 | | biographies on the people their shared |
| 106 | | work, people who are |
| 107 | | interested about some |
| 108 | | projects, events etc. |
| 109 | | User Summary |
| 110 | | |
| 111 | | Name Description Stakeholder |
| 112 | | |
| 113 | | Name the user type [Briefly describe what [List how the user is |
| 114 | | they represent with respect represented by the |
| 115 | | to the system.] stakeholders. |
| 116 | | For example, Represented by |
| 117 | | Stakeholder 1.1 |
| 118 | | |
| 119 | | |
| 120 | | |
| 121 | | User Environment |
| 122 | | |
| 123 | | |
| 124 | | For completion of this project there is a team from 5 professional programmers who will work 5 |
| 125 | | months in this company. First they will make some prototype and after that they will upgrade the |
| 126 | | application and will make the final version. |
| 127 | | |
| 128 | | Stakeholder Profiles |
| 129 | | |
| 130 | | <Stakeholder Name> |
| 131 | | |
| 132 | | Representative [Who is the stakeholder representative to the project? (optional if |
| 133 | | documented elsewhere.) What we want here is names.] |
| 134 | | |
| 135 | | Description [Brief description of the stakeholder type.] |
| 136 | | |
| 137 | | Type [Qualify the stakeholder’s expertise, technical background, and |
| 138 | | degree of sophistication—that is, guru, business, expert, casual user, |
| 139 | | etc.] |
| 140 | | |
| 141 | | Responsibilities [List the stakeholder’s key responsibilities with regards to the system |
| 142 | | being developed—that is, their interest as a stakeholder.] |
| 143 | | |
| 144 | | Success Criteria [How does the stakeholder define success? |
| 145 | | How is the stakeholder rewarded?] |
| 146 | | |
| 147 | | Involvement [How the stakeholder is involved in the project? Relate where |
| 148 | | possible to RUP workers—that is, Requirements Reviewer etc.] |
| 149 | | |
| 150 | | Deliverables [Are there any additional deliverables required by the stakeholder? |
| 151 | | These could be project deliverables or outputs from the system under |
| 152 | | development.] |
| 153 | | |
| 154 | | Comments / [Problems that interfere with success and any other relevant |
| 155 | | Issues information go here.] |
| 156 | | User Profiles |
| 157 | | |
| 158 | | <User Name> |
| 159 | | |
| 160 | | Representative [Who is the user representative to the project? (optional if |
| 161 | | documented elsewhere.) This often refers to the Stakeholder that |
| 162 | | represents the set of users, for example, Stakeholder: Stakeholder1.] |
| 163 | | |
| 164 | | Description [A brief description of the user type.] |
| 165 | | |
| 166 | | Type [Qualify the user’s expertise, technical background, and degree of |
| 167 | | sophistication—that is, guru, casual user, etc.] |
| 168 | | |
| 169 | | Responsibilities [List the user’s key responsibilities with regards to the system being |
| 170 | | developed— that is, captures details, produces reports, coordinates |
| 171 | | work, etc.] |
| 172 | | |
| 173 | | Success Criteria [How does the user define success? |
| 174 | | How is the user rewarded?] |
| 175 | | |
| 176 | | Involvement [How the user is involved in the project? Relate where possible to |
| 177 | | RUP workers—that is, Requirements Reviewer, etc.] |
| 178 | | |
| 179 | | Deliverables [Are there any deliverables the user produces and, if so, for whom?] |
| 180 | | |
| 181 | | Comments / [Problems that interfere with success and any other relevant |
| 182 | | Issues information go here. |
| 183 | | These would include trends that make the user’s job easier or harder.] |
| 184 | | |
| 185 | | |
| 186 | | |
| 187 | | Key Stakeholder / User Needs |
| 188 | | |
| 189 | | |
| 190 | | • Little information about group work on some team |
| 191 | | • This problem is solved with this application because all group works will |
| 192 | | be networked between the people. |
| 193 | | |
| 194 | | Need Priority Concerns Current Proposed Solutions |
| 195 | | Solution |
| 196 | | Broadcast messages |
| 197 | | |
| 198 | | |
| 199 | | |
| 200 | | Alternatives and Competition |
| 201 | | |
| 202 | | Our purpose is to tell to the IT world that we can be quality and competitive on the market. |
| 203 | | |
| 204 | | |
| 205 | | 4. Product Overview |
| 206 | | |
| 207 | | Product Perspective |
| 208 | | |
| 209 | | |
| 210 | | There are a lot of similar sites where there are parts for biography but they are not connected |
| 211 | | which one in which file, activity and etc worked, so there wouldn’t be overlap of the files and |
| 212 | | etc. |
| 213 | | Summary of Capabilities |
| 214 | | Customer Support System |
| 215 | | Customer Benefit Supporting Features |
| 216 | | |
| 217 | | Less spent time for the admin Only with few clicks you’ll get the |
| 218 | | needed information for a certain type |
| 219 | | of a person. |
| 220 | | |
| 221 | | Easier way for reviewing of |
| 222 | | the biographies |
| 223 | | |
| 224 | | Assumptions and Dependencies |
| 225 | | |
| 226 | | |
| 227 | | The web site can be accessible through mobile and PC. |
| 228 | | Cost and Pricing |
| 229 | | |
| 230 | | We’ll need a certain server where will be our web site which will have certain configuration |
| 231 | | (more users more memory ex. 500 users, 1GB ram). |
| 232 | | |
| 233 | | Licensing and Installation |
| 234 | | |
| 235 | | |
| 236 | | The application will be able to be used by everyone, but the registered users will have more |
| 237 | | possibilities and more functions. |
| 238 | | 5. Product Features |
| 239 | | The user can list all the projects that he entered or participated in. He will be also able to search |
| 240 | | thought the projects using the keywords. |
| 241 | | |
| 242 | | If a project is rewritten the user should be able to add only the year to the existing data for the |
| 243 | | project. |
| 244 | | |
| 245 | | When a user applies for a new job/project the system should select only the projects that are |
| 246 | | necessary for the new job/project so that the employer can see the experience on the user. |
| 247 | | |
| 248 | | Avoidance from additional costs. |
| 249 | | |
| 250 | | |
| 251 | | |
| 252 | | 6. Constraints |
| 253 | | • Users can limit which data will be visible for others. |
| 254 | | • Users will have access only if they are connected on the internet. |
| 255 | | • The user interface design must be simpler so that it could be handled by |
| 256 | | people with lack of computer experience. |
| 257 | | |
| 258 | | |
| 259 | | 7. Quality Ranges |
| 260 | | 7.1. Usability |
| 261 | | 7.1.1. The software must be easy to learn and operate with. |
| 262 | | 7.2. Performance |
| 263 | | 7.2.1. The system must return results in no more than 3 seconds. |
| 264 | | 7.3. Robustness |
| 265 | | 7.3.1. |
| 266 | | 7.4. Fault tolerance |
| 267 | | 7.4.1. |
| 268 | | 8. Precedence and Priority |
| 269 | | 9. Other Product Requirements |
| 270 | | Applicable Standards |
| 271 | | |
| 272 | | System Requirements |
| 273 | | |
| 274 | | Performance Requirements |
| 275 | | |
| 276 | | Environmental Requirements |
| 277 | | 10.Documentation Requirements |
| 278 | | User Manual |
| 279 | | |
| 280 | | The user manual will help the users of the software to understand better its functionality |
| 281 | | and have a full benefit from it. The manual will be detailed with all the things that the users |
| 282 | | need to know, such as what to do with the login page, what to do with the groups, |
| 283 | | assignments, user’s CV-s, events etc. According to the number of groups of users, the |
| 284 | | manual will be separated into as many parts as groups. Also there will be information |
| 285 | | about what the user has to do in an error event or some wrong input/display. All of the |
| 286 | | above will be explained graphically. |
| 287 | | On-line Help |
| 288 | | If needed, an online instruction/help will be provided, along the user manual. The online |
| 289 | | help will be used in case of a system error or wrong input/function so that the user can |
| 290 | | apply the solution fast and successful. The online help will contain information about some |
| 291 | | unpredicted action that the users may conduct and solutions. |
| 292 | | |
| 293 | | Installation Guides, Configuration, Read Me File |
| 294 | | |
| 295 | | The software does not require installation, configuration or Read Me File. The |
| 296 | | configuration, i.e. the login actions will be provided in the user manual. |
| 297 | | . |
| 298 | | |
| 299 | | Labeling and Packaging |
| 300 | | |
| 301 | | The CD cases (with the user manual and access to the software ) will be printed in black |
| 302 | | color and some simple logo. |
| 303 | | |
| 304 | | |
| 305 | | 11.Appendix 1 - Feature Attributes |
| 306 | | Status |
| 307 | | |
| 308 | | |
| 309 | | Prop • Adding new users |
| 310 | | osed |
| 311 | | • Inserting new CV-s |
| 312 | | • Inserting new assignments and |
| 313 | | events |
| 314 | | • Inserting new companies |
| 315 | | • Editing/Inserting Assignment’s details |
| 316 | | • Inserting/Editing User’s details |
| 317 | | • Inserting data has to be |
| 318 | | Simultaneously with all user’s groups |
| 319 | | |
| 320 | | Appr / |
| 321 | | oved |
| 322 | | |
| 323 | | Incor / |
| 324 | | porat |
| 325 | | ed |
| 326 | | |
| 327 | | Benefit |
| 328 | | |
| 329 | | The benefit from this project is to have all the CV-s at one place of a group of people with |
| 330 | | certain qualifications, their assignments and events they participated in. That way, all of |
| 331 | | the essential information can be found on one place, so that users could search for |
| 332 | | specific assignment/events. |
| 333 | | |
| 334 | | |
| 335 | | |
| 336 | | C • Adding new users |
| 337 | | rit |
| 338 | | • Adding new group of users |
| 339 | | ic |
| 340 | | al • Adding new projects |
| 341 | | • Administrator’s approval |
| 342 | | |
| 343 | | I • Assigning users to projects/events |
| 344 | | m |
| 345 | | • Inserting/Editing user’s information |
| 346 | | p |
| 347 | | or |
| 348 | | ta |
| 349 | | nt |
| 350 | | |
| 351 | | U • User manual |
| 352 | | s |
| 353 | | ef |
| 354 | | ul |
| 355 | | |
| 356 | | |
| 357 | | Effort |
| 358 | | |
| 359 | | |
| 360 | | The implementation of this project will be conducted in the time period of 18-24 |
| 361 | | months. User’s training will be conducted in the time period of 1-7 days. The full |
| 362 | | amount of time to implement this software in the society is 24-30 months. |
| 363 | | Risk |
| 364 | | |
| 365 | | |
| 366 | | The risk of the development/implementation of this software is the consistency of |
| 367 | | the data different users has access to, therefore misleading users that use the |
| 368 | | software. |
| 369 | | |
| 370 | | Stability |
| 371 | | |
| 372 | | Target Release |
| 373 | | |
| 374 | | Assigned To |
| 375 | | |
| 376 | | Reason |
