1 / 46

New Vision Concept School Portal Phase I MSE Project Sindhu Thotakura Committee Members

New Vision Concept School Portal Phase I MSE Project Sindhu Thotakura Committee Members Dr. Mitchell Neilsen (Major Professor) Dr . Gurdip Singh Dr. Daniel Andresen. Outline. Purpose and Motivation Project phases Project Requirements User Interface Cost Estimation Documentation

berny
Download Presentation

New Vision Concept School Portal Phase I MSE Project Sindhu Thotakura Committee Members

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Vision Concept School Portal Phase I MSE Project SindhuThotakura Committee Members Dr. Mitchell Neilsen(Major Professor) Dr. GurdipSingh Dr. Daniel Andresen.

  2. Outline • Purpose and Motivation • Project phases • Project Requirements • User Interface • Cost Estimation • Documentation • Project Deliverables

  3. Purpose and Motivation • Developing Web application. • To excel in the language. • Inspired by ksu.edu

  4. Phases of Project • Inception Phase • Elaboration Phase • Production Phase

  5. Inception Phase • Vision Document 1.0 • Project Plan 1.0 • Software Quality Assurance Plan • Prototype

  6. Vision Document requirement elicitation, scope, purpose, and goals of the project • Project Plan 1.0 describes the tasks carried out in each phase and estimates the cost, effort and schedule. • Software Quality Assurance Plan standards and conventions of the project, required project documentation, steps to be taken to ensure project quality.

  7. Users for this system • Visitors • Students • Teachers

  8. Project Requirements

  9. Actor: Teacher

  10. User Registration • Purpose: The New User registers into the system so that he can gain access to particular information like student reports, balance due etc. • Actor: Student, Teacher • Input: The User needs to enter registration information like User Name, Password, Name, Address, Email, and Contact Number. • Output: The details entered by the User will be verified so that the Username does not get repeated, Password meets the standards. After verification, system stores the User Information in the database and gives the message saying Registration is successful.

  11. User Login/Logout • Purpose: The User can login into the system to view the particular information. • Actor: Student, Teacher • Input: The User should provide the User Name and Password to login. If the user forgets the password user can also request for the new password. • Output: The system checks the user authentication by verifying the User Name and Password given by the user matches with the details in the database. If it matches the user can successfully login to the system and access the required information.

  12. View Individual results • Purpose: The User can view the individual results in each subject along with the total marks, rank and teacher comments. • Actor: Student • Input: The user just clicks on the icon showing the individual results. • Output: The individual results which are stored in database will be retrieved and displayed to the user.

  13. View Class results • Purpose: The user can view the results of the class in graphical format. This helps user to assess about him properly. • Actor: Student • Input: The user just clicks on the icon showing class results. • Output: The class results which are stored in database are retrieved from the database and are displayed in a graphical format.

  14. View Balance Due • Purpose: The user can view the balance due of the tuition fee. This helps the student to know the last date of payment and can pay the fee promptly. • Actor: Student • Input: The user just clicks on the icon showing Tuition information. • Output: The tuition fee details which are stored in the database are retrieved from the database and are displayed to the user.

  15. View Class Schedule • Purpose: The user can view his class schedule along with the break times. • Actor: Student, Teacher • Input: The user just clicks on the icon showing class schedule. • Output: The class schedule, which is stored in the database is retrieved and displayed to the user in table format including break times.

  16. View Homework • Purpose: The user can view the homework given by each teacher. • Actor: Student • Input: The user just clicks on the icon showing Homework • Output: When the user request homework details, the information is retrieved from the database and is displayed to the user.

  17. View Comments • Purpose: The user can view the comments written by each teacher. • Actor: Student • Input: The user just needs to click on the icon showing Comments. • Output: The comments, which are stored in the database is retrieved and displayed to the user.

  18. Update results • Purpose: The user can update the results of each student of the class and mention the average marks of the class along with highest and lowest. • Actor: Teacher • Input: The user just needs to click on the name of the class. Then the user can write the scored marks by each student under their names and click save button. • Output: When the user completes entering the results of each student they will be stored in the database.

  19. Write Comments • Purpose: The user if required can write the comments of each student under their name. • Actor: Teacher • Input: The user just needs to click on the name of the class. Then the user can update the comments under the name of each student and click save button. • Output: When the user completes writing the comments of each student they will be stored in the database.

  20. Add/Delete Students of the Class • Purpose: The user can add or delete the students of the class. • Actor: Teacher • Input: The user just need to click on the name of class and click on Add to add student and on Remove to remove student. • Output: When the change is made by the user it will immediately be stored in the database whether it is adding a student or removing a student.

  21. Post Homeworks • Purpose: The user will post the homeworks for the students of the class taught by user. • Actor: Teacher • Input: The user just needs to click on the Post Homework link to post homeworks. • Output: The homeworks will be posted and if the students login to their accounts they will be able to view them.

  22. Feedback • Purpose: The user can provide the feedback by filling the feedback form • Actor: Student, teacher • Input: If the user has any feedback the user can just click on the icon showing give feedback. • Output: When the user gives the feedback it will be stored in the database.

  23. Contact the management • Purpose: The visitor of the website can contact the management directly by filling the form. Also, there are contact details of different people of Management like director, principal etc. The user can also email them directly by collecting the contact details • Actor: visitor • Input: In the Contact us page user can just fill the form and click on submit. • Output: The form filled by the user will be stored in the database.

  24. What do we have? • Home Page • Login/Register • About Us • Admissions • Beyond Academics • Contact Us

  25. Home Page • The most important information should be included in this page as the user will be directed to this page by search engines when user tries to know about the school. Therefore news, Events, Contact information, slide show of images is included here.

  26. Login/Register • To view the particular information of student, users should register using the registration form. There are two types of the users for system Student and Teacher. After completing the registration form user gets id and password with which he can login. • Students can view their fee due, individual marks, class average, highest, lowest, teacher comments and rank in the class. • Teacher can update the marks of a student and can also view the reports of the classes taught by teacher. • In addition the reports can be viewed in graphical format by the users so that it would be easy to assess.

  27. About Us • This page includes all the information about school by which user can know better about the school. The information include • Campus area, Libraries, Laboratories, Number of campuses and their description. • Facilities provided by school which includes Transportation , Dining Facility, Accommodation, Tours and Activities, Safety and Security, Life Style, Medical Facilities, Water Purifier. • Number of staff working for the school in each department. • Cultural and other activities by school.

  28. Admissions • This page includes the admission procedure, Criteria for admissions, Application procedure, details regarding the Aptitude/Entrance test, documents required for the student to apply, Required age for the admission. Also, student will be able to take the practice exams.

  29. Academics • This page includes the course curriculum of various standards and also different methodologies of teaching.

  30. Beyond Academics • This User can browse the information of the activities that school offers apart from the academics. They include Learning Resource Center, Classroom Resource Center, Life Skills, Mathematics Exploratory, Music and Drama, Drawing/Art Studio, Yoga/Meditation.

  31. Contact Us • This User can get the contact information including email id and phone numbers of important persons of the school, address of the school, Google Map showing the address of school and the contact form where user can fill the form and submit in case of any questions. Apart from this User can provide the feedback about the school.

  32. Additional Features • Online Chat • Graphs

  33. User Interface • Support JakobNeilsen’s Rules • Facilitates scanning • Placing Logo on every page • Placing Home Link all through the site • Do the same as everybody else • Writing simple headlines • Update the users with ongoing information • Using user’s language not system oriented terms • Providing proper error messages • Proper navigation

  34. Sample User Interface

  35. After Student Signs In

  36. After Teacher Signs In

  37. Tools and Technologies • Front End: C#, ASP.NET • Back End: Microsoft SQL Server 2008 • IDE: Microsoft Visual Studio .NET

  38. Documentation Standard: • The project documentation will follow the IEEE standards • Coding Standard: The project follows the ASP.NET standards for web part development and custom code deployment. • Commenting Standard: Each block of statements will be well commented. Comments are used in the project to give a brief description of the code, mainly intended to describe the functionality and purpose of commented areas. • Metrics: COCOMO model is used to estimate the cost of the project in terms of effort and time.

  39. Cost Estimation-COCOMO Effort = C1 * EAF * (Size)P1 Time = C2 * (Effort)P2 Organic Mode • C1= 3.2 • C2= 2.5 • P1= 1.05 • P2= 0.38

  40. EAF= 0.609 Size= 1.5 I estimate the size to be 1.5 as I am using the Visual Studio it reduces the amount of code to the maximum. Effort = 3.2 * 0.609 * (1.5)1.05 = 2.98staff months Time = 2.5 * (2.98)0.38 = 3.78months

  41. Gantt Chart

  42. Elaboration Phase • Vision Document 2.0 • Project Plan 2.0 • Architectural Design • Test Plan • Formal Requirement Specification • Formal Technical Inspection Letters • Architecture Prototype

  43. Production Phase • User Manual • Component Design 1.0 • Source Code • Assessment Evaluation • Project Evaluation • References • Formal Technical Inspection Letters • Presentation 3

  44. All my documentation can be found at http://people.cis.ksu.edu/~sindhu

  45. Questions/Comments

More Related