Rev.: 0.1
Revision History
| Rev. | Date | Author | Change Description |
| 0.1 | 2014-10-08 | Bogdan Semjanik | Add user stories, scope and high-level requirements. |
| 0.2 | 2014-10-13 | Bogdan Semjanik | Add use-case diagram, terms and definitions, solution highlights and diagram high-level design. |
1 System vision. 4
1.1 Document purpose. 4
1.2 Scope. 4
1.2.1 High-level requirements. 4
1.2.2 Out of scope. 4
The following is out of scope of this application: 4
1.3 Terms, abbreviation and definitions. 4
1.4 References. 5
2 Preliminary Epics and User Stories. 6
2.1.1 Preliminary use case diagram.. 6
2.1.2 Preliminary epics and user stories. 6
3 Solution Highlights. 7
AttachmentA. High-leveldesign. 8
System vision
Document purpose
The purpose of this document is to collect, analyze, and define high-level needs and features of the Application. It focuses on the capabilities needed by the clients and the target users, and why these needs exist. The details of how the Application fulfils these needs are detailed in the supplementary documentation.
Scope
Должна быть разработана система управления учебными курсами, которая позволяет взаимодействовать нескольким видам пользователей (лектор и студент). Базовой функциональностью системы является возможность одних пользователей добавлять учебные курсы, а других – проходить обучение по выбранным курсам и оценивать полученные знания посредством прохождения контрольных тестов.
Эта система даст возможность изучать курсы удаленно тем пользователям, которые, по различным причинам, не смогли бы получить эти знания иным способом. Так же система предназначена для студентов как заочной так и дневной форм обучения.
Данная система предоставляет возможность пользователям типа «Лектор» автоматизировать процесс контроля знаний и обучения студентов.
High-level requirements
· Lecturershouldbeabletocreatenewcourses, lessonsandquestionnairesandpopulatethemwiththeactualdata, attachrelatedmaterials, etc.
· Thereshouldbeanemailnotificationmechanismtonotifyaboutsystemevents (subscriptions, progressing, etc).
· Studentshouldbeabletosubscribe/unsubscribefrom a particularcourse, proceedthroughthelessons, andpasstestsbasedonthequestionnaires.
· Optional: Thereshouldbe a markcalculationsystembasedonquestionnairesresults.
· Optional: Lecturershouldbeabletokeeptrackofthestudents’progress, rejectoracceptquestionnairesresults.
· Optional: Thereshouldbe a possibilityfortheparticipantstocommunicate, provideandreceivefeedback, comments, etc.
Out of scope
The following is out of scope of this application:
· Item 1
· Item 2
· Item 3
Terms, abbreviation and definitions
| Course | Some training program composed lecturer to study students. |
| Lector | Registrated teacher. |
| Student | Registrated user, who use this system for study some courses. |
| CMS | Course Management System – web-application for study. |
| Test | Some set of questions after each lesson for test of knowledge. |
| Exam | Set of questions after each course for the final assessment. |
| Lesson | Set of materials which provides a lector and associated with a specific theme. After each lesson there is a question to control mastery of the material. |
References
No references
| ## | Date | Document Title | |
| 1. | |||
Preliminary Epics and User Stories
Preliminary use case diagram
Figure 1[Solution Name] actors and use-cases
Preliminary epics and user stories
Our user-stories:
· Work with courses:
Lector can create, edit and delete courses, lessons and test. Thus, the lecturer provides educational materials for students and students can study.
· Exchange messages:
Personal communication between users.Some messenger, through which students can communicate with lecturers for more productive learning.
· Comments:
Anyone registered user can write a comment to the course or lesson.
· Assessment of student:
Lector can check the open-ended question, rate and approval of the final assessment.Thus, a lecturer independently assess a student's knowledge, so evaluation would be more correct.
· Notification by e-mail:
A student who has subscribe for some courses will receive an e-meil any updates (new lessons, for example).
· Subscribe and unsubscribe courses:
Student can to choose and subscribe or unsubscribe to courses. If a student signed, on his e-mail address will be sent to a variety of news related to its subscriptions.
· Learning lessons:
Student can view some materials and lessons.Student can view history of visited courses.
· Intersystem notifications:
The system includes notification about upgrading for witch the user has subscribed.Each registered user can get notifications about different news at system. For example, for lector it can be notification about successful completion of the test some student.
· Rating of courses:
Every registered student can evaluate courses.It’snecessary for all other student, because user can choose course with a higher rating.
· User settings:
Settings of behavior of the system for user. User can configure notifications at system and by e-mail, their subscriptions and other.
· E-mail alerts:
System can send alerts on E-mail about registration, password recovery, courses and students who have passed tests.
· Registration:
Guest can enter data for registration and choose type of user. By that, guest canregistrer as a student or lecture.
· Password recovery:
Guest can send a request for password recovery and it will be sent an email message with instructions.
· Login:
Guest can enter data for authorization in the system.
· Getting info:
Guest can get information about the selected course.
· News:
All users can read news.Moderator and administrator can add news.
· Assessment view:
Student can see his assessment results of test and exam.
Solution Highlights
The following should be considered during implementation:
· First version of the solution has to be delivered in very short term and with minimal budget.
Key highlights in the version 1:
· Work with courses:
Lector can create, edit and delete courses, lessons and test. Thus, the lecturer provides educational materials for students and students can study.
· Learning lessons:
Student can view some materials and lessons.
· Registration:
Guest can enter data for registration and choose type of user. By that, guest canregistrer as a student or lecture.
· Login:
Guest can enter data for authorization in the system.
· Intersystem notifications:
The system includes notification about upgrading for witch the user has subscribed.Each registered user can get notifications about different news at system. For example, for lector it can be notification about successful completion of the test some student.