REQUIREMENTS
There are three main requirements that are concerned with actors. Altough system users are many more, these actors are processing under three different user groups which have different tasks and access rights. These are the mentioned actors:
- Student
- Instructor
- System Admin
1-Requirements of the Student
1.1-Student has to be registered to the system.
1.2-Student may log in and log out from the system.
1.3-Student is able to request a problem solution by writing a problem
definition entry that is visible only to System Admin.
1.4-Student is able to search for Problem Definition & Comments
and Final Solution & Synthesis in the system.
1.5-Student is able to search for problem type
1.6-Student is able to write comments about final solution.
1.7-Student is able to view Final Solution & Synthesis.
1.8-Student is able to see some graphs about the topic
1.9-Student is able to view messages from system admin
2-Requirements of Instructor
2.1-Instructor has to be registered to the system.
2.2- Instructor has to log in and may log out from the system.
2.3-Instructor is able to Search by Intermediate Solutions and Final
Solution & Synthesis. Final Solution & Synthesis Comments
2.4-Instructor is able to search for the problem types.
2.5-Instructor has to select the best idea for problem may add his/her opinion due to make and view Final Solution & Synthesis
2.6-Instructor is able to view the graphs about the topic
2.7-Instructor is able to view topics.
2.8- Instructor is able to manage info and contact system admin.
3-Requirements of System Admin
3.1-System Admin has to be registered to the system.
3.2-System Admin has to log in and may log out from the system.
3.2-System Admin has to manage user accounts, memberships, user
rights and user access procedures and maintain system verification
such as updating and registering.
3.4-System Admin is able to Search by Intermediate Solutions and Final
Solution & Synthesis , Final Solution & Synthesis Comments , Problem
Definition & Comments
3.5-System Admin is able to create topics to the system and
also, is able to view.
3.6-System Admin is able to view the Final Solution & Synthesis
3.7-System Admin is able to write the Final Solution& Synthesis
Comments.
3.8-System Admin is able to view the Final Solution& Synthesis
Comments.
3.9-System Admin is able to add final decision to database of the system.
3.10-System Admin is able to view Graphs.
3.11-System Admin is able to make manage info and contact the other actors .
3.12-System Admin is able to view Problem Definition & Comments which
Students write on the discussion board.
3.13-System Admin is able to create message according to final comments which writes Student .
Tuesday, 18 November 2008
MEETING MINUTES
MEETING MINUTES
25/10/2008
Attendees:
Murat Albayrakoğlu (Project Client)
M.Nevzat Özyurt (Team Member)
Topics Discussed:
General Process and development of the project
Setting Up Project Web-site
Content Management
Use-case version 1
Next Meetings Topics
Work Items:
Nevzat has started the meeting.
The Version 1 of the usecase was found too much detailed by Murat Albayrakoğlu ; so it will be shortened and will be kept as simple as possible.
Final thoughts about the Project and its development.
12/11/2008
Attendees:
Mustafa Tülü (Project Supervisor)
İzzet Barokas (Team Member)
M.Nevzat Özyurt (Team Member)
Topics Disscussed
· Work Review
· The work break-down
· The milestones and work plan for the following month and for the end of the semester if possible.
· The Scope Statement
· Project Deliverables.
Work Items:
· Mustafa Tülü started the meeting
· Nevzat and Izzet presented the work handled so far to the supervisor
· Mustafa Tülü analyzed the work and told the team members the points to be checked.
· The Gantt Chart , Milestones will be done as soon as possible
· Work Break-Down sturcture will be made so that every step will be planned.
25/10/2008
Attendees:
Murat Albayrakoğlu (Project Client)
M.Nevzat Özyurt (Team Member)
Topics Discussed:
General Process and development of the project
Setting Up Project Web-site
Content Management
Use-case version 1
Next Meetings Topics
Work Items:
Nevzat has started the meeting.
The Version 1 of the usecase was found too much detailed by Murat Albayrakoğlu ; so it will be shortened and will be kept as simple as possible.
Final thoughts about the Project and its development.
12/11/2008
Attendees:
Mustafa Tülü (Project Supervisor)
İzzet Barokas (Team Member)
M.Nevzat Özyurt (Team Member)
Topics Disscussed
· Work Review
· The work break-down
· The milestones and work plan for the following month and for the end of the semester if possible.
· The Scope Statement
· Project Deliverables.
Work Items:
· Mustafa Tülü started the meeting
· Nevzat and Izzet presented the work handled so far to the supervisor
· Mustafa Tülü analyzed the work and told the team members the points to be checked.
· The Gantt Chart , Milestones will be done as soon as possible
· Work Break-Down sturcture will be made so that every step will be planned.
Monday, 17 November 2008
REQUIREMENTS VERSION 1
REQUIREMENTS
There are four main requirements that are concerned with actors. Altough system users are many more, these actors are processing under four different user groups which have different tasks and acces rights. These are the mentioned actors
:
- Decision Users
- Decision Maker
- Decision Manager
- System Admin
1-Requirements of Decision User
1.1-Decision User has to be registered to the system.
1.2-Decision User has to loged in and may loged out from the system.
1.3-Decision User is able to request a problem solution by writing a problem
definition entry that is visible only to System Admin.
1.4-Decision User is able to search for Problem Definition & Comments
and Final Solution & Synthesis in the system.
1.5-Decision User is able to view statistics in the system.
1.6-Decision User is able to write comments about final solution.
1.7-Decision User is able to view Final Solution & Synthesis.
1.8-Decision User is able to view topics
1.9-Decision User is able to view messages from system admin
2-Requirements of Decision Maker
2.1-Decision Maker has to be registered to the system.
2.2-Decision Maker has to loged in and may loged out from the system.
2.3-Decision Maker has to generate and view intermediate problem solutions due to
problems announced by the System Admin.
2.4-Decision Maker is able to Search by Intermediate Solutions Final
Solution & Synthesis. Final Solution & Synthesis Comments.
2.5-Decision Maker is able to vote on decision polls in the system.
2.6-Decision Maker is able to view Statistics.
2.7-Decision Maker is able to view topics.
2.8-Decision Maker is able to view Final Solution & Synthesis Comments
2.9-Decision Maker is able to view Final Solution & Synthesis
3-Requirements of Decision Manager
3.1-Decision Manager has to be registered to the system.
3.2- Decision Manager has to loged in and may loged out from the system.
3.3-Decision Manager is able to Search by Intermediate Solutions and Final
Solution & Synthesis. Final Solution & Synthesis Comments
3.4-Decision Maker has to generate intermediate problem solutions due to
problems announced by the System Admin.
3.5-Decision Manager has to select the best idea for problem solution by
the comments that committed by Decision Maker and may has add
his/her best idea due to making and viewing Fınal Solution & Synthesis
3.6-Decision Manager is able to view Statistics
3.7-Decision Manager is able to view topics.
3.8-Decision Manager is able to view Intermediate Solution.
3.9-Decision Manager is able to view Final Solution& Synthesis Comments.
3.10-Decision Manager is able to view topics
4-Requirements of System Admin
4.1-System Admin has to be registered to the system.
4.2-System Admin has to loged in and may loged out from the system.
4.3-System Admin has to manage user accounts, memberships, user
rights and user access procedures and maintain system verification
such as updating and registering.
4.4-System Admin is able to Search by Intermediate Solutions and Final
Solution & Synthesis , Final Solution & Synthesis Comments , Problem
Definition & Comments
4.5-System Admin is able to create topics to the system and
also, is able to view.
4.6-System Admin is able to view the Final Solution & Synthesis
4.7-System Admin is able to write the Final Solution& Synthesis
Comments.
4.8-System Admin is able to view the Final Solution& Synthesis
Comments.
4.9-System Admin is able to add final decision to database of the system.
4.10-System Admin is able to view Statistics.
4.11-System Admin is able to make and view Intermediate Solution.
4.12-System Admin is able to view Problem Definition & Comments which
writes decision user .
4.13-System Admin is able to create message according to final comments which writes decision user .
There are four main requirements that are concerned with actors. Altough system users are many more, these actors are processing under four different user groups which have different tasks and acces rights. These are the mentioned actors
:
- Decision Users
- Decision Maker
- Decision Manager
- System Admin
1-Requirements of Decision User
1.1-Decision User has to be registered to the system.
1.2-Decision User has to loged in and may loged out from the system.
1.3-Decision User is able to request a problem solution by writing a problem
definition entry that is visible only to System Admin.
1.4-Decision User is able to search for Problem Definition & Comments
and Final Solution & Synthesis in the system.
1.5-Decision User is able to view statistics in the system.
1.6-Decision User is able to write comments about final solution.
1.7-Decision User is able to view Final Solution & Synthesis.
1.8-Decision User is able to view topics
1.9-Decision User is able to view messages from system admin
2-Requirements of Decision Maker
2.1-Decision Maker has to be registered to the system.
2.2-Decision Maker has to loged in and may loged out from the system.
2.3-Decision Maker has to generate and view intermediate problem solutions due to
problems announced by the System Admin.
2.4-Decision Maker is able to Search by Intermediate Solutions Final
Solution & Synthesis. Final Solution & Synthesis Comments.
2.5-Decision Maker is able to vote on decision polls in the system.
2.6-Decision Maker is able to view Statistics.
2.7-Decision Maker is able to view topics.
2.8-Decision Maker is able to view Final Solution & Synthesis Comments
2.9-Decision Maker is able to view Final Solution & Synthesis
3-Requirements of Decision Manager
3.1-Decision Manager has to be registered to the system.
3.2- Decision Manager has to loged in and may loged out from the system.
3.3-Decision Manager is able to Search by Intermediate Solutions and Final
Solution & Synthesis. Final Solution & Synthesis Comments
3.4-Decision Maker has to generate intermediate problem solutions due to
problems announced by the System Admin.
3.5-Decision Manager has to select the best idea for problem solution by
the comments that committed by Decision Maker and may has add
his/her best idea due to making and viewing Fınal Solution & Synthesis
3.6-Decision Manager is able to view Statistics
3.7-Decision Manager is able to view topics.
3.8-Decision Manager is able to view Intermediate Solution.
3.9-Decision Manager is able to view Final Solution& Synthesis Comments.
3.10-Decision Manager is able to view topics
4-Requirements of System Admin
4.1-System Admin has to be registered to the system.
4.2-System Admin has to loged in and may loged out from the system.
4.3-System Admin has to manage user accounts, memberships, user
rights and user access procedures and maintain system verification
such as updating and registering.
4.4-System Admin is able to Search by Intermediate Solutions and Final
Solution & Synthesis , Final Solution & Synthesis Comments , Problem
Definition & Comments
4.5-System Admin is able to create topics to the system and
also, is able to view.
4.6-System Admin is able to view the Final Solution & Synthesis
4.7-System Admin is able to write the Final Solution& Synthesis
Comments.
4.8-System Admin is able to view the Final Solution& Synthesis
Comments.
4.9-System Admin is able to add final decision to database of the system.
4.10-System Admin is able to view Statistics.
4.11-System Admin is able to make and view Intermediate Solution.
4.12-System Admin is able to view Problem Definition & Comments which
writes decision user .
4.13-System Admin is able to create message according to final comments which writes decision user .
SCOPE STATEMENT
Scope Statement (Version 01)
Project Title: E-Learning Systems for Operation Management
Date: 18.10.2008(October 18, 2008)
Prepared by: M. Nevzat Özyurt & İzzet Barokas
Project Justification:
Being more helpful for students who are studying for Operation Management.
Product Characteristics and Requirements:
Product will be open source so development part of project is necessary only for setup process. And the people who want to do revision can easily make by the help of open source characteristic of the system.
Product requirements are;
· Web based Server
· Web 2.0 compliant.
· Database
· Capability of integration with major Learning Management Systems (LMSs), groupware and other collaboration tools.
· Capability to support multiple platforms on both server and client sides
· Capability of handling data from textbook problems.
· Extensive documentation of the code.
· For implementation part of project we can use animation or flash programs for taking attention of user. So that it will be more interactive and fun for the users.
· Ease of navigation
· Extensive online documentation about deployment, operation and use
· Personal computers
· Ability of integration with a sample business database.
· Built-in collaboration tools such as chat, messaging, whiteboard etc.
· Capability of handling data from case studies.
. We will use Macromedia Captivate programme for helping all users when they want to use our web page.
Summary of Project Deliverables
Project management-related deliverables:
The team contract can be read
Product-related deliverables:
1- There is no operation for this part. (writing codes)
2- Analyze documents:
· Use case:
The use case is available also on-line
Project Success Criteria:
If we can be successful to be able to do what is wanted from us , If the implementation can be created user friendly and also if people can create new ideas from by the help of this project, our projects(as an open source) that time we will be successful . Also time is very important for while setting a success criteria. Again if we finish first version of our project at 18 May, 2009 we can consider ourselves as we achieved our goal.
Project Title: E-Learning Systems for Operation Management
Date: 18.10.2008(October 18, 2008)
Prepared by: M. Nevzat Özyurt & İzzet Barokas
Project Justification:
Being more helpful for students who are studying for Operation Management.
Product Characteristics and Requirements:
Product will be open source so development part of project is necessary only for setup process. And the people who want to do revision can easily make by the help of open source characteristic of the system.
Product requirements are;
· Web based Server
· Web 2.0 compliant.
· Database
· Capability of integration with major Learning Management Systems (LMSs), groupware and other collaboration tools.
· Capability to support multiple platforms on both server and client sides
· Capability of handling data from textbook problems.
· Extensive documentation of the code.
· For implementation part of project we can use animation or flash programs for taking attention of user. So that it will be more interactive and fun for the users.
· Ease of navigation
· Extensive online documentation about deployment, operation and use
· Personal computers
· Ability of integration with a sample business database.
· Built-in collaboration tools such as chat, messaging, whiteboard etc.
· Capability of handling data from case studies.
. We will use Macromedia Captivate programme for helping all users when they want to use our web page.
Summary of Project Deliverables
Project management-related deliverables:
The team contract can be read
Product-related deliverables:
1- There is no operation for this part. (writing codes)
2- Analyze documents:
· Use case:
The use case is available also on-line
Project Success Criteria:
If we can be successful to be able to do what is wanted from us , If the implementation can be created user friendly and also if people can create new ideas from by the help of this project, our projects(as an open source) that time we will be successful . Also time is very important for while setting a success criteria. Again if we finish first version of our project at 18 May, 2009 we can consider ourselves as we achieved our goal.
Tuesday, 11 November 2008
Subscribe to:
Posts (Atom)
