CoDBIS Biography

Vision

Version <1.1>

Table of Contents

1.Introduction

1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview

2.Positioning

2.1 Business Opportunity
2.2 Problem Statement
2.3 Product Position Statement

3.Stakeholder and User Descriptions

3.1 Market Demographics
3.2 Stakeholder Summary
3.3 User Summary
3.4 User environment
3.5 Stakeholder Profiles

3.5.1 <Stakeholder Name>

3.6 User Profiles

3.6.1 <User Name>

3.7 Key Stakeholder / User Needs
3.8 Alternatives and Competition

3.8.1 <a Competitor>
3.8.2 <another Competitor>

4.Product Overview

4.1 Product Perspective
4.2 Summary of Capabilities
4.3 Assumptions and Dependencies
4.4 Cost and Pricing
4.5 Licensing and Installation

5.Product Features

5.1 <a Feature>
5.2 <another Feature>

6.Constraints

7.Quality Ranges

8.Precedence and Priority

9.Other Product Requirements

9.1 Applicable Standards
9.2 System Requirements
9.3 Performance Requirements
9.4 Environmental Requirements

10.Documentation Requirements

10.1 User Manual
10.2 Online Help
10.3 Installation Guides, Configuration, Read Me File
10.4 Labeling and Packaging

11.Appendix 1 - Feature Attributes

11.1 Status
11.2 Benefit
11.3 Effort
11.4 Risk
11.5 Stability
11.6 Target Release
11.7 Assigned To
11.8 Reason

Vision

1.Introduction

Software (web site) for research group of people data base
The purpose of this document is to collect, analyze, and define high-level needs and features web site Biography. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. The details of how the web site Biography fullfils these needs are detailed in the use-case and supplementary specifications.

1.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.

1.2 Scope

Scope of this vision refers to the website biography, which will be developed by the team ALDIS. Prof. Vangel us open space ​http://develop.finki.ukim.mk/projects/biography where you can work on this system.

1.3 Definitions, Acronyms and Abbreviations

BIO - Biography project - Refers to the project that users worked on, all kinds of labor, articles, assignment, papers.

1.4 References

Beside this document we have other documents for example: weekly reports, interview, presentations and etc.

1.5 Overview

This document represents the vision of the software, review and access to the software.

2.Positioning

2.1 Business Opportunity

The software will be used for reading, searching and discovering certain information, files etc, for a certain person.

2.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 is Searching of one person whose files have wrote and what worked. a successful solution would be Here the files are connected with that person and he can add and summarize.

The problem of	Making many copies of part from our biographies and there are many different types of biographies
Affects	For now everybody that makes biographies
the impact of which is	That who makes more copies
a successful solution would be	will not allow duplication

2.3 Product Position Statement

For	For now everybody that makes biographies
Who	They have filtering
The (product name)	Web software for biography
That	Simpler way of having more biographies on one place
Unlike	There is many other similar applications (getcited.org) Getcited it allow us to write anything and leave it like that but it offers option to linking with another that is not the best solution.
Our product	But our application requires early filtering. Much better is premature filtering because from the beginning we can know whether there is already an existing part (element) and we can add to so there is no duplication.

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.

3.1 Market Demographics

Our small team that work on this project is respected by the users on this project (application). Users will be very surprised by the characteristics and opportunities that will be shown in this software. Help on the users will be big because they will not take care about the group tagging on projects and classification on info about their work and activities that want to put in their biographies.

3.2 Stakeholder Summary

Name	Represents	Role
Biography writer	Main users on this application	They will write information about their work
Direct users	Users who read the biographies from this application	People who will see the work on the people their shared work, people who are interested about some projects, events etc.
Administrator	Maintenance, help and error corrections on users and biographies	User who give priorities and other opportunities to other users on this application
Indirect users	Users who read biographies taken from this software	Read information about writers on biographies given by other user(direct user)
Project manager	Stakeholder that is primary for leading the system development.	Plans, manages, coordinates activities between developers and users

 

3.3 User Summary

Name	Description	Stakeholder
Biography writer	Primary(Main) end user
Direct users	End user of the software
Administrator	End user with different tasks from "Writer"

3.4 User Environment

Users can use this application from every networked device, in every time of the day and from different locations. For writers best use is on PC because they will have difficulties if they want to write from other machine with that possibilities, others can use this application (read biographies) on every device.

3.5 Stakeholder Profiles

3.5.1 <Stakeholder Name>

Representative	Biography writer
Description	Main users on this application
Type	Different type of users but big probability to be business man, expert or casual user
Responsibilities	Idea to have group biographies and one copy from their biographies and easy way to find priority informations
Success Criteria	[How does the stakeholder define success? How is the stakeholder rewarded?]
Involvement	They are main users and they write their biographies in this application
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

Representative	Direct users
Description	Users who read the biographies from this application
Type	Every people not important if there are experts, guru etc.
Responsibilities	Easy way to find information about writers
Success Criteria	Categorizated information about biography writers and easy way to find what are they interested
Involvement	They ar involved
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

Representative	Administrator
Description	Maintenance, help and error corrections on users and biographies
Type	expert in information technology
Responsibilities	Give priorities and other opportunities to other users on this application
Success Criteria	[How does the stakeholder define success? How is the stakeholder rewarded?]
Involvement	Maintenance of the application
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

Representative	Indirect users
Description	Users who read biographies taken from this software
Type	expert or business man from some business branch
Responsibilities	Read and analyze biographies
Success Criteria	[How does the stakeholder define success? How is the stakeholder rewarded?]
Involvement	Read parts taken from application
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

Representative	Project manager
Description	Stakeholder that is primary for leading the system development
Type	expert in information technology and software engineering
Responsibilities	manage the development on this project
Success Criteria	[How does the stakeholder define success? How is the stakeholder rewarded?]
Involvement	Give tasks to developers
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

3.6 User Profiles

3.6.1 <User Name>

Representative	Biography writer
Description	Primary (Main) end user
Type	Different type of users but big probability to be business man, expert or casual user
Responsibilities	Idea to have group biographies and one copy from their biographies and easy way to find priority informations
Success Criteria	[How does the user define success? How is the user rewarded?]
Involvement	They are main users and they write their biographies in this application
Deliverables	[Are there any deliverables the user produces and, if so, for whom?]
Comments / Issues	/

Representative	Direct users
Description	Users who read the biographies from this application
Type	Every people not important if there are experts, guru etc.
Responsibilities	Easy way to find information about writers
Success Criteria	Categorizated information about biography writers and easy way to find what are they interested
Involvement	They ar involved
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

Representative	Administrator
Description	Maintenance, help and error corrections on users and biographies
Type	expert in information technology
Responsibilities	Give priorities and other opportunities to other users on this application
Success Criteria	[How does the stakeholder define success? How is the stakeholder rewarded?]
Involvement	Maintenance of the application
Deliverables	[Are there any additional deliverables required by the stakeholder? These could be project deliverables or outputs from the system under development.]
Comments / Issues

3.7 Key Stakeholder / User Needs

• Little information about group work on some team or people
  o This problem is solved with this application because all group works will be networked between the people.
  
• Users search in big quantity of information to find something for which are interested
  o This problem is solved because information will be categorized and the search into information will be easy.
  
• Searching information about people is very boring and difficult
  o Information about people on one place.
  

Need	Priority	Concerns	Current Solution	Proposed Solutions
Broadcast messages

3.8 Alternatives and Competition

Our purpose is to tell to the IT world that we can be quality and competitive on the market.
There are some alternative software that are our competitors
​http://getcited.org/
​http://writerssummit.com/biography-software.php

4.Product Overview

4.1 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.

4.2 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.
Easier way for reviewing of the biographies

4.3 Assumptions and Dependencies

The assumption that is a web site.

4.4 Cost and Pricing

/

4.5 Licensing and Installation

/  

5. Product Features

5.1 The user can list all the projects that he entered or participated in.
5.2 User can search thought the projects using the keywords.
5.3 If a project is rewritten the user should be able to add only the year to the existing data for the project.
5.4 When a user applies for a new job/project the system should select (using keywords) only the projects that are necessary for the new job/project so that the employer can see the experience on the user.
5.5 User can create new project.
5.6 User can add people on existing project.
5.7 User can create profile with personal informations.
5.8 Editing/Inserting project details.
5.9 Inserting/Editing User’s details.
5.11 Creating companies.
5.12 Creating events.

6. Constraints

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

Feature	Release	Priority
5.1 List all projects	1	High
5.2 Search projects	1	High
5.3 Rewrite project	1	High
5.4 Applying for a job	1	High
5.5 New project	1	High
5.6 Add people to project	1	High

9. Other Product Requirements

9.1 Applicable Standards

9.2 System Requirements

9.3 Performance Requirements

9.4 Environmental Requirements

 

10. Documentation Requirements

10.1 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.

10.2 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.

10.3 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.

10.4Labe ling 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

11.1 Status

Proposed - Adding new users

• 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

Approved

• Adding new users
• Inserting new CV-s
• Inserting new assignments and events
• Inserting new companies

Incorporated /

11.2 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.

Critical-Adding new users

• Adding new group of users
• Adding new projects
• Administrator’s approval

Important-Assigning users to projects/events -Inserting/Editing user’s information Useful-User manual

11.3 Effort

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.

11.4 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.

11.5 Stability

After detailed analysis of the system’s needs, we have come to conclusion that the basic features, such as adding new users, inserting new CV-s and new assignments are fully understand and our point of view for them will not change during development. If something is to be changed during development, we have decided that the change will be implemented only if all of the team members agree of the change and all of them have the full understanding of the change. After analyzing all of the features, the team members have decided if there is need for a feature change, it will have small impact on the development or none at all. Development priorities are: inserting new users, new CV-s and events.

11.6 Target Release

11.7 Assigned To

11.8 Reason

Adding new users – This feature is needed because the users will use the system and its full capabilities, based on their authorization

• Inserting new CV-s – This feature is needed because this is essential part of the system, explaining other user’s capabilities and experience, and also events and assignments they have worked on

• Inserting new assignments and events – Explaining the assignments and the work done to complete the assignment that the users have done in the past or present

• Inserting new companies – Searching for specific assignments and people with certain qualifications

• Editing/Inserting Assignment’s details – Better understanding of the assignments by the users of the system

• Inserting/Editing User’s details - Better understanding/updating user’s information

• Inserting data has to be simultaneously with all users’ groups – Preventing errors and wrong displays to the users of the system

• Adding new users – Enlarging the system and making it more efficient

• Inserting new CV-s – After a new user is added, it is essential that a new CV is inserted, explain user’s experience

• Inserting new assignments and events – Information about the current work for a new assignment/event