The Base of Software Development and WEB - Research Paper Example

1 Methodology The methodology of software development will help to understand the situational problem presented by designing a new system for SQL learning. Additionally, it will also aid in the design and development by solving the problems presented in the development of a system design specifically for student to teacher interaction. In this work, the life cycle model of development will be used to engender the work and carry it to completion. The waterfall scheme is used in this methodology, providing a robust method for enabling the needs of the program to be met. This results in a program that is fast in its responses and free of errors. Also, a Unified modeling Language (UML) will be used to study use requirements in the system and identify possible cases for users at various levels. Use Case diagrams in UML will allow us to establish behavioral patterns for the users of the system in order to correctly asses and develop programming features necessary in an organized manner. 1.2Waterfall Model: Figure 1: Schema of the Traditional Waterfall Model Adapted from Hoffer et al. (2009)  According to the notes of Jeffrey A. Hoffer, Joey F. George, Joseph S. Valacich (2009) presented in association with their distinguished course in modern systems analysis, the definition for the waterfall model is a traditional model that works in many phases, and is often useful in the design of new software systems. In this model, the first phases begins upon the completion of the proceeding phase, with each phase following sequentially. These systems have either no instance or only isolated instances of backtracking and looping. This system provides both simplicity in management and ease of use for the end user, and so lends itself to goal development in each phase (Higgins 2009). 2.1 Functional Requirements Specifications: The performance of the system will be evaluated in this section, including a detailed discussion of the operations necessary for the system to function. Functional requirements will necessitate the division of the system between two user types to be referred to as administrative users (Admin) and student users (students). Assessment of functional requirements will allow for the effective assessment of system requirements. 2.2 Functional Requirements: Admin should be able to: 1. Add a new student or students; 2. Add questions/assignments; 3. View the results for individual student or groups of students; 4. Remove student or students; 5. Remove question or questions. Student should be able to: 1. View the lesson; 2. View the example; 3. Complete tests; 4. Create a database(s); 5. Create table(s); 6. Create query(s); 7. Insert table(s). 2.3 Non-Functional Requirements: Non-functional requirements enhance the understanding of unique and specified requirements of the system that are not related to system functionality, including the ease of use and specific hardware/software/upkeep necessary for the successful implementation of the project. Usability: The system is simple and effective for a variety of users, including those with disabilities. Efficiency: The system provides fast feedback, little lag, and secure transmission of data with little instance of error or interruption. Satisfaction: Students should exhibit satisfaction with results and provide positive feedback to instructors. The ultimate goal is to enhance the learning process through application of new media. 3.1 UML: According to the Inopedia hompage, the definition UML provides a nonproprietary standard of best-practices for engineers in software development. UML is a third generation language used for both specification and modeling, with noted success in large architectural projects for complicated and advanced software systems. In object-oriented systems, UML is an open method, particularly suitable for software-intensive systems during the development or testing stages, as it allows for a great amount of flexibility while maintaining a high reliability (Unified Modeling Language 2004). It is also a language that is well documented and supported, and it is currently the leading notation for graphical development architecture and design level information in systems development. The language follows the traditional ‘executable model’, and a number of resources are available to support UML providing the developers additional assistance for the completion of their projects (Atkinson 2002). 1.3 Use Case Diagram: According to Fowler (1999), Use Case diagramming is a part of the UML that aids in understanding how the system works as well as describing the requirements for system operation and development. Use Case diagramming also aids in identification of the actors necessary for system functionality, and the behaviors that must be supported within the system for each actor. Use Case diagram structure for this system includes the functionality of both the admin and student actors, allowing for complete understanding of system functionality. In our system we have two actors which are: Admin Student Figure 3: Use-Case diagram of Student Actor Functionality 1.3.1 Use-Case Description: The Use Case description provides a logical format for interaction between the user and the system for a particular case instance. It is essentially a conversation between user and system that will give more details about what the user will do in the system, or the performance of user in system. Figure 3, above, graphically represents this system. Use Case View the lesson Actor Student The system provides students with four choices which are “Create DB, Create table, insert table and select” by clicking the link for any of them. The system displays the selection to the user. Use Case View the example Actor Student Based on the student’s lesson selection, the system displays the examples. The system opens the example in a new window. Use Case Do the test Actor Student Precondition: user and password of the ‘Student’ are validated for secure login. The System provides five things options which are “Create DB, Create table ,insert table , insert query and logout” by clicking on a link that will be presented to the student. Use Case Create Database Actor Student By choosing “Create Database”: System will display the question and text selections to answer the question and button labeled “submit”. The system randomly displays a question to the student which will draw from the bank of questions created by the admin user The student will answer the presented question and put the name of database in the text then click the button “Submit”. The system show the code for the question in SQL and compare the student answer with the admin answer. If the answers match (are the same) the system will print “correct Answer!” otherwise, it will print “Incorrect Answer!” Students can select ‘logout’ to exit from system. Use Case Create Table Actor Student By choosing “Create Table”: The System will display the question and possible answers for the questions representing the table name and number of fields. The button “submit” will appear. The system randomly shows students questions which come from the bank of questions created by the admin user. The student has to answer the question and put the “Table Name” in the text as well as a numerical value for how many fields are in this table and then click the button labeled “Submit”. The system then shows text for the name of field, select option for Type of field for example “int and Varchar”, text for Length/Values , select option for field is null or not, select option Default is the field, auto increment or not, and field primary key or not for user selection. The system shows the code for the question in SQL and compares the student answer with the admin answer. If it matches (is the same) the system prints “correct Answer!” otherwise, it prints “Incorrect Answer!” Students can select ‘logout’ to exit from system. Use Case Create Query Actor Student By choosing “Create Query”: The System will display the question, presenting four text choices to answer the question which are Field Names, Table Name, Where clause, and Order by (with a select option asking if the order is ascending or descending), and button “submit”. The system randomly shows students questions which come from the bank of questions created by the admin user. The student has to answer the question and put in the Field Names with a separate comma for Table Name, Where clause, and Order by. The student should put Where clause and Order By depending on the context of the question asked, and then click the button “Submit”. The system will display the code for the question in SQL and compare the student answer with the admin answer. If it matches (is the same) the system print “correct Answer!” otherwise, it will print “Incorrect Answer!” Students can select ‘logout’ to exit from system. Use Case Insert Query Actor Student By choosing “Insert Query”: The System will display the question along with three text based options for the answer which are Field Names, Table Names, field values, and the button “submit”. The system randomly shows students questions which come from the bank of questions created by the admin user. The student has to answer the question and enter the Field Names separated by commas along with Table Name and Field Values also separated by commas and then click the button “Submit”. The system will display the code for the question in SQL and compare the student answer with the admin answer. If it matches (is the same) the system print “correct Answer!” otherwise, it will print “Incorrect Answer!” Students can select ‘logout’ to exit from system. Use Case Login Actor Admin Precondition: user and password of the ‘Admin’ are validated for secure login. The System provides four things which are “Add student , Add question, Result and logout ” that are made available when the user clicks the appropriate link. Use Case Add student Actor Admin By choosing “Add student”: The System will display four text selections which are username , password , first name and last name and button “submit”. The system add a new student to the database . The Admin can then remove the student user from the system. The Admin user can select ‘logout’ to exit from system. Use Case Add Question Actor Admin By choosing “Add student”: The System will display for the admin user one select option for question type, one text for question, one text area for answer and button “submit”. The answer for the question has to be in SQL . The system adds a question to the database . The Admin can remove the question from the system. The Admin user can select ‘logout’ to exit from system. Use Case Results Actor Admin By choosing “Results”: System will display for admin two select options in which the admin can chose the specific student or all students in the system. In the another select option, the admin can show all answer or can specifically create tables, create databases, create queries, insert tables, or insert query followed by the button “submit”. The system shows the admin a number of question options including full name of student, question type, question, correct answer (which the admin user can add upon addition of a new question, or modify at a later time. These selections will appear as the answer the student for this question and correct/incorrect for this question). The Admin user can select ‘logout’ to exit from system. All others use case descriptions in Appendix B User Interface Design The user interface is a visible face of the system with which the end user, presumably the student or admin, will interact. For the Student, it provides a way to navigate the system and input/output data necessary to interact with the system to complete assignment. The interface is designed to be fundamentally simple to operate, leaving little room for operator error or confusion as well as simplifying the maintenance process. Figure ():Interface Structure Diagram Figure () Navigation Mechanism References Atkinson, Colin. 2002. Addison-Wesley. Component-based product line engineering with UML. Inopedia. Accessed August 11, 2010. Available at http://books.google.co.uk/books?hl=en&lr=&id=o4rYM7aqJQoC&oi=fnd&pg=PR17&dq=uml+definition&ots=daWmfbausu&sig=Ee-YQOUF8XfpLfhPGblqedtwN0w#v=onepage&q=uml%20definition&f=false Fowler, Martin. 1999. UML Distilled: A Brief Guide to the Standard Object Modeling Language. Second Edition. Addison-Wesley Professional. Accessed August 11, 2010. Available at http://my.safaribooksonline.com/0-201-65783-X Hoffer, J, George, J, and Valacich, J. 2009. Modern Systems Analysis and Design Notes. Accessed August 11, 2010. Available at http://hal.cs.camosun.bc.ca/~weston/comp230/LectureNotes/CH01New09.pdf Higgins, Colin. 2009. Presentation 7: Integrating Quality Activities in the Project Life Cycle. University of Nottingham, UK. Accessed August 11, 2010. Available at http://www.cs.nott.ac.uk/~cah/G53QAT/G53QAT06pdf6up.pdf Unified Modeling Language. 2004. Accessed August 11, 2010. Inopedia. Available at http://www.indopedia.org/Unified_Modeling_Language.html Read More