Student Curriculum Planning System MSE Project Presentation I Kevin Sung

Overview  Background/Motivation  System Overview  Requirements/Use cases  Project Plan  Cost Estimation  Software Quality Assurance Plan  Architecture Elaboration Plan  Demonstration

Background  Currently, CIS Department provide curriculum flowchart file online for reference.  No automation application for student curriculum planning from the department. College of Engineering flowchart system  The communication between advisor and student are still paper base.

CIS Flowchart Example

Motivation and Goals  Main motivation is to provide automation application for CIS student curriculum planning for students and advisor.  Also, to provide an new communication medium between students and their faculty advisor.

System Overview  System front-end and logic will be developed under ASP.NET with C#. which can will able to embedded various other languages such as XML, JavaScript, Jscript,..etc.  System back-end will be support by Internet Information Services (IIS) Server with the SQL Server for Database Support Testing will be using the MSDE server

Requirements/Use cases

Requirements  Login Requirement User will provide login name and password through login web form. Web server will verify and validate the user identity which will be either the student, academic advisor, and database administrator If login successful, web server will log the user in the user log And, the web server will generate user interface according to user identity

Requirements -- Users  Add/Drop Course Requirement User can add the course to the curriculum plan. User Inputs will be generated and validated by the system with the mean of checking the course prerequisites and other constraints prior accepting user input. User can drop course from the curriculum plan. System will assess the related changes need to be made and process them accordingly  Generate Report Requirement A option of generate a savable and/or a printable format of the plan should be provided

Requirements -- Administrator Users  Add/Drop Course Requirement Administrator can add new course to the course database. Administrator can drop (delete) a course record form the database.  Add/Drop User Requirement Administrator can add new user to database. Administrator can drop a user from the database. Administrator can change user information in the database

Project Plan  Phase I February 4 – May 17 Vision document, Project plan, Requirement, SQA plan, Prototype Presentation May 17  Phase II May 18- June 29 Updated Vision document, project plan Architecture design, Formal Requirement Specification, Test plan, Architecture prototype Presentation June 29  Phase III June 30 – Aug 19 Coding, Testing, User manual, Project evaluation Presentation Aug 19

Cost Estimation  COCOMO I model Effort = 3.2*EAF*(Size) ^1.05 Time = 2.5*(Effort) ^0.38 Where:  Effort = number of staff-months (PM)  EAF = Effort Adjustment Factor  Size = number of lines of code for completed product. It is measured in KLOC (thousands of lines of code)  Time = total number of months  The Effort Adjustment Factor is the product of the 15 adjustment parameters. Each adjustment parameter is categorized as very low, low, nominal, high, or very high.

Cost Estimation (cont.)  My adjustment factors as follow: Required reliability as nominal and a value of Database size as high and a value of Product complexity as low and a value of 0.85 Execution time constraint as nominal and a value of 1.00 Main storage constraint as nominal and a value of Virtual machine volatility as nominal and a value of Computer turnaround time as low and a value of Analyst capability as high and a value of 0.8. Applications experience as nominal and a value of Programmer capability as nominal and a value of Virtual machine experience as nominal and a value of Language experience as nominal and a value of Use of modern practices as high and a value of Use of software tools as high and a value of 0.91 Required development schedule as nominal and a value of 1.00.

Cost Estimation (cont.)  The EAF value is calculated to I estimated the size to be 3000 LOC. Effort = 3.2*0.61*(3) ^1.05 = 6.18 staff months Time = 2.5*(6.18) ^0.38 = 4.99 months (the development time)  Since the project only involved with the one staff member and the project is relatively small scale. I have project the time of completion will be a lot shorter to about 3 months.

Software Quality Assurance Plan  Review and Auditing Supervisory Committee  Three phases – Presentation Regular meeting with Major Professor  Formal Technical Inspection Technical Inspectors  Esteban Guillen  Cem Oguzhan  Functional testing

Architecture Elaboration Plan  Update Vision document, project plan, cost estimation  Architecture design Class diagram Sequence diagram  Formal requirement specification UML/OCL  Implementation plan

Architecture Elaboration Plan  Test plan  Formal technical inspection Class diagram Technical Inspectors  Esteban Guillen  Cem Oguzhan  Executable Architecture Prototype

Demonstration

Question ?