Team #10
This presentation is the property of its rightful owner.
Sponsored Links
1 / 87

Student Scheduling System Part II FCR ARB PowerPoint PPT Presentation


  • 55 Views
  • Uploaded on
  • Presentation posted in: General

Team #10. Student Scheduling System Part II FCR ARB. Bo Wang, Bohan Zheng , Chenyang Bai , Xiaoran Li, Rui Tong, Shuai Wang, Frank Varela. Remote Team Member. Team’s Strong Points. Operational View. Technical View.

Download Presentation

Student Scheduling System Part II FCR ARB

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Student scheduling system part ii fcr arb

Team #10

Student Scheduling System Part II

FCR ARB

Bo Wang, BohanZheng,

ChenyangBai, Xiaoran Li,

Rui Tong, Shuai Wang,

Frank Varela


Remote team member

Remote Team Member


Team s strong points

Team’s Strong Points

Operational View

Technical View

Extensive knowledge of programming languages/environments.

Low Level: Assembly, C/C++

Managed languages: C#, Java

UI: QT, MFC

Scripting: PHP, Python, Perl

Web: HTML, JavaScript, CSS, XML, JSP

Database: MySQL

IDE: Eclipse, Visual Studio, Dreamweaver

  • Highly motivated.

  • Shared responsibilities.

  • Good team players.

  • Diligent and hard working.

  • Punctual with deliveries.

  • Good negotiation skills with client.

  • Good project management.

    • Very responsive.

    • Milestone/delivery tracking.

    • Provides extra motivation.

      • Ends almost all e-mails with “Fight On!”


Team s weak points

Team’s Weak Points

Operational View

Technical View

No team member has any experience with some of the libraries and or frameworks utilized in the leveraged software.

PLAY framework.

  • Lack of collaborative history between some teammates.

    • First time the off-campus student is working with any of the team members.

  • Ineffective team communication.

    • Sparse details in meeting notes.

      • No action items linked to owners.

      • Open issues not highlighted.

      • Progress of tasks unclear.

    • No regularly scheduled team meeting.

      • Schedule complexity among all members of team makes it difficult to regularly meet.


Technical concerns

Technical Concerns

  • Concern #1:

    • Lack of prior experience/understanding of the primary “Solver” algorithm.

    • Possible Solution:

      • Increase frequency and effectiveness of communication with the algorithm designer.

  • Concern #2:

    • Relatively low practical “Real World” development experience.

    • Possible Solution:

      • Increase effective communication amongst team in to collaborate and collectively solve challenges and resolve any road blocks.


Operational risks

Operational Risks

  • Risk #1:

    • Lack of a regular “effective” communication due to very busy schedules for each team member.

    • Possible Mitigation:

      • Increase verbosity in team meeting notes.

        • List open issues and proposed resolution strategies.

        • Specify status of tasks in progress.

        • Enumerate action items with assigned owners and delivery dates.

      • Make usage of more collaboration tools.

        • Shared project pages (e.g. Wiki or discussion board).

        • Collaborative document editing/sharing tools (e.g. Google Docs).

      • Schedule at least 1 team meeting on a regular basis.

        • It could be on the weekend or more convenient time for everyone.

        • It doesn’t have to be long, just enough to make sure that no critical issues are blocking people.


Requirements

Requirements


Based on last year project

Based on last year project.

  • Current scenario: Manually choose courses

  • Problem with current system: Slow solver

  • Project shared Vision:

    1. Run faster

    2. Enhance system GUI


Student scheduling system part ii fcr arb

There is only ONE main goal!

That is


Five categories

Five categories


Algorithm level of service

Algorithm & Level of Service


System constraints

System Constraints


User interface

User Interface


Tools and languages

Tools and Languages


Operational concept description

Operational Concept Description


System purpose

System Purpose


Student scheduling system part ii fcr arb

  • The vision for this system is to create an easier and less complicated way for students to be able to create schedules in order for them to graduate in the time frame they desire.

  • The major goal for system part II is to improve efficiency for students to generate study plan with more clear and friendly user interface.


Student scheduling system part ii fcr arb

Shared Vision


Student scheduling system part ii fcr arb

  • The Program model


Student scheduling system part ii fcr arb

  • Benefits Chain Diagram


Student scheduling system part ii fcr arb

SystemBoundary&Environment


Student scheduling system part ii fcr arb

System Objectives Constraints & Priorities


Student scheduling system part ii fcr arb

  • Capability Goals


Student scheduling system part ii fcr arb

  • Levelof Service Goals


Student scheduling system part ii fcr arb

  • Organizational Goals


Student scheduling system part ii fcr arb

OG-1: Improve better user satisfaction via clearer and friendlier user interface design.

OG-2: Reduce frustration of the course director via better error hint during degree program construction phase.

OG-3: Reduce frustration of the course director and students during study plan construction phase.


Student scheduling system part ii fcr arb

OG-4: Save time by allowing students to create schedules on their own time.

OG-5: Reduces incorrect course selection.

OG-6: Improve speed and reduce the study plan construction time via more efficient algorithm.


Student scheduling system part ii fcr arb

  • Constraints


Student scheduling system part ii fcr arb

CO-1: Zero Monetary Budgets.

CO-2: The system must use technological infrastructure that can be maintained by client.

CO-3: The current system shall be compatible with the previous version of the system written by the Play Framework and MySql.


Student scheduling system part ii fcr arb

Proposed New System


Student scheduling system part ii fcr arb

  • Element Relationship Diagram


Student scheduling system part ii fcr arb

  • Business Workflows


Student scheduling system part ii fcr arb

  • Organizational and Operational Implications


Student scheduling system part ii fcr arb

  • OrganizationalTransformations


Student scheduling system part ii fcr arb

  • The need to make sure that the if the server in SIT could support for the proposed system

  • The need to hire a maintainer to take care of the system.

  • The need for system to store study plans.

  • The need separately store courses, course groups, requirements and degree programs in database.


Student scheduling system part ii fcr arb

  • OperationalTransformations


Student scheduling system part ii fcr arb

  • The course director needs to add/update degree program as following steps: add courses-> add courses groups-> add requirements ->add degree programs.


Student scheduling system part ii fcr arb

  • The course directors would have to update the degree programs online. This can be as minor as adding or updating a course in the current degree requirement or as major as adding a new degree programs and its corresponding requirements. They may also authorize any other employee (ex: a student worker, part time employee) to update degree programs.


Student scheduling system part ii fcr arb

  • The proposed systems reduce workloads for course directors. They don’t need to teach students how to generate study plan manually, update degree requirements and course selection limitation by modifying the department website than announce it to all students. Also they don’t need to help students to fix their plan bugs manually, With the proposed system, they could make any requirement change by updating database and teach students how to use the systems.


Student scheduling system part ii fcr arb

  • Students don’t need to fill in their desire in one step and wait for result coming out without error hints. With new system, students needs to fill in their desires step by step: add basic & history information-> add desire courses -> add desire course order ->relax desires -> get study plan.


Students info

Students’ info


Course selection

Course selection


Semester selection

Semester selection


Courses list

Courses List


Course information

Course information


Group list

Group List


Group information

Group information


Complex group

Complex Group


Requirement

Requirement


Degree program

Degree Program


Architecture

Architecture


Student scheduling system part ii fcr arb

Top-level Physical Architecture


Student scheduling system part ii fcr arb

Top-level Logical Architecture

Graphical

Display

User Interface

Data Set

User

Interface

Events

Data Access

Data Processing

Solver


Student scheduling system part ii fcr arb

NDI Choices

WC_2660: The current system shall be compatible with the previous version of the system written using the Play Framework and MySql.


Life cycle plan

Life Cycle Plan

  • Life Cycle Strategy

  • Project Plan for Foundation Phase

  • Key Stakeholder’s Responsibilities

  • Resource Estimation


Life cycle strategy architected agile

Life Cycle Strategy(Architected Agile)


Project plan for foundation phase

Project Plan for Foundation Phase

10/21 – 12/09


Key stakeholder s responsibilities

Key Stakeholder’s Responsibilities


Resource estimation

Resource Estimation


Resource estimation1

Resource Estimation


Resource estimation2

Resource Estimation


Student scheduling system part ii fcr arb

Feasibility Evidence

1.Business Case

2.NDI Analysis andResults

3.Major Risks

4. 5 Personas


Student scheduling system part ii fcr arb

Business Case(program model)


Student scheduling system part ii fcr arb

Cost Analysis(Personnel Costs)


Student scheduling system part ii fcr arb

Cost Analysis-Hardware and Software Costs(Development)


Student scheduling system part ii fcr arb

Cost Analysis-Hardware and Software Costs(Operation)


Student scheduling system part ii fcr arb

Benefit Analysis

With the Student Scheduling System, students can reduce the time and effort of making study plan. What is more, this system can also save time for both students and advisors by reducing their conversation time about study plan.


Student scheduling system part ii fcr arb

ROI Analysis

Note: In 2013, cost just contains Fall semester(Exploration, Valuation and Foundation period).

In 2014, cost contains Spring Semester(Development and Operation period), Fall Semester(Maintenance period). Benefit contains Fall Semester.


Student scheduling system part ii fcr arb

Figure 1: ROI Analysis Graph


Student scheduling system part ii fcr arb

NDI Analysis and Result

(1) MySQL

It is used for implementing database entities and module, such as save course information and constraints about course select. It is quite capable for database needs and brings no extra costs since it is open source,and it can applied to all platform.

(2) Paly Framework

It is used for User Interface and Controllers. It will save a great deal of time on implementing controller interface, since it has a large number of modules, and there is no need to find other integration frameworks. With the aid of Play Framework, more focus can be given on more risky aspects of the project.


Student scheduling system part ii fcr arb

Major Risks


Student scheduling system part ii fcr arb

Personas

Andrew: Freshman in SIT Computer Science School

Description:

Andrew just graduated form BYD high school and got offer from several Universities, then he decided to go to SIT and major in computer science. Cause he interested in programming Apps for cellphone since he was in middle school.

User Scenario:

Andrew has designed 3 Apps for ios platform and he is familiar with C language and Java. But on the other hand,he is confused about what other knowledge the SIT CS School offer can attract him because he want to get more skill about CS not only cellphone Apps.

Basic Demographic:

Age: 18

Gender: Male

Occupation: CS Student

Hometown: New York City

Marital Status: Not Married

Goals and Aspirations:

Explore more knowledge in CS

Finding domain he does not touch before and related courses.

Keep developing his interest in programming Apps for cellphone.

Attributes:

Interested in CS

Already have some basic knowledge and practical experience in coding.

Information source:Gmail, Facebook, Twitter.


Student scheduling system part ii fcr arb

Personas

Tracy: Failed in two exams and retake courses

Description:

Tracy is a Junior student in SIT, she Failed in two final exams last year, so she need to retake the two courses this year and get the credit back.

User Scenario:

Tracy failed in the exam last semester but she do not think it is her real ability. She wants to prove herself in the coming semester ans she has to retake the two courses this year, she want to know how to conduct it.

Basic Demographic:

Age: 21

Gender: Female

Occupation: CS Student

Hometown: Chicago

Marital Status: Not Married

Goals and Aspirations:

She wants to take courses which are more helpful to her to get practical skills

She want to graduate in time although she is changing major, so she want to take as more courses as possible.

Attributes:

Retake courses

Busy schedule

Information source:Gmail, Facebook, Twitter.


Student scheduling system part ii fcr arb

Personas

Lucy: Double major student in SIT CS School and Political School

Description:

Lucy was top students in class science she was in middle school, she has talent absorbing all kinds of knowledge, so she can get more knowledge than others using same times. What is more, she is eager to learn different things and exploring different domain.

User Scenario:

Occupied with the strong ability of learning, Lucy has enough times and energy to handle two major’s courses. At the same time, she should be careful of the time conflicts of courses, because her schedule is very busy.

Basic Demographic:

Age: 19

Gender: Female

Occupation: CS, Political student

Hometown: Boston

Marital Status: Not Married

Goals and Aspirations:

She wants to arrange her time reasonable, so she should make sure which course must be take in a certain semester(some courses just offered in one semester in the whole year) and the priority among courses. She also wants to know how much courses she can take in one semester.

Attributes:

Double major

High talent

Busy schedule

Information source:Gmail, Facebook, Twitter.


Student scheduling system part ii fcr arb

Personas

Byron: Transfer student in SIT CS School

Description:

Byron has finished freshman and Sophomore study in IIT, and he decide to transfer to SIT this summer, because he think it is near his hometown and SIT’s CS department is more competitive.

User Scenario:

Byron his finished first two years study in IIT major in CS, so he has take the basic courses in CS, and he found him self interest in software engineering, he also get excellent performance in his classes.

Basic Demographic:

Age: 20

Gender: Male

Occupation: CS Student

Hometown: New Jersey

Marital Status: Not Married

Goals and Aspirations:

He want to transfer his credit form IIT to SIT and do not take same courses again.

He want to development his interest in software engineering.

Attributes:

Transfer student

Already took two years courses in CS

Information source:Gmail, Facebook, Twitter.


Student scheduling system part ii fcr arb

Personas

Jordan: One of the administrators in SIT CS School

Description:

Jordan is a administrators in CS School, he got married 3 years ago and know he has a 2 years old daughter. His duty is to input courses and course’ introduction to the Study Scheduling System. Also has duty to help students make their study plans.

User Scenario:

Because many students confused by the course selecting rules, so Jordan has to introduce many details to students, which will take a lot of time and lead to repeating work and work overtime. On the other hand Jordan wants to spends more time with his daughter.

Basic Demographic:

Age: 30

Gender: Male

Occupation: Administrators in CS

Hometown: New York City

Marital Status: Married

Goals and Aspirations:

He wants a system to lighten his workload, which can easily accept by students in short time.

He also needs higher limits of authority, so he can add courses or delete courses depend on need, sorting courses, affirming the degree requirement.

Attributes:

Repeating work

Work overtime

Busy

Information source:Gmail, Facebook, Twitter.


Quality focal point

Quality Focal Point


Student scheduling system part ii fcr arb

Traceability Matrix


Student scheduling system part ii fcr arb

Quality Management Strategies

  • ToolsBugzillaWinBook

  • Defect Prevention Strategies

  • Prototyping, Dry Run, Project Reviews

  • Incremental Commitment Model Standard

  • Defect Identification Strategies

  • Team Artifact Process Reviews

  • IIV&V Reviews, Auxiliary Reviews

  • IIV&V Coordination


Student scheduling system part ii fcr arb

Defect Removal Tracking


  • Login