DOC PREVIEW
WVU CS 430 - Mathodactyl

This preview shows page 1-2-22-23 out of 23 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 23 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 23 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 23 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 23 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 23 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

MathodactylSoftware Requirements SpecificationFebruary 14, 2008Team IllusionJoshua DodsonPhilip FahnestockStephen SchoenbergerNathan Vickers1.0 IntroductionThe goal of team Illusion is to set up a convenient and easy to use website whichaccesses a Mathodactyl, a math program deployed in Kanawha county schools to unify and guide their curriculum, database and offers the teachers using the program a chance to check up on grades, student information, and problem sets.The website also offers administrators the chance to view a table of Error logs, sent by the program to the website, which describe various problems that may have occurred within the program’s runtime. The website design will be implemented using a number of drop down menus, search bars, and charts describing all student info, grades, and problem sets. These charts will be pulled straight from the Mathodactyl database itself and neatly organized for the website and casual viewing. The website designed for Mathodactyl will be accessible from anywhere with a stable internet connection, and is viewable by any Windows or Linux operating system. 1.1 Goals and objectivesAs always, Team Illusion is concerned with the user and operator of this system, so our number one goal and objective is to deliver a product which satisfies the customer’s needs and wants. With a firm foothold in place with the customer our objective thereafter is to deliver a website which performs exactly as expected and delivers all the necessary information that is needed. In addition to stability and correctness, our next goal is to establish a website that is easy to use, and convenient for the user. Offering charts, drop down menus, and more, we hope to build awebsite which can accomplish this ease of use. As a final objective we want to be able to ensure our website will work in the future. Therefore wewill make weekly checks on the website to ensure that it is up to par with the users needs. 1.2 Statement of scopeThe websites works based upon a number of major inputs. These inputs have very simple and easy to use forms. Inputs will either be selected by clicking areas of the website which are labeled accordingly, or selected information from drop down menus. Since all the data from the Mathodactyl database will be available from the website, each bit of information to be selected from the drop down menus is ensured to be an available selection. In other words you will not be able to select a student from the website which has been deleted from the database in Mathodactyl. When an input is selected, say student name, then thedatabase is queried and all information regarding that student is retrieved and sent to the user as an output. There are several ways to query the database of Mathodactyl, and some of these methods may include checking for student information, student scores, problem sets, problem descriptions, and the website could be used for some administrators to check Error Logs of the program Mathodactyl. 1.3 Software contextThe big picture of this program is such that a teacher will be able to check online to see the progress of his/her students. The teacher will be able to view student records, as well as make minor changes to the problem sets,incase he/she decides that the problem is insufficient. In other words this website will be a convenient workplace away from work allowing the user access to Mathodactyl without being at the school itself. 1.4 Major constraintsIt is implied that the user have an actively deployed Mathodactyl database within their school. Without this, the website will not function correctly. Website creators will deal with the link between the two, so this is not a concern. All navigation of the website is done with the mouse, so this will be needed on the website accessing computer. 2.0 Usage scenarioThis section provides a usage scenario for the software. It organized information collected during requirements elicitation into use-cases. 2.1 User profilesTeacher: The teacher will have the ability to login to the system, view and alter problem sets as well as student grades.Administrator: The administrator will be able to view problem sets, grades, and error logs while having the ability to add or remove users.2.2 Use-cases 2.3 Special usage considerationsThe administrator will not have the ability to alter anything within the system. 3.0 Data Model and DescriptionThis section will describe the interactions of the Website with the MySQL database of Mathodactyl. 3.1 Data DescriptionWithin Mathodactyl website the following tables will be accessed.ErrorLog: Errors encounter when running the main program.GradeTotal: Total grades of all students are shown.ProblemScores: The score for each student on individual problems.Problems: Shows the set number plus the problems in the set.Students: Shows a list of students.TotalScore: Overall Total scores.3.1.1 Data objectsErrorLogIDError_NameError_NumberGradeTotalNametotalScorepercentProblemScoresNameSet_NumberProblem_NumberProblem_ScoreProblemsSet_NumberProblem_NumberProblemHint1Hint2Hint3Hint4Anwser1Anwser2Anwser3Anwser4Picture_PathStudentsIDNameTeacherPasswordTotalScoreNameSet_NumberTotal_Score3.1.2 RelationshipsThe following ER diagram generated from the MySQL database structure already in place is shown below. This diagram shows the relationships thatwill exist between tables.4.0 Functional Model and Description 4.1.1 Description for Function Login 4.1.1.1 Processing narrative (PSPEC) for function LoginThe user will enter a username and password into a web page which will query the database to either allow or deny them access to the site. 4.1.1.2 Function Login flow diagram 4.1.1.3 Function Login interface descriptionThe inputs to the login function will be the users username and password. These inputs will then be directed to a database table in which the login credentials will be verified. If the credentials are validated the user will be logged into the system. 4.1.1.4 Performance IssuesThere will be no performance issues that will need to be consideredin the login subsystem. The database allows for and handles concurrent connections. 4.1.2 Description for Function View Individual Grades4.1.2.1 Processing narrative (PSPEC) for function View Individual GradesThe user will select the individual student that they want to view thegrades on. Once this selection is made the information will be retrieved from the database and displayed to the


View Full Document

WVU CS 430 - Mathodactyl

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download Mathodactyl
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Mathodactyl and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Mathodactyl 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?