T10-Student Scheduling System Part II CS-577B Software Engineering TRR TRR Individual Presentation Student Scheduling System Part II Team 10 Shuai Wang.

Slides:



Advertisements
Similar presentations
Companies can suffer numerous problems due to poor management of resources and careless decisions. In real-world decision- making, many organizations lack.
Advertisements

Assessment of Undergraduate Programs Neeraj Mittal Department of Computer Science The University of Texas at Dallas.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Real-Time Systems Scheduling Tool Developed by Daniel Ghiringhelli Advisor: Professor Jiacun Wang December 19, 2005.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Green Software Engineering Sheryl John Introducing green elements and guidelines in Software Engineering.
Thammanoon Kawinfruangfukul CSSE MS, ID:
Stepan Potiyenko ISS Sr.SW Developer.
Software engineering, program management. The problem  Software is expensive to design! – Industry estimates put software development labor costs at.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Academic Advisor: Prof. Ronen Brafman Team Members: Ran Isenberg Mirit Markovich Noa Aharon Alon Furman.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
Faculty Information System Team Members Aaron Flocke Geetha Krishnasamy Leena Paulose James Curry.
ININ 4017 Computer-Based Information Systems 1st Semester
Chapter 2 The Process.
Implementation Considerations Yonglei Tao. Components of Coding Standards 2  File header  file location, version number, author, project, update history.
BMAN Integrative Team Project Professor Linda A Macaulay.
Software Engineering 2003 Jyrki Nummenmaa 1 CASE Tools CASE = Computer-Aided Software Engineering A set of tools to (optimally) assist in each.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Supporting Large Projects in a Small College Computer Systems Management Program Ellen L. Walker Oberta A. Slotterbeck Hiram College {walkerel,
SE3183 Advance Web Programming Programming Session 2013/2014.
Software Engineering Management Lecture 1 The Software Process.
Healthy Kids Zone Team Operational Concept Description Xu Zhang 2.
TRANSITION READINESS REVIEW GOTRLA TEAM 15 Aayush Jain, Ankith Nagarle, Anushila Dey, Deepak Earayil, Elaine Lo, Nidhi Baheti, Presha Thakkar, Suhani Vyas.
ISYS 562 Microcomputer Business Applications David Chao.
Lecture 3 Software Engineering Models (Cont.)
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Student Curriculum Planning System MSE Project Presentation I Kevin Sung.
First-Year Engineering Program Performance Test 3: Energy Optimization Objective and Goals Lab Procedure Analysis Test Readiness Review.
1 These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science.
Construction 2 BTNC-ILA ISDM Group 3. Agenda Diagram Risk Testing Progress Next Plan Demo.
Senior Design II proposal A step-by-Step review. What is Senior Design?  Senior Design is a sequence of two courses during two consecutive semesters.
Courselist Project Automated Graduate Student Information System Final project for CS 3354.
Presenter: Eghosa Ugboma Florida Memorial University
Reviews and Inspections. Types of Evaluations Formal Design Reviews conducted by senior personnel or outside experts uncover potential problems Inspections.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Mission Science By Team Team 07 Members Jiashuo Li Chen Li Sergey Mukhin Hanadi Mardah Yun Shao Farica Mascarenhas 2.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
January 4, School of Computer and Information Sciences Graduate Program Orientation University of South Alabama David L. Feinstein, Ph.D. Dean, School.
Structural Design Software TYLER HUTCHISON. Requirements  Develop an interface to generate a text file.  The text file is then passed to one of five.
Bioswales Hands-on activity Earth and Space Science Full lesson –Step 1: Reading activity –Step 2: Explore available materials –Step 3: Design a Bioswale.
D R A T D R A T ABSTRACT Every semester each department at Iowa State University has to assign its faculty members and teaching assistants (TAs) to the.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Web-based Front End for Kraken Jing Ai Jingfei Kong Yinghua Hu.
GMR – Business Workflow System (BWS) Presented by: Sulakshman Madala Kumar Konakalla Ganesh Cheedella.
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
Tieflow Workflow Toolkit -:By:- CSCI 6831 Capstone project Instructor: Dr. Kwok-Bun Yue Mentor: Mr. Scott Hetherington Midterm Presentation 04/15/2008.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
1 Assessment of Undergraduate Programs Neeraj Mittal Department of Computer Science The University of Texas at Dallas (UTD) January 22, 2016.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Study Plan by : Muhammad Rasyad Safran Ab. Rahim, Katelyn Kasperowicz, Raphael Salas, Ucchishta Sivaguru, Nabilah Farhana Yahya.
Software Engineering Management
Cash Doctor 3.0 Mobile Application
CMPE 412 Software Engineering
Theory and Practice of Web Technology
ShareTheTraining TRR ARB Presentation Team 11
Strategies For Software Test Documentation
Mission Science By Team 07.
ARB Schedule Locations
CS 577b Software Engineering II -- Introduction
CS577a Software Engineering ARB #2 Workshop
CMSC 345 Software Design and Development Spring 2004 Sections 0101 & 0201 Ms. Susan Mitchell Leave Your Ego at the Door! CMSC 345, Spring 2004.
Software Development In Agile
Presentation transcript:

T10-Student Scheduling System Part II CS-577B Software Engineering TRR TRR Individual Presentation Student Scheduling System Part II Team 10 Shuai Wang

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Project Role con’t  Exploration, Valuation and Foundation phases Prototyper – Develop algorithm prototype – Prepare development production Operational Concept Engineer – Identify system objectives, constraints and priority – Finish Operational Concept Document

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Project Role cont’d  Development Phase Builder (Focus on back-end) – System data structure designer (100%) – System data structure builder (100%) – Algorithm designer (50%) – Algorithm developer (97.5%) – Finish Algorithm Improvement Evidence Description (80%)

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Main Responsibility cont’d Design and develop back-end data structures (100%) Implement auto course selection algorithm (95%) Develop prerequisite & corerequisite calculation sub-algorithms Conduct requirement satisfaction sub-algorithms Construct interfaces between GUI and back-end algorithm controller Implement interfaces between database and back-end algorithm Implement interfaces to Import student’s desired courses into algorithm controller Finish auto assign semester algorithm (90%) Implement corerequisite satisfaction sub-algorithm Conduct “the worst earliest semester assignment” satisfaction algorithm Develop sub-routine to fill course into different semester Construct interface to get students’ desired semester from front-end

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Demo

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Algorithm Performance Analysis Time complexity: – Exponential time complexity Space complexity: – Assume: Requirement r, Course c – 2*O(rc) + O(c)  The client expects response time of system: 1 hour to calculate 1 study plan and return result.  Based on GUI error alert to guide student making feasible constraints, the system can generate study plan within 1 second and return correct result.

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Related Win condition Win condition (WC_2657): Done (100%) – The system shall auto generate the course schedule for undergraduate student given the following constraints: Degree program constraints. Students desired courses related to his schedule. Win condition (WC_2658): Done (100%) – The algorithm for generating the course schedule shall have guarantee bounds on its execution time and/or bounds on optimality.

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Additional Requirement (not in win condition) Already taken course function – It is because this requirement is given after we design the system back-end, we just prepare interfaces at the end of the CCD, but not implement it.

T10-Student Scheduling System Part II CS-577B Software Engineering TRR Thank You