Part 2 - Design.docx

pdf

School

Florida International University *

*We aren’t endorsed by this school

Course

5011

Subject

Information Systems

Date

Dec 6, 2023

Type

pdf

Pages

29

Uploaded by AmbassadorDiscovery3308

Report
Striving Educational Efforts College Informative Application for High School Students Part 2: Design
Striving Educational Efforts Abstract The process of applying to universities can be stressful for many students. There is a period of confusion and stress when students must choose which institution they are interested in attending. This is due to a lack of information and lack of opportunity to communicate with current students of the institution they wish to attend. Although it is possible to take a tour of the institution, there is little to no communication before visiting the institution. As a team, we strive to create a less stressful and more enjoyable environment for students seeking higher education. An application such as this can serve as a one-stop location for students who wish to continue their education, but do not know where to begin. Through this application, students can keep in touch with those who are currently enrolled in a university as well as their teachers. With the help of this application, students and teachers of existing institutions can come together to provide a welcoming environment for newcomers interested in enrolling at their schools. The application provides a one-stop solution because not only will the user be able to communicate with those already enrolled, but they will also be able to see every university in one place and broaden their options. We intend this application to be a fun place where students do not feel stressed and can have access to additional information about higher education.
Striving Educational Efforts Introduction As part of the project, aspiring college students will be the customers. The college application process can be overwhelming to high school students, and for that reason, they delay submitting it until after graduation, or skip it altogether. The apps and websites that currently exist do not give enough consideration to the student culture of each institution, which can only be understood and explained by students who are currently enrolled in the institution. Rather than focusing on numbers and percentages, they present institutions by analyzing numbers and percentages. As a result, students may enroll in colleges and move into them, only to discover that they do not like the college environment - which adds to the complexity of the college experience and may lead to them transferring or dropping out. This application will not only focus on the statistics and percentages that define an institution but will also give students the opportunity to express the culture or "soft characteristics" that define their school. Applicants will be able to obtain a more comprehensive picture of the institution and determine whether it is a good fit for their educational objectives by doing this. A prospective student will be able to make a more informed decision about where they would like to attend college. Additionally, the students will be able to access valuable information regarding the college application process and college readiness. Challenges
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts · It is expected that the project will be completed within three months. The successful completion of our project depends on the effective management of time. · Resources - There are four people working on this project. Our project will utilize every skill set at our disposal to be successful, even though we do not have many engineers. · Equipment - It is possible that some team members will not have the proper equipment, but we will work together to ensure that everyone has access to the right technology and that we assist one another in providing it. Tools and Resources JavaScript React Native GitHub Projects Firebase (Google Authentication) Project Schedule The purpose of this section is to describe the project flow throughout the entire development process. This section will incorporate user stories to guide our development process and provide an understanding of how each user will utilize the application. There will be sprint periods assigned to each user story with specific dates as to when these user stories will be completed as well as a burndown chart showing the application's progress. User Story Backlog
Striving Educational Efforts It is anticipated that changes will be made throughout the development of this application as it progresses. The agile methodology provides us with the flexibility to handle these types of changes, and as user stories are developed, the way each of these features will be implemented in the system may change. User: Student Goal Reason Acceptance Criterion As a student user, I should be able to register myself as a student So that I will be able to have a student account. Let us say when I click on the register, I should be able to create an account. If there is an error when registering, an error message should appear. As a student user, I want to be able to input my username and password in the login page So that I will be able to view my dashboard. When I enter my information and click login, I should be directed to the dashboard. If my login information is wrong
Striving Educational Efforts an error message should appear. As a student user, I want to search for institutions in the search bar. As a result, I will be able to view information about these institutions. When I click the search bar, I should be able to type in an institution and be directed to their page. If an institution does not exist, I should see an error message. [Text Wrapping Break] As a student user, I should be able to log out of my account. As a result, I will no longer be logged in and my information will be safe. When I click login, I should be directed back to the home page. As a student user, I should be able to filter by category As a result, I will be able to view the right institutions. When I click the filter, it should be saved. When I click filter and search it should search only for what I filtered.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts As a student user, I should be able to post a comment when clicking on the institution. As a result, my comment will be posted, and teachers can view it. When I type my comment and click post, it should post as my name. If my comment does not post, I should expect an error message. As a student user, I should be able to give ratings when clicking on institutions. As a result, my rating will be posted, and others will be able to see my rating. When I click ratings, I should be able to rate the institution. My rating should automatically be shown. If my rating does not post, I should get an error message. User: Teacher Goal Reason Acceptance Criterion
Striving Educational Efforts As a teacher user, I should be able to log in with my information. So that I will be able to have an account. Let us say when I click on the register, I should be able to create an account. If there is an error when registering, an error message should appear. As a teacher user, I should be able to register when I click register as a teacher So that I will be able to have an account as a teacher. Let us say when I click on the register, I should be able to create an account. If there is an error when registering, an error message should appear. When registering, I should provide my institution access code to be assigned to it. If register or access code is wrong, an
Striving Educational Efforts error message should appear As a teacher user, I should be able to search for institutions when I click on the search bar As a result, I will be able to view other institutions When clicking the search bar and typing my institution I should be directed to that institution. I should be able to have direct access to my institution next to the search bar. As a teacher user, I should be able to click on my institution As a result, I will be able to view comments and ratings from students When clicking my institution, I should be directed to a panel where I can see all comments and feedback from students. If the institution does not appear, an error
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts message should appear. As a teacher user, I should be able to click log out As a result, I will be safely logged out of my account and directed back to the homepage. When I click log out, I should be logged out of my account. If clicking logout does not log out, an error message should appear. As a teacher user, I should be able to flag a comment or post As a result, this comment or post can be reviewed by an admin When clicking the flag button, a success message should appear. My flag should be resolved within 2 days. As a teacher user, I should be able to click request institution As a result, I should be able to input details of an institution and submit for it to be approved. Click request institution will direct me to a form to fill.
Striving Educational Efforts Clicking submit will prompt a successful message. User: Admin Goal Reason Acceptance Criterion As an admin user, I should be able to login As a result, I should be logged in and directed to the admin panel. When clicking login and entering my information, I should be directed to the admin panel. If there is an error when logging in, an error message should appear. As an admin user, I should be able to click flag button As a result, I will see all flags that teachers have submitted When clicking the flag button, all flags should appear. I should be able to resolve any flags.
Striving Educational Efforts As an admin user, I should be able to click delete on a flag As a result, the flag submitted will be resolved and the comment deleted. When clicking delete on the flag, it should automatically delete and notify the teacher that the flag has been resolved. As an admin user, I should be able to click create institution As a result, a new institution will be available in our database for teachers and students to register for. Clicking create should prompt a small form to create an institution. When finishing, a success message should appear. If an institution was created by a teacher or student, I should be able to click accept or deny. Clicking accept will create a new institution.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Clicking deny will delete request to create a new institution. Sprint Period Timeframe: 1 week Iteration #1 : The team continues to work on the functionality of the homepage. Upon completion of this phase, the team will design and implement the homepage, which will provide direct access to students, teachers, institutions, and the admin page. The product manager will provide feedback following the demonstration of the functionality by the team at the end of the iteration. Timeframe: 2 weeks Interaction #2 , the homepage is created and all routes to the individual pages are functional. To ensure that each page has its own proper design and functionality, the team will work on each page individually. To ensure that each page's functionality is implemented properly, the team will utilize the user story backlog during this period. The team will demonstrate their own page and functionality at the end of this iteration, and the product manager will provide feedback. Timeframe: 1 week Iteration #3, The team will present the functionality to the product manager and receive feedback on iteration #3. Students will be able to log in to the system using their student IDs.
Striving Educational Efforts Timeframe: 1 week Iteration #4: Once the individual user pages have been completed, the team will work together to finish the institution page, which will provide additional functionality to the users. As soon as the institution page is completed, it will be presented to the product manager for feedback. Timeframe: 1 week Iteration #5, the team will work on the functionality for logging out for student users. The team will present the functionality to the product manager for his review. Timeframe: 1 week Iteration #6, the team will develop functionality to enable teachers to login. The team will present the functionality to the product manager for feedback. Timeframe: 1 week Iteration #7, Team will work on the functionality of logout for teacher users. The team will present the functionality to the product manager and get feedback. Timeframe: 1 week Iteration #8, Team will work on the functionality of registering for teacher users. The team will present the functionality to the product manager and get feedback. Timeframe: 1 week Iteration #9, Team will work on the functionality of teacher users being able to review comments and feedback. Functionality will be presented to the product manager for feedback.
Striving Educational Efforts Timeframe: 3 weeks Iteration #10, Team will work on the functionality of the admin user. The team will show functionality to the product manager and receive feedback. User Story Allocation The process was determined by the functionality that is related to another user story. In the case of the admin panel, for example, it seems essential, but that user story cannot be developed until the project is completed, as we must make sure that a functional flag is available for the teacher user first so that the administrator has the option of reviewing the flag. Before creating the teacher's flag functionality, student feedback must be available. Depending on the relationship between each functionality, each iteration is allocated differently. Burndown Chart Using the burndown chart, we can visualize how our team is progressing with their user stories. This graph does not just illustrate a single progression, but rather an indication of how hard the team is working in terms of effort and the amount of work delivered through each interaction. A chart is generated based on the user story data such as sprints as to when we anticipate finishing the task, and based on this data, we will generate a burndown chart indicating the progress of the project.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts
Striving Educational Efforts Our Team Name / Role Responsibilities Role: Project manager, Developer. It is my responsibility as a product manager to review each iteration, provide feedback on each functionality, and assist my team in developing them.
Striving Educational Efforts Role - Developer, UI/UX While working on those iterations, I am responsible for assisting my team in developing the student and teacher profiles. Developer Among my responsibilities in this team is to assist in the development of the universities page, which will be integral to the development of user stories. Technical Writer It will be my responsibility to help with the documentation. Design Defining Design
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Define design //using scholarly literature to support your definition; following APA citation – Anne There are several ways that design can be defined. In software engineering, design can refer to system design or object design. They may sound similar however they have different objectives. System design refers to the process in which the project is defined, and the entire system is broken up into segments for multiple teams to work on. Object design refers to the Bruegge, B., Dutoit, A. (2010). Object-Oriented Software Engineering Using UML, Patterns, and Java. Prentice Hall. Ralph, P., Wand, Y. (2009). A Proposal for a Formal Definition of the Design Concept. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds) Design Requirements Engineering: A Ten-Year Perspective. Lecture Notes in Business Information Processing, vol 14. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-92966-6_6 Design process The design process began with an idea to create an application that would create a more positive and welcoming environment for individuals who are interested in pursuing higher education at an institution. The idea was developed by each team member because of his or her previous experience with applying to universities and how the process was conducted. Despite having the opportunity to speak with university advisors, there was little prior interaction with how current
Striving Educational Efforts enrolled students felt about the university. It was evident to many of us that an application like Rate My Professor exists, but this application is primarily designed for students currently enrolled in university courses. Based on our findings, we decided to create a one-stop application that allows users to search for any university in their area as well as create a one-stop application for any university in their preferred location. The goal of this one-stop application is to provide the optimistic user with access to university information and the ability to learn more about the current experience of other students and faculty members. It was essential that we first selected the correct technologies so that we could turn this idea into a reality before we could consider how the structure and user interface would be. By understanding what technologies will be used for this application, we were able to begin developing ideas and features we would like to implement and determine whether these technologies can do so. With the appropriate technologies selected, the team moved on to designing the user interface, user experience, and most importantly the project's system architecture. We reverted back to the application process when we applied to universities to enhance our user experience. As a result, we began our design process for the user interface with what we would have liked to see. The user interface of the application should be as simple and straightforward as possible, with the least amount of unnecessary information and consistent routing to make navigation easier for the user. During the development of our application, our team focuses on how our application will be able to deliver the create, write, update, and delete operations. User profiles, university profiles, and even the administrative dashboard would require CRUD operations. Although the design process continues to evolve, our team decided to use React as our framework and Firebase as our backend to ensure a seamless experience. There are four
Striving Educational Efforts different diagrams that represent our design. A use case, activity, class, and sequence diagram provide a structure for the entire application. Demonstrate the design graphically- Example - Software Design Document Figure 1.5/ 3.3.4/4.2.1 UML Diagrams Use case Diagrams The Use Case Diagram is helpful for identifying system-user interactions.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Activity Diagrams Activity Diagrams are used to describe the behavior of the system.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Class Diagrams The Class Diagram provides a visual structure of the system including their classes and entity relationships. Sequence diagrams The Sequence Diagrams summarizes the object interactions in sequential order.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Rationale Management The issues that were addressed For our design, we wanted to keep the application simple and easy to navigate for the user while providing the privacy of a personal account. We also wanted the users to be able to read about the different institutions and be able to write, delete, and read comments made by other users. We addressed the issue of organizing the information that will be posted in the application by the users. Since the users will be able to share their experiences in their institution, the display of these comments had to be organized so that the students aspiring to enroll in an institution would find it useful. We also needed to utilize a database that would manage the information of the users and allow developers to work with the user’s inputs such as comments and pictures. Alternatives Considered For our database, we considered using MongoDB. We also considered building an application where users did not have to log in and could just browse through the pages and read other users’ comments without having to sign up.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Similarly, we considered displaying the user’s comments on the universities pages together so that it would be simpler for the user to read and write comments without having to choose a category such as Academics, Culture, or Housing. Decisions Made We opted for a home page that would be informational, a dashboard where users would be able to look up and save their favorite universities, and a profile page where they could update their accounts as needed. We also decided to use Firebase as our database for its simple installation to our application. Moreover, since the nuance of our application is the ability to comment on institutions and read the comments of other students, we decided that it would be best to require users to sign in so that the system administrator would have the option to enforce accountability if a comment is reported and the user that uploaded it must be flagged. Criteria Used There were several criteria used to guide (design) decisions. Some of them were: Functionality : The system should fulfill the user's or client's functional needs. The design should be capable of managing all necessary tasks and procedures in an effective and efficient way. Performance : The projected load and usage patterns should be supported by the system within reasonable response time constraints.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Scalability : Throughout time, user load and usage patterns should be able to increase without the design needing a significant overhaul or redesign. Security : To prevent unwanted access and data breaches, the design should include the necessary security safeguards. Maintainability : The design should have well-structured, well-documented code that is simple to adapt and maintain. Usability : An easy-to-use user interface and intuitive design are essential. Compatibility : The design must work with the required hardware, software, and operating systems. Portability : The design should be portable to various platforms, operating systems, and environments. Testability : All components should be tested thoroughly and successfully as part of the design process. Cost-effectiveness : Given the project's budget and resource constraints, the design should be economical. These criteria helped to ensure that the software design is functional, efficient, secure, and maintainable, while also meeting the needs of the user or client and being compatible with the required platforms and tools. Developer Debates There were several debates that developers went through when making design decisions. Some of the common debates were as follows:
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts Trade-offs : The trade-offs of various design options were discussed by developers. We discussed trade-offs such as those between usability and security or between performance and maintainability, for instance. Best practices : The optimal methods for achieving a specific feature or function were a topic of discussion among developers. We debated the advantages of various coding techniques, design patterns, and architectural decisions. Requirements : Developers argued on how to interpret and implement user or client requirements. The best technique to fulfill a specific criterion was considered, as well as whether it was possible. Technologies : Developers debated over the merits of various technologies or implementation methods for a specific feature or function. We talked about the benefits and drawbacks of utilizing a specific framework, database, or programming language. Constraints : The project's limitations in terms of time and resources were a topic of discussion. The developers discussed if it was possible to achieve specific requirements within the limitations. User experience : The user experience of a specific design decision was a topic of discussion among developers. We talked about the system's usability, accessibility, and prospective effects on user satisfaction. These debates were important because they helped us ensure that the design decisions made are well-informed and well-justified. By weighing the trade-offs, discussing best practices,
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Striving Educational Efforts interpreting requirements, considering technologies and constraints, and focusing on user experience, developers arrived at the best possible design decision.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help