DIT Grangegorman (Gomobile) Mobile Application

Question: The DIT Grangegorman (goMobile) mobile application will provide information for students, lecturers and college management. The application will list modules, locations and lecture times for all courses in the institute alongside being a means of communication for users. It will also provide scheduling assistance and other information resources. Brief Requirements For the goMobile application, the following are required: Define at least one scenario for the above application Answer: Introduction The DIT Grangegorman (goMobile) mobile proposed application aims at providing information for students, lecturers and college management. The application also lists different modules, locations and lecture times for all courses in the institute. In addition to this, the application will also facilitate interactions among the users. It will also provide scheduling help and other sources of information. In this report, the proposed system has been designed using the principles of UML where in user scenarios have been identified. Thereafter, use case descriptions have been framed. From these use cases, their respective extensions and inclusions are discussed and finally rankings have been given to the use cases. User Scenarios Following user scenarios have been identified: When user arrives at the proposed system, the user browses for the login page. They provide their username and password and click login. Then system checks the entered information and if valid, displays the welcome page for the user. The user looks through the page. He/she decides to add a new course by clicking Add course link. The system responds by displaying a new course form. The user enters the name of the course and duration and then clicks Add modules. The system responds by displaying a form to add multiple modules along with Cancel, Reset and Submit buttons. Use case description The use case model identifies the proposed key functionalities of the system. A use case represents a discrete interaction unit between the user which can be a human or on-human and the system. It can also be defined as the single unite of meaning work. Each use case has a description which describes the functionality of the proposed system. Login Use Case Login in DITGS Actors Students, lecturers and school administrator Description Allows Students, lecturers and school administrator to access the DITGS system. Pre-Condition Students, lecturers and school administrators have a valid userID and password. The user is not logged in the system. Post-Condition Students, lecturers and school administrator successfully access the system along with operations as per their respective roles and privileges. Type Complex Normal Course of Action 1. The user clicks on the Login link on DITGS home screen. 2. DITGS displays a screen with fields username and password along with submit and cancel button. 3. The user enters the username and password (A1). 4. DITGS system allows users to access the system on the basis of access control mechanism. Alternate Course of Action A1: User enters incorrect username or password. DITGS displays an error message Username or password is incorrect on the login screen. Add course Use Case Add new course Actors School administrator Description Allows school administrator to add a new course. Pre-Condition School administrator is already logged in the system. Post-Condition School administrator has successfully created a new course in the system. Type Complex Normal Course of Action 1. The school administrator clicks on the Add Course link. 2. The DITGS system displays a screen with course name, course duration, description, start date and end date along with submit, reset and cancel buttons. 3. The user clicks on submit button. (A1) 4. DITGS system processes the information and adds a new course in the system. Alternate Course of Action A1: If an incorrect or inappropriate format information is entered by user the add-course screen will be displayed again. References Add module Use Case Add new module Actors School administrator Description Allows school administrator to add a new module of the selected course. Pre-Condition School administrator is already logged in the system. The selected course already exists in the system. Post-Condition School administrator has successfully created a new module under a course in the system. Type Complex Normal Course of Action 1. The school administrator clicks on the Add Module link. 2. The DITGS system displays a screen with course name dropdown, module name, description along with submit, reset and cancel buttons. 3. The user clicks on submit button. (A1) 4. DITGS system processes the information and adds a new course in the system. Alternate Course of Action A1: If incorrect or inappropriate format information is entered by user the add-course screen will be displayed again. Interaction diagrams The sequence diagrams are interaction diagrams which provide detailed descriptions of the operations to be performed. They depict key runtime interactions among the parts of the system. They perform following functions: Depicts the object context which plays an important role in defining the collaboration. Depicts the order of interaction visually with the help of vertical axis of the diagram. This represents what and when the messages have been sent. Depicts the elements as and when objects interact over time. Depicts the interactions of instances. Do no depict the structural relationship between the objects. Login use case Figure 1: Login interaction diagram Add course Figure 2: Add Course interaction diagram Data Model Data model defines the logical structure of database. These models are fundamental entities which introduce abstraction in DBMS. They also define the connection of data with each other. They also represent the methods of their processing and storage in the system. Figure 3: User model Exclusion and inclusion Extend use case The extend relationship allows user to modify the basic behaviour of the use case. For instance: An Add course use case can be extended to add module functionality. Similarly, when a module is added then module leader/lecturer can be allocated to module instantly. Figure 4: Extends relationship Include use case The relationship allows user to include the steps from the use case into another. This relationship is important when the included steps arises as a sequence in many different scenarios. For instance: A course can not be deleted until its modules are deleted. Similarly, until user has registered, he/she can not login in the system. Figure 5: Includes relationship Prioritization of use cases Use case Name Rank Reason Login 1 Until user get access to the system, he/she cannot edit the data of the system. Registration 1 Until an user has been assigned specific role and privileges, he/she cannot edit the data of the system Add course 2 Course forms the base of the entire application. Until a course is added, students will not be able to opt or take admission in the institution. Add module 3 A course is a collection of one or many modules. They are required to be added to make a complete course. Add course leader 4 A course leader is required to be entered in the system but it will be added once the course corresponding to it has been added. Add student 2 Student frames the base of the application. If student cannot be added then courses remain without any use. Allocate lecturer 5 A lecturer can be added only when course and corresponding module has been added. Delete course 5 The course deletion is not a very frequent to use functionality. Update course 4 A course is required to be updated for duration and start and end date hence it is of more importance as compare to other use cases. Delete module 5 The module deletion is not a very frequent to use functionality. Update module 4 A module will be updated when a new lecturer is allocated to it. Delete lecturer 5 A lecturer is not a very frequently used functionality. Update lecturer 4 This functionality can be used frequently when lecturer upgrades their subject areas. References Fowler, M. (2004).UML distilled. Boston: Addison-Wesley. Fowler, M., Scott, K. (2001).UML. Paris: CampusPress. George, J. (2004).Object-oriented systems analysis and design. Upper Saddle River, N.J.: Pearson Prentice Hall. Hoffer, J., George, J., Valacich, J. (1999).Modern systems analysis and design. Reading, Mass.: Addison-Wesley. Maksimchuk, R., Naiburg, E. (2005).UML for mere mortals. Boston: Addison-Wesley. Marakas, G. (2001).Systems analysis and design. Upper Saddle River, N.J.: Prentice Hall. Podeswa, H. (2005).UML for the IT business analyst. Boston, MA: Thomson Course Technology PTR. Schmuller, J. (2004).Sams teach yourself UML in 24 hours. Indianapolis, Ind.: Sams. Valacich, J., George, J., Hoffer, J. (2001).Essentials of systems analysis and design. Upper Saddle River, N.J.: Prentice Hall. Weilkiens, T., Oestereich, B. (2007).UML 2 certification guide. Amsterdam: Elsevier/Morgan Kaufmann.